Breaking News
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
Show HN: Stop returning raw JSON from MCP servers, build rich inline UIs https://ift.tt/1NwO6VF
Show HN: Stop returning raw JSON from MCP servers, build rich inline UIs https://ift.tt/9OjrnbE June 8, 2026 at 10:37PM
Sunday, June 7, 2026
Show HN: An mkv player that uses WASM to render you videos https://ift.tt/GjN3YSq
Show HN: An mkv player that uses WASM to render you videos hello HN i want to share this wasm experience i built for a universal mkv player on the web using wasm to ship a lean decoder only ffmpeg build, thus way codecs unsupported by the browser can be played I wonder if this holds any value to anyone anymore https://parallax.kinosoft.moe/ June 8, 2026 at 03:57AM
Show HN I scraped 743 large employers' careers pages to find their ATS https://ift.tt/eUTns5l
Show HN I scraped 743 large employers' careers pages to find their ATS https://ift.tt/ZCsNkLM June 7, 2026 at 09:45PM
Show HN: I Derived a Pancake https://ift.tt/IPwv4UH
Show HN: I Derived a Pancake After 25 years of making other people's pancake recipes - always yearning for more tang, more fluff, and more predictability - I decided to derive the pancake recipe from the chemistry. You mark checkboxes for what you have on hand (ricotta, sour cream, kefir, buttermilk, yogurt, cottage cheese, lemon, cream of tartar, etc.) and it computes the best recipe based on targets for acid, fat, salt, sugar, and CO2. My particular favorite are the yeast-raised lemon ricotta kefir pancakes - the best I've ever had. The math is done in a small pure-ESM library: ingredient composition to component masses and acid moles, a stoichiometry layer, and a bisection solver for the target deficits. I'm not a chemist, so if something is off, tell me and I will fix it! https://ift.tt/HM12ac9 June 5, 2026 at 10:42AM
Show HN: Nightwatch, The open-source, read-only AI SRE https://ift.tt/ZkShXja
Show HN: Nightwatch, The open-source, read-only AI SRE nightwatch is a local-first, read-only layer on top of your monitoring. it groups alert storm into incidents, flags noisy checks and has an agent that can investigate for you live systems. You can e.g. jump from the incident into the agent directly. the reason for this weekend project is that we had a kubernetes upgrade that went wrong, and at some point a rollback wasn't possible anymore, so it had to be fixed live during the night while several problems came together. We run a lot of different systems, on-prem and several Kubernetes clusters, and in a situation like that you spend most of the time just figuring out what is actually broken and where. So i thought that it would be pretty cool to have eyes in the dark in each system that can talk to your "brain". so the idea is to put a baby owl into each environment. Each owl runs where the systems live, keeps that environment's credentials local, and only dials outbound to a central brain, so there is no inbound hole into prod. It exposes a set of read-only skills, and the agent uses them to gather evidence and form a root-cause hypothesis, so the on-call engineer starts with a head start instead of from zero. read-only for now, i don't trust it near prod yet and honestly neither should you. llocal-first for easy self-hosting and to keep credentials on your side. the clustering and recommendations run fully offline with no llm at all. the agent needs a tool-calling llm, you can point it at a remote one, or self-host one (ollama etc.) if you want to stay fully offline. for non selfhosters: before every remote llm call, nightwatch strips real secrets (unrestorable) and swaps identifiers like ips, hostnames and paths for reversible placeholders, so the model only sees masked data while real values are restored only in the proposed commands and tool calls Would love if you try it in your Systems https://ift.tt/R4n2PYk June 8, 2026 at 12:24AM
Subscribe to:
Posts (Atom)