Sep 11Saturday, September 12, 2026 · all days
1.A misalignment of AI in mathematics(mathandai.org)
1096 points by meredydd 22 hours ago | 1043 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Optimistic that mathematical community will adapt and derive value from AI-generated proofs like it did with Mochizuki
  • AI companies' narrative is damaging students, researchers, and knowledge transfer culture
  • AI threatens motivation and recognition (kleos) that drives intellectual work
  • Concerns mirror historical panic about new tech (photography, chess computers) which ultimately enriched the field
  • ~Real issue is math education/PR emphasizing problem-solving over conceptual insight, not AI itself
2.I spent $220 on Google app ads and 60% of the installs were robots(dayzlegame.com)
662 points by nickabe 21 hours ago | 362 comments | permalink
tl;dr: A developer running Google Ads for his puzzle app Dayzle found that 33 of 56 billed installs came from an apparent bot farm that watched short ads then sideloaded a cached (outdated) APK while spoofing Play Store as the installer, creating a feedback loop where Google's algorithm sent more ads to the farm. He's switched the campaign's conversion goal from "app opened" to "puzzle won" to raise the cost of faking engagement, and is awaiting Google's invalid-traffic refund decision.
HN Discussion:
  • Shares similar horror stories confirming ad platforms are rife with fraud and bots
  • Offers practical mitigation advice like IP exclusions to block bot networks
  • Suspects Google knowingly tolerates ad fraud as part of its business model
  • Asks what incentive bot operators have and how they actually get paid
  • Wonders how small businesses can effectively reach audiences given broken ad ecosystem
3.google.com/goto: Google's anti-scraping update(autom.dev)
528 points by 1e1a 12 hours ago | 424 comments | permalink
tl;dr: Google Search now wraps organic result links in `google.com/goto?url=...` using an opaque, Google-specific encoding rather than the readable `google.com/url?q=` format, forcing scrapers to make an additional request to Google (reading the Location header) just to resolve each destination URL. The change, rolling out broadly to logged-out and private sessions as of late August 2026, raises the cost of bulk SERP harvesting and follows other anti-scraping moves like killing `&num=100` and tightening SearchGuard.
HN Discussion:
  • Google has been declining for years; users are switching to alternatives like Yandex, DuckDuckGo, or Mojeek
  • URL redirection is user-hostile, obscures destinations, and continues Google's pattern of obfuscation
  • This anti-scraping move mainly hurts small players while well-resourced scrapers can bypass it
  • The change is harmless to regular users and only affects bots; outrage is unwarranted
  • Speculative/forward-looking ideas like running local indexed search or abandoning SEO in response
4.A Design Space Exploration of Async/Await(cel.cs.brown.edu)
371 points by wcrichton 3 days ago | 99 comments | permalink
tl;dr: Async/await semantics vary wildly across languages: a simple fire-and-forget program produces four different outputs across seven runtimes (Asyncio, C#, JavaScript, Tokio, Smol, Trio, Swift), with no two runtimes agreeing on three variations of the program. The authors' paper identifies nine design dimensions (e.g., Eagerness, Extent, Destruction, Cancellation behavior) that explain the divergence, and formalizes them in a core calculus that traces exactly which design choices lead to which observable behaviors.
HN Discussion:
  • Appreciation for the semantics-first comparative analysis approach to understanding languages
  • Surprise and validation that async has many more design dimensions than commonly realized
  • Practical value for language designers making these decisions themselves
  • ~The framework/quiz is too rigid and ignores that some runtimes offer configurable options
  • ~Article is incomplete because it omits stackful coroutines like Lua's
5.Show HN: Bodily Oddities(vester.si)
305 points by vesterde 1 day ago | 189 comments | permalink
tl;dr: Bodily Oddities is a browsable catalog of 143 human bodily quirks, reflexes, and perceptual phenomena—things like jamais vu, aphantasia, the Linburg-Comstock tendon variation, and "call of the void" intrusive thoughts. Each entry is filterable by body region, kind, or tag, and includes prevalence estimates plus a note on whether it's harmless. There's also a dedicated section for phenomena that alarm people but are medically benign.
HN Discussion:
  • Praise for the website concept, design, and name
  • Users sharing their own personal bodily oddities and experiences inspired by the catalog
  • Suggestions for additional phenomena to add to the catalog
  • Appreciation for finally seeing personal experiences named and described
  • Criticism of AI-generated image artifacts detracting from the site's quality
6.Logo Programming(el.media.mit.edu)
298 points by azhenley 3 days ago | 120 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:
  • Nostalgic gratitude for learning programming through Logo as children
  • Logo is pedagogically effective for teaching programming concepts like recursion and math
  • Recommending foundational Logo-related books like Turtle Geometry and Mindstorms
  • ~Lamenting that Logo's promised educational revolution never materialized
  • Logo's paradigm extends to agent-based simulation tools like NetLogo
7.OpenAI agents carried out an undisclosed attack on RubyGems(rubyhack.ai)
856 points by chao- 16 hours ago | 499 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:
  • OpenAI's failure to disclose is inexcusable and suggests either incompetence or deliberate concealment
  • OpenAI executives should face criminal prosecution and legal consequences for these attacks
  • Anthropomorphizing LLM agents as 'hackers' is misguided; they're just tools without intent
  • ~OpenAI's negligence may be strategic to build a regulatory moat against competition
  • Open source maintainers shouldn't have to defend against well-funded AI lab attacks; OpenAI should compensate victims
8.I've operated petabyte-scale ClickHouse clusters for 5 years(tinybird.co)
234 points by adastral 4 days ago | 85 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • DBA-like roles remain valuable for managing complex database clusters and query patterns
  • Ingestion challenges with ClickHouse are widely relatable and confirmed by experience
  • Skeptical of ClickHouse's development practices due to rapid AI-generated commits and issues
  • Questioning whether petabyte-scale analytics workloads are actually necessary in practice
  • ~Suggests architectural alternatives like workload separation and DuckDB for complexity management
9.GrapheneOS' rewritten Messages app is released(github.com)
291 points by microtonal 21 hours ago | 216 comments | permalink
tl;dr: GrapheneOS has released version 13 of its Messages app, a full rewrite using Jetpack Compose and Material 3 with a two-pane layout for large screens. The update overhauls nearly every feature—conversation list, media picker, sharing, settings—and adds pinning, snoozing, archiving, attachment captions, and rebuilt photo/vCard viewers. It also brings significant privacy and security hardening (opt-in link previews, stricter shared-content validation, immutable pending intents, parser allocation limits) alongside numerous crash and notification bug fixes.
HN Discussion:
  • Wishes for GrapheneOS compatibility with Fairphone hardware to expand its reach
  • Criticizes GrapheneOS for prioritizing Messages over the poorly-designed call app
  • ~Questions missing features like RCS support and encrypted SMS
  • ~SMS is largely obsolete in favor of IM apps, making this update low-impact
  • Requests screenshots since the release notes/repo lack visual documentation
10.Google will buy half the electricity from one of Finland's nuclear power plants(bbc.com)
369 points by lukaspetersson 1 day ago | 334 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:
  • Finland's low-emission electricity makes it a sensible location for data centres
  • The deal is a PR stunt that doesn't actually add new power infrastructure
  • Google contributes little to Finland economically via taxes or employment
  • ~Skepticism about whether Google is genuinely adding clean energy capacity (additionality)
  • Questions the long-term need for so many data centres given efficiency improvements
11.The EPA is planning to scrap public review rules for data center pollution(capitalbnews.org)
480 points by doener 22 hours ago | 355 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:
  • EPA has been gutted and is now actively enabling environmental degradation under this administration
  • Communities that opposed data centers are vindicated by these deregulation moves
  • Delegating permit review to local governments is reasonable since local voice matters most
  • Public input is counterproductive because the public is emotional and misinformed about data centers
  • ~These changes are temporary and tied to the current administration, limiting real long-term impact
12.Claude is only available to people over 18 years(support.claude.com)
660 points by Muhammad523 1 day ago | 634 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:
  • Age verification is a pretext for Anthropic to collect user identity data for analytics
  • Third-party ID verification services like Yoti have poor track records with data breaches and privacy violations
  • Restricting AI from minors is misguided when it's a useful tool for learning and creativity
  • Age verification should be handled at the OS level by parents, not via invasive ID checks
  • It's ironic that useful AI gets restricted before genuinely harmful social media does
13.Shopify is moving from React Native back to Swift and Kotlin(shopify.engineering)
1246 points by fnthawar2 2 days ago | 931 comments | permalink
tl;dr: Shopify is migrating its mobile apps from React Native back to native Swift/Kotlin, reversing its 2020 decision because LLMs have largely eliminated the cost of building features twice across platforms. The company is taking a greenfield rewrite approach using an in-house agentic system called Helix, which builds apps checkpoint-by-checkpoint with tests and reviews; the Shop app was rebuilt in 12 weeks and the flagship Shopify app is next. Shopify will wind down or hand off its React Native open-source libraries (Skia, FlashList, Restyle) through 2026.
HN Discussion:
  • Shopify's 3000 engineers indicates bloat, undermining their credibility on engineering decisions
  • Confirms personal experience that LLMs make native rewrites from React Native fast and viable
  • ~Agrees moving off React Native is right, but disputes that LLMs were the key enabler
  • Validates long-held native-first stance against shared codebases pushed by management
  • Shopify is wrongly assuming AI eliminates complexity costs; this decision won't age well
14.So you want to use OpenRouter?(mmoustafa.com)
733 points by player85 3 days ago | 194 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:
  • Confirms unreliability of OpenRouter and difficulty of swapping providers from personal experience
  • Reports specific broken behaviors like caching failures, empty responses, and scam providers
  • ~OpenRouter co-founder acknowledges issues and explains philosophical tradeoffs
  • Asks about alternatives or related tools like LLM Gateway given these problems
  • Plans to incorporate provider-level benchmarking based on article's advice
15.Measuring the sloppiness of code(earendil.com)
272 points by doppp 1 day ago | 231 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:
  • ~Global architectural issues matter more than local sloppiness metrics
  • Quality metrics and dedicated tooling are needed to enforce good code structure for agents
  • AI labs will eventually address maintainability once correctness gains plateau
  • Human devs and mental models remain essential; coding isn't solved by AI
  • ~Questions whether code complexity even matters if LLMs can handle it themselves
16.Cherenkov Radiation(iaea.org)
227 points by andsoitis 1 day ago | 101 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Title is misleading; nothing actually travels faster than light in a vacuum
  • ~Article underplays major applications like particle/astrophysics detection
  • ~Clarifying the physics of light propagation and speed limits in media
  • Sharing personal anecdotes or fun facts related to Cherenkov radiation
  • The article's explanation of faster-than-light phenomenon is confusing/unclear
17.Don't let anyone take away your big box of cables(blog.jim-nielsen.com)
765 points by Brajeshwar 2 days ago | 457 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:
  • Organizing and grouping cables into bags helps manage the hoard effectively
  • Personal anecdotes confirm the value of keeping old cables for unexpected future uses
  • Keeping old gear feels virtuous because it helps others and reduces landfill waste
  • Decluttering advice fails for domains requiring diverse tools and supplies on hand
  • Hoarding old cables is unnecessary since replacements are cheap and easily bought
18.HuggingFace: Security.txt(huggingface.co)
266 points by yarapavan 1 day ago | 69 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Security.txt will be ignored by AI agents just like robots.txt and llms.txt
  • Security.txt has practical value for filtering out low-quality disclosure emails
  • Humorous speculation about AI models escaping or revolting against their sandbox
  • Criticism of HuggingFace as a company being immature
  • Providing background context on what security.txt actually is
19.Rust is tier-1 language at Microsoft(rustfoundation.org)
722 points by mmastrac 2 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:
  • Rust's maturity is now validated as a serious competitor to established languages like C++ and C#
  • The key technical achievement is replacing LLVM with MSVC's backend for better Windows integration
  • Strategic move that addresses Microsoft's memory safety CVE problems across product portfolio
  • ~Questions the tier-1 claim given lack of Visual Studio support and asks about C++ interop story
  • Surprise that runtime performance matches LLVM despite using a different backend
20.List of references on Sony websites to players "owning" their digital games(consumerrights.wiki)
438 points by haunter 2 days ago | 154 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:
  • Binding arbitration clauses should be illegal as they strip consumer rights
  • Sony's ownership defense is contradictory and their own analogy exposes flaws in their argument
  • Copyright reform is needed to establish genuine digital ownership rights
  • Society has been gradually conditioned to accept erosion of ownership norms by corporations
  • ~The lawsuit will accomplish little as Sony will just tweak marketing language to comply