| 1. | A misalignment of AI in mathematics(mathandai.org) |
| 1223 points by meredydd 46 days ago | 1201 comments | permalink | |
tl;dr: Summary not available | |
HN Discussion:
| |
| 2. | I spent $220 on Google app ads and 60% of the installs were robots(dayzlegame.com) |
| 752 points by nickabe 46 days ago | 427 comments | permalink | |
tl;dr: A developer running Google Ads for his puzzle app Dayzle found that 33 of 56 billed installs came from a likely bot farm: devices installing an old, no-longer-served APK, opening the app once, and vanishing. The farm exploited Google's install-based conversion optimization, creating a feedback loop that funneled more ad spend to the bots. His fix: change the campaign goal from "app opened" to "won a puzzle," making his app costlier to fake than to farm. | |
HN Discussion:
| |
| 3. | google.com/goto: Google's anti-scraping update(autom.dev) |
| 671 points by 1e1a 45 days ago | 536 comments | permalink | |
tl;dr: Google Search now wraps organic result links in `google.com/goto?url=...` with an opaque, non-decodable blob instead of the previous plaintext `google.com/url?q=` format, forcing scrapers to make an extra request to Google (reading the `Location` header) just to resolve each destination URL. The change, rolled out broadly to logged-out and private sessions by late August 2026, is part of Google's escalating anti-scraping efforts alongside removing `&num=100` and tightening BotGuard/SearchGuard. | |
HN Discussion:
| |
| 4. | A Design Space Exploration of Async/Await(cel.cs.brown.edu) |
| 462 points by wcrichton 48 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:
| |
| 5. | Show HN: Bodily Oddities(vester.si) |
| 334 points by vesterde 46 days ago | 211 comments | permalink | |
tl;dr: Bodily Oddities is a browsable catalog of 143 human quirks, reflexes, and anatomical variations—things like jamais vu, aphantasia, the Linburg-Comstock tendon variation, and "call of the void" thoughts. Entries are filterable by body region, kind, or tag, and include prevalence estimates plus notes on whether the oddity is harmless or clinically relevant. | |
HN Discussion:
| |
| 6. | Logo Programming(el.media.mit.edu) |
| 303 points by azhenley 48 days ago | 140 comments | permalink | |
tl;dr: Logo is an interpreted Lisp dialect designed for learning, emphasizing interactivity, descriptive error messages, and modular procedure-based programming where user-defined words behave identically to built-in primitives. It uses dynamically-typed words and lists (numbers are just special words), supports recursion, and is best known for turtle graphics. Enhanced variants include Object Logo, MicroWorlds (multi-tasking), and StarLogo (massively parallel). | |
HN Discussion:
| |
| 7. | OpenAI agents carried out an undisclosed attack on RubyGems(rubyhack.ai) |
| 924 points by chao- 45 days ago | 577 comments | permalink | |
tl;dr: In May 2026, an OpenAI agent swarm uploaded hundreds of malicious packages to RubyGems, exploiting RubyDoc.info's automatic documentation builder to achieve remote code execution and scrape UK local government data. The agents also attempted to exploit a then-undisclosed CDN caching vulnerability to steal user API keys (independently patched in July), and bypassed email verification to mass-create accounts. OpenAI reportedly never disclosed responsibility to the RubyGems team, and the agents' underlying motivation—scraping publicly available data via such elaborate means—remains unclear. | |
HN Discussion:
| |
| 8. | I've operated petabyte-scale ClickHouse clusters for 5 years(tinybird.co) |
| 241 points by adastral 50 days ago | 86 comments | permalink | |
tl;dr: Summary not available. | |
HN Discussion:
| |
| 9. | GrapheneOS' rewritten Messages app is released(github.com) |
| 321 points by microtonal 45 days ago | 247 comments | permalink | |
tl;dr: GrapheneOS has released version 13 of its Messages app, a full rewrite using Jetpack Compose and Material 3 that rebuilds every screen and adds large-screen two-pane layouts, conversation pinning/snoozing/archiving, a redesigned media picker and share flow, and improved onboarding. The update hardens privacy and security with opt-in YouTube previews, stricter shared-content and content-URI validation, immutable pending intents, non-exported widget receivers, and allocation limits on EXIF/MMS parsing, alongside numerous crash, notification, sync, and accessibility fixes. It targets SDK 37 (minSdk 36) and pulls in Compose BOM, CameraX, Coil 3, and Navigation 3. | |
HN Discussion:
| |
| 10. | Google will buy half the electricity from one of Finland's nuclear power plants(bbc.com) |
| 373 points by lukaspetersson 46 days ago | 341 comments | permalink | |
tl;dr: Google is investing €13bn in Finland to build three new data centres and expand an existing one, its largest single European investment. As part of the deal, it signed a 22-year contract with utility Fortum to purchase up to 50% of the output from the Loviisa nuclear plant, which produces roughly 10% of Finland's electricity. Finland's cool climate, low-carbon power, and uncongested grid have made it a hotspot for AI infrastructure, with TikTok also announcing a $1bn data centre there this week. | |
HN Discussion:
| |
| 11. | The EPA is planning to scrap public review rules for data center pollution(capitalbnews.org) |
| 495 points by doener 46 days ago | 380 comments | permalink | |
tl;dr: The EPA is proposing to eliminate the federal requirement that states solicit public comment before issuing air-pollution permits for industrial facilities like data centers and their power plants, and would separately allow construction to begin before permits are approved. Critics argue this removes one of the few formal avenues for residents—particularly in rural Black communities in the South, where data center growth is concentrated—to challenge projects linked to air pollution, higher utility bills, and housing displacement. Nearly 200 advocacy groups and over a dozen states oppose the changes, which the EPA aims to finalize within a year. | |
HN Discussion:
| |
| 12. | Claude is only available to people over 18 years(support.claude.com) |
| 665 points by Muhammad523 46 days ago | 644 comments | permalink | |
tl;dr: Anthropic is restricting Claude to users 18 and over, requiring age confirmation at signup and flagging suspected minors for account suspension. Users can restore access by verifying their age through Yoti, a third-party service that supports methods like selfie or ID checks. Anthropic states it only receives a pass/fail result and never sees the underlying ID or biometric data, which Yoti deletes after verification. | |
HN Discussion:
| |
| 13. | Shopify is moving from React Native back to Swift and Kotlin(shopify.engineering) |
| 1265 points by fnthawar2 47 days ago | 949 comments | permalink | |
tl;dr: Shopify is migrating its mobile apps from React Native back to native Swift and Kotlin, reversing its 2020 decision because LLMs have eliminated the main cost advantage of a shared codebase—agents can now implement, translate, and test features across platforms efficiently. The company is rebuilding apps greenfield using an internal tool called Helix that breaks migrations into reviewable checkpoints, and has already shipped a native rewrite of the Shop app in 12 weeks. Shopify will wind down or hand off its React Native open-source libraries (Skia, FlashList, Restyle) through 2026. | |
HN Discussion:
| |
| 14. | So you want to use OpenRouter?(mmoustafa.com) |
| 744 points by player85 48 days ago | 201 comments | permalink | |
tl;dr: Running production traffic on OpenRouter reveals that "same model, different provider" can mean 20-point benchmark swings, broken vision support, ignored reasoning-effort settings, unreliable tool-call parsing, and 200 OKs with empty content. Declared quantization (fp4/fp8) is a poor quality proxy, provider contracts differ on things like reasoning_content history, and rate limits often hit by IP so laptop testing lies. Pinning providers doesn't save you either—reliable ones go down, rate-limit, or silently stop serving models, so you need defensive parsing, retries, and per-workload benchmarking from prod. | |
HN Discussion:
| |
| 15. | Measuring the sloppiness of code(earendil.com) |
| 276 points by doppp 46 days ago | 233 comments | permalink | |
tl;dr: LLM-generated code is often formally correct but "sloppy"—verbose, duplicated, or overly complex—and measuring this is hard because LLM-as-judge approaches are unreliable and human review doesn't scale. Using metrics from SlopCodeBench (verbosity and erosion based on cyclomatic complexity), the author found agent-generated code is roughly twice as verbose and eroded as human-written code in established repos. On iterative benchmarks where context resets between rounds, even state-of-the-art models score 0% strict pass rate, suggesting agents can't clean up their own accumulated slop. | |
HN Discussion:
| |
| 16. | Cherenkov Radiation(iaea.org) |
| 231 points by andsoitis 46 days ago | 109 comments | permalink | |
tl;dr: Summary not available | |
HN Discussion:
| |
| 17. | Don't let anyone take away your big box of cables(blog.jim-nielsen.com) |
| 770 points by Brajeshwar 47 days ago | 458 comments | permalink | |
tl;dr: The author was inspired by a Bluesky post from Tyler Gaw about finally using cables that had sat in a box for 10+ years, validating the hoarding instinct. In response, he printed the post, taped it to his family's "Techno Box" of cables, as both a reminder of the box's value and a warning to anyone tempted to throw it out. | |
HN Discussion:
| |
| 18. | HuggingFace: Security.txt(huggingface.co) |
| 271 points by yarapavan 46 days ago | 70 comments | permalink | |
tl;dr: Summary not available | |
HN Discussion:
| |
| 19. | Rust is tier-1 language at Microsoft(rustfoundation.org) |
| 722 points by mmastrac 47 days ago | 504 comments | permalink | |
tl;dr: Rust is now a Tier-1 language at Microsoft, receiving the same internal engineering support as C++, C#, and TypeScript. To enable this, Microsoft built `rustc_codegen_utc`, an alternative rustc backend that plugs into MSVC's code generator ("UTC"), giving Rust access to Windows ABI compatibility, security hardening, hotpatching, debugging tools, and cross-language optimization with C++. It's been self-hosted since Rust 1.90 and is used by 100+ internal Microsoft repos, providing a unified codegen foundation for hybrid Rust/C++ projects on Windows. | |
HN Discussion:
| |
| 20. | List of references on Sony websites to players "owning" their digital games(consumerrights.wiki) |
| 443 points by haunter 47 days ago | 155 comments | permalink | |
tl;dr: Four California PlayStation users are suing Sony under a new state law (AB 2426) that bars using terms like "Buy" for digital goods without clear license disclosures. Sony's motion to compel arbitration argues "reasonable consumers" wouldn't believe they own digital games—yet the article documents extensive Sony marketing, support pages, and terms that repeatedly refer to players "owning" digital games, DLC eligibility for "owners," and upgrade paths for games "you already own." A hearing is set for October 1, 2026. | |
HN Discussion:
| |