Top HN Daily Digest · Fri, May 15, 2026

A daily Hacker News digest with story summaries, thread context, and direct links back to the original discussion.


0. I believe there are entire companies right now under AI psychosis (twitter.com)

2077 points · 1232 comments · by reasonableklout

Mitchell Hashimoto suggests that some companies are experiencing "AI psychosis" by prioritizing artificial intelligence integration over fundamental product quality and user needs. [src]

The discussion centers on "AI psychosis," defined as the outsourcing of critical thinking and decision-making to pattern-matching models that often produce generic or flawed results [1]. While some users report successfully using AI to ship higher-quality features and address tech debt within standardized environments [8], others warn of a looming "complexity crisis" where AI-generated systems become too unstable for humans to understand or repair [0][4]. Notable anecdotes include a non-technical individual winning hospital contracts through "vibecoding" only to face immediate deployment and data-state failures [2], leading to predictions that "AI rescue consulting" will become a necessary high-value industry [0][7].

1. Project Gutenberg – keeps getting better (gutenberg.org)

1207 points · 275 comments · by JSeiko

Project Gutenberg offers a library of over 75,000 free, volunteer-proofread eBooks, primarily focusing on classic literature with expired U.S. copyrights available in Kindle, epub, and online formats. [src]

Project Gutenberg is undergoing significant site improvements, though developers admit they are currently struggling with performance issues caused by massive amounts of bot traffic [0][3][5]. Users expressed frustration that major eBook vendors do not offer native integration for the library, forcing readers to rely on manual transfers or third-party tools like Calibre [1][8]. While some contributors appreciate the site's long history and transition to ePub formats, others still prefer the high-fidelity scans found on Archive.org or criticize the lack of professional formatting in plaintext-derived files [2][6][9]. Additionally, users in certain regions like Italy reported being unable to access the site due to judicial seizures [7].

2. Bill to block publishers from killing online games advances in California (arstechnica.com)

593 points · 405 comments · by Lihh27

California’s Protect Our Games Act, which recently cleared a key committee, would require publishers to provide refunds or offline patches to keep digital games playable after their servers are shut down. [src]

Proponents argue that requiring 60-day notices or the release of server binaries would prevent the loss of purchased content and restore the historical standard of community-hosted servers [0][4]. However, industry veterans highlight that open-sourcing modern server code is a massive legal and engineering undertaking due to complex microservice architectures, third-party licensed libraries, and potential security risks to a company's other active titles [1][9]. Critics warn these requirements could create significant financial liabilities, potentially bankrupting small studios or pushing the industry toward more aggressive monetization models like subscriptions and ads [3][8][9].

3. Mullvad exit IPs are surprisingly identifying (tmctmt.com)

599 points · 376 comments · by RGBCube

Mullvad VPN’s practice of deterministically assigning exit IPs based on a user's WireGuard key creates a fingerprinting vector that can correlate different sessions to the same user. By analyzing IP ranges across multiple servers, researchers found they could narrow a user's identity to a small percentage of the total userbase. [src]

Mullvad's co-CEO acknowledged that certain exit IP behaviors allow for highly accurate user identification, noting that while some aspects were intended for user experience, a patch is already being tested for unintended flaws [0][1]. The discovery sparked a debate over the utility of VPNs, with some labeling them "snake oil" due to public exit IPs while others argued they are essential for shifting trust away from ISPs [2][4]. Additionally, the thread criticized the researcher for not practicing responsible disclosure, though others pointed out Mullvad’s lack of a formal bug bounty program [1][3][6].

4. U.S. DOJ demands Apple and Google unmask over 100k users of car-tinkering app (macdailynews.com)

473 points · 351 comments · by tencentshill

The U.S. Department of Justice has subpoenaed Apple, Google, Amazon, and Walmart to identify over 100,000 users of EZ Lynk’s Auto Agent app, alleging the software is used to bypass vehicle emissions controls in violation of the Clean Air Act. [src]

The DOJ's demand for user data is widely criticized as a "gross privacy intrusion" and an overreach, with commenters arguing that the government should target specific violators rather than every user of a tool with legal applications [0][1][7]. While there is strong consensus that "rolling coal" is a harmful nuisance that warrants enforcement, many believe traditional policing or reporting systems are more appropriate than mass digital surveillance [1][2][4]. Some suggest that users should seek anonymous alternatives like F-Droid to avoid such data collection, while others debate whether the environmental impact justifies stricter regulations on diesel engines altogether [3][6].

5. Amazon workers under pressure to up their AI usage are making up tasks (fastcompany.com)

395 points · 428 comments · by hackernj

Amazon employees are reportedly creating unproductive AI agents and extraneous tasks to inflate their "AI token" usage in response to corporate pressure to meet high internal activity targets. [src]

Hacker News commenters describe a "bonkers" corporate environment where Big Tech employees are incentivized to maximize AI token usage, often leading to performative waste and "magical thinking" [0][8]. Anecdotes include workers receiving accolades for creating agents that intentionally burn tokens [2] and using expensive LLMs to perform tasks that previously required a single command [1]. While some argue this shift lowers the barrier to entry for complex work [4] or overcomes initial engineer resistance [9], others compare the forced quotas to Soviet-era inefficiencies that ignore environmental costs and actual productivity [3][8].

6. Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust" (github.com)

481 points · 341 comments · by ndiddy

A GitHub issue reports that Bun's Rust rewrite contains widespread undefined behavior and fails basic Miri checks due to improper memory management and lifetime erasure. Developers attributed the flaws to a 1:1 translation from Zig and AI-generated code, leading to multiple pull requests to fix the unsoundness. [src]

The Bun rewrite into Rust has sparked criticism regarding its heavy reliance on AI-generated code and "unaudited" unsafe blocks, which critics argue results in a codebase less trustworthy than the original Zig version [1][3][7]. While some view the move as a marketing stunt that exploits the "memory-safe" reputation of Rust despite persistent undefined behavior [0][4][5][9], others defend it as a necessary first step toward long-term safety, especially given the project's friction with the Zig community [6][8]. The core technical dispute centers on whether a "vibe-coded" port that fails basic safety checks provides any of the actual benefits typically associated with the Rust language [1][3].

7. A 0-click exploit chain for the Pixel 10 (projectzero.google)

445 points · 237 comments · by happyhardcore

Google Project Zero researchers developed a two-stage, zero-click exploit chain for the Pixel 10 by leveraging a patched Dolby vulnerability and a new, "exceptionally simple" memory mapping flaw in the Tensor G5's VPU driver that granted full kernel read-write access. [src]

The discovery of a 0-click exploit chain has sparked debate over the security risks introduced by AI-powered messaging features, which increase the attack surface by decoding media before a user even opens a message [0][4]. While some users argue for extreme legal consequences for developers of "catastrophic code," others point out that modern LLMs are already capable of identifying such vulnerabilities through first-principles analysis [1][5][9]. There is also a notable contrast in vendor responsiveness; while Google patched this driver bug within 90 days, anecdotal reports suggest Apple can take up to six months to resolve similar issues [2][6].

8. Explore Wikipedia Like a Windows XP Desktop (explorer.samismith.com)

533 points · 121 comments · by smusamashah

The Wikipedia File Explorer is an interactive web project that allows users to browse Wikipedia categories and Wikimedia Commons media through a functional interface modeled after the Windows XP desktop. [src]

Users praised the project for its aesthetic appeal and its ability to map Wikipedia's vast data to a familiar, object-oriented mental model [0][2]. While some argue that knowledge is too subjective and non-linear for rigid hierarchies [1], others suggest that "symlinks" or multi-tagging systems could bridge the gap between structured folders and fluid data [4][7]. Despite some minor confusion over Wikipedia's redirect logic [3][5][8] and the "Temu-like" visual style [9], the interface was lauded for its speed and for revealing the depth of Wikipedia's existing classification systems [2][6].

9. We are retiring our bug bounty program (turso.tech)

359 points · 285 comments · by tjek

Turso is retiring its $1,000 bug bounty program after being overwhelmed by a surge of low-quality, AI-generated submissions that wasted maintainers' time with nonsensical or fraudulent claims of data corruption. [src]

The decision to retire the bug bounty program highlights how AI-generated "low-effort bullshit" is overwhelming maintainers with an unmanageable volume of reports [3][6]. Commenters compare this phenomenon to the "tactical tornado"—a prolific but destructive developer who prioritizes speed over code quality and long-term maintainability [1][9]. While some suggest technical or social fixes like enforcing smaller PRs or charging submission fees [2][4], others argue that the "Pandora’s box" of AI has fundamentally broken the incentive structures of open-source collaboration [5][8].

10. The sigmoids won't save you (astralcodexten.com)

303 points · 282 comments · by Tomte

Scott Alexander argues that while all exponential trends eventually become sigmoids, this fact does not predict an imminent slowdown in AI progress; instead, he suggests using Lindy’s Law as a default, which implies that current dramatic improvements are likely to continue for several more years. [src]

The debate centers on whether AI progress follows a "sigmoid" curve toward diminishing returns or a "Lindy" trend that suggests continued exponential growth [0][1]. While some argue that current models lack the reasoning and internal world models necessary for AGI [9], others contend that even a remote possibility of superintelligence necessitates taking fast-approaching timelines seriously [5]. Critics point out that these mathematical models are often used as "excuses" for personal biases [4], noting that specific predictions of AGI by 2027 are frequently hedged or adjusted as deadlines approach [0][6].

11. ABC News has taken all FiveThirtyEight articles offline (twitter.com)

385 points · 167 comments · by cmsparks

ABC News has removed all FiveThirtyEight articles from the internet, redirecting the site's former URLs to the ABC News politics section. [src]

The removal of FiveThirtyEight’s archives is widely viewed as a "petty" move by ABC/Disney, especially following Nate Silver’s claim that the network refused to sell him the IP because he criticized their management [0][1][2]. While some users argue that Silver bears responsibility for "selling out" a once-reliable brand [3], others contend that ABC's decision to "fritter away" a recognizable asset is a baffling failure of corporate stewardship [8]. There is also debate regarding the brand's legacy, with some citing a "credibility hit" from the 2016 election [6], while defenders note that Silver’s model was actually more accurate than most competitors at the time [7].

12. SQL patterns I use to catch transaction fraud (analytics.fixelsmith.com)

319 points · 130 comments · by redbell

This guide outlines six essential SQL patterns for detecting transaction fraud, including monitoring velocity, identifying "impossible travel" between locations, and spotting suspicious amount anomalies. It emphasizes using window functions to create composable signals that help analysts quickly identify high-risk activity like card testing and merchant skimming. [src]

The discussion is dominated by skepticism regarding the article's authenticity, with users identifying the author as a likely AI-generated persona and the content as speculative or "generated from whole cloth" [1][5]. Commenters argue that the proposed SQL patterns, such as flagging round-number transactions, are deeply flawed because round prices are common in many regions, at gas stations, or through "round up to donate" features [0][2][6]. Furthermore, critics suggest that manual SQL rules are inferior to machine learning models that can discover complex fraud patterns directly from data [8].

13. Access to frontier AI will soon be limited by economic and security constraints (writing.antonleicht.me)

209 points · 214 comments · by thoughtpeddler

Frontier AI access is increasingly restricted by security concerns, high computational costs, and U.S. government interests, creating a "geopolitical rift" between nations with early access to top-tier models and those limited to older or restricted versions. [src]

Commenters largely argue that the "technological genie is out of the bottle," as open-weight models from China and Meta are rapidly closing the gap with US frontier labs [0][1]. While some maintain that the highest-tier models still hold a significant lead in complex reasoning and specialized benchmarks like Arc-AGI [2], others contend that "good enough" models at a fraction of the cost will satisfy most users and undercut economic moats [1][9]. However, significant concerns remain regarding the physical bottlenecks of hardware, specifically the high cost of GPUs and RAM required to run frontier-level capabilities locally or at scale [4][5][7].

14. Bitwarden scrubs 'Always free' and 'Inclusion' values from its site (fastcompany.com)

265 points · 140 comments · by gpi

Bitwarden has removed "Always free" and "Inclusion" branding from its website following a leadership shakeup that saw its CEO and CFO replaced by executives with experience in mergers and acquisitions. [src]

The removal of "Always free" and "Inclusion" values from Bitwarden’s site, combined with a quiet change in leadership, has led users to speculate that the company is being prepped for a sale or acquisition [2]. While Bitwarden remains open-source, commenters argue that even OSS projects can experience "rugpulls" where hosted tiers are restricted, leaving non-technical users who cannot self-host in a difficult position [0][1][6]. While some suggest switching to alternatives like Vaultwarden or KeePass, others warn that a new owner could potentially block third-party client compatibility or restrict the software's future direction [4][5][7].

15. How Claude Code works in large codebases (claude.com)

241 points · 158 comments · by shenli3514

Claude Code optimizes large-scale development by using agentic search on live codebases rather than static indexes, utilizing a "harness" of CLAUDE.md files, hooks, and plugins to provide context and specialized skills while maintaining symbol-level navigation through Language Server Protocol (LSP) integrations. [src]

The discussion centers on the efficacy of "agentic search" in Claude Code, with some users questioning why it avoids traditional indexing/LSPs that human engineers rely on for speed [6]. While some argue that AI has already automated the majority of coding tasks in startups [8], others remain skeptical of bold industry claims regarding AI productivity and accountability [0][5]. A significant debate also emerged regarding security: while some view AI-driven database deletion as a failure of organizational permissions [1][9], others note that high-privilege access is common in early-stage startup environments [3].

16. The Zulip Foundation (blog.zulip.com)

309 points · 80 comments · by boramalper

Zulip founder Tim Abbott is stepping down to join Anthropic and donating the company to the newly formed, nonprofit Zulip Foundation to ensure the open-source chat platform's long-term independence, stability, and commitment to its core values. [src]

The transition of Zulip’s leadership to a non-profit foundation as the team joins Anthropic has sparked debate over the "brain drain" of open-source talent into AI labs [0][1]. While some critics view the move as a cynical departure for higher compensation, others defend the developers' right to be paid and argue that the move is driven by a genuine desire to address AI's societal impact [2][4][8]. Amidst the controversy, users praised Zulip’s unique threading model as superior to Slack or Discord, though some questioned the timing of the announcement [5][6][7].

17. Details of the Daring Airdrop at Tristan Da Cunha (tristandc.com)

265 points · 102 comments · by kspacewalk2

The UK military successfully executed a daring airdrop of medical supplies and personnel to Tristan da Cunha on May 9, 2026, to combat a hantavirus outbreak. Paratroopers and medics arrived via an RAF A400M to support the remote island's overstretched hospital following a suspected case from a cruise ship. [src]

The discussion highlights a divide between those who view the high-stakes medical airdrop as a source of national pride and a valid use of military resources for life-saving purposes [0][7][9], and critics who argue the expense would be better spent on domestic infrastructure like the NHS [1][2]. Some users question the geopolitical necessity of maintaining such remote, subsidized colonies [3][6], while others point out that the island was originally uninhabited and serves a strategic role in maritime control [5][8]. There is also curiosity regarding the island's economic self-sufficiency, which primarily relies on lobster exports and government subsidies [4][6].

18. Steve Jobs in Exile – New book on his years at NeXT Computer (spectrum.ieee.org)

200 points · 159 comments · by rbanffy

Geoffrey Cain’s new book, *Steve Jobs in Exile*, explores how Jobs’s 12 years leading NeXT Computer transformed him from an immature founder into a disciplined leader, creating the software foundation for Apple’s modern operating systems and future success. [src]

The acquisition of NeXT is widely viewed as the catalyst for Apple’s survival, effectively replacing the failing "classic" Mac OS with NeXT’s superior architecture and design [0][4][8]. While some debate the exact timeline of Apple's near-collapse, there is consensus that Jobs' return brought a necessary strategic purge of bloated product lines and ineffective leadership [1][3]. Commentators highlight that NeXT's legacy persists through modern macOS internals and the work of key engineers who pioneered technologies like Objective-C and Interface Builder [7][8]. Despite Jobs' reputation for brilliance and "sui generis" taste, some remain critical of his management style and Apple's occasional disregard for ergonomic user feedback [3][5][6].

19. Radicle: Sovereign {code forge} built on Git (radicle.dev)

266 points · 90 comments · by KolmogorovComp

Radicle is an open-source, peer-to-peer code collaboration stack built on Git that enables decentralized, censorship-resistant repository hosting without reliance on centralized third parties. [src]

Radicle is praised as a sovereign, decentralized alternative to GitHub that is particularly well-suited for agentic workflows and cryptographic identity [0][9]. However, critics argue the documentation fails to clearly define the project's value proposition or distinguish its features from standard Git [2]. While the team is currently redesigning the website and considers future support for other version control systems, users currently desire easier local-only deployments and more information regarding CI/PR capabilities [4][5][6][8].