Top HN Daily Digest · Mon, Apr 13, 2026

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


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].