Top HN Daily Digest · Thu, Apr 30, 2026

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


0. Claude Code refuses requests or charges extra if your commits mention "OpenClaw" (twitter.com)

1333 points · 718 comments · by elmean

Anthropic's Claude Code tool reportedly refuses to process requests or imposes additional charges if a user's commit messages contain references to "OpenClaw," a third-party open-source project. [src]

Users have reported that mentioning "OpenClaw" in commits or chat prompts causes Claude Code to immediately disconnect and exhaust the user's entire usage quota [0][6]. While some commenters suggest this could be an unintentional bug [5], many view it as a "scam" or a malicious attempt to sabotage tools that might bypass Anthropic's pricing models [1][7]. The incident has intensified existing frustrations regarding Claude's uptime and strict usage limits, leading some to question the company's ethical reputation relative to competitors [2][4][8].

1. Belgium stops decommissioning nuclear power plants (dpa-international.com)

865 points · 1035 comments · by mpweiher

Belgium has halted the decommissioning of its nuclear power plants as the government enters exclusive negotiations with operator ENGIE to nationalize the country's seven-reactor fleet to ensure energy security. [src]

Belgium is reversing its nuclear phase-out policy by extending the life of its remaining reactors and purchasing plants from French-owned Engie to ensure energy security following the Russia-Ukraine conflict [0]. While some argue that shuttering safe, operational plants is a "terrible idea" during a climate crisis [0][2], others express concern that aging Gen II reactors lack the passive safety mechanisms of modern designs and should be decommissioned in favor of Gen IV technology [1][4]. Critics of nuclear power point to the massive construction and decommissioning costs compared to solar and batteries [7][9], though proponents highlight its reliability and the successful safety record of organizations like the US Navy [2][5].

2. Where the goblins came from (openai.com)

1061 points · 655 comments · by ilreb

OpenAI researchers discovered that GPT models developed a "goblin" metaphor tic because reinforcement learning for a "Nerdy" personality over-rewarded creature-related language. This behavior unintentionally spread to other model versions through training feedback loops, leading the team to retire the personality and implement new auditing tools. [src]

The discovery of bizarre system prompts forbidding mentions of "goblins" and "pigeons" has sparked a debate over whether LLM development is a rigorous science or a form of "sorcery" based on unpredictable "hacking" [0][1][2]. While some argue that we shouldn't wait for a first-principles understanding to utilize powerful technology, others find it absurd that trillion-dollar companies rely on "tweaking and measuring" to control emergent behaviors [0][2][4]. This unpredictability, characterized by "style tics" and strange linguistic obsessions, has led to calls for a new field of "AInthropology" to study how these models develop proto-cultures through reinforcement learning [3][7][8].

3. For Linux kernel vulnerabilities, there is no heads-up to distributions (openwall.com)

598 points · 542 comments · by ori_b

The Linux kernel security team has ceased providing advance notice of vulnerabilities to distributions, meaning security fixes are now released publicly without a prior embargo period for coordinated patching. [src]

The current Linux kernel security model is criticized for lacking a formal communication channel between kernel developers and distribution maintainers, often leaving the burden of notification on the vulnerability reporter [0][1][6]. While some argue that releasing a working exploit before distributions can patch is "extremely irresponsible" [0][9], others contend that researchers have no obligation to coordinate disclosure and that immediate transparency is preferable to "reputation management" by corporations [7][8]. Furthermore, the specific disclosure in question was viewed by some as a marketing tactic for an AI security tool rather than a purely security-driven act [3][5].

4. The Zig project's rationale for their anti-AI contribution policy (simonwillison.net)

675 points · 457 comments · by lumpa

The Zig project maintains a strict ban on AI-generated contributions to prioritize long-term human contributor growth over immediate code output, arguing that reviewing LLM-assisted work fails to build the trusted, skilled community necessary for the project's future. [src]

The Zig project's anti-AI policy stems from a surge in "worthless drive-by PRs" and "vibe coding" that often fail to compile or contain hidden hallucinations, placing an unsustainable review burden on maintainers [0][2][4]. While some argue that LLMs allow experienced developers to focus on high-level architecture rather than syntax [9], others contend that the technology primarily empowers "bad programmers" to generate high-volume, low-quality noise that threatens the integrity of open-source projects [2][4]. This tension is exemplified by recent friction over a large performance PR from the Bun team, which critics suggest was rejected more for its inherent complexity and lack of alignment with Zig's language design than for its use of AI [3][7].

5. Can I disable all data collection from my vehicle? (rivian.com)

751 points · 348 comments · by Cider9986

Rivian owners can disable vehicle connectivity to stop data collection, though doing so limits features like navigation and over-the-air updates; Canadian users can use a settings toggle, while others must request a service appointment to disable the vehicle's eSIM. [src]

While Rivian offers a supported privacy feature to disable data collection, users worry that disconnecting internet access creates a "dark pattern" where safety features like lane-keeping assistance are disabled [1][3][4]. There is significant concern regarding the "creepy" data categories car companies claim to collect, such as sexual activity and genetic information, leading some to wonder if these policies are generated by unreviewed LLMs [2][6]. Furthermore, the shift toward over-the-air (OTA) updates as the sole remedy for recalls raises legal and safety questions, as EVs lack the standardized diagnostic requirements mandated for internal combustion vehicles [0]. While some value connected services for emergency assistance during accidents, others argue that modern smartphones have rendered these privacy-invasive vehicle features redundant [5][7].

6. How Mark Klein told the EFF about Room 641A [book excerpt] (thereader.mitpress.mit.edu)

702 points · 251 comments · by the-mitr

Retired AT&T technician Mark Klein provided the Electronic Frontier Foundation with internal documents and schematics proving the NSA used a secret room in a San Francisco facility to conduct mass, untargeted surveillance of internet backbone traffic. [src]

The discussion centers on the moral dilemma of whistleblowing, with one commenter revealing they witnessed the illegal erosion of the "wall" between foreign and domestic surveillance decades ago but remained silent due to NDAs and fear of government retaliation [0][2]. While some users criticize this silence as a lack of fortitude, others argue it is easy to judge from a distance when a person's livelihood and safety are at stake [1][6]. The thread also features a personal account of alleged intelligence community harassment [5] and broader concerns that pervasive surveillance has become a normalized, global phenomenon [3][4].

7. Meta in row after workers who saw smart glasses users having sex lose jobs (bbc.com)

521 points · 417 comments · by gorbachev

Meta terminated a major contract with Kenyan outsourcing firm Sama, leading to over 1,100 redundancies, shortly after workers alleged they were required to review graphic and intimate footage captured by users of Meta’s smart glasses. [src]

Meta terminated its contract with an outsourcing firm after workers blew the whistle on privacy violations, including viewing intimate footage captured by smart glasses [0][6]. While some argue that human classification is a necessary, albeit traumatic, requirement for moderating illegal content like CSAM [3], others contend that if a platform is too large to respect privacy and law, it should be dismantled or federated [4]. The discussion highlights a sharp divide between those who view smart glasses users as "glassholes" to be avoided [1][5] and those who point out that Meta maintains strict internal protocols against unauthorized data access [8].

8. Mozilla's opposition to Chrome's Prompt API (github.com)

655 points · 231 comments · by jaffathecake

Mozilla has formally opposed Chrome's Prompt API, arguing it risks "calcifying" the web around Google’s specific AI models, creates interoperability issues due to model-specific quirks, and introduces non-neutral usage policies that could force developers to block non-Google browsers to avoid legal or functional risks. [src]

Commenters largely support Mozilla’s opposition to the Prompt API, arguing it would create a new vector for device fingerprinting and force competitors to license or emulate Google’s specific models to maintain interoperability [0][6][8]. Critics contend that the proposal serves Google's commercial interests rather than user needs, potentially turning browsers into resource-heavy "super computers" that exclude users with cheaper hardware [0][1][3]. While some debate whether this reflects a generational divide in AI adoption, others emphasize that the API undermines the open web by establishing "first-class" and "second-class" browsers based on their access to proprietary LLMs [0][1][7].

9. Spain's parliament will act against massive IP blockages by LaLiga (democrata.es)

517 points · 226 comments · by akyuu

Spain's Congress has approved an initiative to reform the Digital Services Act to prevent LaLiga's anti-piracy efforts from causing indiscriminate IP blockages that collapse legitimate third-party websites and public services. [src]

Spanish courts previously allowed LaLiga to compel ISPs to block IP addresses associated with illegal streams, but the use of shared Cloudflare IPs resulted in significant collateral damage to legitimate websites [0][2]. While some argue that Cloudflare should be held accountable for hosting illegal content [1], others contend it is unreasonable to expect a third party to proactively distinguish between legal and illegal streams [9]. Critics emphasize that these broad blocks lack a "stopping principle," potentially leading to an untenable situation where the internet's utility is sacrificed to protect corporate assets [8].