AI Summarized Hacker News

Front-page articles summarized hourly.

Show HN: C# Game Engine with its own scripting language and IDE

ArcadeMaker is an open-source, beginner-friendly 2D game engine and IDE written in C#, using its own Exp language (not C#) and MonoGame for graphics/audio, with web export planned via a KNI engine. Inspired by GameMaker 8, it evolved from C# scripting to its own language, and the IDE currently includes features not yet implemented in the engine. It's unfinished by design; long-term goals are parity with the old engine, full IDE features, web export, and broader templates. Licensed under MIT; contributions welcome.

HN Comments

How do you sell a CPU design when the instruction set is free?

Darian Domocos of Fiora5 argues that the hardest barrier to starting a CPU company is credibility—getting investors to believe two unknown founders can succeed. The interview covers building a business around open RISC-V, where RVA23 standardization accelerates ecosystem maturity even as closed systems keep advantages. It also discusses sovereignty through supply chains: Europe seeks a local, resilient chip ecosystem rather than total self-sufficiency. Fiora5 attracts talent with equity and responsibility. Reading list includes The Confidence Game and Onur Mutlu’s ETH Zürich lectures.

HN Comments

Blog about things you don't understand yet

Sean Goedecke argues that every blog post should reveal what sparked it and what the writing taught the author; if nothing new is learned, it isn’t publishable. Writing clarifies thinking and often changes the author’s views, so he favours posts that argue a position rather than meandering. He advocates blogging about topics you don’t fully understand, explaining why it’s acceptable for beginners to explain complex fields, and why public consensus can be wrong. Key tips: write with research, defend controversial points, rewrite the intro after finishing, and seek feedback (including from LLMs).

HN Comments

Compute-Optimal Is Not Cluster-Optimal

MOSAIC argues that compute-optimal models are not cluster-optimal: optimizing for model FLOPs alone misses how a cluster delivers work. The authors integrate the systems stage into the scaling-law stage, pricing architectures by deliverable FLOPs, MFU, and goodput on a cluster. In MoEs, sparsity and the expert-split factor G reshape MFU and the feasible design space. With a fixed FLOP budget, predicted loss favors sparsity, but hardware constraints push deliverable FLOPs interior, flipping the optimum. Ranking by FLOPs misorders designs; the same run can win on loss-per-FLOP yet lose on efficiency. Architecture and systems co-design are required; cluster-aware pricing matters.

HN Comments

SparrowMap – Cameras that watch government vehicles

SparrowMap is a volunteer, crowd-sourced live map that watches government vehicles. Volunteers run a detector on spare phones or PCs in-browser; video never leaves the device. Government vehicles’ photos and license plates are kept and become public records, while plates of other vehicles are destroyed locally. Only anonymous detections, not photos or plates, are sent to the server as a dot on the map. No accounts or apps required. It runs on old phones or laptops, with desktop setup scripts for Windows/Linux. Built in Michigan.

HN Comments

Bluesky Protocol Services

Bluesky launches Bluesky Protocol Services to organize infrastructure docs and contracts for Jetstream and Bluesky endpoints. Jetstream v2 adds Network Replay, enabling backfill history and point-in-time snapshots via planBackfill, listSegments, getSegment, and getBlock; archive requests require a token, live tail remains unauthenticated. v2 is live in west/east regions; v1 remains. New Jetstream SDKs (TypeScript and Go) and a Bluesky TypeScript SDK rebuilt on @atproto/lex. Updated endpoints.bsky.app docs cover the Jetstream surface. The infrastructure is self-hostable and open source.

HN Comments

How a device finds encrypted DNS by itself

DDR (Discovery of Designated Resolvers) lets a DNS resolver publish encrypted endpoints (hostname, port, protocol) for devices already talking to it. Devices ask _dns.resolver.arpa to see if encrypted endpoints exist; the resolver replies with available endpoints (DoH, DoT, DoQ) and a preference order. The device then connects to its chosen endpoint, so all further queries are encrypted. Windows 11 and Apple devices auto-ask on network join. Replies may be global or per-profile, depending on the resolver. If no endpoints are published, none are offered. Upgrading from plain DNS is susceptible to on-path tampering; device-config is stronger.

HN Comments

How AI text watermarking works

AI text watermarking hides a pattern in the writer’s word-choice process, not in the letters themselves. At each word fork, a secret key colors candidate words green or red, nudging the outcome while keeping meaning intact. A detector replays the key and counts greens; with the right key, green wins beyond chance. Editing erases the mark where word-runs survive—light edits dilute it, heavy rewrites erase it. Watermarks are private, probabilistic tests controlled by providers (not universal detectors), and detection depends on text length and the specific scheme.

HN Comments

Show HN: My solar died for 6 months, so I built a watchdog

SunRanker is a free watchdog for home solar that checks daily production and emails you the moment something breaks. After a one-minute setup (via Enphase or SolarEdge), it reports in plain language what was produced and whether that’s normal, plus a short monthly review. It highlights outages where monitoring goes quiet or output drops below typical levels, catching issues in days rather than weeks. Built by a solar owner to avoid silent bills, it aims to provide simple, actionable alerts rather than engineer portals.

HN Comments

Made by Johno Whitaker using FastHTML