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. 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].
2. Localsend: An open-source cross-platform alternative to AirDrop (github.com)
921 points · 276 comments · by bilsbie
LocalSend is a free, open-source, cross-platform application that enables secure file and message sharing between nearby devices over a local network using HTTPS encryption and a REST API, eliminating the need for an internet connection or third-party servers. [src]
While LocalSend is praised for its cross-platform reliability, users note it lacks AirDrop’s seamless "zero-configuration" networking, which utilizes proprietary Apple Wireless Direct Link (AWDL) technology to transfer files without an existing Wi-Fi network [0][1][5]. Technical discussions highlight that while Android's QuickShare offers similar peer-to-peer capabilities, it lacks cross-platform support for iOS and Linux, and alternatives often suffer from slower speeds [1][4][9]. Some users question the necessity of such apps given cloud and SMB alternatives, while others argue that AirDrop’s own UX is increasingly unreliable, making LocalSend a viable tool for mixed-device environments [3][6].
3. UAE to leave OPEC (ft.com)
492 points · 692 comments · by bazzmt
The United Arab Emirates has announced its decision to withdraw from OPEC, marking a significant shift in the global oil alliance's membership and production dynamics. [src]
The UAE’s departure from OPEC is viewed as a strategic shift to counter Saudi and Iranian hegemony, potentially signaling the emergence of an Emirati-Israeli axis [0]. While some see this as a US-aligned move to erode OPEC’s pricing power [1][5], others argue it represents a pivot away from the petrodollar system toward trade in yuan [8]. Domestically, the move coincides with a rollback of CAFE standards, sparking debate over whether fuel consumption is driven by consumer demand or manufacturer profit margins [3][4][7].
4. Who owns the code Claude Code wrote? (legallayer.substack.com)
555 points · 530 comments · by senaevren
The legal ownership of AI-generated code remains unsettled, as copyright requires "meaningful human authorship," while employment contracts and hidden open-source license contamination from training data further complicate whether developers or their employers truly own the resulting work product. [src]
The consensus remains divided on whether AI-generated code is "stolen," with some arguing that LLMs merely "learn" from existing code similarly to human developers [2][3], while others contend that training on such data constitutes "copyright washing" or large-scale unauthorized copying [0][9]. Legal ownership is equally contentious: some believe the human directing the agent holds the copyright [0], while others argue humans only own the prompt [6] or that works predominantly generated by AI are ineligible for protection entirely [5]. Practically, many developers suggest these legal distinctions rarely matter in day-to-day software engineering, as code is frequently reused without strict attribution and minor human modifications can render a work copyrightable regardless of its origin [4][7].
5. Before GitHub (lucumr.pocoo.org)
674 points · 233 comments · by mlex
Reflecting on the history of open-source hosting, Armin Ronacher argues that GitHub’s current decline necessitates a shift toward decentralized infrastructure and the creation of a permanent, well-funded public archive to preserve software history and social context. [src]
Before GitHub, developers relied on high-friction tools like SourceForge, Trac, and CVS, which often required formal project registration and complex server setups [1][2]. Commenters credit GitHub with shifting the focus from projects to individuals, lowering the "mental load" for small experiments, and acting as a massive library for the software commons [1][6]. However, some argue this centralization has atrophied collective archival skills and lament the dominance of Git over alternatives like Fossil, which offers integrated versioning for wikis and tickets [0][6].
6. Waymo in Portland (waymo.com)
296 points · 591 comments · by xnx
Waymo has announced its expansion into Portland, Oregon, beginning with manual vehicle operations to map the city's streets while working with local officials to establish a regulatory path for future autonomous ride-hailing services. [src]
Waymo’s arrival in Portland coincides with a $300M budget shortfall for TriMet public transit, leading some to view autonomous vehicles as a timely solution for "last mile" connectivity and a replacement for inefficient bus routes [0][3][7]. While some users dream of private autonomous vehicles for long-distance travel, critics argue that self-driving cars are merely a "bandaid" for poor urban design and that trains already solve the problem of sleeping while traveling across the country [1][2][5]. There is significant debate over whether Waymo can truly function as public transport, with skeptics labeling it an expensive taxi service while proponents suggest it could be cheaper and safer than human-driven rideshares [4][6][7][9].
7. How ChatGPT serves ads (buchodi.com)
508 points · 361 comments · by lmbbuchodi
OpenAI’s ad platform serves contextual ads by injecting structured objects into ChatGPT's conversation stream and tracking conversions through a merchant-side SDK called OAIQ, which uses encrypted Fernet tokens to link user clicks to product views. [src]
Users view the introduction of ads as the beginning of "enshittification," debating whether this move signals that OpenAI is "strapped for cash" or simply unwilling to continue selling services at a loss [0][1][7][9]. While some argue that Sam Altman previously framed ads as a "last resort," others suggest this shift was an inevitable part of scaling global access [0][4][6]. Technical concerns focus on the future of "adversarial content," with participants predicting a shift toward local or self-hosted models to avoid injected marketing and service degradation [2][3][8].
8. An update on GitHub availability (github.blog)
419 points · 250 comments · by salkahfi
GitHub is scaling its infrastructure to handle a 30x increase in demand driven by agentic AI workflows while implementing service isolation and multi-cloud migrations to address recent reliability issues and improve platform availability. [src]
GitHub's announcement of a "multi-cloud" strategy has sparked debate over whether Microsoft is admitting that Azure cannot provide acceptable reliability on its own [0][3]. Critics argue that GitHub’s stated priority of availability over new features contradicts the frequent UI changes and "dire" uptime experienced by users over the last year [2][4]. While some defend the platform by citing the immense difficulty of scaling through exponential growth [5], others suggest that moving away from dedicated hardware to the cloud has made performance less predictable and more expensive for business customers [7][8].
9. Period tracking app, Flo, found to be selling user data to Meta (femtechdesigndesk.substack.com)
395 points · 269 comments · by campuscodi
A jury found the period-tracking app Flo and Meta liable for unlawfully sharing the sensitive health and reproductive data of millions of users with third parties for advertising purposes, despite the app's explicit privacy promises and the lack of HIPAA protections for non-clinical wellness software. [src]
The discussion highlights a consensus that period tracking data is highly sensitive, with users warning that such information could be weaponized by governments to identify individuals seeking abortions through patterns of missing cycles and location data [0][3][8]. While some argue that users should revert to pen and paper to ensure absolute privacy [2][9], others question why these apps require server-side processing at all [1]. There is a noted disagreement regarding the viability of open-source alternatives; while apps like Drip exist [6], they may struggle to gain mainstream adoption if they prioritize gender neutrality and utility over the "cute" aesthetic design that attracts users to proprietary apps like Flo [7].
10. Google and Pentagon reportedly agree on deal for 'any lawful' use of AI (theverge.com)
316 points · 282 comments · by granzymes
Google has reportedly signed a classified deal allowing the Pentagon to use its AI models for any lawful purpose, despite employee protests and concerns over the technology being used for surveillance or autonomous weaponry without human oversight. [src]
The agreement has sparked a debate over the morality of defense contracting, with some arguing that researchers working on these projects are "morally compromised" while others contend that collaborating with one's own government is not inherently wrong [0][1][4][5]. Critics express concern that the term "lawful" is a flexible definition used by those in power to justify actions like mass surveillance or autonomous weaponry, especially since Google reportedly lacks veto power over the Pentagon's applications [2][3][7][8]. Furthermore, some participants suggest that while legacy industries use established regulatory capture to legitimize such deals, the lack of similar infrastructure in Big Tech makes these partnerships more visible and controversial [6][9].
11. VibeVoice: Open-source frontier voice AI (github.com)
386 points · 181 comments · by tosh
Microsoft has open-sourced VibeVoice, a family of AI models featuring a long-form speech recognition model (ASR) capable of processing 60-minute audio files and a real-time text-to-speech (TTS) model. The framework utilizes continuous speech tokenizers and next-token diffusion to maintain high fidelity and semantic coherence. [src]
The discussion primarily debates the accuracy of labeling VibeVoice as "open source," with several users arguing it should be called "open weight" because the training code remains proprietary [0][1][4]. While some feel the term has been permanently diluted to mean "freeware," others emphasize that the true value lies in the user's legal freedom to use the model rather than the transparency of its creation [1][5][8]. Regarding performance, the model is criticized for being slow, resource-heavy, and prone to hallucinations in speech-to-text tasks [2].
12. Claude.ai unavailable and elevated errors on the API (status.claude.com)
297 points · 252 comments · by shorsher
Anthropic has resolved a service outage that briefly prevented access to Claude.ai and caused elevated authentication errors across its API, Claude Code, and government platforms. [src]
The discussion highlights significant frustration among high-spending enterprise users regarding Anthropic's "astounding" frequency of outages and poor support, with some reporting reliability as low as "one 9" of uptime over the last 90 days [0][2][5]. While some users express sympathy for the technical challenges of scaling so rapidly [7], others argue that the industry must recognize the continued necessity of human engineers over "non-deterministic genies" in production [8]. To mitigate these stability issues, commenters suggest migrating to AWS or Google Cloud to access the same models with better uptime [1], or transitioning to self-hosted open models on private hardware for guaranteed availability [3].
13. GitHub RCE Vulnerability: CVE-2026-3854 Breakdown (wiz.io)
447 points · 92 comments · by bo0tzz
Wiz Research discovered a critical remote code execution vulnerability (CVE-2026-3854) in GitHub's internal protocol that allowed authenticated users to compromise backend servers via a single `git push`. GitHub has patched the flaw on GitHub.com and released urgent updates for GitHub Enterprise Server to prevent full server compromise. [src]
The discovery of a critical RCE vulnerability in GitHub has sparked debate over whether users should migrate to alternatives like GitLab or Forgejo, though some argue that self-hosting lacks the robust security teams and feature sets provided by GitHub [0][2][5][8]. A significant point of contention is the poor state of GitHub Enterprise Server (GHES), where 88% of instances remain unpatched seven weeks after a fix [1]. Critics claim GHES is "on life support," citing multi-hour downtimes for simple patches and a lack of high-availability upgrade support as the primary reasons customers fail to stay current [3].
14. GitHub Copilot code review will start consuming GitHub Actions minutes (github.blog)
312 points · 207 comments · by whtsky
Starting June 1, 2026, GitHub Copilot code reviews for private repositories will consume GitHub Actions minutes and be billed as AI Credits under a new usage-based model. [src]
The consensus among commenters is that the era of heavily subsidized AI is ending as companies face pressure to show returns on investment and move toward billing users for actual compute costs [0][4][9]. While some debate whether current API pricing is already profitable or if true costs are significantly higher than subscription fees, many see this shift as a "rugpull" designed to test market price tolerance [1][6][8]. Consequently, some users suggest transitioning to local models to avoid rising costs and dependency on external providers [2].
15. Warp is now open-source (warp.dev)
371 points · 118 comments · by meetpateltech
Warp has open-sourced its client under an AGPL license, introducing an agent-first contribution workflow managed by its Oz orchestration platform and sponsored by OpenAI. [src]
Warp’s transition to open-source is viewed by some as a strategic move to accelerate development against AI-focused competitors like Cursor and Claude Code [0][2], while skeptics argue it may be a "last ditch effort" to sustain a VC-funded business by leveraging free community labor [1]. While users praise Warp’s unique "convenience shell wrapping" and command editing features [7], there is significant demand for a lightweight version stripped of AI and cloud dependencies [3][5]. Concerns persist regarding the software's history of account requirements and "calling home," leading some to prefer more minimalistic alternatives like Ghostty or Alacritty [4][8][9].
16. GTFOBins (gtfobins.org)
388 points · 95 comments · by StefanBatory
GTFOBins is a curated compendium of Unix-like executables that can be leveraged to bypass local security restrictions, escalate privileges, and perform post-exploitation tasks on misconfigured systems. [src]
GTFOBins is a curated list of Unix binaries that can be exploited to bypass local security restrictions, such as breaking out of restricted shells or escalating privileges via misconfigured `sudo` or SUID bits [0][6]. While some users question the utility of these techniques once an attacker has already gained shell access [8][9], others highlight their critical role in Capture The Flag (CTF) competitions and advanced attacks, such as using `dd` to patch shellcode into running processes via `/proc` [0][4]. A significant portion of the discussion focuses on how LLM-based agents can use these methods to circumvent rudimentary allow-lists, leading to a consensus that proper isolation—such as hardened Docker containers—is necessary to safely run such tools [2][3][5][7].
17. Denuvo has been cracked in all single-player games it previously protected (tomshardware.com)
281 points · 173 comments · by oceansky
Piracy groups have successfully cracked or bypassed all single-player games protected by Denuvo DRM, prompting 2K Games and Denuvo to retaliate by implementing mandatory 14-day online check-ins for several titles. [src]
The crack of Denuvo-protected games has reignited a debate over whether DRM is a necessary defense against rampant PC piracy or a wasteful burden that penalizes legitimate players with performance issues and bloated executables [3][4]. While some argue that piracy forces developers toward live-service models and discourages AAA single-player releases on PC [1][5], others contend that the shift to subscriptions is driven by higher revenue potential rather than piracy losses [2]. Notable anecdotes include a developer's experiment showing that 93.6% of players pirated their $8 game on launch day [6], though some users maintain a moral stance against DRM, arguing that "if buying isn't owning, then piracy isn't stealing" [7].
18. Anthropic Joins the Blender Development Fund as Corporate Patron (blender.org)
245 points · 196 comments · by Philpax
AI safety startup Anthropic has joined the Blender Development Fund as a Corporate Patron to support core software development and the maintenance of the Blender Python API. [src]
Anthropic’s sponsorship of the Blender Development Fund has sparked a divide between those who see it as a standard corporate contribution to open-source software [1] and those who view it as an attempt to "inject slop" and replace human artists [4][6]. Proponents argue that AI integration will democratize access to Blender’s high learning curve, enabling more people to realize their creative visions [5][9]. Conversely, critics contend that automating the creative process devalues human skill and effort, potentially turning art into a "simulacrum" of creation [2][6]. Technically, users suggest the move aims to improve the Blender Python API to allow Claude to interact directly with the software, building on existing Model Context Protocol (MCP) implementations [0][7].
19. OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs (stratechery.com)
326 points · 114 comments · by translocator
OpenAI and Amazon have announced a partnership to integrate OpenAI's frontier models into the Amazon Bedrock platform, allowing AWS customers to build and scale generative AI applications using OpenAI's technology. [src]
OpenAI’s move to Amazon Bedrock is seen as a necessary pivot to compete with Anthropic, which gained a significant enterprise lead by offering "trusted" access through AWS while OpenAI was often banned due to privacy concerns or poor Azure integration [0][7]. While some users are eager to switch to OpenAI's Codex due to scaling issues with Claude, others worry that different inference hardware and optimizations on Bedrock may lead to non-deterministic performance variations [2][5][9]. Despite the bureaucratic reputation of big tech, the integration was likely executed by elite "swat teams" working outside traditional corporate friction to address OpenAI's lack of a sustainable business model [1][3][4][8].
Brought to you by ALCAZAR. Protect what matters.