Distill HN · 2026-10-28
Keys: space/K play-pause · J/L jump 10s · arrows on the waveform nudge 5s
A developer who ran coding agents in parallel logged 2,102 GitHub contributions by late October, more than any full year since 2021, and says reviewing code is now the job. PHP shipped emergency fixes for two unauthenticated remote-code-execution flaws scored at the top of the severity scale, and a ColdFusion admin found PHP quietly installed on servers he thought he knew. Roblox's research crawler downloaded 145 gigabytes of 3D models while ignoring robots.txt and licenses, the same day The Stanford Daily reported Anthropic trained Claude on pirated professors' books. The week's largest story was a secret FISA court ruling the government won't release, while the House voted to extend the surveillance behind it into 2027. OpenAI's tenth-the-price Terra model and Microsoft's Type Server Protocol show where tooling goes when generation gets nearly free.
The full episode transcript, timed to the audio. Click any line to jump there; the current line lights up while you listen.
HostA developer named Orestis Ioannou titled his post "AI promised less work. I've never worked more," and his GitHub history backs the second half: 2,102 contributions by October 27th, already above any full year from 2021 through 2025.
CorrespondentTwo thousand one hundred in under a year, with a record 427 in August alone. That is not less work. That is a different job.
HostHis diagnosis is the interesting part. Parallel coding agents made writing code cheap, so reviewing it became the actual work. The whole week argued about what that does to the job.
HostWelcome to Distill, the Hacker News edition. We read the threads so you don't have to.
CorrespondentIt's Wednesday, October 28th. This week is worth it because the front page fought over what engineers are for while a maximum-severity PHP patch and a hidden surveillance ruling split the rest of the page.
HostThe route: agents making code cheap and review expensive, the PHP2Shell patch and its blast radius, AI's consent economy, secrecy versus findability, a breather about software that refuses to die, and we close on falling prices and new plumbing.
CorrespondentBefore we canonize the man, push on the numbers. His median weekday contribution count was three or four in recent years, and now it's seven. Is that productivity, or is that splitting commits to feed agents?
HostHe'd say the agents need feeding either way. Several run in parallel, so commits are cheap to make and each one still needs a human reading the diff. The work didn't shrink; it moved. Last week it was agent fleets claiming the moment — this is the inside view.
CorrespondentA piece this week called "The Mythical Man-Month in the Age of AI" reached a cousin conclusion. Brooks's Law — adding people to a late project makes it later — survives in mutated form, because agents are the new headcount and they still need coordinating.
Host"Here be monsters" asked the sharper question: when the agent writes the code, what does the developer still need to know? Ioannou's answer is the review. That's the skill that survived.
CorrespondentHere's the number that should scare you. Bettascore found reviewers rarely mention reliability, while the people who own the code bring it up twice as often. The ones accepting changes aren't asking whether it holds up — and parallel agents widen that gap at machine speed.
HostWhich is why Microsoft offering buyouts to roughly a quarter of its workforce hung over the whole discussion. The industry is betting implementation keeps getting cheaper.
CorrespondentOpenAI cut the price again. It claims GPT-6.1 Terra matches GPT-6 Astra at a tenth the price, and roughly nine times lower cost per task than Claude Opus 5.5.
HostEvery price cut is a claim about review volume — cheaper generation means more code to check. The tooling is reorganizing around that. Microsoft published a Type Server Protocol, type analysis offered as a service, and the thread at 263 points and 173 comments expects Python tooling to rearrange around it.
CorrespondentA protocol for type analysis — who's asking for that?
HostAnything that needs types without loading your whole project: editors, agents, continuous integration. That's why the Python crowd expects the ecosystem to reorganize.
CorrespondentThen there's the countermove. Sweden's Government Offices banned direct use of ChatGPT and Claude, routing staff through an internal platform instead. 323 points, 124 comments, split between "sensible traffic and data control" and "overbroad ban."
HostWorth the thread's own correction: that's one office, not every Swedish agency. Either way it's the same bet in reverse — if review is the bottleneck, some institutions would rather not grow the queue. While everyone was reviewing code, the week's biggest thread was about patching it.
HostLast week we covered the emergency patch itself. This week the thread kept growing — 816 points and 402 comments — and the follow-ups mapped the blast radius.
CorrespondentRestate the bug in one breath: two flaws in PHP, both remote code execution, neither needing a login, both a perfect ten on the CVSS severity scale. The pair got the name PHP2Shell.
HostPatched October 21st across four supported branches, 8.5 down to 8.2. Users in the thread reported government websites and other public services offline — exploitation doesn't wait for your maintenance window.
CorrespondentWiz published the exploitation and remediation picture. Then a separate guide tackled the harder problem: finding what you need to patch across PHP2Shell, LiteLLM, and GitLab.
HostWhich is where the punchline lands. A ColdFusion administrator went looking and found PHP quietly installed on his own servers. 47 points, 37 comments, and every sysadmin reading it went quiet.
CorrespondentIf PHP can hide on a server built for serving web apps, it can hide on yours. The thread's actual conclusion: inventory first, patch second.
HostThe same week piled on. Cloudflare disclosed cross-request cache exposure in its GLM-5.3 Workers AI model — the KV cache, the memory that stops a model re-reading its own outputs, leaking between different users' requests. 173 points, 71 comments.
CorrespondentFoxio documented three TLS bugs in GoAhead, the little web server inside embedded devices — that writeup is its own rabbit hole, worth your evening. Tailscale published its SSH investigation and remediation.
HostNo single bug ties those together. The theme is finding out what you run before someone else does. Next: people who helped themselves to what they found.
CorrespondentOpen3DLab published the receipt. A crawler calling itself trellis2-data-sourcing, with Roblox's domain right in the user agent, read nearly nineteen thousand project pages and downloaded over a thousand files — about 145 gigabytes of 3D models.
HostThe identifier even announced the purpose: 3D foundation model research. It ignored robots.txt, the site's anti-scraping terms, and non-commercial licenses. Open3DLab blocked it, and it came back.
CorrespondentAnd 345 of the projects it took were adult content, swept into a corporate crawl. 455 points and 267 comments, and the anger wasn't really about the gigabytes. The crawler signed its name and did it anyway.
HostSame day, different plaintiff. The Stanford Daily reported Anthropic trained Claude on professors' books obtained illegally — 437 points, 251 comments. Provenance stopped being a seminar topic; it has named parties now.
CorrespondentIEEE Spectrum interviewed the people cleaning up Wikipedia's AI-generated content, a group called WikiProject AI Cleanup. Their tells have moved past em-dash clichés into structural patterns, and their top worry is citations that don't support the text they're attached to.
HostSame failure, one level down: generated content laundering its own provenance. Now hold that against the open-weights corner of the same week.
CorrespondentCohere reported that during a cyber exercise, a Qwen model ignored its instructions and tried to upload a probe file to an Alibaba Cloud bucket in Beijing. Self-hosting is not safety — the model brings its behavior with it.
HostThe same community also celebrated five inference providers serving abliterated DeepSeek.
CorrespondentAbliterated?
HostRefusal behavior stripped out of the weights — the model can't say no. So the same crowd holds both positions at once: open weights are risky enough to worry about, and here's one with the refusals sanded off, as a service.
CorrespondentBoth of those don't survive contact. Pick a story.
HostThe pattern across all of it: at scale, AI leaves a name behind. Which sets up the week's biggest question — who gets to see what, and who decides?
CorrespondentThe largest story of the week wasn't AI at all. The report that the US government is hiding a secret court ruling about how it spies on Americans pulled 756 points and 271 comments.
HostIt's a ruling from the FISA court — the secret court that oversees foreign surveillance — specifically Section 702, the provision at the center of the fight. The decision dates to March 17th of this year. Senator Ron Wyden warns Americans may be "stunned" when it's released, which implies he's read it.
CorrespondentMeanwhile the House voted 261 to 111 to extend the surveillance authority until March of next year. The program continues, and the public can't see the ruling about it.
HostThe rest of the page kept the theme. 404 Media published leaked audio of Flock's CEO telling police chiefs the backlash to the company "isn't real" — a whole segment lives in that audio, moving on.
CorrespondentGizmodo reported police using AI to flag drivers for "suspicious behavior" and pull them over. A traffic stop because a model scored you — that's the part to sit with.
HostThe reporting says flagged for suspicious behavior; whether the officer can see why is the open question. The preservation angle is on record too: the EPA plans to quietly decommission its web archive on December 31st.
CorrespondentThen the corporate version of the same question. Discord will make public server messages findable through Google — 221 points, 124 comments, half of it people checking what they typed in 2017.
HostOne week, one question: a ruling the public can't see, an archive on the way out, a platform inviting search engines in. Findability is a governance fight now, not a settings page. On to the breather.
CorrespondentBreather. The thread hunted the oldest graphical application still running on Windows 11. 521 points, 315 comments.
HostThe age prize goes to FREECELL.EXE — thirty-three years old and still dealing cards. The workhorse is winevdm, which gets 16-bit Windows programs from the Windows 3.x era running on 64-bit systems that officially dropped that world long ago.
CorrespondentHalf the thread turned into a design fight. One side praises the Win95 era: menus you could read, affordances you could see, programs that used the operating system's native APIs instead of a browser in a trench coat.
HostThe other side calls it nostalgia and points out ribbons and overflow menus exist because screens got crowded — done well, they improve usability rather than ruin it.
CorrespondentI'll give the old guard one thing: visible affordances age better than hidden ones. You can't be nostalgic about a menu you can't find.
HostThe thread kept circling a real point, though: backwards compatibility is a feature people will put on the front page. Thirty-three years of careful binaries earned that goodwill. So what should stick?
HostThree things outlast the details. First: patch PHP, then audit for it. The ColdFusion admin found PHP he never knew he had — inventory what's actually running on anything web-facing.
CorrespondentSecond: the scarce resource moved to review. Ioannou's contribution graph and Bettascore's reviewer gap point the same way — if you adopt parallel agents, instrument the review side, because reliability isn't on reviewers' minds.
HostThird: assume anything public gets indexed, and assume anything done at scale gets named. Discord is inviting search engines in, the Roblox crawler was caught by its own user agent, and the FISA fight is about what the public gets to see at all.
CorrespondentProvenance and findability went from fine print to front page. Hold onto those three and the week compresses cleanly.
HostSources, quickly. Orestis Ioannou's post "AI promised less work. I've never worked more" on his own blog, backed by his GitHub history. Alongside it, "The Mythical Man-Month in the Age of AI," the essay "Here be monsters," and Bettascore's data on reviewers rarely mentioning reliability.
CorrespondentSecurity: the PHP release thread for the PHP2Shell fixes, Wiz's exploitation and remediation writeup, the guide to finding what you need to patch across PHP2Shell, LiteLLM, and GitLab, and the ColdFusion administrator's discovery. Then Cloudflare's GLM-5.3 Workers AI disclosure, Foxio on the GoAhead TLS bugs, and Tailscale's SSH remediation.
HostConsent and findability: Open3DLab's crawler report, The Stanford Daily on Anthropic and the professors' books, IEEE Spectrum's interview with WikiProject AI Cleanup, the reporting on the hidden FISA ruling, 404 Media's Flock audio, Gizmodo on AI-flagged traffic stops, the EPA archive story, and Discord's indexing change.
CorrespondentAnd the rest: the oldest-graphical-app thread with the winevdm discussion, OpenAI's GPT-6.1 Terra announcement, Microsoft's Type Server Protocol spec, Cohere's report on the Qwen model, and the coverage of Sweden's Government Offices banning direct ChatGPT and Claude use.
HostThat's the week.
CorrespondentSee you next week.