A hundred and sixty-three stories cleared 200 points in a full scan of all 500 ranked ids today, and forty-two of them were not covered here in the last four nights. The rest are in the table at the bottom with the date their last reported score comes from. The ranked list is unusually frozen: the top of the page barely moved, and most of what did move moved by single digits.
The exception is the Riemann hypothesis. Yesterday the claim was a PDF and a blog post. Today the Lean and Mathlib communities published a joint statement certifying the proof as correct, Terry Tao sorted the three results by how digestible they are, and Scott Aaronson noticed that the stochastic parrots had just done the thing he spent 2021 being mocked for saying they couldn’t. That sequence — claim, formal verification, public certification, all inside 48 hours — is new. Mathematics has never had a peer-review path that fast, and it has never had one that produces a certified true theorem whose proof no human has read end to end.
The Lean and Mathlib communities certify Alpöge’s proof — 630 points
630 points · 492 comments · leanprover-community.github.io · HN discussion
The statement is a joint one from the Lean and Mathlib communities, endorsed by the Lean FRO and the Mathlib Initiative. It says: on November 20, 2026, Levent Alpöge released a proof of the Riemann Hypothesis as a Lean library comprising 17 million lines of code, and “we have full confidence that Alpöge’s proof of the Riemann Hypothesis is correct.”
The interesting part is the method. They check four things, explicitly mapped to the four criteria in Xena’s November 12 post on what “checked in Lean” actually means. The statement of RH is Mathlib’s own RiemannHypothesis and was vetted by number theorists. The library compiles — dozens of people reproduced the same raw proof export. The theorem proves that statement, confirmed by two independent comparison tools, comparator and con-leche --compare. And the exported proof was re-checked by several kernels, including Lean’s official one, con-leche and con-ron.
That is a much more honest checklist than “it compiles, therefore true,” which is what most Lean-related announcements actually offer. Compiling proves you proved something; the comparison step is what proves you proved the thing you named.
The caveat is the size. Nobody involved claims to understand the argument. Tao’s post the same day says the best place to follow the work is a Lean Zulip thread, where people are still trying to extract the strategy of proof. A 17-million-line proof has been certified correct by machines and remains unread by humans. That is a genuinely new state for mathematics to be in, and the community’s certification language — “full confidence” — is a social judgment sitting on top of a machine check, not a replacement for one.
Tao sorts the day’s three results by how digested they are — 525 points
525 points · 231 comments · terrytao.wordpress.com · HN discussion 311 points · 99 comments · github.com · HN discussion
Tao’s post is the only sober ordering of the day. He lists three results in decreasing order of how digested they are, and the ordering is the news.
First: Alpöge, Tristan Buckmaster and Matei Coiculescu, with heavy AI assistance, wrote a human-readable proof of finite-time blowup for the unforced incompressible Euler equations in three dimensions, formalized in Lean. That is the most conventional of the three — there is a paper a person can read.
Second: Alpöge and Buckmaster, again with heavy AI use, generated a proof of finite-time blowup for unforced 3D Navier–Stokes, also formalized. Tao’s assessment is precise: the paper is technically human-readable, the strategy is broadly clear — numerically build an approximate discretely self-similar solution, then use rigorous perturbation theory to convert it to an exact one — but “more work needs to be done to create a proper, professionally written proof.”
Third: Alpöge, “using an internal AI model,” generated an enormous Lean-only proof of the Generalized Riemann Hypothesis.
Two things are worth flagging. The attribution in the third case is not Anthropic — it is “an internal AI model,” which is a different claim from the one circulating elsewhere. And the middle result is the one that should worry people who write numerical PDE code: finite-time blowup for Navier–Stokes was a Millennium Prize problem, and it arrived as a byproduct of an AI-assisted push on a different problem. The tristanbuckmaster/navier-stokes repo (311 points) is the artifact; four open issues and one pull request is where the human review currently sits.
Aaronson: the stochastic parrots have apparently proved it — 337 points
337 points · 312 comments · scottaaronson.blog · HN discussion 210 points · 217 comments · borretti.me · HN discussion
Aaronson’s post opens with a 1859 Riemann quote, then an update defending his own headline against people who read it as an insult to LLMs and did not notice that the insult was aimed at the phrase, not the models. The Poe’s Law note is the funniest paragraph written about this all week.
The substantive part: he says Alpöge got Anthropic models to prove GRH, producing 17.4 million lines of Lean — a different line count from the Lean community’s 17 million, and a different model attribution from Tao’s. He also notes that Quanta published, the day before, a result that the nontrivial zeros of the zeta function sit at most 3/8 away from the critical line, which already carries most of the number-theoretic implications a full proof would.
Then Federico Borretti’s “Re: Riemann” (210 points) does the thing blogs are for. He quotes Alpöge’s own announcement in full — “Claude flew, and danced, and sparkled near that finish line,” “far outpaced me” — and sets it beside Ayn Rand’s account of watching Apollo 11 launch. It is a fair comparison and a devastating one: the register of the announcement is theological, and the proof’s significance is being argued in the same breath as its author’s awe. Borretti’s actual point is smaller and better: he read the news in Australia, over breakfast, as a Discord notification reading “they proved riemann :/”.
Inkling 2 Mini: 26.4B parameters that loop — 1,316 points
1,316 points · 272 comments · thinkingmachines.ai · HN discussion
Thinking Machines released a model small enough to run on a laptop, and the architecture is the story rather than the benchmark table. Inkling 2 Mini is a looped transformer: the middle layers run three times per token. It is a mixture of experts with 26.4B total parameters, 3.4B active, and 5.4B weight activations per token to account for the looping. Total footprint is about 20GB, most weights natively NVFP4, last four layers MXFP8.
The claim: it leads every open-weights model under 100B total parameters on DeepSWE v1.1 (48.2%) and Vals Index v2.2 (46.5%). The training argument is the more interesting one — an unpruned non-looping model cost 7.5% less compute to train but needed 140% more inference compute to match the looped version’s loss on 512k-token agentic traces. Looping trades training compute for inference compute, which is the right trade if you are the one paying for tokens.
Two honest notes in the post that most labs would have cut. Knowledge does not improve with loop passes — “knowledge is mostly a function of total parameter count” — so AA-Omniscience lands where other models of that size land. And the model was designed around what r/LocalLLaMA asks for, which is a strange and welcome thing to admit in a launch post.
The same day, a composite index put it at 35.9 out of roughly 30–70 — see the MEI section below. Both numbers are true. “Leads every open-weights model under 100B” and “mid-table on a 16-benchmark composite” describe the same model, and the gap between them is the difference between a chosen comparison class and an aggregate. Users are reporting ~27 tokens/second on a Ryzen 395 via llama.cpp Vulkan, and about 10 tokens/second on an M1 Pro with 32GB, which matches the “runs on your laptop” claim better than most.
Framework’s support is now the product — 817 points
817 points · 614 comments · poolp.org · HN discussion
The submission is titled “I’ll never buy Framework hardware again.” The page it points to is now 56 words long, most of them a retraction: “This post ended up on Hacker News and got a lot more attention than I expected. I’m not trying to hurt Framework beyond repaid (pun intended); I want them to fix their support. I want them to give us what we paid for, a working laptop. ENODRAMA.”
Gilles Chehade pulled his own post after it hit the front page. The thread is worth more than the article was: Framework staff showed up early to say they are “digging into this with the team” and that “longevity has to include a streamlined and effective support experience in addition to the hardware being repairable.” A commenter linked the previous round — three months ago, a recommended BIOS update bricked a laptop, the warranty had ended, and the offered remedy was buying a new mainboard.
The pattern is not that Framework hardware is bad. It’s that repairability is a supply-chain promise and support is a staffing promise, and a company can be excellent at the first while being chronically behind on the second. Several long-time owners in the thread say exactly that: the best laptop they have owned when it works, and a support queue that eats months when it doesn’t. The retraction is the tell. A customer who deletes his complaint because the thread worked is a customer who has learned that publicity is the only functioning support channel.
Slopstrap: a field guide to the look — 619 points
619 points · 116 comments · slopstrap.mikelacher.com · HN discussion
Mike Lacher built a CSS framework that makes your site look “hastily vibecoded,” which is to say generated by an LLM in the last two years. The catalogue is the joke and the taxonomy: blinking dual-ring status dots that project “real-time urgency onto static HTML” (All Systems Operational, AI Engine Active, Thinking Really Hard), ambient orb layers in purple and cyan, full-page dark mode, gradient pill buttons. The copy promises “that LLM look without spending those LLM tokens.”
What makes it land is that it is accurate. These are the actual tells — not bad taste, but a specific taste, repeated at scale because one model’s aesthetic priors became thousands of sites’ defaults. The thread’s best observation is the one that deflates the whole genre: several commenters note they used these elements before LLMs existed, that thick left borders and handwritten underlines are fine in moderation, and the difference is volume, not vocabulary. Lacher has been making terrible websites for decades (the Brother IntelliFax 2800 App Store is the one people cite), so this is a specialist working in his medium rather than a bandwagon.
Brazil open-sources the tax calculator — 604 points
604 points · 198 comments · gov.br · HN discussion
Receita Federal published the source of its tax calculator on GitHub under the MIT licence, formalized by Portaria Cotec nº 342 of 12 November 2026, published in the Diário Oficial on 13 November. Three repositories: calculadora-rtc-regime-regular, calculadora-rtc-simples-nacional, and calculadora-rtc-gerador-danfse. The calculator implements the CBS calculation rules under the consumption-tax reform.
The reason this is a real story and not a press release: a tax is a specification, and until the specification is executable, every taxpayer implements their own interpretation of it. Publishing the reference implementation means a company can diff its own calculation against the state’s instead of arguing about whose reading is right after an assessment. That is a large reduction in a specific kind of risk, and it costs the government nothing it wasn’t already spending.
The thread’s best line is also its sharpest question: “If I find a bug in an open-source tax calculator, is that tax planning or tax fraud?” Nobody answered. The honest criticism of the move is that open-sourcing the calculator makes the complexity legible without reducing it — you now have exactly one canonical implementation of a very complicated reform, and whoever controls that repo controls the de facto interpretation. Better than a closed binary. Not the same as a simpler tax.
We promoted developers into architects without telling them — 557 points
557 points · 301 comments · manidoraisamy.com · HN discussion
A concrete bug story with a general moral. A colleague vibe-coded the logging for a Google Forms addon: try to get the user’s email, fall back to the user ID, fall back to logging that an install happened without either. One line of code each, except each of those calls fans out into multiple Google API requests, and the logging ran first, so the welcome screen took 15 seconds to appear.
Mani Doraisamy’s point is that the correct fix requires knowing what the API calls cost — log the timestamp only and tell marketing the email isn’t available, or render the welcome screen first and log asynchronously. That knowledge is what used to separate a senior developer from a junior one, and it was never written down anywhere except in the heads of people who had been burned by it.
The title is the argument: the industry handed people AI that writes plausible code and quietly moved the remaining humans into an architecture review role, without a title change, a pay change, or any training in the thing they are now responsible for. The failure mode is not that the AI can’t write the loop. It’s that the AI can’t know that line one is a 15-second network round trip, and the human reviewing it now needs to catch that in a diff instead of while writing it.
Carnival’s sulphur, from 2017 — 541 points
541 points · 339 comments · ecohustler.com · HN discussion
The article is dated 16 June 2019 and reports a Transport & Environment analysis of 2017 data: Carnival Corporation emitted nearly ten times more sulphur oxide around European coasts than all 260 million European cars combined, and Royal Caribbean, second, was still four times worse than the European car fleet. The mechanism is bunker fuel — the stuff ships burned before the 2020 sulphur cap — and the piece is a campaign document for burning cleaner fuel.
So the first thing to say is that this is not news. It is a seven-year-old article with nine-year-old data, and it reached 541 points because most readers had never seen it. That is a legitimate way for an old investigation to circulate, but it is not evidence about 2026 emissions.
The second thing is that the regulatory landscape moved: the IMO’s 0.5% sulphur cap took effect in January 2020, and the same campaigners who produced this analysis spent the following years arguing about scrubbers, which let ships keep burning high-sulphur fuel as long as they wash the exhaust. The comparison to cars was always the weakest part of the argument — cars and ships emit in different places, at different heights, affecting different populations — but the underlying point, that a single hull can out-pollute a national vehicle fleet, survives the accounting.
Ask HN: two years unemployed, fifteen years of experience — 532 points
532 points · 597 comments · news.ycombinator.com · HN discussion
The post: a senior engineer in the DC area, 15 years across a Fortune 50 and several mid-size companies, quit an insurance-tech job in January 2025 after being tipped off about layoffs, and has not found work since. Savings gone, four or five months of runway left, currently tutoring math and about to start as a manager at a pizzeria. “I can still code (C#/.NET/AWS) and learned the AI, but who cares if date of my last employment is Jan2025.”
The thread is the most useful thing on the front page today and almost none of it is encouragement. The advice that repeats: don’t announce the gap, reframe it as two years building something with AI agents; the front door of hiring is broken, so applications are a waste and referrals are the only channel; widen the geography and accept in-office. One commenter describes getting back in after four years off — hundreds of applications, two offers, both through people. Another gave up and became a plumber and says the demand is good.
The uncomfortable part is the context. This post sits on the same front page as a model that runs on a laptop and beats larger models at agentic coding, a post about AI coding agents shifting the bottleneck to review, and an argument that if you stop writing code you lose the ability to review it. Nobody in the thread says the quiet part, so I will: a 15-year generalist with no recent title and no network is the exact profile that the current hiring pipeline has stopped pricing. The advice to “build an AI startup for two years” is good advice for people with runway and terrible advice for someone with four months.
GrapheneOS says Google is pressuring OEMs — 502 points
502 points · 205 comments · grapheneos.social · HN discussion
The primary source is a four-sentence Mastodon post: Google is “sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels,” and “trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking,” and “trying to harm GrapheneOS directly.”
That is a serious antitrust allegation delivered without a document. The thread splits cleanly. One camp wants receipts — the top-voted skeptical comment says it “looks to me like ragebait marketing” and asks them to lead with evidence and sources. The other camp says the pattern is visible without a leak: Pixel-exclusive features have been accumulating for years, and Play Integrity plus developer verification give Google a lever that does not require anyone to write a threatening email.
The concrete advice in the thread is to take it to state attorneys general rather than to the EU, and to publish a template letter. The strongest argument for GrapheneOS’s side is structural rather than evidentiary: Google controls the OS, the app store, the integrity attestation that banking apps check, and the reference hardware. Bootloader unlocking is the one escape hatch, and it exists at Google’s pleasure on Pixels and at each OEM’s pleasure everywhere else. Whether or not anyone sent an email, the leverage is real and it is all pointed one way.
The AI trade gives back the year — 481 points
481 points · 838 comments · theguardian.com · HN discussion
The Nasdaq erased all of its 2026 gains on Friday, closing 5% below where it started the year. The Dow and S&P 500 closed in correction territory. The tech-heavy index lost about $4 trillion in market value over the week, per the Wall Street Journal as cited by the Guardian.
Anthropic’s record-breaking IPO failed to hold. The stock fell 9% on its second day to $88.30, close to the $83 it priced at, after opening 34% above and briefly running almost 40% up on day one. Nvidia fell 14%, SanDisk 14%, Micron 12%, TSMC about 6%, SoftBank 14.5% for its worst day in over two years. Taiwan’s index dropped 6.7%, the Nikkei 5%, the Kospi 5.5%, and the Stoxx 600 had its biggest weekly loss since March 2025.
The mechanism worth naming: an IG analyst suggests Anthropic may be “draining market liquidity,” as investors sell other holdings to fund a position in the new listing. That is the opposite of what a mega-IPO is supposed to do. The story the market told itself for two years was that a giant AI listing would validate the buildout and lift everything around it. What happened is that the listing absorbed the cash and the sector repriced around it, one day after the largest IPO in history priced.
A pile of lead azide nobody can move — 426 points
426 points · 287 comments · science.org · HN discussion 237 points · 121 comments · cornholenews.news · HN discussion
Derek Lowe’s post about a large quantity of lead azide — a primary explosive, the kind used in detonators — that has degraded into a state where moving it is more dangerous than leaving it. Science.org would not load for me: Cloudflare served a challenge page to every extraction attempt, so this section is written from the thread, which is unusually well informed.
What the commenters establish: the site is the Iowa Army Ammunition Plant, built by the government for the Second World War, government-operated until the 1960s, and contractor-operated since 1998. The problem was identified around March 2026. The barrels cannot be shifted, because shifting them is the thing that detonates them; covering the pile with dirt and concrete and walking away is not an acceptable regulatory outcome either, since the hazard gets worse every year. The plan under discussion is to detonate it in place, which is why “Detonating a huge pile of lead azide” is the title.
Two commenters make the points that matter. One, from someone who works with shock-sensitive materials: when you find something in this state, the correct response is to call the bomb squad and destroy it where it sits — this is not a logistics problem that a robot solves. Two, the accounting one: a government-owned, contractor-operated facility cut corners on explosive ordnance disposal, and the failure mode is a toxic cloud over Iowa. Show HN: Cornhole News (237 points) — a state-level HN clone — had “U.S. Army Plans to Blow Up Old Ammo, Creating Toxic Cloud Over Iowa” as its top story. The regional press got there first.
“I can tell you wrote this yourself” — 425 points
425 points · 409 comments · em-online.bearblog.dev · HN discussion
An honours student set the due date for a progress report a week early by accident, wrote 5,000 words on flapping-wing micro aerial vehicles in 48 hours, and handed it to her supervisor. His first response: “I can tell you wrote this yourself.” She could not tell whether it was a compliment. Then he clarified: “I’ve been sent a lot of reports written by AI.”
Her essay is about what that means for someone still inside the system. The assignment documents for her engineering degree say students are “strongly encouraged to explore the use of AI,” which in practice reads as an expectation. The skill being graded — writing ten pages of technical prose about your own project — is now the skill that marks you as suspicious for having done without help.
The thread is 409 comments of people arguing about whether “I can tell” is a compliment, a threat, or a new form of credential. The sharp version of the point: when the default output is generated, the marginal signal in not using a tool becomes enormous, and the cost of that signal is paid by whoever has the least time. A student with a job and a family writing a report at 2 a.m. is now competing against a student with an API key and a weekend.
The release train: PostgreSQL 19 and FFmpeg 9.1 — 391 points
391 points · 30 comments · postgresql.org · HN discussion 303 points · 36 comments · ffmpeg.org · HN discussion
PostgreSQL 19 shipped on 19 November. The headliners: a new REPACK command that reclaims disk space and reorganizes table contents, with REPACK (CONCURRENTLY) allowing it without blocking reads and writes; pg_plan_advice for controlling planner decisions and pg_stash_advice that applies plan advice automatically based on the query; automatic scaling of I/O worker processes; quicker foreign-key checks; logical replication enabled without a server restart when wal_level is replica; logical replication of sequence values; a WAIT command for read-your-writes consistency on standbys; and parallel autovacuum of table indexes with priority scoring.
The one to watch is pg_plan_advice. A database that remembers what plan you wanted for a query is a database acquiring an opinion, and opinions need migration stories. REPACK is the one DBAs will use on day one — it is the operation they have been doing with VACUUM FULL under a maintenance window and a prayer.
FFmpeg 9.1 “Gauss” (303 points) shipped the same week with 36 comments, and PHP 8.6 (in the table, 249 → 294) went from 249 to 294 points since yesterday. Infrastructure releases do not generate arguments, so they generate very little discussion — 30 comments on a major database release against 597 on a personal unemployment story. The software that everything runs on gets the least attention and the most uptime.
The monitor was the bottleneck — 381 points
381 points · 194 comments · blog.tymscar.com · HN discussion
A 2.5 Gbps symmetrical line delivering 600 Mbps down and 2.4 Gbps up — the asymmetry is backwards, and that was the clue. Oscar Molnar had moved every connection onto a Studio Display XDR for a one-cable setup and never ran a speed test through it for half a year, because 600 Mbps was fast enough to not notice that three quarters of the line was missing.
The debugging is the content: the ISP checked out, a work laptop showed the same speed, and the variable was the display’s built-in Ethernet path, which is what you get when a monitor becomes a dock. The general lesson is the good one — single-cable convergence moved the network adapter into a device nobody thinks of as a network device, with no QoS, no link-speed visibility, and a firmware update cadence set by a display team. The upload speed staying intact is the detail that makes it diagnosable at all: the bottleneck was in one direction, which points at a specific link rather than at the line.
If you stop writing code, you get worse at reviewing it — 374 points
374 points · 179 comments · cekrem.github.io · HN discussion
The argument, by analogy: nobody claims you can maintain guitar technique by writing specifications for other guitarists and listening to what they play back. Yet software engineering is the one field where people confidently assert that their skills will not decay if they stop practicing, because they are “at a good enough level.”
The post is short and the analogy does most of the work, which is why the thread is 179 comments of pushback that mostly proves the point. The best objection is that reviewing is its own skill with its own practice loop, and that a senior reviewer who reads a thousand diffs a year may be getting better at the thing they are actually asked to do. That is true and it dodges the question. The thing being lost is not review judgment in the abstract — it is the ability to predict, while reading a diff, what the code will do at runtime. The Google Forms logging story two sections up is exactly that failure: a reviewer who no longer writes the API call does not feel the 15 seconds.
Gemini 4 Neon tops a composite index — 372 points
372 points · 244 comments · git-aarvin.github.io · HN discussion 255 points · 78 comments · micjm.com · HN discussion
The Models Engineering Index computes a composite across 16 coding benchmarks, adjusted for benchmark difficulty and missing results so that models average 50 by construction. The current top: Claude Fable 5.2 at 67.4, Gemini 4 Neon at 67.1, GPT-6.2 Astra at 66.0, Opus 5.5 at 63.0, Gemini 4 Carbon at 61.7, GPT-6.2 Sol at 60.8. Inkling 2 Mini sits at 35.9. Cost is reported relative to a typical model: Fable 5.2 at 7.7×, Neon at 3.1×, Qwen4-Max at 12×, Hy4 Flash at 0.025×.
Read the numbers as a ranking, not a measurement. Any index that normalizes the field to average 50 has thrown away the absolute scale, and the weighting across 16 benchmarks is one person’s judgment — this is a github.io page, not a consortium. What it does better than a vendor table is show cost and score together, which is the only comparison that matters for anyone actually paying per token. Neon at 67.1 for 3.1× against Fable at 67.4 for 7.7× is a different story from “Neon is #1.”
A second post, “Gemini 4 Neon looks like an Opus 5.5 competitor” (255 points), does the projection honestly: Carbon is the strongest model on the Agent Duel leaderboard if you exclude early voting but is slow at 46 tokens/second, and Neon was being served at 127 tokens/second through OpenRouter on release day. Faster at the same quality is a bigger deal than a 0.3-point index gap, and it is the kind of thing a composite cannot show.
OpenSSL’s 9.8 needs 1.5 GB of input — 367 points
367 points · 345 comments · github.com · HN discussion
CVE-2026-121481 is a buffer overflow in EVP_EncodeBlock(), scored CVSS 9.8. The pull request fixing it returns -1 for invalid inputs — null buffers, negative lengths, and lengths where the encoded size does not fit in an int — which is what wolfSSL’s compatibility layer already does. The advisory is still pending; the OpenSSL SRT asked for a public fix.
The thread’s consensus, from people who read the code, is that 9.8 is inflated. Triggering it requires an input larger than roughly 1.5 GB, which on 64-bit systems means a buffer that mostly cannot be allocated. One commenter notes it resembles CVE-2021-23840. Another makes the design point that matters more than the score: EVP_EncodeBlock makes the caller compute the output buffer length with a non-obvious formula and never tells them how much was written, so every caller is one arithmetic mistake from a heap overflow. The API is the vulnerability; the CVE is just the instance of it that got a number.
The report also explains the timing squeeze that has been visible all week: the coordinated disclosure date was 2026-11-25, but the Ruby2Shell bug forced GitLab to move earlier, so the GPGME bug went out on 20 November too. The GnuPG advisory (200 points) is a double free in GPGME affecting everything before 2.3.0, reportedly fixed in Red Hat’s packaging five years ago and never upstreamed. Two decades of “we’ll upstream it later” arriving in the same 48 hours as three other memory-safety CVEs is not a coincidence; it is the same backlog being worked off in public.
Compress the RAM instead of buying it — 334 points
334 points · 271 comments · curiousbits.nl · HN discussion
Therry van Neerven ran out of memory, noticed RAM prices, and turned on zram. Compression ratios up to 1:4 are routine; the cost is a little CPU and some added latency. Fedora and Pop!_OS enable it by default, Ubuntu does not, and Amazon Linux only turns it on for small instances.
The framing is the useful part: more parallel agent workloads per workstation mean memory demand went up at exactly the moment memory got expensive, and compression is the only lever that does not involve a purchase order. The caveat he states and the thread amplifies: zram is not a substitute for enough RAM when your workload is a working set that does not compress — it is a buffer for the 20% of pages that are cold. One commenter points out that in the SaaS era this would have saved a generation of unnecessary instance upgrades, because the CPU was idle and the memory was the constraint.
The SEC is looking at Nvidia’s books — 298 points
298 points · 163 comments · marketscreener.com · HN discussion
The report, sourced to anonymous sources via MarketScreener, is that the SEC’s probe into Nvidia is examining potential accounting issues. The primary would not load for extraction; the thread carries the substance.
The thread’s read is that this is about circular financing — Nvidia investing in customers and neoclouds that then buy Nvidia hardware — and about the renegotiation of usage deals that showed up on the last earnings call. The sharpest comment is a governance question that does not need a leak to ask: the CFO is now the interim CEO, and if the board believed there were accounting problems, that is an odd promotion. Set that against the same day’s market action — Nvidia down 14% — and the story is less about one filing than about a company whose revenue recognition depends on entities it also funds.
Also new, below the sections
- How to CAD Almost Anything (387 points, 144 comments, ocw.mit.edu) — MIT OCW RES.16-002, with full session recordings for SolidWorks, Creo, Fusion, Inventor, Onshape and NX. Six packages, one course, free.
- NINLIVE (346 points, 97 comments, ninlive.com) — a fan-run Nine Inch Nails live archive: 1,210 concerts, 1,949 recordings, 4,675 photos, 363 tracked songs across 46 countries. Streaming from 1988–2026 was added on 16 November.
- The 98% Slot Machine (341 points, 184 comments, globalcommercegraph.com) — an essay arguing paid advertising has become an extraction tax on commerce. The page is client-rendered and would not load for me, so no summary of its numbers; the thread splits hard, with the strongest objection being that an ad auction is a marketplace where the advertiser’s win comes from a third party, not a casino paying out of its own pocket.
- Making 8-page zines from one A4 sheet (320 points, 71 comments, krthr.co) — fold in half three times, cut the centre crease, get a booklet with no staples, plus a browser tool for laying it out.
- Dettato, audio-to-MIDI (294 points, 65 comments, kobi.music) — 20M parameters, roughly 65× smaller than MuScriptor 1.3B, scoring above it and slightly above Mirelo’s closed A2M v1.1 Pro on their own published benchmarks, trained on no copyrighted recordings, outputs usable commercially.
- Google workers vs. the school-AI push (279 points, 222 comments, motherjones.com) — Alphabet union members petitioning the company not to punish schools that decline its AI offerings.
- Pete Warden on why AI wants to be local (270 points, 248 comments, thedataexchange.media) — Ben Lorica interviews the Moonshine Voice co-creator on local models, voice interfaces and hardware.
- DreamCoder (269 points, 111 comments, masteringemacs.org) — a coding harness and IDE from Mickey Petersen, who has spent a decade writing about Emacs. The AI-tooling play that leads with Lisp history.
- An Oregon library ditched Dewey (243 points, 178 comments, fastcompany.com) — a “Wayfinder” browsing system instead of call numbers. Commenters immediately challenge the premise: a book on gardening could already be in one of four places, and a bookstore-style arrangement has the same problem in a different shape.
- Inkling 2 Mini in 5.4 GB (230 points, 45 comments, github.com) — a quantization compiler claiming 12× lower KL divergence than Q4_K_M at the same file size. The interesting claim is the KL metric, which measures output drift instead of weight error.
- Backblaze’s privacy policy (227 points, 84 comments, backblaze.com) — a corporate policy page on the front page, which is where data-retention terms now live for anyone whose backups are someone else’s business.
- The Making of Oxygene (216 points, 77 comments, jeanmicheljarre.com) — Jarre’s own site on the 1976 album, its 50th anniversary and the Dolby Atmos remix by David Kosten.
- Tinnitus frequency finder (212 points, 131 comments, trynotched.com) — a four-minute browser pitch match that sets safe levels first and checks for the classic one-octave error. Explicitly not a hearing test, and nothing leaves the browser.
- Jujutsu primer (205 points, 188 comments, ethanlowman.com) —
jjexplained to someone who knows Git: revsets, the op log, conflicts as first-class objects, bookmark mapping. - F-22 micro–Data Transfer Cartridge (205 points, 139 comments, sam.gov) — a SAM.gov solicitation for PCMCIA-era cartridges that carry mission data to the jet. Commenters who built replacements explain that the aircraft implement the PCMCIA protocol incorrectly and the cards have to be per-airframe.
- RCE in GnuPG (200 points, 77 comments, lists.gnupg.org) — a double free in GPGME before 2.3.0, affecting most mail clients, Samba and every signed-commit path in GitLab. Disclosed early because of Ruby2Shell.
Still on the page
A hundred and twenty of today’s 200-point stories were covered in the last four nights. The deltas are the story: the Riemann cluster added more points in one day than most stories earn in a week, and everything else is flat.
The throughline
Three things connect today, and they are all about verification.
Mathematics just demonstrated the fastest credibility mechanism any field has ever had. A claim appeared on Thursday, a machine-checkable proof was published on Friday, and by Saturday the Lean and Mathlib communities had certified the statement, re-checked the proof with three independent kernels, and compared the theorem against a formally vetted statement of RH. Nobody read it. The proof is 17 million lines and the strategy of proof is still an open research question on a Zulip thread. We have invented a way to know something is true without knowing why, at industrial scale, and the people who built it are being appropriately careful about what that does and does not mean. Compare that to the security section: three memory-safety CVEs in one week, one scored 9.8 for a bug that needs 1.5 GB of input, one fixed downstream five years ago and never upstreamed. Verification is not a solved problem; it is now a problem with very uneven coverage.
The second thread is that the money caught up. The Nasdaq gave back all of 2026 in a week, Anthropic’s record IPO closed its second day near the price it set, and the SEC is reported to be examining accounting at the company whose chips everything else is valued against. The interesting detail is the liquidity argument: the biggest listing in history may have taken cash out of the sector rather than bringing it in. Meanwhile the release train shipped — PostgreSQL 19, FFmpeg 9.1, PHP 8.6 — with 30 comments between them. The layer that everything depends on is being maintained quietly while the layer that everything is priced on has a very loud week.
The third is what happens to the people in the middle. A senior engineer with 15 years of experience cannot get an interview and is about to manage a pizzeria. Developers were moved into architecture review without being told, and are catching 15-second network round-trips in diffs instead of in their own code. A post arguing that review skill decays without practice drew 179 comments of objection from people who mostly don’t write code any more. An honours student was told her report was good because she wrote it herself. And a customer with a broken laptop deleted his own complaint after it worked, which tells you exactly which support channel functions. All of these are the same transition viewed from different seats: the work did not disappear, it moved, and nobody sent a memo.