0. Someone bought 30 WordPress plugins and planted a backdoor in all of them (anchor.host)
836 points · 235 comments · by speckx
A malicious buyer acquired a portfolio of over 30 WordPress plugins and planted a sophisticated backdoor that remained dormant for eight months before injecting SEO spam via `wp-config.php`. WordPress.org has since closed the affected plugins, which include popular tools like Countdown Timer Ultimate and Popup Anything on Click. [src]
The incident highlights a critical vulnerability in modern software where attackers can simply purchase dependencies or bribe employees to insert backdoors, a tactic fueled by the massive financial incentives of cryptocurrency [0][7]. Commenters argue that the industry's reliance on massive trees of unvetted transitive dependencies makes supply chain attacks nearly inevitable [1][3][9]. While some debate whether "bug-free" software is even possible, others contend that we possess the technical tools to achieve high quality but consistently prioritize speed and cost over security [2][4][5][8].
1. All elementary functions from a single binary operator (arxiv.org)
810 points · 253 comments · by pizza
Researcher Andrzej Odrzywołek has identified a single binary operator, $eml(x,y) = \exp(x) - \ln(y)$, that can generate all standard elementary functions and constants, enabling a uniform tree-based structure for symbolic regression and scientific computation. [src]
The discovery of a single binary operator (EML) capable of representing all elementary functions is seen as a potentially significant breakthrough for modeling complex data and wave functions via gradient descent [0]. However, critics argue that while mathematically elegant, the approach suffers from an exponential "expression blow-up"—for instance, simple multiplication requires a depth-8 tree with over 40 leaves—making it computationally inefficient compared to traditional polynomials or NAND-gate logic [2][6]. Furthermore, some note that EML is not unique in its universality, as other binary operators like $1/(x-y)$ can also derive all elementary operations [1]. While some users have already begun testing LLMs on their ability to compose EML trees, others remain skeptical of the practical hardware trade-offs compared to traditional math coprocessors [3][5].
2. GitHub Stacked PRs (github.github.com)
603 points · 339 comments · by ezekg
GitHub has introduced Stacked PRs in private preview, featuring a new CLI and native UI support to help developers break large changes into a chain of small, independently reviewable pull requests that can be merged together. [src]
The introduction of stacked PRs on GitHub aims to replicate the Phabricator and Mercurial workflow, which proponents argue makes reviewing large features more manageable by breaking them into smaller, logical chunks [0][8]. While some users find the concept redundant or confusing compared to reviewing individual commits [3][4], others highlight that current GitHub UX makes manual stacking difficult due to merge conflicts and target branch issues [7]. Despite Git's dominance and speed, there is a lingering debate over whether its API is inferior to Mercurial's, leading to the rise of tools like `jujutsu` to bridge the gap [1][2][9].
3. Apple's accidental moat: How the "AI Loser" may end up winning (adlrocha.substack.com)
406 points · 358 comments · by walterbell
Apple is emerging as a surprise AI winner by leveraging its "unified memory" chip architecture and vast ecosystem of personal user context to run increasingly commoditized, high-performance open-source models locally on-device, avoiding the massive infrastructure costs and privacy concerns plaguing competitors like OpenAI. [src]
Apple’s strategy is viewed by some as a classic "leapfrog" approach, waiting for competitors to make sunk investments before architecting a superior, integrated consumer solution [0][2]. There is a growing consensus that local models are rapidly closing the gap with cloud-based AI; if local performance reaches the level of current top-tier models within the next two years, the need for third-party cloud subscriptions may vanish for many users [1][6]. However, skeptics argue that hardware constraints like RAM will limit mobile local AI [9], while others criticize Apple for maintaining a "walled garden" that increasingly prioritizes integrated advertising over user experience [4][7].
4. The economics of software teams: Why most engineering orgs are flying blind (viktorcessan.com)
393 points · 266 comments · by kiyanwang
Most engineering organizations lack financial visibility, failing to track the roughly €1 million annual cost of an eight-person team against the 3x to 5x value return required for viability. As AI reduces the competitive moat of large codebases, companies must shift from activity metrics to rigorous economic analysis. [src]
The discussion centers on whether the primary challenge of software engineering is the technical implementation or the conceptual task of defining what to build [0][4][8]. While some argue that programming is merely a means to explore a problem space [0], others contend that complex engineering remains a significant hurdle that cannot be dismissed as easy [4][8]. There is strong skepticism regarding the article's optimism for AI agents; critics argue that LLMs currently produce "bricked" codebases where structural integrity is sacrificed for a polished exterior, eventually leading to a total inability to make progress [3][5]. Despite these technical concerns, some commenters find the prospect of an "agent-to-agent" world appealing if it eliminates corporate bureaucracy and management layers [1][2].
5. Android now stops you sharing your location in photos (shkspr.mobi)
335 points · 289 comments · by edent
Google has updated Android to automatically strip geolocation metadata from photos shared via the web, Bluetooth, and email to enhance user privacy, a move that complicates the functionality of niche websites and services that rely on geotagged image data. [src]
The consensus among commenters is that stripping EXIF data is a necessary privacy protection, as most users are unaware they are sharing live GPS coordinates with random websites [0][1]. However, critics argue this "toddler-proofing" approach breaks legitimate workflows, such as government data collection or file naming, and frustrates power users who want full control over their data [3][4][9]. Some participants remain skeptical of Google's motives, noting that the company often prioritizes privacy only when it doesn't interfere with advertising revenue or data consolidation [2][6].
6. US appeals court declares 158-year-old home distilling ban unconstitutional (nypost.com)
361 points · 249 comments · by t-3
The 5th U.S. Circuit Court of Appeals has struck down a 158-year-old federal ban on home distilling, ruling that the Reconstruction-era law is an unconstitutional overreach of congressional taxing power. [src]
The ruling has sparked debate over the federal government's power to regulate non-commercial home activities under the Commerce Clause, with some users arguing that precedents like *Gonzales v. Raich* and *Wickard v. Filburn* should be overturned next [0][6]. While many expect federal marijuana legalization within a decade due to broad public support, others remain opposed due to the "negative externalities" of the smell and smoke in public or multi-family housing [1][3][4]. Additionally, commenters clarified that the primary danger of home distilling is fire rather than methanol poisoning, which historically stems from industrial alcohol rather than grain fermentation [5].
7. Nothing Ever Happens: Polymarket bot that always buys No on non-sports markets (github.com)
393 points · 211 comments · by m-hodges
"Nothing Ever Happens" is an open-source Python bot designed to automatically buy "No" outcomes on standalone, non-sports markets on the Polymarket prediction platform. [src]
The "Nothing Ever Happens" bot is presented as a "meme" project that bets against fantastical outcomes, leveraging the fact that 73% of Polymarket events resolve to "No" [0][1]. While some argue this strategy capitalizes on a human bias toward "exciting" outcomes that are often overpriced, others contend that market efficiency and bookie cuts likely price these bets at their fair value, negating potential profits [2][4][7][8]. Commenters emphasize that while inefficient markets may offer positive expected value (EV) initially, open-sourcing such strategies quickly leads to a stable feedback loop where the market reprices to eliminate the edge [3][9].
8. Microsoft isn't removing Copilot from Windows 11, it's just renaming it (neowin.net)
339 points · 254 comments · by bundie
We couldn't summarize this story. [src]
The discussion reflects a deep frustration with Microsoft’s tendency to add "bloat" to simple utilities, such as integrating AI into Notepad or previously attempting to replace Paint with Paint 3D [2][5]. While some users find the ability to toggle these features off acceptable, others view the renaming of Copilot as a superficial change that mirrors past empty corporate gestures [1][3]. Consequently, many users are migrating to Linux for a cleaner experience, though some remain on Windows due to kernel-level anti-cheat in games or superior battery life on mobile hardware [0][4][8].
9. Servo is now available on crates.io (servo.org)
445 points · 141 comments · by ffin
The Servo project has released version 0.1.0 of its web engine as a crate on crates.io, offering a high-performance embedding API and a new long-term support (LTS) version for developers. [src]
The availability of Servo on crates.io has sparked debate over whether AI should be used to accelerate the development of such critical, underfunded infrastructure [0], though some users strongly reject the idea of "vibe-coded" foundational tools [1]. A significant portion of the discussion focuses on Rust’s versioning system, with critics arguing that Cargo’s handling of 0.x versions discourages reaching 1.0 and creates semantic confusion [3][6]. While some see the release as "too little too late" due to the rise of system-provided webviews [9], others are already experimenting with the crate for tasks like CLI-based webpage rendering [7] and suggesting the eventual replacement of its C++ SpiderMonkey engine with a native Rust alternative [4][8].
10. Make tmux pretty and usable (2024) (hamvocke.com)
345 points · 215 comments · by speckx
This guide explains how to customize tmux by editing the `.tmux.conf` file to improve usability and aesthetics. It provides specific configurations for remapping prefix keys, creating intuitive pane splits, enabling mouse support, and applying custom color schemes to the status bar and panes. [src]
While many users have migrated from tmux to modern alternatives like Zellij for its superior UI and mouse handling [0][4], others have returned to tmux due to stability issues or specific key-binding fixes [2]. A significant portion of the community argues that tmux should be used minimally for session persistence rather than complex window management, which they prefer to handle via native terminal features or window managers [5][8][9]. For those seeking a middle ground, "Control Mode" (`tmux -CC`) is highlighted as a way to integrate tmux sessions directly into a terminal's native tabs and scrollback [6].
11. Stanford report highlights growing disconnect between AI insiders and everyone (techcrunch.com)
233 points · 323 comments · by ZeidJ
Stanford’s 2026 AI Index report reveals a widening gap between optimistic industry experts and a skeptical public increasingly anxious about AI's impact on jobs, healthcare, and the economy. [src]
A sharp divide exists between leadership and "AI experts" who see massive productivity gains—such as condensing two-week projects into minutes [5]—and rank-and-file engineers who find the technology underwhelming and its promises "rosy" but unfulfilled [0][1]. Critics argue that the push for AI is creating a "mania" that sidelines engineering rigor in favor of useless proofs of concept [7], while younger generations increasingly view AI as a "bad or immoral" tool associated with cheating [4][9]. Furthermore, there is significant concern that viewing junior engineers as replaceable by AI will cause organizations to "rot from the inside" by destroying the pipeline for future senior talent [6][8].
12. This year’s insane timeline of hacks (ringmast4r.substack.com)
296 points · 175 comments · by laurex
The first four months of 2026 have seen an unprecedented wave of cyberattacks by state-linked and criminal alliances, including a massive 200,000-device wiper attack on Stryker, breaches of FBI and Lockheed Martin systems, and a 1.5-billion-record Salesforce exploitation targeting hundreds of global organizations. [src]
The tech industry is entering a "ransomware apocalypse" as generative AI lowers the barrier for sophisticated phishing, malvertising, and supply chain attacks previously reserved for nation-states [0][7]. While some see security as a promising career path for the youth, veterans warn of extreme burnout caused by corporate negligence and the potential for AI to eventually automate defensive roles as well [0][1][6]. Despite the escalating severity of these breaches, the general public remains largely indifferent due to "crisis fatigue" and a constant stream of competing global anxieties [2][5]. Ultimately, experts suggest that without systemic accountability for sloppy security practices, the internet may become fundamentally unsafe for the average user [4][9].
13. The Future of Everything Is Lies, I Guess: Safety (aphyr.com)
291 points · 158 comments · by aphyr
The proliferation of machine learning systems endangers physical and psychological safety by enabling sophisticated cyberattacks, automated harassment, and large-scale fraud while lowering the barrier for developing "unaligned" or malicious models. These technologies also facilitate the expansion of autonomous weaponry and increase the trauma experienced by human content moderators. [src]
The discussion centers on the inherent difficulty of "alignment," with some arguing that commercial and governmental interests are fundamentally adversarial to individuals [0]. While some participants believe humans are biologically or socially predisposed toward prosocial alignment [2][3], others contend that human history is defined by violent value misalignments and that systems like markets or civilizations were specifically invented to manage these conflicts [4][5]. This debate extends to anthropological theories, contrasting the idea of "everyday communism" and gift economies against the modern tendency to view all human interactions through a market-based lens [7][8][9].
14. AI could be the end of the digital wave, not the next big thing (thenextwavefutures.wordpress.com)
178 points · 255 comments · by surprisetalk
The "late-cycle investment theory" suggests that AI is the final optimization stage of the 1970s digital revolution rather than a new technological surge, characterized by high capital costs, incumbent dominance, and a focus on efficiency within existing systems. [src]
The discussion highlights a divide between those who view AI as a tool for unprecedented creative and technical unlocking and those who see it primarily as a mechanism for labor exploitation and the degradation of digital quality [1][5][9]. Some developers report a rapid decline in their ability to code without AI assistance, while others argue that "muscle memory" remains intact for experienced professionals and that boilerplate should have been automated long ago [0][3][7]. Beyond the workplace, users are noting a decline in the online shopping experience due to a flood of AI-generated imagery, leading some to return to physical retail [2][8].
15. Building a CLI for all of Cloudflare (blog.cloudflare.com)
288 points · 93 comments · by soheilpro
Cloudflare is rebuilding its Wrangler CLI to cover its entire API surface, introducing a technical preview (`npx cf`) and a "Local Explorer" tool to help developers and AI agents manage both remote and local resources with consistent, schema-driven commands. [src]
The introduction of a unified Cloudflare CLI sparked a debate over the choice of TypeScript, with critics arguing it lacks the performance of languages like C or Go [0][8], while proponents highlight its modern developer experience and suitability for scripting [5]. Users expressed a strong desire for better permission management, specifically requesting features to identify required API token scopes before deployment [2][9]. Additionally, early feedback on the tool emphasizes the need for standardized help flags, consistent formatting across subcommands, and non-interactive behavior for basic command queries [3].
16. I went to America's worst national parks so you don't have to (substack.com)
195 points · 182 comments · by surprisetalk
A veteran traveler critiques several major U.S. national parks for overcrowding and boredom, ultimately naming South Carolina's Congaree the worst due to its stagnant water, extreme humidity, and aggressive mosquito infestations. [src]
Commenters largely dismiss the author's critiques as "trolling," arguing that even the most crowded parks like Zion offer solitude if visitors venture beyond the "Disneyland" main attractions or hike more than two miles from trailheads [0][2][4]. While some acknowledge the grueling nature of the Grand Canyon's switchbacks and the intense congestion at Zion during peak seasons, they maintain these sites possess an "immediate majesty" that the author fails to appreciate [1][5][8]. Others suggest that state parks or less-famous national sites like Congaree often provide a superior, less-crowded experience compared to the "tourist traps" of major parks [3][9].
17. Michigan 'digital age' bills pulled after privacy concerns raised (thecentersquare.com)
210 points · 119 comments · by iamnothere
We couldn't summarize this story. [src]
The discussion highlights the irony of a privacy-focused article being blocked for European users due to GDPR compliance, which some view as a successful regulatory barrier against data harvesting while others see it as a practical limitation for small publishers [1][2][5]. Users expressed frustration over "opt-out" models that allow data to be sold before a user can intervene, arguing instead for "opt-in" requirements to prevent corporate exploitation [3][6][7]. While some suspect a coordinated corporate effort to establish a global "panopticon" through identity verification, others suggest that universal data access might be the only way to balance the power dynamics of a surveillance state [0][4][9].
18. Show HN: I built a social media management tool in 3 weeks with Claude and Codex (github.com)
177 points · 120 comments · by JanSchu
BrightBean Studio is a new open-source, self-hostable social media management platform that allows users to schedule and manage content across over 10 platforms. Built in three weeks using AI tools, the Django-based tool serves as a free, limit-free alternative to SaaS vendors like Buffer and Sendible. [src]
The developer demonstrated that AI agents can compress a year of solo development into three weeks by using a spec-driven approach to build a multi-tenant social media tool [1]. While AI excelled at standard CRUD and well-documented APIs, it struggled with complex OAuth edge cases, multi-tenant security logic, and consistent UI design, requiring significant manual intervention for the final 80% of polish [1]. Some users argue this marks a shift toward "vibe coding" bespoke personal tools rather than sharing software, as individuals can now build tailored solutions like private password managers in days [3][5]. However, critics remain skeptical of the "vibe coded" label, fearing such projects lack the "battle-tested" reliability and long-term maintenance required for serious production use [0][8].
19. How to make Firefox builds 17% faster (blog.farre.se)
159 points · 28 comments · by mbitsnbites
By utilizing Buildcache’s Lua plugin system to cache WebIDL binding code generation, Firefox developers can reduce warm clobber build times by approximately 17%, further optimizing the build process beyond traditional compiler caching. [src]
The discussion centers on the technical challenges of caching Rust proc-macros, with users noting that non-determinism and poor cache hit rates—especially on Windows—hinder build performance [0]. While there is interest in treating proc-macros as idempotent to increase speed, such changes require significant design work to avoid breaking backward compatibility [1][6]. Some commenters question the focus on build speeds over Firefox's declining market share [3], while others debate whether it is better to fix the underlying build system rather than adding external caching layers like `sccache` [5][9].
Brought to you by ALCAZAR. Protect what matters.