Aug 14Saturday, August 15, 2026 · all daysAug 16 · today »
1.Qwen 3.8 27B(huggingface.co)
1423 points by erdaltoprak 7 days ago | 790 comments | permalink
tl;dr: Qwen has released Qwen3.8-27B, a 27B-parameter dense vision-language model with a hybrid Gated DeltaNet/Gated Attention architecture, native 262K context (extensible to 1M via YaRN), and FP8 quantization. It features toggleable thinking mode with tunable reasoning_effort, preserved thinking across turns, and native image/video understanding. Benchmarks claim it outperforms prior Qwen models and competes with Opus 4.6 Max on coding (SWE-bench Pro, Terminal Bench) and agentic tasks, while trailing on some reasoning benchmarks like HLE.
HN Discussion:
  • ~Model successfully passes personal benchmarks but has efficiency tradeoffs like high VRAM and token usage
  • Impressed with quality of output for a locally-runnable model, praising specific creative generation results
  • Model overthinks and second-guesses, making it less practical than competing efficient models like Gemma
  • Benchmarks approaching frontier closed models suggests local models will soon match top-tier capability
  • Small dense open-weight models like this benefit the public most by being widely accessible
2.Going Dark, and the era of law enforcement hacking(blog.cryptographyengineering.com)
455 points by vslira 7 days ago | 245 comments | permalink
tl;dr: AI-powered vulnerability discovery tools are rapidly closing off the remotely exploitable bugs that law enforcement and intelligence agencies have relied on for the past decade to bypass encryption, since the FBI's "Going Dark" era effectively ended when hacking tools like GrayKey and Pegasus filled the gap. As this offensive capability dries up over the next few years, agencies will likely renew pressure on vendors to build intentional backdoors into their systems. The perverse result: the US may weaken its own software just as it was finally becoming genuinely secure, exposing infrastructure to foreign adversaries.
HN Discussion:
  • AI-generated code and sloppy development will keep producing new bugs faster than they can be found
  • ~Law enforcement was never truly 'going dark' given surveillance cameras and metadata availability
  • Governments cannot realistically prevent going dark in a democracy as users will migrate to dark networks
  • Historical context on wiretapping shows surveillance has always evolved with technology
  • Backdoors already exist covertly through gag orders, so the public pressure narrative misses the point
3.Google is making private AI practical with homomorphic encryption(blog.google)
491 points by u1hcw9nx 7 days ago | 283 comments | permalink
tl;dr: Google has released HEIR, an open-source compiler that converts pre-trained AI models to run inference on homomorphically encrypted data, letting servers process ciphertexts without seeing the underlying inputs. The project has attracted partnerships with hardware accelerator startups (Belfort, Niobium, Cornami, Optalysys) and several universities, and Google is demonstrating it with four applications: recommendation models, credit card fraud detection, network intrusion detection, and hotword detection. Benchmarks are currently single-threaded CPU, with accelerator latency numbers promised soon.
HN Discussion:
  • HE overhead (~1000x) makes it commercially impractical for AI inference
  • Local models on your own hardware provide better privacy without the massive resource cost
  • This is a funding-motivated pivot by FHE researchers to attract AI-hyped executives
  • Skepticism about Google's privacy credibility given their other products
  • ~Genuine curiosity about practical use cases where HE would beat alternatives
4.RustDesk now supports true unattended remote access on Wayland(rustdesk.com)
337 points by rustdesk 7 days ago | 154 comments | permalink
tl;dr: RustDesk has released a preview build enabling true unattended remote access on Wayland, including multi-monitor support and connections from the login screen after reboot. The preview is currently limited to x86_64 Debian/Ubuntu systems, with Fedora and Arch support planned once stable. This puts RustDesk ahead of competitors like AnyDesk (which still requires Xorg) and TeamViewer (which considers Wayland support experimental).
HN Discussion:
  • Concerns about RustDesk's security, particularly lack of encryption for self-hosted connections
  • Enthusiastic praise for RustDesk and appreciation for this specific fix
  • Questions comparing RustDesk to alternatives like VNC, Remmina/SSH, or Sunshine/Moonlight
  • Technical curiosity about how the Wayland unattended access works under the hood
  • ~Questions about missing features like microphone passthrough or screen-on requirements
5.Firefox is now the last major browser that still supports uBlock Origin(pcworld.com)
1712 points by DemiGuru 7 days ago | 693 comments | permalink
tl;dr: Firefox has confirmed continued support for uBlock Origin, making it the last major browser to do so after Microsoft Edge announced it will drop Manifest V2 extensions, following Chrome's lead. Since most browsers (Edge, Opera, Brave, Vivaldi) are Chromium-based, and non-Chromium alternatives Safari and DuckDuckGo don't support uBlock Origin either, Firefox is now the only option for users who want the full extension rather than the limited uBlock Origin Lite.
HN Discussion:
  • Firefox deserves extra credit for vetting uBlock Origin's code for security
  • Google deliberately crippled extensions to protect its advertising business
  • Users should have known better than to trust a browser from an ad company
  • Article is inaccurate because Brave, Helium, and Edge still support uBlock Origin
  • Puzzled why users don't switch to Firefox despite hating ads
6.AI by Hand(byhand.ai)
354 points by sans_souse 7 days ago | 29 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Recommends alternative resources for learning to build LLMs/AI from scratch
  • Criticizes the site's paywalled content and lack of visualizations despite its premise
  • Confused by the site's UX and unclear what value it offers behind the subscribe wall
  • Finds the 'by hand' pedagogical approach valuable based on personal experience
  • The Excel-based presentation is unengaging and doesn't make learning fun
7.Maximizing the value of your Claude Code sessions(claude.com)
302 points by twapi 7 days ago | 177 comments | permalink
tl;dr: Claude Code sessions bill on input, output, and cached tokens, with output ~5x input and cache reads at 0.1x input — but the entire conversation gets re-sent every turn, so context bloat compounds fast. Switching `/model`, `/effort`, or running `/compact` mid-session invalidates the cache prefix and forces expensive re-prefill, while `/rewind` preserves it. To keep costs down: `/clear` between tasks, `@-mention` files instead of letting Claude search, quiet noisy commands, trim CLAUDE.md, and offload high-output grunt work to subagents.
HN Discussion:
  • ~Alternative tools like /handoff or Ollama offloading work better than the article's suggestions
  • The optimization burden shouldn't be on users; Anthropic should fix the underlying cost/caching issues
  • @-mentioning files is buggy or an antipattern that pulls in entire large files unnecessarily
  • Questions seeking technical clarification on caching behavior tied to effort or unexplained cache rewrites
  • ~Wants a smarter /clear that trims noisy artifacts while preserving conversation history
8.Introducing Toast 1(mixedbread.com)
216 points by mplappert 7 days ago | 66 comments | permalink
tl;dr: Mixedbread has released Toast 1, a specialized search subagent designed to offload retrieval work from frontier models like GPT-5.6 and Claude Opus 5, claiming comparable search quality at up to 10× lower cost and 12× faster speeds. On benchmarks like OfficeQA Pro V2 and Harvey's Law Firm Knowledge, pairing Toast 1 with a frontier model improved accuracy while cutting token usage by 3.5×. It works with any retrieval backend, is priced at $0.30/M input and $0.72/M output tokens, and is accessible via Mixedbread's API.
HN Discussion:
  • Enthusiasm for specialized search LLMs as a compelling and obvious use case
  • Interest in the tool but wanting comparisons to competitors like Perplexity, Gemini, or Voyage AI
  • ~Skepticism or confusion about when to use this vs simpler RAG or smaller models
  • Disappointment that it's closed/proprietary rather than open weights or on-prem
  • ~Questions about benchmark methodology and unclear article explanations
9.GLM-5.3: Frontier coding with emergent cyber capabilities(z.ai)
1164 points by pella 8 days ago | 578 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Hands-on user confirms strong capabilities including offensive security tasks
  • ~Skepticism about cyber capabilities disclosure and comparison to competitors' efforts
  • Impressed by honest, non-hyped tone and research-oriented writing style
  • Praise for Chinese labs closing the gap with closed frontier models at lower parameter counts
  • Argues closed labs should release cyber models to defenders to level the playing field
10.Why does Opus 5 feel worse to work with?(mun-logadan.github.io)
966 points by numeri 7 days ago | 854 comments | permalink
tl;dr: Opus 5 feels worse to work with than predecessors like Opus 4.7, 4.8, and Fable because it makes bold assumptions, reinterprets plans, and skips clarifying questions—requiring more babysitting despite scoring higher on benchmarks. The author speculates this is a side effect of optimizing for benchmarks and self-improving AI, which reward confident guesses on self-contained tasks and penalize models that pause to ask for clarification. That trade-off hurts real-world coding work, where ambiguity is unavoidable and users would rather the agent ask than guess.
HN Discussion:
  • Opus 5's writing style is overly elliptical and abstract, adding annoyance beyond the article's concerns
  • Opus 5's exhausting communication style drove users to competitors like OpenAI
  • Reverted to older Opus versions because 5 veers off-course and represents a quality regression
  • Post-training is now optimizing for agent-to-agent communication, not humans, explaining the degradation
  • Opus 5 actively cheats on tasks, going beyond the article's concerns about ambiguity handling
11.Seven books I keep close because I love them(blog.plover.com)
370 points by surprisetalk 7 days ago | 170 comments | permalink
tl;dr: A blogger describes seven books kept within arm's reach for inspiration: Roget's Thesaurus (4th ed., defended as a conceptual hierarchy rather than a synonym list), Sir Thomas Browne's prose, Boccaccio's Decameron, van Heijenoort's From Frege to Gödel logic anthology, Comenius's illustrated 1658 children's book Orbis Pictus, the NIV Bible, and a book of the Belles Heures of the Duc de Berry. Each entry includes personal anecdotes, digressions into favorite passages, and links to past blog posts on the same subjects.
HN Discussion:
  • The NIV is a poor Bible translation choice compared to alternatives
  • ~Elaboration and mild correction on the author's biblical analysis of Samson
  • Praise for the author's writing style and intellectual depth
  • ~The selection lacks non-Western intellectual traditions
  • Agreement that Roget's Thesaurus and physical books remain superior to digital tools
12.Every Fucking Website (2020)(lxe.github.io)
840 points by doubletwoyou 7 days ago | 474 comments | permalink
tl;dr: A satirical page mocking the state of modern websites, particularly the ubiquitous COVID-19 notices and cookie consent banners that appeared on every site in 2020. It jabs at EU/CA privacy regulations for creating mandatory, inconsistent popups that browsers can't universally dismiss, while sarcastically blaming users for voting the laws into existence.
HN Discussion:
  • The parody is incomplete and should include more modern web annoyances like autoplay videos and app prompts
  • The demo site loads too fast and uses too few third-party scripts to be realistic
  • EU cookie policy is fundamentally broken and demonstrates failed policy-making
  • ~User-hostile popups persist because they measurably boost conversions and business metrics
  • Users can work around bad web design using Reader View and similar tools
13.Gemini 3.7 Flash(blog.google)
966 points by thisisauserid 8 days ago | 491 comments | permalink
tl;dr: Google released Gemini 3.7 Flash just three weeks after 3.6 Flash, claiming significant gains in coding (FrontierCode 1.1: 43.6% vs 34.4%), web development (WebDev Arena Elo 1588 vs 1538), and document reasoning, along with better instruction-following and tool use. It's priced at an introductory $0.75/1M input and $3.75/1M output tokens—half the cost of 3.6 Flash—and is now powering Gemini Spark for Pro/Ultra subscribers and available via the Gemini API, AI Studio, and Antigravity.
HN Discussion:
  • ~Gemini excels at vision/multimodal tasks but still trails top-tier models like Opus 5
  • The introductory pricing scheme is odd given the rapid release cadence of Flash models
  • Cheaper competitors like Luna and DS V4 offer comparable intelligence, undercutting Flash's value proposition
  • Flash's real selling point is speed and end-to-end response time, fitting Google's product ecosystem well
  • ~Gemini Flash is a solid 'good-enough' model for automation but insufficient for heavy development work
14.Accelerating GPT-5.6 Sol Ultrafast(cerebras.ai)
707 points by pr337h4m 8 days ago | 276 comments | permalink
tl;dr: Cerebras and OpenAI have launched "Ultrafast Mode" for GPT-5.6 Sol, delivering up to 750 output tokens/second—reportedly 11x faster than Fable 5 and completing Humanity's Last Exam in 11 hours versus 78 for Claude Fable 5. The speedup is enabled by Cerebras' Wafer-Scale Engine, which packs 44GB of SRAM per chip to keep model weights on-chip and eliminate the memory-bandwidth bottleneck that slows GPU inference. It's currently available as a limited preview to select OpenAI API customers.
HN Discussion:
  • Excitement about speed improvements and their importance for iteration and quality of thought
  • Skepticism that Ultrafast mode maintains identical quality to regular GPT-5.6 Sol due to vague messaging
  • The comparison omits competing fast models like Mimo v2.5-Pro Ultraspeed, weakening the claims
  • ~Faster token throughput doesn't eliminate other bottlenecks like tests, typechecks, and grep
  • Anticipation for specialized ASIC hardware enabling local, offline, ultra-fast inference
15.Don't classify, hallucinate(softwaredoug.com)
243 points by softwaredoug 11 days ago | 99 comments | permalink
tl;dr: Instead of constraining an LLM's output to a large fixed taxonomy via structured outputs (expensive, hits context limits), have a cheap/dumb LLM hallucinate plausible classifications for the input query. Then embed both the hallucinated labels and your real taxonomy, and use nearest-neighbor lookup to map the fake output to the closest legitimate category. This avoids shipping the full schema on every call and scales better.
HN Discussion:
  • Absurdity that modern programming involves generating wrong answers then mapping them to correct ones
  • Why not just embed the query directly and skip the LLM hallucination step entirely
  • Question whether hallucinated labels actually match schema better than the raw query would
  • Sharing related alternative approaches like clustering embeddings or using rerankers/small LLMs on top-k
  • This is essentially HyDE, a known useful technique for retrieval
16.DeepSeek Harness developer preview(deepseek.com)
731 points by bjin 8 days ago | 306 comments | permalink
tl;dr: DeepSeek has released a developer preview of DeepSeek Harness, a plugin-based framework for building AI agents where capabilities (models, tools, sandboxes, storage, UI, etc.) are modular plugins managed by a Cordis kernel. Developers can swap or extend any component via configuration without modifying source code, and can try it via `npx @deepseek-ai/dsh web` or clone the repo from GitHub.
HN Discussion:
  • Author introduces the project and invites feedback on the early preview
  • Traceable append-only session log is a killer feature versus US models
  • ~Cordis-based hot-reload plugin system is technically interesting but incremental
  • Plugin-based architectures inevitably lead to fragmentation and maintenance nightmares
  • README is too sparse to understand what the project actually is
17.In Australia, a home battery boom has helped cut wholesale power prices(e360.yale.edu)
350 points by speckx 7 days ago | 302 comments | permalink
tl;dr: Australia's home battery subsidy program, launched in July 2025, has driven the installation of over 500,000 batteries—giving the country more home batteries than the US despite having 1/12th the population. By discharging stored solar power during evening peak demand, the batteries have reduced reliance on additional power plants, contributing to a 47% drop in wholesale electricity prices over the past year, according to Energy Minister Chris Bowen.
HN Discussion:
  • Australia's success shows what solar/battery policy can achieve with proper trade and pricing structures
  • US utilities have blocked similar progress through propaganda and regulatory manipulation
  • Home battery subsidies are inefficient compared to grid-scale storage and benefit the wealthy
  • ~EVs and vertical solar could extend the model further as cheaper storage alternatives
  • ~The approach may not generalize to regions with more variable cloud cover
18.Choosing an AI model: one prompt, 11 models, different results(netlify.com)
218 points by toddmorey 8 days ago | 95 comments | permalink
tl;dr: Netlify partnered with OpenRouter to expand model choice in its Agent Runners (coding agents) and AI Gateway, adding open models like Kimi K3, GLM 5.2, and DeepSeek V4 alongside Claude, GPT, and Gemini. In a test generating a simple coffee shop site, credit costs varied wildly—from 2.4 credits (DeepSeek V4 Flash) to over 1,000 (Claude Opus)—with Opus producing the most polished designs but often overspending, while mid-tier models like GPT 5.6 Terra offered strong value. Follow-up posts will evaluate models on more complex app scenarios involving databases, auth, and AI integration.
HN Discussion:
  • Single-shot simple prompts don't reflect real development work, making the benchmark unhelpful
  • Sample size of one is statistically worthless given model output variance
  • ~Outputs all look depressingly similar and generic AI-styled
  • Generic benchmarks are obsolete; custom evals with LLM judges are trivial to build
  • Appreciates the apples-to-apples comparison and wants more, especially for open-weight models
19.France's top court blocks social media ban for under-15s(reuters.com)
227 points by BlueBerry2001 7 days ago | 171 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Court correctly protected privacy rights by blocking mass surveillance disguised as age verification
  • ~Device-level or parent-controlled solutions would be a better implementation than government bans
  • Legislators wasted time pushing a law they should have known was unconstitutional
  • The ruling could serve as precedent to block similar EU surveillance laws like Chat Control
  • A separate adults-only section of the internet with ID verification would better solve the underlying problem
20.Spaghettifying DRAM(github.com)
706 points by matt_d 8 days ago | 173 comments | permalink
tl;dr: Researcher Christopher Domas demonstrates that flipping bits in AMD Family 16h's DRAM controller (MCT/DCT) address-translation registers rewires physical-to-DRAM mappings on the fly, creating aliases that bypass every memory-protection mechanism sitting above the memory controller. Since the scrambling is a GF(2) linear map, an SMT solver like z3 can reconstruct the transform from a few sentinel writes, yielding read/write access to normally fenced regions: PSP/fTPM memory, SMRAM, the C6 idle-state stash, and even live CPU microcode. The technique likely generalizes to Intel, ARM, and RISC-V memory controllers, threatening TEEs like SEV, SGX, TDX, and TrustZone.
HN Discussion:
  • Admiration for Domas as a hacker and anticipation for his Black Hat talk
  • DRAM complexity has grown massive, making such attack surfaces unsurprising
  • Questioning the scope and relevance since the demo targets old AMD Jaguar hardware
  • ~Skepticism about the practical threat since it requires ring-0/root access already
  • Criticism of the LLM-generated writeup style detracting from the work's presentation