Monday, June 8, 2026

Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js https://ift.tt/6r9sJXl

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/1gzhtl2 npm: https://ift.tt/ZqIRN16 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/1gzhtl2 June 9, 2026 at 12:08AM

Show HN: Stop returning raw JSON from MCP servers, build rich inline UIs https://ift.tt/vD735s9

Show HN: Stop returning raw JSON from MCP servers, build rich inline UIs https://ift.tt/jHEdoWD June 9, 2026 at 12:07AM

Show HN: A minimal, ad-free World Cup web-app for fixtures and live scores https://ift.tt/T5KhyGU

Show HN: A minimal, ad-free World Cup web-app for fixtures and live scores Hi all! With the World Cup around the corner, and being a football fan, I went looking for apps that would give me a detailed overview of groups, matches categorized by group or team, a daily timeline of when games happen that day (especially useful for us in Europe, since some games run pretty late), and a way to follow my favorite team or teams. The problem I ran into was that most apps out there are pretty bloated — like, really bloated. The ones that weren't either didn't focus on the World Cup specifically, or were ridden with betting ads and ads in general. So I built a very minimal ad-free (mostly tailored for myself) World Cup web app for fixtures and live scores. The fixture data comes from the openfootball/worldcup.json project - https://ift.tt/erSgjq7 . I hope you find it helpful, would love any feedback. https://ift.tt/5TO2W1M June 8, 2026 at 11:04PM

Show HN: A Minecraft builder skill for coding agents https://ift.tt/BzhRSF7

Show HN: A Minecraft builder skill for coding agents https://ift.tt/flFX3Ym June 8, 2026 at 08:21PM

Sunday, June 7, 2026

Show HN: An mkv player that uses WASM to render you videos https://ift.tt/RG5twUZ

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 05:27AM

Show HN I scraped 743 large employers' careers pages to find their ATS https://ift.tt/CwObjkQ

Show HN I scraped 743 large employers' careers pages to find their ATS https://ift.tt/hxLmtJ4 June 7, 2026 at 11:15PM

Show HN: I Derived a Pancake https://ift.tt/bcXmoIn

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/KgmFDc0 June 5, 2026 at 12:12PM

Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js https://ift.tt/6r9sJXl

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...