Jul 24Saturday, July 25, 2026 · all days
1.Android May Soon Restrict On-Device ADB(kitsumed.github.io)
312 points by shscs911 5 hours ago | 149 comments | permalink
tl;dr: A Google ADB maintainer has proposed restricting Android's ADB daemon to only bind to the wlan0 interface in response to CVE-2026-0073, which would break loopback (on-device) ADB connections used by tools like Shizuku, App Manager, and Termux-based workflows. The author, a Shizuku app developer, argues this would kill a legitimate ecosystem of power-user tools since malicious apps can't start ADBD or authenticate connections on their own, and suggests Google instead offer a persistent user-toggleable setting rather than a permanent block.
HN Discussion:
  • Attack vector is unrealistic since it requires developer mode and remote ADB, so restriction is unjustified
  • This is part of a broader trend of Android becoming increasingly locked down and user-hostile
  • Physical access threats from authorities and third parties justify some security concerns
  • Users should switch to Linux phones to escape platform lock-in
  • Sarcastic mockery of security-justification framing used to restrict power-user features
2.Claude Opus 5(anthropic.com)
1595 points by alvis 19 hours ago | 939 comments | permalink
tl;dr: Anthropic released Claude Opus 5, claiming state-of-the-art performance on coding and knowledge-work benchmarks (Frontier-Bench, ARC-AGI 3, OSWorld 2.0) at half the cost of their top "Fable 5" model, though it trails "Mythos 5" on cybersecurity exploitation tasks. Priced at $5/$25 per million input/output tokens (same as Opus 4.8), it emphasizes improved judgment, self-verification, and agentic reliability, and is now the default on Claude Max. Safety testing rates it their most aligned model yet, with relaxed cyber classifiers and optional automatic fallbacks for flagged requests.
HN Discussion:
  • Amazement at the pace of AI capability improvements becoming normalized
  • Values Opus 5's lack of data retention requirements as the key differentiator over Fable
  • Confirms Opus 5's improved real-world performance through hands-on testing
  • ~Criticizes persistent annoying writing style tics that Fable managed to shed
  • Anthropic's messaging and benchmark reporting is confusing or inconsistent
3.Hannah Fry Wins the Leelavati Prize in 2026 for Mathematics Outreach(maths.cam.ac.uk)
278 points by agnishom 10 hours ago | 48 comments | permalink
tl;dr: Professor Hannah Fry, the University of Cambridge's first Professor of the Public Understanding of Mathematics, has won the 2026 Leelavati Prize, awarded every four years by the International Mathematical Union for outstanding contributions to public awareness of mathematics. The prize adds to her prior accolades, which include the Christopher Zeeman Medal, the Royal Society's David Attenborough Award, an Emmy, and a Webby, earned through her books, TV programs, and podcasts.
HN Discussion:
  • Personal anecdotes praising her speaking talent and warmth as a communicator
  • Recommendations of her specific shows, podcasts, and lectures as excellent content
  • Admiration for her personal journey from Cambridge rejection to Cambridge professor
  • Recognition of her exceptional skill as a science/math communicator
  • Concern that algorithms may under-promote her content despite its quality
4.Postgres LISTEN/NOTIFY actually scales(dbos.dev)
318 points by KraftyOne 17 hours ago | 60 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)
309 points by aarondong 16 hours ago | 175 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)
620 points by sohkamyung 5 days ago | 177 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)
597 points by hhh 1 day ago | 202 comments | permalink
tl;dr: A researcher extracted the encrypted firmware of Hanwha Vision security cameras by reverse-engineering their `fwupgrader` binary (with Claude Code's help), recovering hardcoded AES keys shared across the model line. Inside the rootfs, a Vite build had dumped the entire CI environment—including an admin-level GitHub token with access to hundreds of repos—into ~30 UI files, alongside internal IPs belonging to DoD address space. Hanwha revoked the token within 12 hours of disclosure.
HN Discussion:
  • Isolate IP cameras on separate VLANs without internet access as a defensive practice
  • Vendor security practices are chronically poor with hardcoded credentials being common
  • ~The embedded DoD IP addresses are the more alarming finding than the token itself
  • Seeking open/supported firmware alternatives for IP cameras to avoid these issues
  • LLMs have made reverse engineering and defeating obfuscation trivial
8.Firefox Containers Preview(blog.mozilla.org)
366 points by twapi 3 days ago | 105 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)
231 points by Alifatisk 1 day ago | 68 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)
235 points by JumpCrisscross 9 hours ago | 111 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)
309 points by m0do1 23 hours ago | 60 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)
618 points by louiereederson 23 hours ago | 271 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)
303 points by thisislife2 1 day ago | 366 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)
283 points by kristoff_it 1 day ago | 183 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)
760 points by pchm 1 day ago | 582 comments | permalink
tl;dr: Despite AI coding tools promising higher productivity and quality, everyday software (banking apps, car infotainment, warranty forms) keeps getting buggier and more fragile as complexity grows and vendors prioritize KPI-driven features over stability. The author argues LLMs could fix bugs effectively, but companies won't dedicate cycles to it—leaving an opening for individual developers to build better alternatives as big-company software accrues AI debt.
HN Discussion:
  • Non-technical decision-makers and imposters drive product changes, ignoring power users and quality
  • Misaligned incentives and KPI-chasing promotions cause software degradation, not AI itself
  • Coding is far from solved; the premise of AI having solved coding is flawed
  • ~Software quality issues predate AI and stem from market incentives and inexperienced developer growth
  • ~AI speeds up code production but doesn't improve correctness, which still requires human time
16.Government orders GitHub to remove Bluetooth-based chat app Bitchat: Jack Dorsey(thehindu.com)
473 points by rootkea 21 hours ago | 346 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)
494 points by rwmj 20 hours ago | 282 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)
315 points by saikatsg 1 day ago | 159 comments | permalink
tl;dr: Anthropic's Claude Cookbook is a growing collection of practical notebooks and guides covering agent patterns, tool use, RAG, evals, multimodal workflows, prompt caching, fine-tuning, and integrations with services like Pinecone, LangChain, and ElevenLabs. Recent entries focus heavily on the Claude Agent SDK and Managed Agents—covering multi-agent orchestration, memory/context compaction, self-verifying outcomes, SRE and vulnerability-detection agents, and production deployment patterns. Older recipes cover fundamentals like JSON extraction, SQL generation, vision, classification, and summarization.
HN Discussion:
  • AI usage guides and agentic workflow resources are pointless theatre since AI can explain itself
  • The frontend aesthetics examples show no real improvement, undermining the cookbook's credibility
  • Appreciates the resource and points to similar cookbooks from other AI labs
  • Frontend coding with agents remains problematic and seeks better workflows
  • Misread the title expecting actual food recipes, showing naming confusion
19.Em dashes are amazing(psychotechnology.substack.com)
358 points by surprisetalk 23 hours ago | 297 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
459 points by adam_rida 1 day ago | 218 comments | permalink
tl;dr: Echo is a router 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 are combined. On the author's evals, it outperforms any single model in the pool and matches Fable's aggregate quality at roughly one-third the inference cost. A chat UI and OpenAI-compatible API are available for testing, with coding/agentic workloads still a work in progress.
HN Discussion:
  • Dark patterns and forced signup without a try-first option drive users away immediately
  • Lack of transparency: no benchmarks, no listed models, feels like an advertisement rather than a Show HN
  • Routing across specialized models is the future architecture, validating the approach
  • Cost claims are unappealing compared to subsidized flat-rate subscription plans
  • Round-robin routing breaks prompt caching and may actually increase real-world costs