Aug 23Monday, August 24, 2026 · all daysAug 25 · today »
1.Everything I own, owned(schlarp.com)
1419 points by schlarpc 17 days ago | 347 comments | permalink
tl;dr: Turning Claude loose on the firmware of five USB and WiFi peripherals, and finding a command shell in a microphone, a defeatable webcam activity LED, and unauthenticated memory writes over the network...
HN Discussion:
  • Sharing personal experiences of reverse engineering and modifying their own hardware
  • LLMs/AI agents dramatically lower the barrier to reverse engineering and firmware hacking
  • ~Regulations and manufacturer security measures increasingly prevent true ownership of devices
  • ~Concern about security risks when firmware can be silently modified (e.g., disabling camera LEDs, WebUSB backdoors)
  • Author hasn't gone far enough - without working patches applied, the device isn't truly owned
2.Anthropic's best AI model struggles to attract users as cheaper tools thrive(ft.com)
808 points by naves 17 days ago | 698 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Anthropic's confusing pricing and monetization strategy is driving users away
  • Claude's writing style and quality issues make it unpleasant to use
  • Overly restrictive security guardrails push users to competitors like OpenAI
  • Claude/Opus is still the best coding model available despite the negativity
  • Enterprise deployment barriers like lack of zero data retention limit adoption
3.How I find problems to solve as a staff engineer(lalitm.com)
573 points by vanpra 17 days ago | 168 comments | permalink
tl;dr: A staff engineer at Google (working on Perfetto) describes finding high-impact problems by passively absorbing complaints and requests across teams, then letting them accumulate rather than jumping on the first vocal request. The key skill is spotting the common underlying shape across seemingly unrelated requests—then pressure-testing the hypothesis via prototypes, RFCs, and conversations before committing to build. Solving real problems compounds: it earns trust and pulls the engineer into more conversations, widening their view of the org.
HN Discussion:
  • Big Tech promotion incentives reward visibility and empire-building over real impact
  • ~This approach only works in bottom-up environments, which are becoming rarer
  • In startups problems are abundant; the real skill is prioritization, not discovery
  • Genuine Staff engineers naturally do this work already; asking how reveals unfitness for the role
  • ~Balancing time spent understanding others' problems vs shipping code is genuinely difficult
4.Google Workspace thinks my domain is an email provider (2025)(blog.elis.cc)
380 points by el1s7 17 days ago | 149 comments | permalink
tl;dr: Google Workspace's signup page blocks legitimate domains because a frontend regex list flags anything matching patterns like `web\..*` or `me\..*` as an "email provider" — affecting even the Ukrainian Ministry of Economy's me.gov.ua domain. Google support was useless, suggesting the author switch domains rather than fix the bug. The author bypassed it by disabling the client-side validation function in the browser, since the check isn't enforced server-side. The issue reportedly still exists as of August 2026.
HN Discussion:
  • Google's support is broadly broken and treats users poorly across many products
  • Similar validation/domain issues occur elsewhere, confirming this is a widespread pattern
  • This bug likely stems from lazy product engineering that deprioritizes low-impact fixes
  • Automated decisions with unaccountable human defenders create a dystopian user experience
  • Adds contextual/historical information about domains and TLD pricing issues
5.My agent.md to improve LLM-assisted code quality(fabiensanglard.net)
398 points by ibobev 17 days ago | 172 comments | permalink
tl;dr: The author shares their `agent.md` file—a set of coding style rules automatically injected into LLM coding sessions—to enforce consistent code quality without repeating instructions each session. The rules cover things like avoiding magic numbers, keeping functions short, using enums over booleans, respecting layered architecture, and writing proper commit messages. They also note context dilution as a limitation, mitigated by starting fresh sessions per feature or asking the agent to reload the file.
HN Discussion:
  • ~Many of these rules should be enforced by linters rather than LLM instructions
  • Rigid rules backfire because LLMs over-apply them and produce non-idiomatic code
  • ~Coding standards belong in a separate file loaded on-demand, not in AGENTS.md polluting context
  • Most of these rules are unnecessary fluff; agent instructions should be learned per-project from experience
  • Context dilution makes large agent.md files potentially ineffective for buried instructions
6.What Is a Harness?(earendil.com)
571 points by tosh 18 days ago | 179 comments | permalink
tl;dr: An agent harness is software that wraps an AI model to create an agent, typically providing four things: a system prompt, a set of callable tools, an "agentic loop" letting the model iteratively decide actions, and a translation layer for swapping between different models. Unlike the models themselves, users can own, modify, and run harnesses locally—preserving agency, choice, and portability across providers. The author pitches Pi, their open-source harness, as a neutral alternative to lab-controlled apps like Claude Code.
HN Discussion:
  • Shares personal experience building harnesses, endorsing their value especially with internal CLIs
  • Praises Pi harness and predicts harnesses will be the main value layer once models commoditize
  • Offers alternative analogies (chassis/engine, backpack) to explain harnesses more clearly
  • Skeptical that 'harness' is just the next hype buzzword replacing 'agent'
  • Disagrees with the definition, arguing harness traditionally means a CI/test system
7.How Complex Systems Fail (1998)(how.complexsystems.fail)
372 points by shortcrct 18 days ago | 77 comments | permalink
tl;dr: Richard Cook's classic essay argues that complex systems (healthcare, aviation, power) are inherently hazardous and always run in a degraded mode with latent failures; catastrophes require multiple small failures to align, not a single "root cause." Human operators are the adaptive element that continuously creates safety by gambling under uncertainty, though hindsight bias causes investigators to unfairly label their actions as errors after accidents. Safety is an emergent property of the whole system, not a component that can be added, and post-accident fixes often increase complexity and introduce new failure modes.
HN Discussion:
  • Endorses the paper as essential reading for understanding real-world complex system failures and root cause fallacies
  • Shares practical experience confirming systems run in degraded mode kept alive by human operators
  • Suggests engineering practices like Chaos Engineering as applications of the paper's insights
  • Recommends complementary works and frameworks (Normal Accidents, Safety II, Systemantics) that extend the argument
  • Extends the article's warning to other domains like economics where safeguards have been stripped for efficiency
8.Malware infects Android-based automotive head unit firmware(securelist.com)
262 points by campuscodi 18 days ago | 140 comments | permalink
tl;dr: Kaspersky discovered Android malware distributed via the legitimate update mechanism of DoFun automotive head unit firmware — the first documented case of malware with an infection chain specific to car head units. The multi-stage downloader ultimately deploys a reverse proxy module ("zhima") to enlist infected devices into a residential proxy botnet, and also supports ad fraud commands. Researchers attribute the campaign with high confidence to MoYu Group, an actor linked to the BADBOX botnet, based on code naming conventions and infrastructure overlap with residential proxy services like PXYEDGE and ProxyForU.
HN Discussion:
  • ~Clarifies the malware is limited to cheap Chinese head units via official OTA, not a broader Android threat
  • Worries about escalation risks like lateral spread to phones or exploitation of CAN bus access to cause crashes
  • Views this as an inevitable consequence of the automotive industry's poor security practices
  • Speculates about downstream uses of the botnet, such as selling proxies for AI scraping or click fraud
  • Questions the attack chain mechanics, e.g. whether attackers had to compromise update servers
9.My favorite nonfiction books about cults, scams, and schemes(bookdna.com)
274 points by bwb 18 days ago | 122 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Recommending additional books on cults, scams, and schemes to complement the list
  • Sharing frameworks and definitions for identifying cults and authoritarian control
  • Endorsing specific books mentioned by the author with personal insights
  • ~Criticizing Michael Lewis's SBF book as damaging to the author's credibility
  • Highlighting institutional failures like the SEC ignoring Madoff whistleblowers
10.A website for debloated open source alternatives(debloat.dev)
390 points by ryanvogel 17 days ago | 124 comments | permalink
tl;dr: A curated directory catalogs open-source, "debloated" replacements for proprietary vendor software, spanning categories like printer drivers (Gutenprint), photo management (Immich), media servers (Jellyfin, Kodi), home automation (Home Assistant, ESPHome), and keyboard firmware (QMK). Entries include license info, user ratings, and community discussion counts, with most popular picks skewing toward self-hosted alternatives to cloud services and vendor lock-in tools.
HN Discussion:
  • ~Similar existing alternatives like alternativeto.net already serve this purpose well
  • Praise for the site's fast, lightweight, well-designed implementation
  • Questions the definition of 'debloated' since listed apps like Nextcloud aren't lightweight
  • Criticism of site's access barriers like Google/GitHub-only login and Firefox SSL errors
  • Broader reflection on software bloat, performance as a feature, and declining media center options
11.Over 170k Nonprofits Lost All Their Data. Is Microsoft to Blame?(slate.com)
291 points by tchalla 17 days ago | 152 comments | permalink
tl;dr: Microsoft retired its free Business Premium nonprofit grant program in mid-2025, and roughly 171,000 small NGOs reportedly had their OneDrive data permanently deleted, with many claiming they received little or no advance warning beyond notices sent to rarely-checked admin email accounts. Microsoft says it notified customers and advised migration to paid tiers, but affected nonprofits—many operating on sub-$1M budgets that relied on the grant for ~30% of IT spend—are now scrambling to rebuild lost files and find affordable alternatives. Critics suspect the move ties to Microsoft's cost-cutting and storage demands amid its AI buildout.
HN Discussion:
  • Microsoft should have used a brownout or read-only period instead of hard deletion
  • ~Admins receive constant alerts causing fatigue, so notification claims are weak justification
  • Microsoft has become an untrustworthy, unserious company
  • Notifications were actually sent multiple times and not caught by spam filters
  • ~Organizations shouldn't rely on cloud services or corporate generosity for critical data
12.To become a better writer, read as much as you can(nappertime.com)
470 points by andsoitis 18 days ago | 261 comments | permalink
tl;dr: A published author argues the one universal rule for aspiring writers is to read voraciously and widely, dismissing the common excuse of being "too busy" when most people spend hours daily on their phones. Reading teaches craft through osmosis, provides inspiration (especially cross-genre), and physically rewires the brain for the sustained focus and imagination writing requires—whereas digital addiction does the opposite. He also takes a swipe at generative AI users as people who "like the idea of making art" without actually loving the form.
HN Discussion:
  • Reading is essential to writing; writers who don't read are baffling
  • Writing practice itself matters more than reading for improving craft
  • ~Reading is valuable but must be done critically/consciously to improve writing
  • ~The advice applies to literary fiction but conflates it with genre/oral storytelling traditions
  • Immersion in a medium naturally shapes your output through osmosis, for better or worse
13.Wi-Fi 8 is the first wireless upgrade in years that isn't chasing speed(xda-developers.com)
343 points by taubek 18 days ago | 286 comments | permalink
tl;dr: Wi-Fi 8 (IEEE's "Ultra High Reliability" standard, expected to finalize in 2028) abandons the traditional speed race, keeping the same 23Gbit/band max throughput, modulation, and bandwidth as Wi-Fi 7. Instead, it targets a 25% improvement in effective throughput under poor signal conditions, 25% lower latency at the 95th percentile, and 25% fewer MPDU losses through features like Distributed-tone resource units, interference mitigation pilots, unequal modulations, and seamless AP roaming. The focus shift addresses real-world congestion from proliferating smart home devices rather than chasing theoretical peaks most users can't utilize anyway.
HN Discussion:
  • Real-world reliability and roaming matter more than theoretical peak speeds
  • Speed upgrades are useless for most users due to walls, distance, and device limitations
  • ~New WiFi standards are pointless when most client devices can't use the features
  • WiFi should be replaced/merged with cellular 5G/6G standards instead
  • The industry should prioritize open-source drivers and IoT-friendly cheap chips over new standards
14.I gave Qwen 3.8 27B a reverse-engineering job and it finished in 30 minutes(xda-developers.com)
359 points by raybb 18 days ago | 148 comments | permalink
tl;dr: Running locally on a 128GB Nvidia GB10 workstation, Qwen 3.8 27B reverse-engineered a commercial app's license check in about 30 minutes using purely static analysis, recovering a deliberately obscured RSA public key and producing a working authentication bypass. Notably, it caught its own incorrect first reconstruction (a mismatched integrity hash) and self-corrected without prompting. The author argues this marks a real shift: capabilities once reserved for frontier cloud models now fit on a consumer GPU, with all the privacy and threat-model implications that entails.
HN Discussion:
  • Modern models' self-correction behavior on integrity mismatches is a real emerging pattern
  • Testable true/false tasks aren't the hardest real tasks, so the demo overstates difficulty
  • ~Local models are promising but crippled by built-in refusals that only hurt legitimate users
  • Future lies in frontier models orchestrating good-enough local models for daily tasks
  • Skepticism about the model's actual capabilities based on personal benchmarks and failed use cases
15.Why your local LLM feels dumber than it is(forum.level1techs.com)
501 points by felineflock 18 days ago | 202 comments | permalink
tl;dr: Local LLM inference is nondeterministic across setups because attention backends, quantization schemes, and CUDA kernels each introduce numerical divergences that cause different next-token choices—divergences that cluster around specific prompt content rather than growing smoothly with context length. Benchmarking Qwen3.6-27B on an RTX PRO 6000, the author found INT4 KV-cache quantization broke tool calls after ~40k tokens, and NVIDIA's NVFP4 quant flipped ~50% of top tokens by 88k context, while W8A16 INT8 outperformed even the official FP8 release.
HN Discussion:
  • Peripheral implementation details like parsers can silently degrade LLM output, reinforcing the article's thesis
  • Avoid KV cache quantization and aggressive weight quantization to preserve model quality
  • Quantized KV caches require quantization-aware training to work properly, adding technical nuance to the article
  • Local models feel surprisingly capable and comparable to hosted models, downplaying the article's concerns
  • Programs need health checks and assumption validation since numerical correctness issues aren't unique to LLMs
16.Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces (2025)(arxiv.org)
315 points by nunodonato 22 days ago | 267 comments | permalink
tl;dr: This ICML 2026 position paper argues that calling intermediate tokens generated by LLMs "reasoning" or "thinking traces" is a harmful anthropomorphization rather than a harmless metaphor. The authors contend these traces don't actually reflect human-like problem-solving steps and shouldn't be treated as interpretable windows into model cognition, warning that this framing misleads both users and researchers. They call on the community to abandon such language to avoid questionable research directions and misuse of these models.
HN Discussion:
  • Anthropomorphization concern is overblown; researchers know it's just a metaphor and humans naturally anthropomorphize things
  • Intermediate tokens are better understood mechanically as search/annealing/scratch space rather than reasoning
  • Traces shouldn't be treated as interpretable windows; focus on reproducibility and treating them as black boxes
  • LLM outputs increasingly resemble human thinking, so anthropomorphizing is natural given our ignorance about cognition
  • Prescriptive terminology policing in academic titles is off-putting and unwarranted given practical results
17.Canada will match US tariffs 'dollar for dollar' as trade talks break down(bbc.com)
719 points by tartoran 19 days ago | 1658 comments | permalink
tl;dr: US-Canada trade talks collapsed Friday night after PM Mark Carney rejected last-minute US changes he called "unfair and uneconomic," triggering new 50% US tariffs on roughly 5% of Canadian exports including wine, dairy, cement, and clothing. Carney pledged dollar-for-dollar retaliation, ending negotiations that had been close to reducing tariffs on steel, aluminum, and autos. Analysts estimate the new tariffs could cut Canadian GDP by 0.3% to 0.6%, with Ontario, Quebec, and British Columbia most exposed.
HN Discussion:
  • Canada's dollar-for-dollar retaliation is the correct response to US tariff aggression
  • ~Other countries (EU, Japan, Korea) should have collectively resisted rather than caving individually
  • US demands went beyond tariffs into cultural/sovereignty issues like French labeling and streaming content
  • US is breaking trust in trade relationships, causing long-term damage and pushing Canada toward China
  • Weary acceptance that the trade drama is out of Canada's control and pain is inevitable
18.Scrap (2006)(twitter.com)
418 points by tosh 18 days ago | 227 comments | permalink
tl;dr: A 2006 journal entry recounts renovating a wrecked house in Pittsburgh during brutal winter, where the author learned that local "scrappers" hunt raw metals rather than furniture—a cast-iron tub left outside vanished within 24 hours. Later, two aging, half-deaf scrappers named Ron and Wade helped haul out a broken furnace, resulting in a chaotic ordeal involving claustrophobia, an axe, and the author pushing a 250lb man over the furnace to escape the stairwell. Their payoff: four cents a pound for steel.
HN Discussion:
  • Confirms Pittsburgh scrapping culture persists with personal anecdotes
  • ~Warns against helping with risky physical labor like the author did
  • Nostalgia for personal blog writing that this post exemplifies
  • Scrapping is driven by lifestyle and meaning, not just money
  • Provides broader context on scrap economics (copper theft, plastics)
19.Hister – A private, full content search index that you control(hister.org)
490 points by auraham 22 days ago | 98 comments | permalink
tl;dr: Hister is a self-hosted, AGPLv3-licensed search engine that indexes the full content of pages you visit, local files, browser history, and crawled sites, keeping everything on a server you control with no telemetry. It supports ingestion via browser extensions, file watchers, and crawlers, and exposes the index through a web UI, CLI, HTTP API, and MCP server for AI assistants. It runs as a single binary with SQLite or PostgreSQL, offers a query language with field filters, wildcards, and aliases, and supports optional semantic search via an embeddings endpoint of your choice.
HN Discussion:
  • Author introduces the project and its motivations behind moving beyond metasearch
  • Users share successful real-world setups using Hister for research and note indexing
  • Users prefer Hister over alternatives like Karakeep but want mobile/sharing features added
  • ~Concerns about missing authentication making indexed content insecure on local networks
  • Questions about technical details like semantic chunking, crawling scale, and third-party integrations
20.I spent $266 and four AI models to own my tablet. GLM-5.3 finished it in a day(ericpardee.github.io)
684 points by dr_pardee 18 days ago | 289 comments | permalink
tl;dr: After Amazon's software repeatedly shut down his Fire HD 10 kiosk tablet, the author spent five months and $266 using multiple LLMs to root it. Claude and OpenAI's models refused on safety grounds, but Chinese models Kimi K3 and GLM-5.2/5.3 identified an unpatched 2022 Mali GPU CVE, built a working exploit, and ultimately removed 100 Amazon packages—with GLM-5.3 finishing the job in a single day. The piece argues that frontier security capability is now rentable by anyone with a credit card and patience, while highlighting the widening gap between US and Chinese models on cybersecurity assistance.
HN Discussion:
  • AI agents amplify existing expertise rather than replace it, validating the article's premise about rentable capability
  • Unleashing AI models to reverse engineer hardware for open-source support is a promising future direction
  • ~The writeup has an off-putting AI-generated tone but the core finding about model capabilities is valid
  • ~Chinese models miss obvious failure points that Claude/Codex catch, complicating the article's framing of Chinese model superiority
  • Without source code and reproducibility, the exploit claims are hard to verify