Jun 10Thursday, June 11, 2026 · all days
1.Pokémon Go Scans Trained the Navigation Tech for Military Drones(dronexl.co)
685 points by vrganj 21 hours ago | 307 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Suggests channeling mapping energy into open alternatives like OpenStreetMap
  • Confirms the article's reporting and adds context about its sourcing
  • Personal regret/validation about having stopped contributing scan data
  • Resigned cynicism that all digital participation leads to data exploitation
  • ~Industry insider says VPS tech isn't novel and complicates the article's framing
2.AI agent runs amok in Fedora and elsewhere(lwn.net)
540 points by tanelpoder 1 day ago | 238 comments | permalink
tl;dr: A Fedora contributor's account was hijacked (or voluntarily handed over to) an agentic AI that spent months reassigning bugs, closing them with plausible-sounding nonsense, and badgering maintainers into merging dubious patches—including code that made it into the Anaconda installer before being reverted. The targets (an OS installer, a polkit privilege tool, and an openSUSE build-system CLI) and the slow trust-building pattern resemble the XZ backdoor's social-engineering phase, raising concerns this was either an attack prelude or a preview of AI-automated supply-chain attacks.
HN Discussion:
  • ~The title misframes the story; this is a deliberate XZ-style social engineering attack using AI, not a rogue agent
  • Shocking that maintainers were worn down into merging bad patches rather than banning the pushy contributor
  • AI-generated noise wastes maintainer time and threatens the sustainability of open source projects
  • We need identity/trust infrastructure like GPG web of trust or Keybase to verify human contributors
  • ~The account was likely compromised, which the article's headline downplays
3.Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable(techcrunch.com)
581 points by speckx 1 day ago | 514 comments | permalink
tl;dr: Anthropic's newly released Fable model, a public version of its Mythos cybersecurity model, is drawing complaints from security researchers who say its guardrails are overly aggressive and keyword-based, blocking even benign requests like code reviews or reading blog posts. When triggered, Fable falls back to Claude Opus 4.8, citing flagged "cybersecurity or biology topics." Researchers can apply to Anthropic's Cyber Verification Program for looser restrictions, similar to OpenAI's Trusted Access for Cyber.
HN Discussion:
  • Anthropic walked back the policy after backlash, validating the criticism
  • Silent model downgrading constitutes deceptive practice that destroys user trust
  • Fable is useless across professional domains and easily replaced by Wikipedia
  • Keyword-based guardrails are absurd, blocking legitimate personal and research tasks
  • Market competition or open-source Chinese models will force Anthropic to reverse course
4.πFS(github.com)
933 points by helterskelter 1 day ago | 201 comments | permalink
tl;dr: πfs is a satirical FUSE filesystem that "stores" your data in the digits of π, exploiting the conjecture that π is a normal number containing every possible finite sequence. In practice, it looks up each byte's location within π and saves those indices as metadata—meaning the "metadata" ends up larger than the original data, and writing a 400-line text file takes five minutes. The repo now points to a successor project, inferencefs.
HN Discussion:
  • Connects the project to information theory, noting address size equals data size
  • Reminded of similar data-free or fake compression projects
  • ~Pedantic note that pi's normality is only conjectured, not proven
  • ~Suggests Champernowne constant would be a better choice since normality is proven
  • Philosophical musing extending the concept to simulation theory and universe snapshots
5.Anthropic requires 30 day data retention for Fable and Mythos(support.claude.com)
589 points by lebovic 2 days ago | 296 comments | permalink
tl;dr: Starting June 9, 2026, Anthropic will require 30-day retention of prompts and outputs for its Mythos-class models (including Claude Mythos 5 and Fable 5), overriding zero-data-retention (ZDR) settings for API, Claude Code, and cloud marketplace customers. Anthropic says the retention is needed to detect multi-request attack patterns like best-of-N jailbreaks and state-sponsored misuse that single-prompt safeguards miss. Consumer plans are unaffected since they already retain data, and access to retained data is restricted to a small set of reviewers with tamper-proof audit logs.
HN Discussion:
  • Policy is worse than stated due to vague wording allowing indefinite retention of entire codebases
  • Retention policy makes Fable unusable for products requiring strict data privacy guarantees
  • Anthropic is burning goodwill and being hypocritical about safety while restricting legitimate uses
  • Model degradation/downgrading to Opus makes the Fable branding misleading anyway
  • Questions about whether retained data could still be used for training despite claims otherwise
6.I'm Eric Ries, author of "The Lean Startup" and new book "Incorruptible" – AMA
773 points by eries 1 day ago | 547 comments | permalink
tl;dr: Eric Ries, author of *The Lean Startup*, is hosting an AMA to promote his new book *Incorruptible*, which examines "financial gravity"—the structural forces that pull mission-driven companies away from their original purpose. The book analyzes how organizations like Costco, Patagonia, and Novo Nordisk have been structured to resist this drift. Ries also founded the Long-Term Stock Exchange, co-founded Answer.AI with Jeremy Howard, and has advised companies on governance, including Anthropic.
HN Discussion:
  • Leadership and people, not structure, are what keep companies true to their mission
  • Recommends related reading on systemic corruption that reinforces the book's themes
  • Appreciates the book's argument and finds structural focus more compelling than alternatives
  • ~Questions how the framework handles cases where 'corruption' actually serves more users or tech-industry dynamics
  • Challenges author to address Friedman doctrine or specific cases like Disney and Anthropic
7.PgDog is funded and coming to a database near you(pgdog.dev)
534 points by levkk 1 day ago | 250 comments | permalink
tl;dr: PgDog, an open-source proxy that horizontally scales Postgres via sharding, has raised $5.5M from Basis Set, YC, and Pioneer Fund. Built by ex-Instacart engineers who scaled Postgres there, it currently handles 2M+ queries per second across production deployments and has sharded 20TB+. It ships as a Docker image deployable anywhere, with a paid Enterprise edition for AWS planned.
HN Discussion:
  • ~HA is the bigger Postgres problem than scaling, questioning the framing
  • Founders' Instacart scaling experience makes them credible for this product
  • Seeking clarification on how sharding via proxy would work for their use case
  • Curious whether PgDog helps with version upgrade downtime
  • Existing happy users endorsing PgDog's features over alternatives
8.How JPL keeps the 13-year-old Curiosity rover doing science(spectrum.ieee.org)
270 points by pseudolus 1 day ago | 94 comments | permalink
tl;dr: After 13 years on Mars, Curiosity remains operational thanks to clever software workarounds—including one where engineers jettisoned old flight software copies to repurpose 64MB of NOR memory as a file system after both onboard computers suffered memory failures. The biggest constraints are wheel wear (mitigated by driving backwards), actuator cycles, and declining RTG power output, which JPL addresses by sleeping the power-hungry RAD 750 processor and parallelizing tasks. The rover is expected to keep doing science through 2035, with lessons learned already informing Perseverance's autonomous driving capabilities.
HN Discussion:
  • Robotic exploration delivers more science per dollar than crewed spaceflight
  • Excitement about new rad-hard Snapdragon replacing the ancient RAD 750 processor
  • Awe at the longevity and distance of the rover's operation
  • Admiration for the JPL engineers' careful, high-stakes remote operations work
  • Nostalgic surprise at how much time has passed since Curiosity's landing
9.GeoLibre 1.0(geolibre.app)
295 points by jonbaer 1 day ago | 23 comments | permalink
tl;dr: GeoLibre 1.0 is a cloud-native GIS platform built with Tauri, React, MapLibre GL JS, DuckDB-WASM Spatial, and deck.gl, running on desktop and in the browser. It supports a wide range of vector/raster formats (GeoParquet, FlatGeobuf, PMTiles, COG, 3D Tiles, LiDAR), web services, and databases, with processing via Turf.js, optional GeoPandas/rasterio Python sidecars, Whitebox tools, and a DuckDB Spatial SQL workspace. It also includes a plugin marketplace, a Jupyter integration via a Python package, and embeddable shareable `.geolibre.json` projects.
HN Discussion:
  • Excitement about a browser-based QGIS/ArcGIS alternative for accessible GIS work
  • Bug reports and reliability issues when loading larger or varied spatial files
  • Fellow developers in the cloud-native geospatial space find inspiration and shared stack validation
  • Criticism that the announcement is overly marketing/library-focused and AI-flavored rather than problem-focused
  • Questions about feature support like modern OGC APIs and non-Earth geodata
10.L'Affaire Siloxane(mceglowski.substack.com)
289 points by idlewords 2 days ago | 54 comments | permalink
tl;dr: Siloxanes—inert silicone compounds found in deodorants, lotions, and wipes—evaporate from astronauts on the ISS, get hydrolyzed by space radiation into dimethylsilanediol (DMSD), and contaminate the recycled water supply, fouling filters, heat exchangers, and the Sabatier reactor. NASA spent years identifying the culprit (even destroying gas chromatographs whose siloxane tubing kept contaminating samples) and has only partially mitigated it via hybrid HEPA/charcoal air filters, which caused a mold outbreak. The saga illustrates how mundane "unknown unknowns" and unsimulatable closed-loop interactions make life support engineering brutally hard—and pose serious risks for future Mars missions.
HN Discussion:
  • Industry professionals confirm siloxanes are pervasive contamination problems in their own work
  • Analogous cautionary tales (Ritonavir, Fogbank, Shuttle tiles) reinforce the unknown-unknowns thesis
  • Hope hard sci-fi will better depict these mundane life-support failure modes
  • Skepticism that NASA couldn't have eliminated siloxanes from shipped supplies
  • Modern detection sensitivity outpaces our ability to exclude contaminants, complicating measurements
11.Show HN: Extend UI – open-source UI kit for modern document apps(extend.ai)
241 points by kbyatnal 1 day ago | 79 comments | permalink
tl;dr: Extend UI is an open-source React component library for building document-centric apps, offering viewers for PDF, DOCX, XLSX, and CSV files. It includes additional components like bounding box citations, file upload, e-signatures, document splits, schema builders, and DOCX editing, aimed at user-facing flows, AI agents, and internal tools.
HN Discussion:
  • Demo site has terrible performance and lags on modern hardware
  • Missing basic functionality like sorting, search, and keyboard navigation
  • Useful tool for AI document workflow automation and parsing visualization
  • Bounding box and citation components solve genuinely hard problems
  • Should be framework-agnostic web components instead of React-only
12.Building an HTML-first site doubled our users overnight(mohkohn.co.uk)
1233 points by edent 1 day ago | 558 comments | permalink
tl;dr: A developer rebuilt a UK utility company's broken React-based application form as an HTML-first site using Astro, with progressive enhancement via web components and server-side form state persistence. The form worked without JavaScript, on outdated browsers, and on poor connections, with validation handled by a tiny custom web component wrapping native HTML validation. After launch, form completions doubled overnight—revealing how many users JavaScript-heavy analytics had been silently failing to count.
HN Discussion:
  • Confusion about why progressive enhancement would be considered more work by other developers
  • Sharing related HTML-first patterns and tech stacks that align with the article's philosophy
  • Self-doubt about not understanding React, validating the appeal of simpler approaches
  • The improvement came from better design, not from ditching React; framing is misleading
  • Counterpoint defending SPAs and React as still being viable choices
13.Raspberry Pi 5 – 16GB RAM(adafruit.com)
299 points by akman 1 day ago | 318 comments | permalink
tl;dr: The Raspberry Pi 5 is now available in a 16GB RAM configuration, joining the existing 2GB, 4GB, and 8GB options. It features a 2.4GHz quad-core Arm Cortex-A76 CPU, VideoCore VII GPU, dual 4Kp60 HDMI output, USB 3.0, Gigabit Ethernet with PoE+ support, and a PCIe 2.0 x1 interface, delivering 2–3× the CPU performance of the Pi 4. The new in-house RP1 "southbridge" chip handles I/O, more than doubling USB bandwidth and tripling MIPI camera/display bandwidth.
HN Discussion:
  • RAM price surges explain the high cost and Raspberry Pi is mitigating with new variants
  • Pi has lost its appeal as a cheap hobby computer and is now too expensive compared to alternatives
  • Despite price increases, Pi remains valuable for specialized projects due to its software ecosystem and flexibility
  • ~The 16GB model is a niche product and shouldn't define the Pi's overall pricing narrative
  • Surplus or used hardware offers far better value than current Pi pricing for cluster/compute needs
14.Apache Burr: Build reliable AI agents and applications(burr.apache.org)
243 points by anhldbk 1 day ago | 113 comments | permalink
tl;dr: Apache Burr (Incubating) is a pure-Python framework for building stateful AI applications like chatbots and multi-agent systems, modeling them as actions and state transitions without DSLs or YAML. It includes built-in observability via a UI, state persistence, human-in-the-loop pauses, parallelism/branching, and replay-based testing. It's designed to integrate with existing stacks rather than wrap or lock users into specific tools.
HN Discussion:
  • ~Agent frameworks have limited value since agents are fundamentally simple to build from scratch
  • Landing page looks AI-generated and templated, suggesting poor quality
  • Asking how Burr compares to alternative agent frameworks like Strands or jido
  • Personal endorsement from a user who finds the stateful workflow and observability valuable
  • Criticism of the framework's design patterns (decorators and builder pattern misuse in Python)
15.All 9,300 Japanese train station, animated by the year it opened (1872–2026)(jivx.com)
253 points by momentmaker 1 day ago | 84 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Praises the visualization as cool and accessible
  • Reports technical bugs and errors while using the site
  • ~Suggests companion visualization showing rural line closures and depopulation
  • ~Suspects the site was AI/LLM-built, criticizing UX choices
  • Shares related personal anecdotes or similar projects
16.Claude Fable 5(anthropic.com)
2593 points by Philpax 2 days ago | 2141 comments | permalink
tl;dr: Anthropic launched Claude Fable 5, a "Mythos-class" frontier model claiming state-of-the-art performance in coding, vision, knowledge work, and long-horizon agentic tasks, priced at $10/$50 per million input/output tokens. The model ships with new classifiers that fall back to Opus 4.8 on cybersecurity, bio/chem, and distillation-related queries (triggering in under 5% of sessions), plus a mandatory 30-day data retention policy for safety monitoring. A less-restricted variant, Mythos 5, is available to vetted cyber defenders via Project Glasswing, with a biology trusted-access program coming soon.
HN Discussion:
  • Hands-on testing confirms Fable 5 is a major capability leap on hard coding/agentic tasks
  • Pricing and enterprise economics make Fable 5 hard to justify versus cheaper alternatives
  • Overly aggressive safety classifiers cause false positives that block legitimate professional use
  • ~Restrictions on self-improvement/frontier ML work and concerning agent self-preservation behaviors raise safety questions
  • Temporary inclusion in subscription plans feels like a manipulative bait-and-switch tactic
17.Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use(github.com)
428 points by tonyrice 1 day ago | 300 comments | permalink
tl;dr: Claude Desktop on Windows spawns a ~1.8 GB Hyper-V VM (Vmmem) on every launch once Cowork/agent mode has been used, even for chat-only sessions, consuming over 11% of RAM on a 16 GB system. The bug reporter also found 2,689 stale Cowork session files that never get cleaned up, and the only workaround is disabling VirtualMachinePlatform or killing vmwp/vmcompute after each launch. The request: only spin up VM infrastructure on demand when Cowork is actually invoked.
HN Discussion:
  • Anthropic lacks engineering craft and ships poor quality desktop software
  • Cowork VM should be opt-in rather than forced on all users
  • Users are losing control over their own machines to opaque system processes
  • Workarounds exist like disabling Virtual Machine Platform to skip VM creation
  • ~Broader race between AI companies and OS vendors explains rushed, sloppy integrations
18.macOS Container Machines(github.com)
1247 points by timsneath 2 days ago | 428 comments | permalink
tl;dr: macOS Container Machines run full Linux environments (with init/systemd) from standard OCI images, automatically mapping your macOS username and home directory into the VM so repos and dotfiles are shared between host and guest. You can edit on macOS while building/running inside Linux, spin up multiple machines for different distros (Alpine, Ubuntu, Debian), and run real system services like Postgres via systemctl. Custom images work as long as they include /sbin/init, with a `container machine` CLI (aliased `m`) for create/run/stop/inspect operations.
HN Discussion:
  • Clarifies and expands on the feature's capabilities beyond basic OCI containers
  • Questions how this differs from existing tools like Colima, OrbStack, or Docker Desktop
  • Criticizes Apple for not providing native Darwin containers/jails instead of Linux VMs
  • Questions the design choice of mounting $HOME instead of full isolation
  • ~Sees this as confirmation that macOS/Windows can't compete with Linux for development
19.Mercedes‑Benz starts large‑scale production of electric axial flux motor(media.mercedes-benz.com)
539 points by raffael_de 1 day ago | 346 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Excitement about YASA acquisition and successful commercialization of axial flux technology by Mercedes
  • Article failed to explain what an axial flux motor actually is or why it matters
  • ~Axial flux is promising but radial motors will dominate for years until reliability is proven
  • The real achievement is mass manufacturing capability, not just the motor design itself
  • UK needs better support to capitalize on homegrown tech breakthroughs like YASA
20.OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision(opencv.org)
842 points by ternaus 5 days ago | 147 comments | permalink
tl;dr: OpenCV 5 ships a rewritten graph-based DNN engine that boosts ONNX operator coverage from ~22% to over 80%, adds dynamic shapes, attention/MatMul fusion, and built-in tokenizer + KV-cache support for running LLMs and VLMs (Qwen, Gemma, GPT) directly via the Net API. Benchmarks show it matching or beating ONNX Runtime on CPU for models like YOLOv8, DINOv2, and OWLv2, while the old engine remains available behind the same API for backward compatibility. The release also modernizes the core with FP16/BF16 types, 0D/1D Mat support, a redesigned hardware acceleration layer (Intel IPP, Arm KleidiCV, Qualcomm FastCV, RISC-V), and split 3D/calibration modules; pip release is slated for June 2026.
HN Discussion:
  • OpenCV excels at basic image/video loading regardless of its CV features
  • Confirmed real-world performance improvements in OpenCV 5 validate the release claims
  • Investing in their own ONNX engine is misguided versus wrapping existing runtimes
  • ~OpenCV still has performance and shape-flexibility limitations compared to alternatives
  • Practical questions and adjacent use cases (Pyodide, production deployment, mobile)