Breaking News
Wednesday, June 10, 2026
Show HN: Kctx – A read-only Kubernetes context engine for SREs and AI Agents https://ift.tt/REDP9i5
Show HN: Kctx – A read-only Kubernetes context engine for SREs and AI Agents https://ift.tt/WBpnHPO June 11, 2026 at 12:44AM
Show HN: Atlasphere – Live Infrastructure Diagrams https://ift.tt/wvmNBWq
Show HN: Atlasphere – Live Infrastructure Diagrams Hi HN. My name is Andrey. On a regular business day, I'm a software engineer working at AWS. Outside of work hours, I spend time on my hobby - writing code. I was once building a pet project that allowed customers to spin up fully synchronized blockchain nodes within just a few minutes. The backend was split into a control plane and a data plane, each with its own AWS account. Later I added two more AWS accounts. One for shared RPC nodes. One for the Analytics Service. Since I love to visualize things, I used drawio to visualize the architecture. With time, I noticed a pattern. I'd write some code, add a few lambda functions, update my drawio diagram, write more code, introduce a few more resources, test things, see that everything works fine and go to sleep with a smile on my face. Next week I'd check my diagram, and shockingly, it's missing some of the resources! This kept happening for a few more weeks until I decided to fully abandon the project until my infrastructure diagrams could stay in sync with my cloud account. That's how Atlasphere.io was born. I've been working on it for the past 6 months and I think the product is ready for some feedback :) A few notes: - Atlasphere uses a ReadOnly IAM role to scan your AWS account (my account reaches your account through a trust relationship). - The number of services is currently limited (WIP) - It's a macOS app - It's NOT an Electron app, i use Rust + Webview What am I looking for? All I really need is for someone to try the app and tell me what they like about it and what they absolutely hate about it, haha! The website is https://atlasphere.io/ June 9, 2026 at 04:35PM
Tuesday, June 9, 2026
Show HN: LocalCode – turn plain English into CLI commands with Apple's local AI https://ift.tt/qWojEPG
Show HN: LocalCode – turn plain English into CLI commands with Apple's local AI https://ift.tt/iWHLkTB June 10, 2026 at 01:04AM
Show HN: OpenYabby, voice-controlled multi-agent orchestrator for Claude Code https://ift.tt/i85B9bz
Show HN: OpenYabby, voice-controlled multi-agent orchestrator for Claude Code https://ift.tt/TnYFQ78 June 10, 2026 at 12:08AM
Show HN: Transit-format (JSON/MessagePack) reader/writer in C https://ift.tt/fNoRyJT
Show HN: Transit-format (JSON/MessagePack) reader/writer in C Transit.c is an addition to the set of libraries to support transit data interchange format written in C11. It supports full 0.8 specification of cognitect's transit-format: JSON, JSON-Verbose and MessagePack encodings, all ground and extension types, compression via keys caching, extensibility via custom tag handlers. https://ift.tt/l8Nmpd9 June 8, 2026 at 01:35PM
Monday, June 8, 2026
Show HN: Courtside – TUI for NBA Games https://ift.tt/4HQE1ZL
Show HN: Courtside – TUI for NBA Games Hi HN, I made this after seeing a few similar projects on the front page. NBA API endpoints are public and there’s a pretty robust python package ( https://ift.tt/RDcyEqB ) that I referenced for the endpoint structure to build an sdk in go. used BubbleTea and LipGloss for styling. It was a bit tricky to test the live endpoints but I watched Friday’s Final game with this and it worked pretty well playball - https://ift.tt/3M7J9Wx faceoff - https://ift.tt/1gb8zWN https://ift.tt/mIUnsu6 June 6, 2026 at 03:43AM
Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js https://ift.tt/XdSvu73
Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js I built this because I wanted to make outbound and accept inbound HTTP/3 and raw QUIC connections from ordinary Node.js code, without building Node from source or putting everything behind a reverse proxy. Repo: https://ift.tt/y4Xqm6J
npm: https://ift.tt/qWKaOo3 It’s a native package around Rust/quiche. It supports both client and server APIs, I'm using it in a couple of projects: creating raw QUIC streams, datagrams, custom ALPN, session behavior, and HTTP/3 client work from Node. I've tried to be very safe in the native code, written in rust, with proofs around the parts I was most concerned about getting wrong. I have it hosting a couple of sites as HTTP3 endpoints and found it working well. https://ift.tt/y4Xqm6J June 8, 2026 at 10:38PM
Subscribe to:
Posts (Atom)