0. Ghostty is leaving GitHub (mitchellh.com)
3509 points · 1049 comments · by WadeGrimridge
Mitchell Hashimoto is moving the Ghostty project away from GitHub, citing frequent service outages and infrastructure reliability issues that have hindered development and pull request reviews. [src]
The departure of Ghostty from GitHub sparked an emotional discussion about the platform's decline, with the project's creator expressing deep sadness over leaving a service that was once central to his identity [0]. While some users attribute GitHub's recent instability and "flimsy" quality to Microsoft's corporate culture or a pivot toward AI [4][5][9], others argue that the issues stem from the immense technical challenges of scaling during a fundamental shift in how software is built [1]. Despite the frustration, there is a divide between those who believe GitHub is a "sinking ship" maintained only by inertia [4][6] and insiders who contend that the platform can only be saved by passionate people working to improve it from within [1][8].
1. Zed 1.0 (zed.dev)
2138 points · 687 comments · by salkahfi
Zed has officially launched version 1.0, transitioning its high-performance, Rust-based code editor out of beta with new AI-native features, cross-platform support for macOS, Windows, and Linux, and the introduction of "Zed for Business" for engineering teams. [src]
The release of Zed 1.0 has sparked debate over its balance of high-performance native speed versus user experience hurdles. While some users praise it as a modern, "top tier" alternative to bloated editors like VS Code [2][7], others are frustrated by a lack of intuitive UI for common tasks, such as the "abysmal" search interface and the difficulty of silencing aggressive Language Server Protocol (LSP) warnings in legacy projects [0][5][6]. Significant controversy also exists regarding the License Agreement; critics worry about broad data processing rights, though others argue the legalese is standard and strictly limited to support and telemetry [1][8].
2. Your phone is about to stop being yours (keepandroidopen.org)
1689 points · 886 comments · by doener
Starting in September 2026, Google will require all Android app developers to register centrally and provide government identification, a move critics argue will effectively block independent apps and alternative stores like F-Droid by imposing high-friction verification processes on all devices worldwide. [src]
Google's move to restrict sideloading on Android is viewed by many as a betrayal of the platform's original promise of openness, leading some long-time users to consider switching to iOS despite its own "walled garden" reputation [0][1][8]. While critics argue that the new nine-step process and 24-hour "cooling-off" period effectively revoke user ownership, others contend the outcry is dramatic since the restrictions can still be bypassed via ADB or developer settings [3][4][7]. The debate centers on whether Android's remaining flexibility still justifies its use over Apple’s ecosystem, which some now find less restrictive than in previous years [0][2][5].
3. VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage (github.com)
1466 points · 815 comments · by indrora
Microsoft has faced backlash after a VS Code update enabled a setting by default that automatically inserts "Co-authored-by: Copilot" into Git commit trailers, with users reporting the attribution appearing even when AI features are disabled or not used for the specific code changes. [src]
The inclusion of "Co-Authored-by Copilot" tags by default is viewed by many as a symptom of a broader corporate trend where AI hype overrides established user experience standards and technical ethics [0][3][4]. While a Microsoft representative apologized for the "mistake" and promised to revert the default setting, critics argue this behavior reflects a return to the company's historically aggressive tactics and a desperate need to justify billions in AI investment [1][6][7][9]. The discussion highlights a deep cynicism toward management's desire for an automated workforce, with some comparing the forced branding to "Sent from my iPhone" marketing [2][5][8].
4. 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].
5. Copy Fail (copy.fail)
1464 points · 511 comments · by unsnap_biceps
CVE-2026-31431, dubbed "Copy Fail," is a critical Linux logic flaw that allows unprivileged users to gain root access or escape containers by writing four bytes into the page cache, affecting nearly every major distribution released since 2017. [src]
The discussion centers on a critical local privilege escalation (LPE) vulnerability involving the Linux kernel's `AF_ALG` interface, which experts argue should never have been exposed to userspace due to its massive attack surface [1][5]. While the exploit claims broad impact across distributions and container environments, commenters noted it fails on Alpine and rootless Podman, and pointed out factual errors regarding RHEL versioning [2][3]. Debate also broke out over the exploit's presentation, with some criticizing the "fetishism" of minimized code and marketing-heavy disclosure, while others argued that code style is irrelevant for a functional proof-of-concept [0][7][8].
6. 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].
7. Microsoft and OpenAI end their exclusive and revenue-sharing deal (bloomberg.com)
986 points · 844 comments · by helsinkiandrew
Microsoft and OpenAI have ended their exclusive revenue-sharing agreement, transitioning to a non-exclusive partnership that allows both companies to collaborate with other industry players. [src]
The termination of the exclusive deal is seen as a move to prevent OpenAI from being "kneecapped" by Microsoft’s limitations, potentially allowing OpenAI to utilize Google’s superior TPU hardware [1][3]. While some argue that current AI models are merely "random token generators" lacking a true moat or thought process [2][7], others contend that the rapid progress in latent space encoding and robotics suggests we are witnessing the emergence of a new kind of intelligence [4][8][9]. Skepticism remains high regarding the industry's shifting definitions of AGI, with critics labeling the term a marketing narrative rather than a scientific reality [0][6].
8. HERMES.md in commit messages causes requests to route to extra usage billing (github.com)
1248 points · 532 comments · by homebrewer
A bug in Claude Code causes API requests to bypass included plan quotas and bill "extra usage" credits when the case-sensitive string "HERMES.md" appears in recent git commit messages, leading to unexpected costs for Max plan subscribers. [src]
Anthropic faced significant backlash after a technical error caused users to be incorrectly billed for usage, with initial support responses—confirmed by an employee to be AI-generated—refusing to issue refunds [0][1][4]. While users debated legal recourse through small claims court or credit card chargebacks, many noted the risk of account bans and criticized the company's reliance on automated support systems [2][5][6][7]. A representative from the Claude Code team eventually intervened, apologizing for the "complex bug" and promising full refunds plus extra usage credits to all affected users [3].
9. 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].
Brought to you by ALCAZAR. Protect what matters.