Show HN: Puzzle with Strangers. A free multiplayer jigsaw https://ift.tt/pN4ghfb

Show HN: Puzzle with Strangers. A free multiplayer jigsaw I built this over the last few days. Me and handful of friends are successfully hooked. I recently went to a — for lack of a better word – social/collaborative performance at an art gallery in Berlin where a group of artists filled a huge industrial hall with wooden 10x10cm cubes for people to build structures with. It was beautiful how universal the concept of playing with wooden blocks is and how ephemeral the structures were, people of all ages were put back into a childlike play. The thought about what kind of games need zero explanation stuck with me and i built an anonymous multiplayer jigsaw. We've already spent hours in there and you're invited now as well. Hope you enjoy. https://ift.tt/gMmKZRH June 26, 2026 at 11:47PM

Show HN: I built a hardware quantum RNG and wired it into a Magic 8-Ball https://ift.tt/D8gIXN3

Show HN: I built a hardware quantum RNG and wired it into a Magic 8-Ball Gday, author here! I've wanted to hack together a "real" quantum random number generator for another upcoming project, and I got carried away a bit, and went down the 'over-engineering' cliff. So, for your nerdy enjoyment, I have documented it all up, and I added something cool for fellow "Multiple World Interpretation" followers in the Quantum Mechanics debate. This QRNG uses sexy bits: Each is the decision of a photon to go left or right after hitting a 50:50 beam splitter. Standard kinda device, where you attenuate a light source down to single photons, offer them semi-mirror to bounce off, and see which PMT detector they hit (or which universe we ended up in ;) ). Basically, Through → bit=0. Bounce → bit=1. As I take the MWI interpretation of Quantum Mechanics (its the more fun options), I have also built a Quantum Magic 8-Ball. Ask it a questions, and you get and receive exactly one answer here, plus every possible answer across the multiverse. https://quantumlever.stream/oracle Enjoy! https://dnhkng.github.io/posts/building-the-beam-universe-splitter/ June 27, 2026 at 01:05AM

Show HN: A map of every UK railway, including stations that no longer exist https://ift.tt/uOrc5Hi

Show HN: A map of every UK railway, including stations that no longer exist Author here (Nathan). The goal for this site was to map the entire UK rail network: not just the parts a journey planner surfaces, but heritage lines, freight-only curves, named tunnels and viaducts, and the thousands of stations that have closed and were never mapped. The project is built entirely on open data. Lines and current stations come from OpenStreetMap via Overpass, closed stations from Wikidata (approximately 6,100 that fall outside a 250 m radius of a live OSM station), and postcode lookups from postcodes.io. The main challenge is that the sources rarely agree with one another, or even with themselves, so much of the work involved small reconciliation rules. For example, the heritage flag is propagated across every segment sharing a line name, so the Swanage Railway is coloured consistently. I shared an early version with a railway enthusiast community, and a large share of the fixes came from people who know the network considerably better than I do. A full write-up of the data challenges is available here: https://ift.tt/5dJPTvN No account or app is required. You can search by postcode, station name, three-letter code, or line name. Corrections are very welcome, as there is always a station someone knows I have got wrong. https://ift.tt/pYOXfT0 June 27, 2026 at 12:44AM

Show HN: Smart model routing directly in Claude, Codex and Cursor https://ift.tt/m5dw3QN

Show HN: Smart model routing directly in Claude, Codex and Cursor We built a model router that plugs into coding agents (e.g. Claude Code, Codex, Cursor, etc.) and intelligently sends requests to the best model to serve them. Here's a quick demo of running it locally: https://www.youtube.com/watch?v=isKhAyivtfM . At Weave, we write ~all our code with AI, and it's been getting more expensive. This came to a head when Opus 4.7 was released and, thanks to its tokenizer changes, our costs shot up. We knew we didn't need Opus for everything but we didn't want to lose out on the intelligence for the cases where you really need it. So we decided to build a model router to handle this for us. The Weave Router acts as an Anthropic/OpenAI endpoint specifically for coding agents. It looks at every inference request and intelligently (more on that in a sec) decides what model to send it to, handling all the translations required along the way. So it can use faster/cheaper models (e.g. DeepSeek v4, GLM 5.2, Kimi K2.6) when possible, and frontier models (Opus 4.8 & GPT 5.5 (& Fable whenever it's back)) when necessary. How do we know what model to route to? We trained an RL model on tens of thousands (so far!) of agent traces. We reward the routing model when it selects an LLM that successfully completes the given task. Here's an example: if you ask the router to plan a complex change, it will (probably) route that request to Opus 4.8. Subagents exploring the codebase to gather context will be routed to more suitable models (e.g. DeepSeek V4 Flash). Then when you have the plan ready to implement, it will be (most likely) be handed to a quicker model (e.g. GLM 5.2) to carry it out. We've been using this internally for the last month or so. We've saved 40% on tokens vs. what we otherwise would have paid, with no noticeable differences in quality or velocity. The router is source-available under Elastic License 2.0, so you can self-host it. Or if you prefer, you can also use our hosted version: weaverouter.com. I'll be here to answer any questions you may have! https://ift.tt/0EhpkNu June 26, 2026 at 11:40PM

Show HN: Hikaru Labs – Bulk image and file processing, 100% in-browser https://ift.tt/P0ngztS

Show HN: Hikaru Labs – Bulk image and file processing, 100% in-browser https://hikarulabs.xyz June 25, 2026 at 10:48PM

Show HN: Bible as RAG Database https://ift.tt/FuMYhno

Show HN: Bible as RAG Database Made this in a free evening. Index an permissive license translation of the Bible (WEB) into a RAG database to allow returning passages of similar semantic meaning. Lots of fun. For example, "more money more problems" returns Ecclesiastes 5:9-13 which, I'll just say, is spot on.. "Moreover the profit of the earth is for all. The king profits from the field. He who loves silver shall not be satisfied with silver, nor he who loves abundance, with increase. This also is vanity. When goods increase, those who eat them are increased; and what advantage is there to its owner, except to feast on them with his eyes? The sleep of a laboring man is sweet, whether he eats little or much; but the abundance of the rich will not allow him to sleep. There is a grievous evil which I have seen under the sun: wealth kept by its owner to his harm." Anyway - thought it was fun enough to share. It's slow and I vibe coded it so I haven't sorted out how to make it not take 15 seconds to vector search against the full 4GB index. https://ift.tt/OxhmjaJ June 25, 2026 at 08:42AM

Show HN: Top' for Redis Using eBPF https://ift.tt/bVuRtZQ

Show HN: Top' for Redis Using eBPF https://ift.tt/moIVgAh June 26, 2026 at 12:01AM

Show HN: iOS Apps on Linux https://ift.tt/isPmcQ9

Show HN: iOS Apps on Linux We developed and tested SwiftUI for Linux (and AppKit, NSFoundation, etc.) -- looking for more Swift apps to test on Linux! https://ift.tt/IgNSofv June 25, 2026 at 10:29PM

Show HN: DBOSify – Drop-in Temporal replacement built on Postgres https://ift.tt/LF6mgEb

Show HN: DBOSify – Drop-in Temporal replacement built on Postgres https://ift.tt/l0q4vRB June 25, 2026 at 12:20AM

Show HN: Metaspec: The DpANS3R Common Lisp Spec in S-Expr and HTML Format https://ift.tt/rjJQBqg

Show HN: Metaspec: The DpANS3R Common Lisp Spec in S-Expr and HTML Format I started this project back in 2015, to translate the TeX original specification into an easily parsed format (s-doc), and to create an HTML rendering of that format as a proof of concept. The project is homed here: https://ift.tt/TWe517g Differences from the Hyperspec (from the README): - Most importantly, it is free to modify and distribute. - The original TeX is very hard to parse and use for things other than generating a printed copy. The Hyperspec is an HTML rendering which can be parsed as HTML, but loses a lot of information. The Metaspec has an easily parsed intermediate form that can be used for all kinds of purposes, like converting into lookups. - Math equations are rendered using MathML. - Includes the acknowledgements and appendix sections. - Uses progressively enhanced Javascript to provide search and light/dark theme switching. - Incorporates over 145 patches for content, using corrections accumulated over the years, and documented in the errata page. - Includes TeX comments, which can contain interesting historical data. - Includes links and identifiers to bibliographical references. https://metaspec.dev/# June 24, 2026 at 11:28PM

Show HN: Forte – Cloud infra to get startups to production faster https://ift.tt/rcvXWRn

Show HN: Forte – Cloud infra to get startups to production faster Forte is an opinionated cloud platform that gets developers to production faster. Developers bring their code and Forte containerizes it with autoscaling and no cold starts, securely configures auth, and provides logging insights and monitoring out of the box. I used to help lead service development at AWS, and even before AI coding was widespread, our biggest bottleneck was rarely feature development. We would spend months on security prep, observability tooling, on-call optimization, and other overhead before launching new features. When I worked in startups, every team hit a surprisingly similar set of problems and spent weeks rebuilding auth, logging, monitoring, and payments. Platforms like Heroku, Render, and Railway are helpful for getting a container running but don't provide the rest of the tooling the teams need to go to production -- auth, secure defaults, and request-level logging. We built Forte to solve that entire stack of problems. You can check out Forte at https://ift.tt/jAQrPn7 (it's free to sign up and doesn't require a payment method). We'd love to hear your questions and feedback! https://ift.tt/jAQrPn7 June 24, 2026 at 11:06PM

Show HN: peerd – AI agent harness that runs entirely in your browser https://ift.tt/uIlsnDL

Show HN: peerd – AI agent harness that runs entirely in your browser Hey HN. http://peerd.ai is an AI agent harness that lives entirely in your browser as a web extension. You don’t have to install a separate “AI browser”. You don’t have to bolt on or run some external process or manage a clunky mcp integration. It’s just a fully contained web extension, written in no build vanilla JS with minimal non-browser dependencies, using your own provider keys, and Apache 2. This isn’t just a fun hack. While it has largely been a solo side project, I genuinely believe the browser and the web could be the most natural platform for AI agents to operate safely, autonomously, and most importantly without A2A middlemen (more on that in a sec). To demonstrate that point peerd doesn’t just drive browser automation. It spins up isolated sandboxes using tabs and worker instances to support various real workload types. Those include headless JS computational work, visual JS notebooks, personal client side apps, and real Linux VMs on top of wasm with full http networking. The industry discourse over the last several months has been dominated by “which substrate is the best for ai agent sandboxes” with many competing answers focused on different models and use cases. Cloudflare is one of the most prominent examples, positioning its v8 isolate based workers as the best in class solution thanks to faster than container startup times and strong isolation guarantees. The v8 isolate is of course the product of chromium, which runs on billions of browsers around the world for free. The browser as a whole is perhaps the most battle tested sandbox system in the entire software industry. It’s been built on 3 decades of learning from hostile content, hostile code, and hostile users. Native and cloud agents are necessarily rebuilding all or most of this posture from scratch. peerd doesn’t. It leverages everything the browser has to offer and pushes it to its functional limits, while inheriting its security baseline and isolation from the host system. Robust sandboxing isn’t the only thing the browser offers and peerd uses. It comes with extremely powerful and underrated primitives, from webCrypto, webRTC, webAuthn, webGPU, and ~soon WebNN. Direct web access, with your real live sessions, and api calls with fetch present an alternative model to MCP integrations. The agent can write and spawn web apps right there in a tab, no hosted service necessary. Then there’s the A2A piece: peerd already has a rudimentary p2p (peerd-to-peerd?) network in place using webRTC. Today you can connect with peers on the network, add them as contacts, and share signed apps you’ve created. I’m working on extending these apps to be able to leverage the same p2p network to support decentralized web apps (dwapps), as well as facilitate true p2p A2A with no platform or middlemen. Given this is an early part time project, this is an extremely experimental build and in a v0.x preview state. I’ve taken care to attempt to address the lethal trifecta: the main agent loops/sessions never ingest untrusted DOM code or possess low level navigation tools. It delegates those tasks to dedicated web runners with no wider tooling or secrets access that return summarized results. Both the DOM and the summarized results are bracketed as untrusted, meaning two stacked prompt injection escapes are needed. All egress goes through a central module that has a customizable deny list, and only models calls to designated allowed endpoints are possible. See more in the docs, site, and the code itself. Ultimately, use at your own risk. Today anthropic, open router, local ollama, and even an experimental WebGPU instance of Gemma are supported. Honest limitations: Chrome store and AMO are still pending until it can get more eyeballs and live usage. Just loading unpacked from GitHub is the easiest way to go, and as a bonus makes it easy to audit thanks to no build. Linux on wasm depends on the Cheerpx engine, which is not open source and has restrictions for commercial use. That may be a good reason to reassess it compared to alternatives, but it’s also the most performant and looks closest to implementing 64bit support. Poke around, use it, critique it, and have fun. https://ift.tt/yzLICVP June 23, 2026 at 10:05PM

Show HN: Caplets - Give your agent capabilities, not giant tool walls https://ift.tt/CoTcFYS

Show HN: Caplets - Give your agent capabilities, not giant tool walls https://caplets.dev June 23, 2026 at 11:31PM