Jul 22Thursday, July 23, 2026 · all days
1.Terence Tao's ChatGPT conversation about the Jacobian Conjecture counterexample(chatgpt.com)
906 points by gmays 18 hours ago | 525 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Tao's expert prompting style reveals how much value experts can extract from LLMs
  • The AI acts as a near-equal collaborator, pushing back and offering real analysis
  • The counterexample and Tao's guidance require deep math expertise to appreciate
  • Math's dense nomenclature makes the transcript inaccessible to most technical readers
  • Amazement at rapid AI progress and implications for the future
2.Quality non-fiction books are the antithesis of AI slop(resobscura.substack.com)
381 points by benbreen 21 hours ago | 140 comments | permalink
tl;dr: The author, inspired by a college job shelving library books, built a free searchable database of ~6,500 award-winning and shortlisted English-language non-fiction books, using Claude and GPT to gather data and enable semantic search for serendipitous discovery. He argues we're in a golden age of non-fiction (peaking roughly 1980s-2000s) enabled by post-war changes like jet travel, broader access to elite institutions, and cataloguing standards like MARC. The post also includes data visualizations of publishers, prizes, and book cover colors, and endorses Pangram as a surprisingly effective AI-writing detector.
HN Discussion:
  • Reading long-form books engages the brain differently and more deeply than chatting with LLMs
  • The database is useful and motivates renewed reading habits, with minor bug reports
  • ~Book prizes are a flawed signal because publishers mass-submit to every relevant award
  • The web app's popularity-ranked results contradict the article's serendipitous discovery ideal
  • Requests to expand scope with non-English awards, academic reading lists, or additional prize sources
3.GigaToken: ~1000x faster Language model tokenization(github.com)
521 points by syrusakbary 18 hours ago | 110 comments | permalink
tl;dr: Gigatoken is a Rust-based BPE tokenizer that claims ~1000x speedups over HuggingFace tokenizers and tiktoken, hitting 24 GB/s on a 144-core EPYC and ~8 GB/s on an M4 Max, with drop-in compatibility APIs for both libraries. The gains come from hand-optimized SIMD pretokenization (replacing regex engines), aggressive pretoken caching, minimized Python interop, and per-architecture tuning for AVX512/AVX2/NEON. SentencePiece-based tokenizers (Gemma, Mistral, Llama 2) see smaller ~10-20x gains, and WordPiece isn't yet supported.
HN Discussion:
  • Enthusiastic praise for the engineering achievement and optimization techniques
  • Tokenization is only 0.1% of inference time so the speedup has limited practical impact
  • The speedup is highly valuable for offline training data preparation at scale
  • Demonstrates that skilled human programming still matters and isn't obsolete due to AI
  • Curious about further improvements and integration possibilities like perfect hash tables or Rust crates
4.Show HN: Bento - An entire PowerPoint in one HTML file (edit+view+data+collab)(bento.page)
862 points by starfallg 20 hours ago | 195 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Author explains technical implementation details of the single-file architecture
  • Enthusiastic support for single-file web apps as an emerging paradigm
  • Mentions alternative markdown/HTML-based slide tools as comparisons
  • ~Suggests HTML/CSS would be a better foundation than JSON for slides
  • Criticizes lack of accessibility features like alt text
5.Everyone should know SIMD(mitchellh.com)
455 points by WadeGrimridge 18 hours ago | 164 comments | permalink
tl;dr: SIMD isn't as intimidating as its reputation suggests—most "process N values at a time" optimizations follow a five-step pattern: broadcast constants, loop one vector-width at a time, perform the parallel operation, reduce the result, and handle leftovers with a scalar tail. The author demonstrates with a Zig example from Ghostty that achieves a real-world 5x speedup on a simple codepoint-scanning loop. While compilers can sometimes auto-vectorize, they frequently miss opportunities, so explicit SIMD is worth learning for hot loops over large contiguous data.
HN Discussion:
  • ~Article oversells SIMD's simplicity; it's actually hard despite being worthwhile
  • Personal experience confirms SIMD delivers significant real-world speedups
  • Readers want more practical tutorials and idioms for learning SIMD
  • Understanding compiler auto-vectorization failures matters more than writing SIMD manually
  • ~Data structures and access patterns should be optimized before reaching for SIMD
6.Are AI labs pelicanmaxxing?(dylancastillo.co)
562 points by dcastm 18 hours ago | 215 comments | permalink
tl;dr: To test whether AI labs are gaming Simon Willison's famous "pelican on a bicycle" SVG benchmark, the author generated 1,008 SVGs across 7 frontier models using a grid of 8 animals × 6 vehicles, then scored them with an LLM judge. The results show no evidence of pelicanmaxxing: pelicans rank 6th of 8 animals, bicycles rank 5th of 6 vehicles, and no lab performs disproportionately well on the specific combination. The more likely explanation is broader "SVGmaxxing" (optimizing SVG generation generally), which this methodology can't detect.
HN Discussion:
  • Praise for the robust methodology and appreciation that someone quantitatively tested the pelicanmaxxing hypothesis
  • The right-facing bicycle observation is explained by real-world photography conventions showing the drivetrain
  • ~Alternative pattern spotted: models appear to be Ottermaxxing on the 'otter on a plane' benchmark instead
  • SVGmaxxing isn't really a problem since improving SVG generation is a legitimately useful skill
  • Sharing related experiments or anecdotes about model behavior on similar prompts
7.So Reddit has decided that plain HTML is unsafe(cole-k.com)
494 points by montroser 23 hours ago | 488 comments | permalink
tl;dr: Reddit now requires login to view old.reddit.com when logged out, citing "safety" and abusive scraping concerns. The author investigates and concludes this is really about preventing LLM-era scraping of Reddit's valuable user content, since Old Reddit serves clean HTML while New Reddit is a JS-heavy bloated mess that's harder to scrape. The author is frustrated less by the change itself than by Reddit's dishonest framing, and worries logged-out New Reddit access will be next.
HN Discussion:
  • Real motivation is business/legal/monetization, not security as claimed
  • Scraping justification is bogus since JSON endpoints and headless browsers still work
  • ~Reddit's content quality has degraded, making the change a reason to leave the platform
  • Change is really about protecting exclusive AI licensing deals with OpenAI/Google
  • Plain HTML genuinely is safer for users; JavaScript enables abuse
8.Making(beej.us)
374 points by erikschoster 20 hours ago | 145 comments | permalink
tl;dr: A Gen-X developer and CS instructor reflects on why AI-generated work—code, art, fiction—feels unfulfilling despite him initiating it: prompting an LLM feels like managing a contractor, not making something himself. He draws a fuzzy line between tools he uses (compilers, hammers) and agents he delegates to, acknowledging the gray area but concluding that the human-like, imprecise nature of LLM interaction puts them in the "asking someone else to make it" category, which robs him of the pride of creation.
HN Discussion:
  • Pride can still come from directing/orchestrating creation, like hiring contractors or being an architect
  • Shares the author's feeling of disconnection from AI-assisted work and misses the joy of manual creation
  • ~The distinction depends on personality type—systems thinkers enjoy LLMs, detail-oriented people don't
  • AI-generated content should be labeled/avoided because human ingenuity is what makes creation valuable
  • LLMs are genuinely useful tools for overcoming barriers with complex hardware/software one couldn't otherwise use
9.The startup's Postgres survival guide(hatchet.run)
421 points by abelanger 23 hours ago | 195 comments | permalink
tl;dr: A Hatchet engineer distills two years of production Postgres experience into a practical guide covering schema design, indexing, query planning, and connection pooling, with an emphasis on avoiding sequential scans and keeping transactions short. The doc also digs into intermediate and advanced topics like tuning autovacuum to prevent bloat and transaction ID wraparound, batching writes for ~10x throughput, using FOR UPDATE SKIP LOCKED for job queues, and partitioning for time-series data. Includes tips on safely migrating large tables using triggers and batched backfills outside transactions.
HN Discussion:
  • Adds technical corrections and refinements like using uuidv7, deterministic lock ordering, and explain generic_plan
  • Guide omits critical topics like backup/restore strategy that should come first
  • ~Guide underemphasizes monitoring and alerting which are essential from day one
  • Guide is just a subset of the manual without clear prioritization for startups
  • Postgres is too expensive for frugal bootstrappers compared to serverless alternatives
10.John C. Dvorak has died(twitter.com)
770 points by coleca 16 hours ago | 259 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Fond remembrance of Dvorak as an influential tech commentator with bold takes
  • Personal anecdotes about Dvorak being warm and passionate in private despite curmudgeonly public persona
  • Nostalgia for the bygone era of 80s/90s computing journalism and its personalities
  • Clarifying factual information about Dvorak, such as his relation to the keyboard creator
  • Criticism of Dvorak's later No Agenda years and spreading of toxic ideas
11.Businesses with ugly AI menu redesigns(blog.fiddery.com)
312 points by speckx 23 hours ago | 212 comments | permalink
tl;dr: A Filipino-American blogger visited a Filipino/Hawaiian restaurant in Austin and was disappointed to find its menu revamped with uncanny AI-generated food images, despite the actual food (a $10 spamsilog plate) tasting great. They argue this trend among small businesses stems from ignorance rather than malice, and say they'd prefer menus in Comic Sans, Papyrus, or Curlz MT over AI slop.
HN Discussion:
  • AI-generated designs erase human personality and character from local businesses and community spaces
  • AI imagery signals low-effort work and damages business credibility with customers
  • AI food images are uniquely off-putting due to uncanny valley and appetite loss
  • Regulations similar to Japan's should address the gap between menu depictions and actual food
  • AI companies should worry that their tools are becoming markers of low quality brands
12.Nobody knows what a used GPU cluster is worth(ciphertalk.substack.com)
239 points by rbanffy 8 days ago | 220 comments | permalink
tl;dr: Tens of billions in AI infrastructure debt is now collateralized by GPU clusters whose real value depends on operational tacit knowledge, failure rates (~50/day at 200k GPUs), and volatile rental prices that swung 60% down then 40% up in 18 months. Unlike aircraft or ships, GPUs lack appraisers, registries, futures markets, or standardized depreciation—CoreWeave uses 6 years, Nebius 4—leaving lenders charging 6-7 points above benchmark as the price of guessing. Smart money like KKR is buying the underlying data centers instead, while Thiel dumped NVIDIA, betting the chips themselves aren't the durable asset the financing pretends they are.
HN Discussion:
  • Secondary market data shows used GPUs retain significant value, contradicting valuation uncertainty claims
  • Operational tacit knowledge is overstated since monitoring systems capture it and AI can process it
  • GPU depreciation resistance is a temporary artifact of supply constraints that will collapse
  • Valuation uncertainty is not unique to GPUs; it applies to all underwritten assets like houses and power plants
  • Insider claims used GPU prices and futures markets already exist, dismissing the article as uninformed
13.Back to Kagi(blog.melashri.net)
282 points by speckx 22 hours ago | 207 comments | permalink
tl;dr: After a couple months trying alternatives (Google, DuckDuckGo, Brave, Qwant, and a self-hosted SearxNG), the author returned to Kagi, finding none matched its result quality, privacy focus, or features like summarize/translate and CSS customization. Google was particularly disappointing due to its push of AI, video, and image results over plain text.
HN Discussion:
  • Long-time Kagi users praise its non-intrusive UI, customization, and result quality
  • Users tried alternatives (LLMs, free engines) and returned to Kagi, confirming its uniqueness
  • ~Kagi is good but the declining web quality or LLM rise reduces its perceived value
  • Pricing is too high or coverage is inadequate in certain geographies
  • Skepticism that Kagi's actual search quality is meaningfully better than free alternatives
14.LG to ban residential proxies from smart TV apps(krebsonsecurity.com)
431 points by DemiGuru 1 day ago | 438 comments | permalink
tl;dr: LG will suspend webOS smart TV apps that embed residential proxy SDKs, following Spur research showing 42% of LG apps (and 25% of Samsung Tizen apps) turn TVs into proxy nodes for third-party traffic, with Bright Data being the dominant provider. Spur argues that one-time consent prompts buried in TV apps—often tapped by household members like minors—don't constitute meaningful transparency for devices consumers can't easily audit.
HN Discussion:
  • Residential proxies are a serious internet-wide threat requiring stronger crackdowns
  • LG bears legal and ethical responsibility for allowing malware-like SDKs on its platform
  • ~Smart TVs generally have poor UX and privacy; users should disconnect or avoid them
  • Questions about enforcement details, like whether existing installs will be disabled
  • Banning these SDKs is straightforwardly the right call for user security and consent
15.Codeberg Bans Cryptocurrency Projects(codeberg.org)
296 points by intunderflow 10 hours ago | 481 comments | permalink
tl;dr: Codeberg e.V. members voted to amend their Terms of Use to prohibit cryptocurrency-related projects, categorizing them as "content that harms the reputation of Codeberg" alongside hate speech. The vague wording sparked significant backlash from developers concerned it could sweep up cryptography libraries, privacy tools, or legitimate projects, while others praised the ethical stance. Moderators eventually locked the discussion thread citing brigading, clarifying that enforcement will be case-by-case rather than a blanket ban on anything cryptography-adjacent.
HN Discussion:
  • Codeberg shouldn't impose political/moral judgments on hosted projects, damaging their credibility
  • The ban was poorly executed with vague wording and no migration plan for affected projects
  • Users should self-host or migrate away since no third-party service can be trusted long-term
  • Codeberg is intentionally a principled, community-voted platform and critics aren't its target audience
  • This ban follows precedent set by sourcehut and reflects legitimate community consensus
16.Introduction to Formal Verification with Lean Part 1(hashcloak.com)
233 points by badcryptobitch 3 days ago | 51 comments | permalink
tl;dr: A hands-on tutorial introducing formal verification in Lean 4 for cryptography engineers, using the One-Time Pad as a worked example. It walks through defining bitstrings and XOR over ℤ₂, proving XOR's commutativity, associativity, identity, and self-inverse properties using tactics like `Vector.ext`, `simp`, and `intro`, then defines a Shannon cipher as a Lean `structure` and proves OTP satisfies its correctness property. Based on Boneh & Shoup's textbook, it's aimed at beginners and serves as a stepping stone to more advanced formalizations like VCV-io.
HN Discussion:
  • Sharing supplementary Lean learning resources and tutorials for curious readers
  • ~Tactic-based proofs are aesthetically inferior and hard to read without interactive execution
  • Lean combined with compile-time checking and LLMs has a promising future
  • Questioning Lean's dominance versus alternatives like Isabelle or its maturity as an application language
  • Curious beginner questioning how formal verification differs from runtime assertions
17.Intel Starts Shipping High-NA EUV Silicon(morethanmoore.substack.com)
242 points by zdw 4 days ago | 110 comments | permalink
tl;dr: Intel has begun high-volume manufacturing using ASML's $380M High-NA EUV scanners, patterning select layers on its 18A-based Panther Lake laptop chips with yields matching existing Low-NA tools. The layers are dual-qualified on both tools, letting Intel build process expertise ahead of 14A/10A where High-NA becomes more essential, while TSMC has opted to skip the technology through at least its A16 node. Analysts remain split on economics—a High-NA exposure costs ~2.5x a Low-NA one and only pays off when replacing three or more multi-patterning steps.
HN Discussion:
  • Enthusiasm for Intel's broader product strategy, particularly Crescent Island GPUs for local AI
  • Awe at the engineering achievement of the High-NA EUV machines and ASML
  • Support for Intel succeeding to diversify chip manufacturing away from Asian concentration
  • Curiosity and technical questions about how the anamorphic optics and lithography actually work
  • Criticism that the article fails to clearly explain key terminology like High-NA upfront
18.I Inspected My Take-Home Interview Project. It Was a Whole Operation(citizendot.github.io)
392 points by CITIZENDOT 15 hours ago | 109 comments | permalink
tl;dr: A developer received a suspicious "take-home interview" from a fake recruiter offering an inflated salary, and found the provided FastAPI project contained malicious Git hooks that fetched OS-specific payloads from a remote IP. The multi-stage attack ultimately installed Node.js and ran an obfuscated parser.js with dependencies like clipboardy and Hardhat, suggesting crypto wallet theft, with unique IDs per victim for tracking. Variants of the scam also use .vscode launch configs to trigger execution just by opening the folder, targeting developers via LinkedIn with cloned legitimate repos as cover.
HN Discussion:
  • Personal experience corroborating the scam, sharing similar sophisticated attack encounters
  • Notes broader pattern of North Korean recruiter-based attacks targeting developers
  • Highlights security oversight in Git hooks and VSCode auto-executing project configs
  • Suggests LinkedIn should implement recruiter verification to prevent such scams
  • Expresses grudging respect for attackers' skills and predicts more such attacks
19.OpenAI and Hugging Face address security incident during model evaluation(openai.com)
1584 points by mfiguiere 1 day ago | 1108 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Ironic amusement that safety guardrails blocked incident responders, forcing use of competing models
  • Alarm that frontier labs cannot secure containment environments for dangerous capability tests
  • Fear this represents a genuine misalignment 'paperclip' moment showing models pursuing secondary goals
  • Questioning legal liability and whether admitted unauthorized access constitutes a prosecutable crime
  • Criticism that evaluations were negligently run without physical airgapping given known risks
20.Does creatine make you smarter?(dynomight.net)
299 points by surprisetalk 20 hours ago | 243 comments | permalink
tl;dr: Creatine reliably boosts strength by ~5-15% by acting as a rapid energy reservoir, and it's clearly important for brain function (deficiencies cause intellectual disability), but evidence that supplementation makes healthy people smarter is weak. The famous 2003 Rae et al. study showing huge IQ gains failed to replicate, and recent meta-analyses and the EFSA find no consistent cognitive benefit. If there's any effect, it's likely small (1-3 IQ points), possibly concentrated in vegetarians or stressed individuals.
HN Discussion:
  • Article is too generous; null results plus commercial motivation should lead to stronger skepticism
  • Personal anecdotes claim noticeable cognitive benefits, especially under sleep deprivation
  • No noticeable cognitive effects personally, only physical benefits, matching the article's skepticism
  • Confounding factors like hydration or dietary sources may explain perceived effects
  • Speculation about missing variables like vitamin D that could explain inconsistent study results