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].
Brought to you by ALCAZAR. Protect what matters.