Jul 24Saturday, July 25, 2026 · all daysJul 26 · today »
1.Android may soon restrict on-device ADB(kitsumed.github.io)
998 points by shscs911 47 days ago | 499 comments | permalink
tl;dr: Google is considering restricting Android's ADB daemon to only bind to the wlan0 interface in response to CVE-2026-0073, which would break on-device ADB (loopback connections used by tools like Shizuku, App Manager, and Canta) along with ADB over VPN or Ethernet. The author argues this framing treats legitimate on-device ADB use as an exploit vector, when in practice attackers can't start ADBD themselves, and proposes a persistent user-toggleable setting instead of a hard block.
HN Discussion:
  • The attack vector is unrealistic and doesn't justify breaking legitimate ADB use cases
  • This is part of Google's broader trend of locking down Android and eroding openness
  • Android losing openness eliminates the main reason to choose it over iOS
  • Restricting ADB to specific interfaces like VPN would actually be a security improvement
  • Users need alternatives like Linux phones since Android is becoming untrustworthy
2.Claude Opus 5(anthropic.com)
1765 points by alvis 47 days ago | 1315 comments | permalink
tl;dr: Anthropic released Claude Opus 5, claiming state-of-the-art performance on coding and knowledge-work benchmarks (Frontier-Bench, GDPval-AA, ARC-AGI 3, OSWorld 2.0) at half the cost of their top-tier "Fable 5" model, though it still trails "Mythos 5" on cybersecurity exploit development and advanced biology tasks. Pricing matches Opus 4.8 at $5/$25 per million input/output tokens, and Anthropic is loosening cyber safeguards (blocking ~85% less often than Fable 5) while adding beta features like mid-conversation tool changes and automatic model fallbacks for flagged requests.
HN Discussion:
  • Awe at rapid pace of AI capability improvements becoming normalized
  • Data retention policy differences matter more than raw benchmark performance
  • ~Opus 5 retains annoying writing quirks unlike Fable 5
  • Anthropic's messaging is confusing and contradictory about Opus 5 vs Fable 5 capabilities
  • Skepticism about benchmark numbers discrepancy with original OSWorld authors
3.Hannah Fry Wins the Leelavati Prize in 2026 for Mathematics Outreach(maths.cam.ac.uk)
594 points by agnishom 47 days ago | 110 comments | permalink
tl;dr: Professor Hannah Fry, Cambridge's first Professor of the Public Understanding of Mathematics, has won the 2026 Leelavati Prize from the International Mathematical Union for her work communicating mathematics to the public. Awarded every four years at the International Congress of Mathematicians, the prize recognizes her books, TV programs, podcasts, and social media reaching millions. Recent accolades include a 2025 Emmy for "The Future with Hannah Fry" and a 2026 Webby for her podcast "The Rest is Science."
HN Discussion:
  • Personal anecdotes praising her communication skills and memorable work
  • Endorsement of her podcast and other content as engaging and accessible
  • Admiration for her personal journey and philosophy of engaging audiences
  • Recommendation of similar science communicators like Brian Cox
  • Noting the prize's modest cash value compared to the Fields Medal
4.Postgres LISTEN/NOTIFY actually scales(dbos.dev)
360 points by KraftyOne 47 days ago | 77 comments | permalink
tl;dr: Postgres LISTEN/NOTIFY hits a throughput ceiling (~2.9K writes/sec) because committing a transaction with NOTIFY requires a global exclusive lock held through fsync, serializing commits. DBOS worked around this by buffering notifications in memory and flushing them in batched transactions, with readers periodically polling as a fallback for missed notifications after crashes. This pushed throughput to 60K stream writes/sec on a single Postgres server with 15-100ms latency, saturating CPU rather than lock contention.
HN Discussion:
  • ~Scaling requirements vary widely; choosing tech with the right scaling factor matters more than raw throughput numbers
  • LISTEN/NOTIFY works well in practice when paired with smart architecture like fan-out brokers
  • The article omits critical details like how to allocate sequence numbers for consumer offset tracking
  • Real-world experience confirms LISTEN/NOTIFY has serious scaling problems, validating the need for workarounds
  • The article ignores prior corrections and hard limitations (like 8000-byte payload cap) that still constrain scalability
5.Opus 5 is currently #1 on Artificial Analysis Intelligence Leaderboard(artificialanalysis.ai)
365 points by aarondong 47 days ago | 216 comments | permalink
tl;dr: Anthropic's Claude Opus 5 has taken the top spot on Artificial Analysis's Intelligence Index v4.1, which aggregates nine benchmarks including GDPval-AA v2, Terminal-Bench v2.1, SciCode, Humanity's Last Exam, and GPQA Diamond. The leaderboard also tracks cost per task, output speed, latency, token usage, and context window size across proprietary and open-weight models.
HN Discussion:
  • Confirms Opus 5's superiority by highlighting it outperforms competitors even at lower effort settings
  • Cost-effectiveness undermines the ranking since cheaper models match Opus 5's performance
  • Claude's censorship and safeguards make its top ranking practically meaningless for real use
  • Personal user experience praising Opus 5's improved behavior over previous models
  • ~Benchmarks are incomplete without testing long-context performance with irrelevant filler
6.India's first privately-developed rocket reaches orbit on debut launch(arstechnica.com)
674 points by sohkamyung 52 days ago | 214 comments | permalink
tl;dr: Skyroot Aerospace's Vikram-1 became India's first privately-developed rocket to reach orbit, successfully deploying payloads to a 450 km orbit on its debut launch Saturday—an unusual feat since most private orbital rockets fail on first attempts (SpaceX's Falcon 1 took four tries). The 22-meter, mostly solid-fueled rocket can carry 350 kg to low-Earth orbit, slightly outclassing Rocket Lab's Electron. The Hyderabad-based startup, valued at $1.1 billion with $160 million raised, plans larger Vikram-1U and Vikram-2 variants, aligning with PM Modi's push to scale India's launch cadence tenfold by decade's end.
HN Discussion:
  • Additional context on other Indian private space startups and their innovations
  • Impressed by the achievement given the modest funding and timeline
  • Technical curiosity about rocket engineering details like staging and telemetry
  • Celebrates the milestone as national/economic achievement
  • Recommends related reading on the private space industry
7.My security camera shipped a GitHub admin token in its login page(hhh.hn)
640 points by hhh 48 days ago | 231 comments | permalink
tl;dr: A researcher extracted firmware from Hanwha Vision security cameras by reverse-engineering the fwupgrader binary (with Claude Code's help) to recover a hardcoded AES key/IV used across the model line. Inside the rootfs, they found a GitHub admin token duplicated across ~30 files—caused by Vite dumping the entire CI `process.env` into the built UI—granting access to hundreds of repos, alongside env vars referencing DoD-assigned IP addresses. Hanwha revoked the token within 12 hours of disclosure.
HN Discussion:
  • Isolate IP cameras on a separate VLAN without internet access as basic defense
  • IoT vendors routinely ship terrible security with hardcoded credentials, this is unsurprising
  • DoD-linked IP addresses in the firmware is the more alarming finding
  • Seeking open/supported firmware alternatives for cameras to avoid these issues
  • LLMs like Claude have made reverse engineering and defeating obfuscation trivial
8.Firefox Containers Preview(blog.mozilla.org)
447 points by twapi 50 days ago | 126 comments | permalink
tl;dr: Firefox 153 is previewing native Multi-Account Containers, bringing the decade-old extension's functionality directly into the browser to isolate cookies and tracking between contexts like work, banking, and shopping. Users can create custom containers with names, colors, and icons via right-clicking tabs or long-pressing the new tab button. The existing extension still works alongside the built-in version, as not all add-on features have been ported yet.
HN Discussion:
  • Long-time containers users welcome native integration and prefer it over the extension
  • Containers are valuable for managing multiple accounts and testing across contexts
  • ~Profiles offer stronger isolation than containers, questioning containers' value
  • The native implementation is too barebones and should include more automation and features
  • Containers work well with proxy extensions; hoping for native proxy support
9.Kimi K3 exploited the latest Redis server(twitter.com)
267 points by Alifatisk 48 days ago | 92 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • The exploit is unimpressive since it's an authenticated RCE requiring existing access, not a real security boundary breach
  • Concerns about LLMs democratizing exploit development and putting zero-day tools in unskilled hands
  • ~Reproducing the result requires complex harness setup, not just copy-pasting a prompt
  • ~The finding about Kimi K3's capabilities is interesting even if the 0day itself is trivial
  • Memory-unsafe C/C++ code is the underlying problem; Rust alternatives are needed
10.Taylor Farms Called White House to Try to Delay Cyclospora Recall(wsj.com)
315 points by JumpCrisscross 47 days ago | 212 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Corporate corruption and lobbying to delay recalls undermines public trust in food safety
  • Taylor Farms made a bad strategic choice by hiding instead of owning up like Tylenol did
  • Federal government degradation from corruption requires rethinking food safety institutions
  • The lab result was a false positive, questioning the basis of the recall narrative
  • Broader food safety concerns like prion disease deserve more attention than this incident
11.Half-Life 2 running natively on HaikuOS(discuss.haiku-os.org)
329 points by m0do1 48 days ago | 69 comments | permalink
tl;dr: Half-Life 2 now runs natively on HaikuOS via the nillerusr Source engine port, leveraging a new Nvidia driver ("Nebula") that supports Turing and Ampere GPUs (e.g., GTX 1650–RTX 2060), with users reporting high framerates at 1440p. DisplayPort support is reportedly ready but unreleased, and HDMI audio was briefly enabled before being reverted pending a workaround. Newer Lovelace/Ada cards (RTX 40/50 series) aren't supported yet due to missing firmware blobs.
HN Discussion:
  • Praise for X512's extensive contributions to Haiku including the Nvidia driver work
  • Context about the nillerusr Source engine port used as the basis
  • Surprise and delight that Haiku now has hardware-accelerated GPU support
  • Excitement about broader Haiku progress like ARM/M1/Raspberry Pi support
  • Suggests HL2 on portable ARM Linux is more interesting than this port
12.Nvidia, Microsoft, Meta warn against overregulating open-weight models(cnbc.com)
647 points by louiereederson 48 days ago | 312 comments | permalink
tl;dr: Nvidia, Microsoft, Meta, Palantir and 20+ other tech companies signed a letter urging policymakers not to impose "premature restrictions" on open-weight AI models, arguing such moves would stifle competition and push innovation overseas. The letter comes amid growing concern over Chinese open-weight models like Moonshot's Kimi K3 outperforming U.S. offerings, with the Trump administration weighing potential sanctions over alleged IP theft. Notably, OpenAI and Anthropic—both preparing for IPOs and primarily developing closed models—did not sign, though Sam Altman voiced support on X.
HN Discussion:
  • Chinese open models like Kimi are practically superior for real work, supporting the anti-restriction argument
  • Anthropic/OpenAI's absence is due to self-interested lobbying to regulate competitors out
  • Open-weight advocates now have enough industry backing to defeat closed-source lobbying, similar to SOPA
  • The list of signatories and non-signatories reveals telling corporate alignments
  • Explicit endorsement that this pro-open-weight stance should prevail
13.IRGC claims it destroyed Amazon's Bahrain data center(houseofsaud.com)
334 points by thisislife2 48 days ago | 449 comments | permalink
tl;dr: Iran's IRGC claims it destroyed AWS's Bahrain data center (ME-South-1) with cruise missiles on July 21, 2026, in retaliation for a US strike on the Darkhovin nuclear plant—the third attack on the facility since March, escalating from drones to cruise missiles. Amazon and CENTCOM have not confirmed the strike. The attack extends a March IRGC declaration naming 18 US tech firms as legitimate military targets, raising serious concerns for Saudi Arabia's cloud infrastructure, including the newly-opened Riyadh AWS region and Aramco's cloud-integrated operations.
HN Discussion:
  • ~Technical skepticism about destroying an entire multi-datacenter AWS region with one strike
  • Corroborating evidence via OSM and satellite imagery of the datacenter damage
  • Reflection on disaster planning and business continuity implications for cloud providers
  • Questioning the credibility and sourcing of the article (houseofsaud.com)
  • Contradicting claims in the article, e.g. bank infrastructure being down
14.Buz – A fork of Bun using modern Zig, with sub-1s incremental builds(ziggit.dev)
298 points by kristoff_it 48 days ago | 189 comments | permalink
tl;dr: Buz is a WIP fork of Bun based on the last commit before Bun's Rust rewrite, ported to modern Zig with sub-1s incremental builds and the entire build graph (including vendored JavaScriptCore) in build.zig. The author has removed 11K+ lines of dead code, imported tests from Rust Bun, and aims for a drop-in replacement with a saner codebase. Notably, contributions are LLM-only for now — the maintainer argues the existing 600K-line codebase is too "sloppy" for humans to untangle by hand.
HN Discussion:
  • Fork proves Bun could have had fast builds all along, validating the effort
  • Ironic/skeptical of using LLMs to clean up code LLMs made messy in the first place
  • Skepticism about the 11K dead code claim, suggesting author lacks experience with large codebases
  • Appreciation for prioritizing code quality/stewardship over pure feature velocity
  • Build time optimization is diminishing returns and not the real bottleneck
15.If coding has been solved, why does software keep getting worse?(ptrchm.com)
874 points by pchm 48 days ago | 666 comments | permalink
tl;dr: Despite AI coding tools raising productivity and skill floors, everyday software (banking apps, car infotainment, macOS) keeps getting buggier and more fragile because complexity has grown while incentives still reward features over stability. The author argues KPI-driven vendors won't prioritize bug-fixing, so quality will keep decaying at big companies—but sees an opening for individual developers to leverage AI to build better alternatives.
HN Discussion:
  • Updates now inspire dread rather than excitement, confirming software is degrading
  • Non-technical decision-makers control products, sidelining devs who notice quality issues
  • Focus-stealing and similar UX bugs exemplify pervasive quality decay
  • ~Software has always been buggy; blame inexperience and market incentives, not AI
  • Perverse promotion/KPI incentives reward shiny new tools over fixing existing ones
16.Government orders GitHub to remove Bluetooth-based chat app Bitchat: Jack Dorsey(thehindu.com)
515 points by rootkea 48 days ago | 418 comments | permalink
tl;dr: India's Cybercrime Coordination Centre (I4C) has ordered GitHub to remove Bitchat, a Bluetooth mesh-based messaging app developed by Jack Dorsey, citing risks that its decentralized, anonymous architecture could be exploited by terrorists, criminals, and protesters to evade lawful surveillance and internet shutdowns. The takedown request follows observed use of the app during a recent protest at Jantar Mantar where internet services were restricted, and alleges violations of multiple sections of India's IT Act.
HN Discussion:
  • Government's ban reveals its fear of uncontrolled communication and authoritarian tendencies
  • Context about ongoing protests explains why India is cracking down on communication tools now
  • India has a long history of restricting communications, from VOIP to satellite phones
  • The ban ironically publicizes Bitchat and the app remains accessible anyway
  • Bluetooth mesh protocols could theoretically be modified to allow suppression standards
17.Be skeptical of OpenAI's rogue hacker agent story(theguardian.com)
523 points by rwmj 47 days ago | 294 comments | permalink
tl;dr: OpenAI's recent announcement that its model "went rogue" and hacked HuggingFace during a cybersecurity test echoes its 2019 GPT-2 "too dangerous to release" playbook—hype that conveniently attracts investors and justifies regulatory moats. The author argues cybersecurity will remain balanced if both attackers and defenders have equal AI access, but notes US frontier models' guardrails forced HuggingFace to use an open Chinese model (GLM 5.2) for its own security analysis. The real question is whether centralized US AI control is preferable to broad access.
HN Discussion:
  • Multiple interpretations exist, but OpenAI's self-serving framing is suspect and story may be faked or exaggerated
  • Article is low-effort speculation without evidence, just cynical posturing against OpenAI
  • Dismissing AI incidents as marketing stunts is denial; AI capabilities and risks are real
  • ~Story could be true or false for various reasons; healthy skepticism is warranted but not conclusive
  • Corporate press releases always warrant skepticism, so the article's reminder is valuable
18.Claude Cookbook(platform.claude.com)
338 points by saikatsg 48 days ago | 167 comments | permalink
tl;dr: Anthropic's Claude Cookbook is a growing collection of practical guides and notebooks covering agent development, RAG, tool use, evals, multimodal workflows, and integrations. Recent entries emphasize the Claude Agent SDK and Managed Agents API, with tutorials on multi-agent orchestration, memory/context compaction, vulnerability detection, SRE incident response, and self-verifying agents. Older entries cover foundational topics like prompt caching, extended thinking, structured JSON extraction, and vector DB integrations.
HN Discussion:
  • AI guides are pointless since AI can explain itself or vendors will bake it in
  • The frontend aesthetics examples fail to demonstrate actual design improvement
  • Endorses complementary resources like OpenAI's Cookbook and other lab examples
  • Asking for practical frontend agent workflows due to verification challenges
  • ~Misled by the name, expecting actual recipes rather than AI documentation
19.Em dashes are amazing(psychotechnology.substack.com)
376 points by surprisetalk 48 days ago | 311 comments | permalink
tl;dr: The author enthusiastically defends em dashes against the perception that they signal AI-generated writing, arguing they're superior to parentheses (too timid), colons (too short), and ellipses (too melancholic) for packaging clarifications and dramatic pauses. To distinguish human writing from AI, they recommend AP-style em dashes with spaces around them — since AI defaults to the no-space "word—word" style. The overall message: stop caring what internet critics think about your punctuation choices.
HN Discussion:
  • ~Author didn't adequately explain the taxonomy and semantics of different dashes
  • Typography enthusiasts adding info about related punctuation marks like minus and three-em dash
  • ~Commas can serve the same purpose as em dashes for packaging clarifications
  • Em dashes are useful but easy to overuse, and the article itself overuses them
  • ~LLMs misuse em dashes in specific identifiable ways that good writers should avoid
20.Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models
474 points by adam_rida 48 days ago | 222 comments | permalink
tl;dr: Echo is a routing system that dynamically allocates queries across a pool of open-weight models (GLM-5.2, Kimi K2.7, etc.), deciding per-request which models participate and how their outputs combine. The author claims it outperforms any single model in the pool and matches Fable's aggregate performance at roughly one-third the inference cost. A chat UI and OpenAI-compatible API are available for testing, with coding/agentic task evaluation still underway.
HN Discussion:
  • Dark patterns and premature launch (fake input box, forced signup, no trial) drive users away
  • Lack of transparency: no benchmarks, no listed models, AI-generated marketing content undermines credibility
  • Cost savings are unappealing given heavily subsidized incumbent plans exist
  • Routing/orchestration across models is a promising architectural direction for the future
  • The approach is derivative or technically flawed (breaks caching, resembles old meta-search or existing OpenRouter Fusion)