I want everything local – Building my offline AI workspace
instavm.io
Tribblix – The Retro Illumos Distribution
tribblix.org
What the windsurf sale means for the AI coding ecosystem
ethanding.substack.com
Breaking the Sorting Barrier for Directed Single-Source Shortest Paths
arxiv.org
I bought a £16 smartwatch just because it used USB-C
shkspr.mobi
Ultrathin business card runs a fluid simulation
github.com
Sandstorm- self-hostable web productivity suite
sandstorm.org
Engineer restores pay phones for free public use
npr.org
Tor: How a military project became a lifeline for privacy
thereader.mitpress.mit.edu
Getting good results from Claude Code
dzombak.com
Efrit: A native elisp coding agent running in Emacs
github.com
Representing Python notebooks as dataflow graphs
marimo.io
How we replaced Elasticsearch and MongoDB with Rust and RocksDB
radar.com
Jim Lovell, Apollo 13 commander, has died
nasa.gov
Hacking Diffusion into Qwen3 for the Arc Challenge
matthewnewton.com
Ask HN: How can ChatGPT serve 700M users when I can't run one GPT-4 locally?
Astronomy Photographer of the Year 2025 shortlist
rmg.co.uk
Let's properly analyze an AI article for once
nibblestew.blogspot.com
A SPARC makes a little fire
leadedsolder.com
Unmasking the Sea Star Killer
biographic.com
The surprise deprecation of GPT-4o for ChatGPT consumers
simonwillison.net
How to safely escape JSON inside HTML SCRIPT elements
sirre.al
Fire hazard of WHY2025 badge due to 18650 Li-Ion cells
wiki.why2025.org
If you're evaluating JSON as JavaScript, you also need to make sure none of the objects have a key named "__proto__", or else you can end up with some strange results.
(This is related to the 'prototype pollution' attack, although searching that phrase will mostly give you information about the more-dangerous variant where two objects are being merged together with some JS library. If __proto__ is just part of a literal, the behavior is not as dangerous, but still surprising.)