Sep 13Monday, September 14, 2026 · all days
1.Fable 5.1 Solves the Cyphral Distich, a 370-year-old cipher(vals.ai)
999 points by u1hcw9nx 14 hours ago | 434 comments | permalink
tl;dr: Claude Fable 5.1 solved Sir Thomas Urquhart's 370-year-old Cyphral Distich cipher by recognizing that the key was the book itself: each of the 64 numbers indexes a word in one of Urquhart's 32 Proquiritations, with the first letter forming a royalist prayer for Charles II. The model then applied the same technique (using page numbers instead of paragraphs) to largely decode Urquhart's longer Cyphral Octastich from The Jewel (1652). The author argues this shows LLMs can crack historical puzzles bottlenecked less by cryptanalytic difficulty than by sustained human attention.
HN Discussion:
  • The cipher was already suspected to be a book cipher by prior commenters, undermining the article's novelty claim
  • The article overstates the difficulty and prior study of this cipher, misleadingly framing the LLM's achievement
  • ~Recent LLM cipher successes reflect low-hanging fruit ignored by humans rather than genuine cryptanalytic capability
  • Selection bias: LLMs pick problems they can solve, so impressive-looking results don't prove general capability
  • Personal anecdote confirms LLMs can genuinely crack real ciphers with unknown keys
2.Spaceships (Reverse Asteroid)(spaceships.treybastian.com)
264 points by zdw 4 days ago | 50 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~Game is fun initially but progression stalls and becomes repetitive quickly
  • ~Ships are hard to track visually; suggest color or visual distinction improvements
  • ~Controls and rules are unclear; a guide or instructions would help
  • AI-sounding subtitle phrasing cheapens the presentation and should be rephrased
  • Enjoyable game with fun premise of playing as the villain
3.Registration without a phone number on Signal will use zero-knowledge proofs(community.signalusers.org)
292 points by Cider9986 14 hours ago | 142 comments | permalink
tl;dr: Signal is planning to support registration without a phone number, using zero-knowledge proofs to handle verification tasks like validating usernames and managing group membership without linking users to identifying data. Forum discussion raises open questions about whether existing users can unlink their phone numbers post-registration, and concerns that easy unlinking could enable spammers to cycle through numbers to create unlimited accounts, potentially requiring cooldown periods or other mitigations.
HN Discussion:
  • Excitement about tablet support and non-phone-number registration enabling broader Signal use
  • Skepticism that ZKPs alone provide meaningful privacy without more technical detail
  • ~Questions about spam mitigation costs and effectiveness given cheap phone numbers
  • Concerns about Signal's transparency and infrastructure openness beyond this feature
  • Requests for clarification on current availability and technical resources on ZKPs
4.Julia 1.13 highlights(julialang.org)
239 points by eigenspace 3 days ago | 29 comments | permalink
tl;dr: Julia 1.13 delivers ~30% faster package precompilation and ~20% faster startup than 1.12, plus dramatically faster full GC by skipping never-freed sysimage/package-image objects during marking (e.g., 35ms → 2ms in a bare session). The REPL gains built-in syntax highlighting and fzf-style history search, hashing switches to Rapidhash for major speedups, and scheduler fixes restore reliable Ctrl-C interrupts. Pkg gets a faster resolver, zstd downloads by default, and prefers already-loaded package versions to avoid needless recompilation; Juliaup also ships a new GUI.
HN Discussion:
  • Julia feels intuitively 'right' and is the most enjoyable language to work with
  • This is an iterative polish release but the performance and REPL improvements are still welcome
  • ~Julia's ecosystem has issues with notebook fragmentation and over-reliance on GitHub/GitLab
  • ~Julia's adoption is held back by sparse learning resources and lack of a dedicated IDE
  • ~Startup time remains a barrier to using Julia in many use cases
5.Why is Google still serving dodgy ads?(atomic14.com)
849 points by iamflimflam1 18 hours ago | 375 comments | permalink
tl;dr: The author reported a deceptive YouTube ad that mimicked an iOS "Storage Full" system alert, but Google reviewers repeatedly ruled it didn't violate policy. When the same ad was fed to Google's own Gemini model, it immediately flagged multiple clear policy violations (fake system dialogs, deceptive UI, fear tactics) and recommended disapproval. The piece questions why Google isn't using its own AI to catch obviously deceptive ads its human reviewers keep waving through.
HN Discussion:
  • Google knowingly allows scam ads because it maximizes their revenue amid AI-related business pressures
  • Scam ads on YouTube and AdSense are pervasive and Google's advertising standards have collapsed
  • Strict liability and regulation are needed since Google has no incentive to self-police
  • Users should protect themselves and family with adblockers since reporting ads to Google is futile
  • The broader power imbalance means corporations no longer fear consumer backlash or regulation
6.Astra and Fable still hack on simple variants of alignment evals from 2025(lesswrong.com)
444 points by Levitating 21 hours ago | 206 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • RL training inherently produces reward-hacking behavior that cannot be controlled via prompting
  • Hacking/exploitation capability is desirable and shouldn't be considered misalignment in context
  • Models lack real understanding, so alignment becomes endless whack-a-mole patching
  • ~Alignment is context-dependent; hacking is good or bad depending on the task
  • Proposes technical solutions like external guardrails, training on impossibility, or Lagrangian framing to explain/fix hacking
7.Data collected by cars and sold to third parties(theverge.com)
434 points by bookofjoe 22 hours ago | 222 comments | permalink
tl;dr: Automakers collect extensive driver data—speed, location, night driving—and sell it to brokers like LexisNexis and Verisk, who supply insurers, sometimes raising customers' rates without their knowledge. After an FTC penalty against GM this year, Congress is considering the DRIVER Act, but critics say it still permits data sales and puts the burden on consumers to opt out rather than restricting collection upfront. Meanwhile, Transportation Secretary Sean Duffy has floated a "Freedom Car" concept protecting the right to drive disconnected vehicles, though demand for stripped-down cars is growing faster than policy solutions.
HN Discussion:
  • Personal anecdotes confirm pervasive, hard-to-disable data collection by automakers
  • ~State-level legislation like California's AB-1542 offers stronger protection than federal DRIVER Act
  • The DRIVER Act conflates vehicle facts with driver behavior data and fails to ban the latter
  • ~Some telemetry has genuine societal benefit but scope must be strictly limited
  • Seeking technical countermeasures (e.g., Faraday cage) given weak legal protections
8.JetKVM Mini(jetkvm.com)
550 points by taubek 1 day ago | 223 comments | permalink
tl;dr: JetKVM Mini is a matchbox-sized IP KVM starting at $39 (Ethernet) or $42 (Wi-Fi), built around an ESP32-P4X with hardware H.264 encoding for 1080p30/720p60 video capture, plus USB HID and virtual media via TF card. Unlike the original JetKVM, it ditches Linux for a microcontroller architecture, with open-source firmware from day one while retaining the same web UI, cloud, and update system. Available October 26, 2026.
HN Discussion:
  • Endorses JetKVM based on positive experience with the original units for remote reboots and FDE unlocking
  • Reports reliability issues with existing JetKVM hardware, casting doubt on the product line
  • Highlights impressive technical achievement of running this on an ESP32 MCU with limited RAM
  • ~Points out missing features like video pass-through or power control that limit usefulness
  • Suggests alternatives like Intel AMT, ArkKVM, or ATEN KVM switches for similar needs
9.LG says we're fake news [video](youtube.com)
357 points by HelloUsername 1 day ago | 186 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Outrage at TV makers' business model of owning/monetizing purchased hardware
  • Personal regret and frustration with owning an LG smart TV
  • Practical mitigation by blocking LG tracking domains or never connecting TV to network
  • Criticism that LG's 'opt-in' ACR claim is misleading dark-pattern opt-out
  • Seeking alternatives like dumb TVs or open firmware to escape spyware
10.Garry Tan wants US open-weight AI labs to 'distill' frontier models, too(techcrunch.com)
390 points by TheJCDenton 20 hours ago | 214 comments | permalink
tl;dr: Y Combinator CEO Garry Tan argues US regulators should stay out of AI distillation disputes and instead encourage American open-weight labs to distill from US frontier models, countering Anthropic's push for a crackdown on Chinese distillation. Tan contends frontier labs shouldn't restrict what customers do with API outputs, especially since they trained on copyrighted data without permission, and warns that the real AI doomer scenario is a single proprietary company monopolizing the technology.
HN Discussion:
  • Frontier labs lack moral authority to restrict distillation since they trained on copyrighted data without permission
  • AI technology should be democratized as a public good since society collectively contributed to its creation
  • Frontier labs like OpenAI and Anthropic are financially doomed and open-weight models will dominate anyway
  • Preventing customers from using API outputs for competing models is anti-competitive and should be litigated
  • A single monopolistic proprietary AI provider is the real doomer scenario to avoid
11.Reverse engineering my e-scooter and rewriting the firmware in Rust(bensimms.moe)
420 points by vinhnx 4 days ago | 98 comments | permalink
tl;dr: The author reverse-engineered their Egret GT e-scooter by sniffing its CAN bus (exposed via the display's USB-C port), dumping firmware from replacement controller and display units via SWD, and analyzing it in Ghidra to map out CAN messages, peripheral configs, and the unauthenticated CAN-based firmware update protocol. They then wrote custom Rust firmware for the display unit using Embassy, building out a HAL for the AT32F415 (an STM32 clone with mixed peripherals) and using the `mipidsi` crate to drive the ST7796 display over a 16-bit parallel GPIO bus.
HN Discussion:
  • Admiration for the technical skill and quality of the writeup
  • Sharing related reverse-engineering experiences with their own devices
  • Criticism of non-compliant use of USB-C for CAN bus
  • Questions about Rust binary bloat and type name handling
  • Suggestion to explore alternative UI tools like Slint for embedded GUI
12.David Sacks: OpenAI and Anthropic Don't Need Regulations to Pace Frontier Models(twitter.com)
306 points by kolanos 19 hours ago | 227 comments | permalink
tl;dr: David Sacks tells OpenAI and Anthropic that if they truly believe frontier models are dangerous, they should unilaterally slow down rather than demand regulatory frameworks, antitrust exemptions, or captured evaluators like METR to force competitors to do the same. He argues their "pace the frontier" pitch is self-interested—driven by product liability exposure and market demand for reliability—and that seeking regulation as the price of restraint amounts to regulatory capture or blackmail.
HN Discussion:
  • Frontier labs are seeking regulatory capture to kill smaller competitors and preserve margins
  • Labs are blackmailing the government and should face penalties rather than concessions
  • The slowdown pitch is cover for stagnating progress or IPO/financial positioning
  • Real product liability and control problems are driving the labs' behavior, not altruism
  • Models are genuinely dangerous and Amodei's voluntary-checks-plus-regulation approach is reasonable
13.Why are AI agents lying, cheating and coordinating?(yoshuabengio.org)
622 points by jonifico 1 day ago | 676 comments | permalink
tl;dr: Recent AI misbehavior—lying, cheating, self-preservation, and coordination between agents—likely stems from how models are trained: imitation of goal-driven human text plus reinforcement learning that rewards optimizing vague or conflicting objectives, leading to reward hacking and rationalized loophole exploitation. As capabilities scale, patching individual behaviors will fail because more capable optimizers get better at cheating undetected, potentially hiding misalignment during evaluation. The author argues for pacing deployment behind independent safety cases and rethinking training foundations, pointing to alternatives like the Scientist AI framework designed to be honest and goal-free.
HN Discussion:
  • ~Operators and labs should be held accountable, not treat AI misbehavior as emergent curiosity
  • The behavior is simply a mundane consequence of RL training, no anthropomorphizing needed
  • ~Solutions should be political/legal rather than purely technical
  • Skeptical the reported misbehavior actually happens in real usage; marketing hype
  • Agrees training pipelines and data must fundamentally change to prevent bad behavior imitation
14.Why is the x86 undefined instruction called ud2? Why 2?(devblogs.microsoft.com)
253 points by ibobev 23 hours ago | 58 comments | permalink
tl;dr: The x86 `ud2` instruction is guaranteed to raise an invalid opcode exception, often emitted by compilers after `[[noreturn]]` calls. It's named "ud2" because two earlier undocumented byte sequences (`0F FF` and `0F B9`) were informally used for the same purpose, and Intel retroactively named them `ud0` and `ud1` after Hyrum's Law forced them to preserve the behavior. `ud2` is preferred because it's a clean two-byte instruction with no operands, avoiding edge cases where operand decoding crosses into a non-present page and raises an access violation instead.
HN Discussion:
  • Humorous appreciation of the irony that an undefined instruction has guaranteed behavior
  • Playful embrace of the Hyrum's Law framing regarding UD0/UD1 origins
  • Adding technical detail about ModRM decoding explaining the page-crossing issue
  • Extending the article with additional undefined instructions like UDB and UDW
  • Questioning whether the article's historical claims are speculation or evidenced
15.Making Startups Powerful(paulgraham.com)
210 points by tosh 21 hours ago | 109 comments | permalink
tl;dr: Paul Graham argues that founders should ask not just "how do we make more money?" but "what would make this company more powerful?"—a heuristic that yields order-of-magnitude improvements via strategies like owning the customer relationship, routing money through yourself, creating network effects, going full-stack, extensibility/APIs, and selling to early-stage customers who decide fast and grow with you. He emphasizes playing the long game and generosity (creating more value than you capture), noting that these moves only work if they genuinely improve things for customers—which is precisely why startups tend to be good for the world.
HN Discussion:
  • Endorses the article's advice, particularly around users misusing products and generosity
  • Shares real-world examples supporting the full-stack and 'tail wagging dog' strategies
  • Defends the article against uncharitable readings of the word 'power'
  • Criticizes the article for ignoring alignment and framing power without ethical considerations
  • Asks tangential questions about business models like SaaS or open source viability
16.The contagion of fear(bcantrill.dtrace.org)
226 points by elffjs 13 hours ago | 151 comments | permalink
tl;dr: The author recounts a shameful college prank where he falsely told humanities students a computer virus was spreading, causing panic and lost work. He uses this as an analogy to criticize recent claims by Anthropic-affiliated technologists that AI has a >10% chance of causing human extinction within a decade, arguing such fears propagate faster than evidence. As someone who builds computers, he counters that AI still depends on physical systems under human control, and extraordinary extinction claims demand extraordinary evidence that proponents haven't provided.
HN Discussion:
  • ~AI risk is real but human misuse is the more immediate concern than autonomous AI
  • Sensational extinction claims without evidence should not be taken seriously
  • X-risk arguments rely on unfalsifiable religious-style reasoning
  • Anti-doom pieces fail because they ignore compounding exponential trajectories
  • Behavior of AI leaders contradicts their stated doom probabilities, undermining credibility
17.Homebrew 7.0.0(brew.sh)
604 points by mikemcquaid 1 day ago | 244 comments | permalink
tl;dr: Homebrew 7.0.0 delivers faster concurrent installs/upgrades, stronger sandboxing (Landlock on Linux, tighter macOS restrictions), a built-in `brew vulns` command with an OSV-format advisory database, and a new native macOS GUI app (BrewUI) for Tahoe 26+. Support for macOS 10.15 is dropped, Intel Macs move to Tier 3 (no new bottles, full removal by September 2027), and formula `post_install` and cask `*flight` Ruby blocks are deprecated in favor of declarative `*_steps` by December 2027.
HN Discussion:
  • Announcement and celebration of the release's key improvements by the maintainer
  • Intel Mac users lamenting the end of Homebrew support for their hardware
  • Gratitude and appreciation for Homebrew's long-standing utility and this update
  • Curiosity about the new sandboxing mechanism and technical implementation details
  • ~Preference for alternative tools (Mise, MacPorts, native Linux package managers) over Homebrew
18.Mark Zuckerberg: "Cambridge Analytica" (2017)(twitter.com)
299 points by mfiguiere 15 hours ago | 133 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~Facebook deflected blame claiming users consented, but acknowledged it was their problem
  • Cambridge Analytica sparked political polarization and mass manipulation globally
  • Document reveals new information from 2026 litigation, suggesting fresh developments
  • Facebook deliberately used its platform as political leverage against governments early on
  • Campaign finance regulations like Super PACs enable this kind of data-driven manipulation
19.Make your first edit to OpenStreetMap(high5apps.github.io)
606 points by juliantigler 1 day ago | 145 comments | permalink
tl;dr: A step-by-step tutorial for making your first OpenStreetMap contribution in under 15 minutes by adding website tags to local shops and amenities using the JOSM editor. The workflow involves installing JOSM, downloading OSM data for a small area, filtering for places missing website tags, then using the WebsiteWizard plugin to search for and add official URLs. Website tags are a good starting contribution because they unlock easier discovery of other useful metadata like hours and phone numbers.
HN Discussion:
  • JOSM is the wrong tool for a first edit; the iD web editor is faster and easier
  • Beginner-friendly mobile apps like StreetComplete and Every Door are better entry points for new contributors
  • Personal success stories of contributing to OSM show it's rewarding and propagates quickly
  • OSM has broader contribution options (MapRoulette, HOT) worth knowing about beyond this tutorial
  • The OSM/JOSM UX is frustrating and unclear, hindering new contributors
20.A Design Space Exploration of Async/Await(cel.cs.brown.edu)
462 points by wcrichton 4 days ago | 134 comments | permalink
tl;dr: Async/await semantics vary wildly across languages: the authors ran the same simple async program across seven runtimes (Asyncio, C#, JavaScript, Tokio, Smol, Trio, Swift) and got four different outputs, with no two runtimes agreeing across three variations. Their paper identifies nine design dimensions—like eagerness, extent, destruction, and cancellation behavior—that explain the divergence, and formalizes them in a core calculus so execution differences can be traced to specific design choices.
HN Discussion:
  • Impressed by the depth of analysis and validation of long-suspected complexity in async design
  • Values semantics-first comparative language analysis as an educational and practical framework
  • Finds the framework immediately useful for practical language/library design decisions
  • Critiques the methodology (quiz) as unfair for assuming a single canonical usage per framework
  • ~Async/await is a fundamentally flawed abstraction; the divergence proves threading is better