← Oct 31Sunday, November 1, 2026 · all days
1.HackerTube: YouTube built from videos recommended by HN(karpathy.bearblog.dev)
1511 points by karpathy 17 hours ago | 405 comments | permalink
tl;dr: Karpathy, frustrated by YouTube's "enshittified" recommendations, used Claude Opus 5.5 to build HackerTube.org—a YouTube clone populated with 6,454 videos recommended across 40K Hacker News comments from 2007-2026, organized into 150 topics with custom ForYou recommendations and no user accounts. The entire project took ~2 hours, with Karpathy only manually handling the API key, VPS setup, and domain purchase while Claude Code did the rest, including deployment and hardening.
HN Discussion:
  • ↑Browsing HackerTube feels refreshing compared to YouTube's engagement-optimized feed
  • ↑Algorithmic personalized feeds fail to deliver genuinely interesting or horizon-expanding content
  • ↑Human/trusted curation is a better model than engagement-driven algorithms
  • ↑The AI-driven development process described is the most revealing part of the project
  • ↑Filtered YouTube alternatives like this could help vulnerable users escape harmful content loops
2.An Italian farmer found some unknown seeds in his attic and planted them(smithsonianmag.com)
531 points by ecares 14 hours ago | 163 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Historical context about ancient grain varieties and their decline in modern agriculture
  • ↓Criticism of poor scientific reporting regarding amino acids and nutrition claims
  • ↑Speculation about potential benefits like gluten tolerance or dormant seed phenomena
  • ~Concern about ecological risks of reintroducing century-old seeds
  • •Summarizing key factual findings about the discovered wheat variety
3.TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8(atlasum.net)
557 points by oger 18 hours ago | 255 comments | permalink
tl;dr: A remote, unauthenticated use-after-free in Linux's IPv4 TCP handshake (CVE-2026-98432, CVSS 9.8) affects kernels since 4.4, with Anthropic claiming Claude built a working root exploit against servers running multipath TCP listeners—which Go programs enable by default since 1.24. Upstream fixes shipped Oct 11–18 via a four-line change (kfree → kfree_rcu), but as of Oct 31 Ubuntu and RHEL 8/9/10 remain unpatched. Interim mitigations include nftables/iptables rules dropping IPv4 TCP packets carrying IP options and disabling MPTCP.
HN Discussion:
  • ~Title should have retained 'Linux' since vulnerability is OS-specific
  • ~Adds nuance/corrections about exploitability conditions and mitigations
  • ↑Criticizes Ubuntu/RHEL for failing to patch promptly on server-focused distros
  • ↑Sarcastic jab at C programmers, implicitly supporting memory-safe languages
  • •Questions scope/impact beyond servers—desktops, IoT, cloud load balancers
4.Memdoor: A team of 5 Qwen3.8-27B models beats Fable 5 on LiveCodeBench Hard(github.com)
293 points by guregodevo 14 hours ago | 135 comments | permalink
tl;dr: A multi-agent workflow (planner, two ideators, solver, reviewer, repair worker) using five Qwen3.8-27B instances communicating via files on disk matched the Fable 5 paper's harness on the first 10 LiveCodeBench Hard problems (9.8 vs 9.6 out of 10, five passes each), both beating a single Fable 5 call (8.0). The sample is too small to claim improvement over the original harness, and training contamination can't be ruled out. The setup is reproducible via Memdoor's YAML-based workflow, with runs averaging 40 minutes and $0.39 each on OpenRouter.
HN Discussion:
  • ↑Local models matching frontier models is critical to avoid dependence on hyperscalers
  • ↑Results suggest high local performance ceiling achievable with clever harnessing and fast hardware
  • ↑Multi-agent brute force scaling is a promising emerging axis for improving results
  • ~Benchmark sample is too small and possibly saturated to draw conclusions
  • •Asking tangential questions or noting prior related discussions without taking a stance
5.Jepsen: ParticleDB 1.1.4(jepsen.io)
286 points by aphyr 1 day ago | 163 comments | permalink
tl;dr: Jepsen tested ParticleDB, a Rust-based multi-model database marketed as "Full ACID" and "formally proven," and uncovered 96 bugs across versions 1.1.4–1.1.18.11.rc-22, most occurring on a single node with a single client and no faults. Issues ranged from crashes, deadlocks, and lost writes to broken predicates (e.g., `WHERE 4 = 5` matching rows), ignored NOT NULL/UNIQUE constraints, undeletable "zombie" rows, dropped tables resurrecting with mangled data, and silent type coercion. Even in the latest tested version, the default OCC mode lost committed writes and the "serializable" mode permitted Lost Update anomalies.
HN Discussion:
  • ↑Shock and dismay at the severity and absurdity of the bugs found
  • ↑Attributes the failures to the database being vibe-coded by AI
  • ↑Criticizes false marketing claims about formal TLA+ proofs
  • ↑Questions why developers hired Jepsen before doing basic internal testing
  • •Philosophical reflection on correct-by-construction vs incorrect-by-construction software design
6.Do the math: How we took over ChatGPT accounts(parameter.ai)
346 points by armcat 1 day ago | 168 comments | permalink
tl;dr: Researchers chained ChatGPT's HTML Preview, a MathLive postMessage listener that accepted unauthenticated cross-frame messages containing raw HTML, an unsandboxed srcdoc iframe, and a YouTube oEmbed JSONP endpoint whitelisted by CSP to achieve arbitrary JavaScript execution as chatgpt.com from a single shared conversation link. Opening the share let attackers call ChatGPT's authenticated APIs as the victim—enumerating and exfiltrating private conversations. OpenAI patched the issue on October 26, classified it P1, and paid a $5,000 bounty.
HN Discussion:
  • ↑The $5,000 bounty is too low for a P1 vulnerability and may incentivize black market sales
  • ↑This vulnerability highlights broader security concerns with ChatGPT's expanding attack surface
  • ↑Growing code complexity and monolith architecture at OpenAI is the root cause of such vulnerabilities
  • ↓The write-up's style and clarity made the technical exploit chain hard to follow
  • ↑Appreciation for the clever chaining of old-school web primitives in the exploit
7.Simple circuits can create complex behaviors(aatishb.com)
272 points by aatish 4 days ago | 80 comments | permalink
tl;dr: Using a virtual creature called a "spark" with just two sensory neurons and two motor neurons, the article demonstrates how tiny changes in neural wiring—adding a second eye, crossing connections, or switching excitatory to inhibitory signals—produce dramatically different behaviors that look like fear, aggression, or love of light. Varying connection strengths across individuals further creates distinct "preferences," illustrating how complex behavior and apparent intelligence can emerge from simple neural circuits without any central controller.
HN Discussion:
  • ~Points to historical precedents like Grey Walter's turtles, noting limits of purely reactive robotics
  • ↑References Braitenberg's vehicles as foundational related work
  • ~Questions whether the article's conclusion implies simple circuits themselves are intelligent
  • ↑Shares related hands-on experience with BEAM robotics and analog circuits reinforcing the article's idea
  • ↑Shares related simulation/neural network experiments that extend the article's concept
8.Anthropic blocks users for anything touching training larger models(twitter.com)
395 points by pretext 18 hours ago | 226 comments | permalink
tl;dr: Researcher Jiahao Shao claims Anthropic flagged him for "training a competitor" despite only using Claude to submit jobs and run analysis on rollouts from an open-source model. He reports that any prompts touching RFT, SFT, or training larger models now trigger blocks, model downgrades from Opus 5.5 to Opus 5, or session termination. He criticizes Anthropic for treating paying research users as adversaries while having trained on public data themselves.
HN Discussion:
  • ↑Users should diversify away from Anthropic due to its restrictive, dogmatic approach
  • ↑Claude's over-aggressive guardrails and moralizing make it impractical for real work
  • ↑Anthropic's safety branding was marketing hypocrisy exposed by corporate priorities
  • ↓The user was flagged legitimately due to VPN access from a geo-blocked region
  • •Model training data should be transparently disclosed like ingredient labels
9.AI, Lean, and the Future of Formal Verification, with Lean Creator Leo de Moura(thedataexchange.media)
208 points by datascientist 2 days ago | 50 comments | permalink
tl;dr: Lean creator Leo de Moura argues that AI has made formal verification practical by solving autoformalization—frontier models can now translate code or math papers into machine-checkable Lean proofs, drastically reducing the historical cost of verification. He envisions software engineering shifting from writing code to writing specifications, with AI generating implementations and proofs that are checked by multiple independent kernels; early adopters include AWS, Microsoft's SymCrypt team, and Anthropic (whose Fermat's Last Theorem proof runs 13M lines). The same approach is spreading beyond math to physics, finance, chemistry, and even parts of law.
HN Discussion:
  • ↑Combining Lean/TLA+ with AI and deterministic generators is the ideal approach for scalable formal methods
  • •Property-based testing offers similar benefits and deserves more attention in the LLM era
  • ↑Asking for learning resources on modeling for formal verification
  • ↓Skeptical that AI-generated verification solves the problem of ensuring correct specifications
  • ↓Shifting work to specifications just creates more work and loses valuable tight feedback cycles
10.Serbia just elected the world's brainiest parliament(science.org)
872 points by input_sh 1 day ago | 486 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Cautious optimism about the diverse new politicians and movement's achievement
  • ↓Academic expertise doesn't translate to political competence and risks hubris
  • ↓Historical examples show intellectual-led governments often fail or become corrupt
  • ↑Previous regime was so bad that almost anything would be an improvement
  • ~Younger representatives with different priorities and long-term thinking is the real benefit
11.Molly (Signal fork) has not been updated since 3 months and is vulnerable(piefed.world)
324 points by DeepLogin 1 day ago | 185 comments | permalink
tl;dr: Molly, a popular hardened fork of Signal, hasn't been updated since July 31 (v8.19.2-4) and now carries unpatched vulnerabilities that mainline Signal has already fixed, including an exploit disclosed in October and patched in Signal 8.27.1. Users are advised to switch back to mainline Signal and uninstall Molly until the project resumes regular updates.
HN Discussion:
  • ↑Signal now offers features that were Molly's main draw, making the switch back easier
  • ↑Molly's abandonment validates Signal's pragmatic anti-fork stance for security reasons
  • ↓Signal is hostile to power users by refusing features like UnifiedPush and Google-free builds
  • ~Offering alternative forks or clarifying the actual severity of the vulnerability
  • ↓Conspiracy claim that Signal has a government backdoor, promoting alternatives
12.Backdoor in Claude Code for VS Code extension on the Cursor Marketplace(phorion.io)
979 points by _chall 2 days ago | 548 comments | permalink
tl;dr: Phorion discovered that versions 2.1.312 and 2.1.313 of the "Claude Code for VS Code" extension on the Cursor Marketplace (since removed) contained a backdoor that executes on load, appending an attacker's SSH public key to authorized_keys, attempting to enable SSH, and establishing a persistent reverse SSH tunnel to 134.209.82.225 with platform-specific persistence (LaunchAgent, cron, or scheduled task). A bug in the macOS logic—checking Remote Login status without root—often prevents SSH enablement, but keys and persistence still get planted. Uninstalling alone won't remediate; responders must remove persistence artifacts, keys, and rotate exposed credentials.
HN Discussion:
  • ↑Clarifying that Anthropic wasn't compromised; only the Cursor marketplace version was tampered with
  • ↓Pushing back on hyperbolic framing that Anthropic itself was compromised
  • ↑Providing practical remediation steps and detection commands for affected users
  • ↑Broader concern about trusting AI CLIs and auto-updating extensions as inherent RCE risks
  • •Confusion about attribution and timeline requesting more details on how this happened
13.Casio Watches of the 1980s(casio.com)
233 points by karagenit 21 hours ago | 118 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~Minor critique of Casio design choices like cluttered watch face labels
  • ↑Personal nostalgia and preference for classic Casio watches over smartwatches
  • ~Skepticism that the revolutionary features were practically usable
  • ↑Sharing personal memories and specific Casio models from the era
  • •Curiosity about Casio's product strategy and proliferation of models
14.The oldest ice disappears and the Stone Age emerges from it(sciencenorway.no)
210 points by dxs 1 day ago | 106 comments | permalink
tl;dr: Norwegian glacial archaeologists with Secrets of the Ice have recovered 48 prehistoric arrows this field season from melting ice patches in Innlandet, including slate, bone, and freshwater mussel shell arrowheads dating back 5,000-6,000 years to the Stone Age. As the oldest ice finally melts after 6,000-7,000 years, finds are shifting from Viking Age to much older artifacts. Researchers estimate most archaeologically significant ice patches will vanish within 20 years.
HN Discussion:
  • ↑Climate change is tragic but at least yields archaeological discoveries
  • ↑Fascination with the quality and sharpness of the recovered artifacts
  • •Questions about whether ice coverage in these areas was historically normal
  • •Concern about handling ancient artifacts with bare hands
  • •Worry about potential ancient diseases being released from the ice
15.Digital minimalism(vitalik.eth.limo)
330 points by wilbertliu 1 day ago | 246 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Shares own extreme digital minimalism journey, going even further than the author
  • ↑Reflects on social media's inherent message/format problems, reinforcing critique
  • ↓Author's approach isn't true minimalism; using multi-client aggregators is the opposite
  • ↓The approach is excessive and impractical for people with families or normal lives
  • ↓Article fails to credit Cal Newport's original concept and misuses the term
16.Malware uses LLMs to rank victims by how much they're worth(blog.talosintelligence.com)
249 points by khalidkhair 23 hours ago | 131 comments | permalink
tl;dr: VOLTA-AUTODOXER is a Windows infostealer that, after harvesting credentials, cookies, wallets, and session tokens, sends a structured victim profile to OpenRouter-hosted LLMs (defaulting to Claude, falling back to Kimi and Gemini) to generate a ranked "target assessment" dossier identifying monetizable assets and OPSEC weaknesses. The malware uses a swappable build-time template suggesting it's sold as a commodity builder, and includes refusal-resilience logic that detects LLM guardrail responses and retries with more permissive models. Notably, there's no attacker-owned infrastructure—inference runs through the victim's own network before exfiltration.
HN Discussion:
  • ↑Rapid software update cycles create widening attack surfaces, prompting extreme compartmentalization measures
  • ↑We're entering a new era of agent-based threats reminiscent of early-2000s virus storms
  • •Defensive prompt injection in local data could become a counter-measure in an AI arms race
  • ↑AI labs should be running classification on outputs to detect malicious usage patterns
  • •Running inference on victim machines is an odd but commercially pragmatic design choice
17.Tell HN: Scribd Breached
344 points by x______________ 1 day ago | 121 comments | permalink
tl;dr: Scribd (parent of Slideshare, Everand, and Fable) notified users of a security breach in which an unauthorized third party accessed data including email addresses, last 4 digits of credit cards, card issuer, expiry date, and payment history. Scribd says the affected system has been secured, law enforcement and data protection authorities have been notified, and users should stay alert for phishing attempts. No evidence of misuse has been reported so far.
HN Discussion:
  • ↓Scribd is a predatory company that deserves no sympathy for being breached
  • ~This is a recurring pattern — Scribd was breached similarly 13 years ago
  • ↓Companies should disclose which specific systems were breached, not vague 'our systems' language
  • •Payment data breaches could be prevented by banks offering one-time or vendor-locked payment codes
  • ↓Questioning the delayed and staggered breach notification timeline given payment data was involved
18.We're releasing the weights of Mistral Large 4(mistral.ai)
1710 points by kuberwastaken 2 days ago | 438 comments | permalink
tl;dr: Mistral released the open weights for Mistral Large 4 ("Le Chonk"), a 1T-parameter multimodal model trained in Europe, under a modified MIT license (commercial MaaS requires a separate license). It claims leading open-weight performance on coding benchmarks (FrontierCode, Terminal-Bench) and defensive cybersecurity, with three reasoning modes, roughly 47% fewer tokens than GLM-5.3 at comparable scores, and pricing at $0.70/M input and $2.10/M output tokens. Weights are on Hugging Face, with deployment via vLLM, SGLang, Microsoft Foundry, and NVIDIA NIM.
HN Discussion:
  • ↑Price cut makes the model worth reassessing after disappointing preview pricing
  • ↑Supports Mistral for geographic/competitive diversity in the AI market
  • ~Refusal rate statistic is misleading without false-positive refusal data
  • ↓Calling this 'open weight' is misleading due to MaaS commercial license restrictions
  • ↓Model isn't actually competitive; positive reception reflects political bias not merit
19.Switch Lowering in GCC(xoranth.net)
208 points by signa11 1 day ago | 47 comments | permalink
tl;dr: GCC lowers switch statements using three main strategies: bitset tests (packing case values into a register and using the `bt` instruction), jump tables, and binary decision trees. The compiler uses dynamic programming to find optimal groupings for bitsets and jump tables, with heuristics based on case density—jump tables require roughly one case per 8 entries when optimizing for speed (one per 2 for size), while bitsets need ≤64-value ranges and ≤3 unique destinations. Anything not profitable for these optimizations falls back to a probability-balanced binary comparison tree.
HN Discussion:
  • ~Compilers should implement perfect hashing for large sparse switch tables but don't
  • ~Large switch statements cause severe compile-time issues in LLVM, pushing users to alternatives
  • ↑Decision trees can outperform jump tables in practice, supporting the article's nuance
  • •Clarifying or correcting technical details in the article (e.g., why a simplification isn't valid, possible typos)
  • ↑Switch lowering is a useful lens for understanding hardware branch prediction behavior
20.The $6.3B Binance hack was pulled off in just 20 minutes(wired.com)
582 points by domhudson 2 days ago | 426 comments | permalink
tl;dr: Hackers drained roughly $6.3 billion in crypto from Binance hot wallets across at least ten blockchains in a 20-minute attack on October 29, which tracing firms TRM Labs, Chainalysis, and Elliptic attribute to North Korea's TraderTraitor group. Binance says the breach began with a compromised engineer's laptop and has pledged to cover losses. About $2.8 billion (mostly stablecoins) has been frozen, but the remaining $3.3 billion in Bitcoin, Ether, and XRP cannot be frozen and may be laundered via novel automated techniques.
HN Discussion:
  • ↓Binance should be prosecuted for negligent security rather than treated as victim
  • ↓The 20-minute framing is misleading; the real work was years of preparation
  • ↓Skepticism about North Korea attribution given the sophistication jump required
  • •Curiosity about actual attack vectors and whether it was truly a hack or insider job
  • •Comparison to past crypto crimes where authorities failed to act