HN Brief: 2026-06-24

What we call "age verification" is actually mass surveillance [comments]

824 points · 444 comments · pluralistic.net · 18h ago

The article argues that so-called "age verification" laws are a Trojan horse for mass surveillance, turning every online interaction into a trackable, recordable event under the guise of protecting kids. The HN thread immediately split: a vocal group pushed back, insisting that privacy-preserving age verification *is* technically possible—pointing to alcohol sales where you flash an ID without a permanent paper trail, or cryptographic one-time codes—and that the article’s all-or-nothing framing is a straw man. The other side countered hard, saying the whole point *is* the surveillance; the tech industry wants ID tied to every click, and any “90% solution” will inevitably be deemed insufficient and escalated until you’re handing over a driver’s license to visit any website. A third camp dove into specific proposals—on-device parental controls, government-issued scratch cards, or “log in with Apple”-style minimised handshakes—but even those got picked apart for either being trivially bypassed or still requiring a central authority you have to trust. Eventually the thread spiraled into a broader argument about whether general-purpose computers should be regulated like alcohol, with one side calling that dystopian and the other noting it’s the logical endpoint of any serious age-gating.

F3 [comments]

628 points · 129 comments · github.com · 15h ago

This is a research paper turned into a prototype for F3, a next-generation columnar data format that embeds WebAssembly decoders directly into files to avoid the interoperability problems of formats like Parquet. The Hacker News crowd immediately dinged the README for being all marketing-speak with no clear “why,” forcing someone to point out that the actual rationale is buried in the academic paper. The core architectural bet—stuffing executable Wasm into every file as a fallback decoder—sparked a long, split argument: half the room called it a clever future-proofing hack, while the other half hammered on security, pointing out that embedding code gives attackers a 0-click DoS vector and that “it’s sandboxed” doesn’t stop compression bombs or halting-problem-style resource exhaustion. Several people noted the repo has no commits in eight months and called it a dead research project, with the pragmatic consensus being “sure, I’ll use it in the future—right now I’m shipping with Parquet.”

FUTO Swipe – A new swipe typing model [comments]

501 points · 155 comments · swipe.futo.tech · 14h ago

FUTO released an open swipe typing model and keyboard app with a dataset of a million swipes, aiming to break the lock that privacy-invasive keyboards and proprietary libraries have had on accurate swipe input. The HN crowd is genuinely excited about the model’s performance—many say it finally competes with Gboard and SwiftKey, and the fully offline, on-device inference is a big draw—but the thread quickly zeroes in on the licensing mess: the inference library is GPLv3, the keyboard app uses a source-available FUTO license with a non-commercial clause and a payment-removal restriction, and the model itself has yet another custom license, which means F-Droid can’t ship it and purists call it proprietary. The comparisons to SwiftKey are heated: longtime SwiftKey users report that FUTO’s suggestions still fall short on context (e.g., nonsensical next-word predictions like “Peterson” after “Jordan” without ever learning the user’s own surname), though others say the latest update closed the gap and the offline voice input is a killer feature. There’s also a side debate about whether the licensing is actually reasonable for preventing app-store leeches or just another dilution of “open source,” and several people note that the keyboard doesn’t support iOS, multilingual layouts without duplicates, or GIF search by design. Overall, the takeaway is that the model itself is a genuinely useful open alternative, but the licensing schizophrenia leaves a bad taste for anyone who wants truly free software.

Fired by Google for creating the Google workspace CLI [comments]

483 points · 291 comments · xcancel.com · 13h ago

Justin Poehnelt was fired from Google after creating a popular open-source CLI for Google Workspace that went viral, hit #1 on HN, and gained thousands of users. The main debate on HN is whether he was fired for the project itself or for bypassing Google's internal release process—commenters are sharply split, with some seeing it as a classic big-company killing innovation story where managers felt threatened by disruption, while others argue he violated clear policies by releasing an official-looking tool with Google branding without approval, putting his team in an impossible position. People who've worked at Google pointed out that the open-source release process is famously strict and documented, and while many similar unofficial projects exist on Google's GitHub, the viral nature of this one forced leadership's hand. A vocal contingent is furious at Google's management culture, calling it MBA-driven fiefdom protection, while others counter that skipping legal and comms review on a high-profile release is a clear firing offense at any company.

Unlimited OCR: One-shot long-horizon parsing [comments]

468 points · 107 comments · github.com · 20h ago

Baidu released Unlimited OCR, a model that can parse very long documents in one shot without running out of memory, using a clever architectural trick called Reference Sliding Window Attention that keeps the full image in view while only remembering the last ~128 tokens of generated text. The thread immediately split into two camps: practitioners who deal with messy real-world documents—handwriting, multi-column layouts, CJK scripts, old scans—pushed back hard on anyone claiming "OCR is solved," arguing that even commercial tools like Textract and Mistral fail regularly and that traditional OCR still struggles with layout and non-English scripts. Meanwhile, the technical crowd dug into the KV cache optimization, noting that the sliding window approach is basically injecting an LSTM-like memory into a transformer, and that it could be a game-changer for local AI inference on long documents. Several people shared war stories of having to slice images manually and glue results together, confirming that the community has been desperate for something that handles long-horizon context without crashing or hallucinating.

Mistral OCR 4 [comments]

464 points · 119 comments · mistral.ai · 18h ago

Mistral released OCR 4, a document-understanding model that extracts text with bounding boxes, block types, and confidence scores across 170 languages, available via API or self-hosted. The HN thread quickly turned into a war story exchange: people who'd fed it 55-year-old degraded paper files were impressed, and several said it beat classic tools like Abbyy FineReader for low-res or non-standard text. Pricing was a flashpoint—$4 per 1,000 pages drew comparisons to Google Vision OCR at $1.50, but counterarguments noted Google's is raw text extraction, not layout-aware, and that Azure Document Intelligence runs $10. Handwriting recognition came up repeatedly, with mixed but generally positive anecdotes. A smaller contingent pushed back on Mistral's broader model quality (coding, chat) but conceded the OCR is genuinely competitive, and a benchmark link from a commenter suggested even open-source models can match it on structured parsing if you force JSON schemas.

Israel targeted Gaza children resulting in genocide, UN inquiry says [comments]

456 points · 201 comments · www.reuters.com · 21h ago

The linked article wasn’t available to this summarizer; from the discussion, it’s a Reuters story on a UN inquiry concluding that Israel’s military campaign in Gaza amounted to genocide, specifically targeting children. The thread immediately turned into a meta-drama about flagging and visibility — people tracked the post being pulled from the front page while still racking up points, and argued that moderation was suppressing the story. Actual content debates quickly abandoned the article’s legal findings and instead spun into whether the UN has any real power, with a long tangent comparing the Security Council’s veto structure to the failed League of Nations. Several people argued that only raw power, nuclear deterrence, and shifting great-power alliances (like the end of Cold War support for South Africa) can actually resolve these situations, while others pushed back that the definition of genocide has become a useless, hyper-legal distraction and that concrete harm reduction or outright boycotts matter more than UN resolutions.

Jerry's Map [comments]

448 points · 52 comments · www.jerrysmap.com · 13h ago

Jerry Gretzinger has been hand-drawing an enormous, ever-evolving map since 1963, using a custom card deck to randomize which panels he works on and how. HN was immediately enchanted by the project's Borgesian absurdity, but a heated split emerged when someone suggested feeding the card system and tiles into an AI generator. Multiple people pushed back hard, arguing that the artist's slow, deliberate process is the whole point and that shoehorning AI in misses what makes it marvelous. Others dug into the procedural-generation angle more sympathetically, comparing it to TTRPG dungeon tables or game-map seeding, and a few recommended the recent People Make Games documentary that covers the project in depth.

Crypto in 2026: Oh, This Is the Bad Place [comments]

397 points · 495 comments · www.stephendiehl.com · 22h ago

Stephen Diehl’s essay argues that by 2026, crypto has become a self-referential gambling ecosystem—meme coins, prediction markets on Jesus’s return, and stablecoins privatizing monetary policy—all designed to farm retail users who think they’re investing. The thread’s top reply immediately compared the essay’s fictional “Mike” pipeline to D.A.R.E.-style drug propaganda, sparking a long back-and-forth about whether the slippery slope from CumRocket to 0DTE options to sportsbook parlays is accurate or just alarmist. Several people pushed back hard, arguing that calling crypto “gambling” conflates high-risk investing with literal betting, and that the real problem is lack of education and heavy regulation, not the asset class itself. Others countered that the vice analogy holds up—pointing to credit card debt as a similarly predatory, regulated system that ruins lives without banning it. The consensus fracture was clear: some see Diehl’s portrait as a necessary wake-up call, while others think it’s hyperbolic moralizing that will backfire the same way the war on drugs did.

The Coming Loop [comments]

385 points · 267 comments · lucumr.pocoo.org · 20h ago

Armin Ronacher's essay argues that AI coding agents are moving into autonomous "loops" beyond simple prompting, producing code that's defensive and overly complex while warning that you can't opt out of this future. The comment thread immediately splits into a nasty flame war over whether these loops are overhyped: one camp demands proof of a billion-dollar solopreneur startup, triggering a prolonged car-vs-Mach-speed analogy debate that gets personal fast, with accusations of deflection and bad thinking on both sides. A quieter but substantial thread focuses on the loss of coding joy—several people admit they've stopped writing code for fun because AI makes their hand-crafted work feel like transcribing a phonebook next to a photocopier, while others say AI actually reignited their interest by handling the busywork so they can focus on the hard parts. The consensus is uneasy: nobody denies the technology is coming, but there's real tension between those who see it as inevitable progress and those mourning the craft.

Show HN: TikZ Editor – WYSIWYG editor for figures in LaTeX [comments]

381 points · 71 comments · tikz.dev · 17h ago

The submission is an open-source WYSIWYG editor for TikZ figures in LaTeX, built almost entirely by an AI coding agent, that lets you drag and resize elements while keeping the source code clean and in sync. Academics who’ve spent years twiddling coordinates and recompiling were thrilled, with many calling it long overdue. The killer feature, repeatedly noted, is that it preserves hand-written TikZ source rather than turning it into generated soup like Inkscape does with SVG—but some users pushed back on the editor’s tendency to emit absolute coordinates for everything, arguing it ignores TikZ’s relative positioning idioms and alignment features; the author acknowledged the difficulty of guessing user intent there. The discussion also branched into requests for support of Typst’s Cetz and pgfplots, with a licensing wrinkle about distributing GPL'd code alongside MIT, plus a nostalgic detour about Xfig as the original WYSIWYG LaTeX diagram tool.

In memory of the man who put red and green squiggles under words [comments]

346 points · 47 comments · devblogs.microsoft.com · 13h ago

The article is a tribute to Tony Krueger, the Microsoft Word developer who pioneered the red and green squiggly underlines for real-time spell and grammar checking—a feature so ubiquitous that most people never think to credit it. The HN thread quickly zeroed in on a delightful bit of citogenesis: Raymond Chen’s article mentions that Wikipedia credits Krueger with porting Chip’s Challenge, but the Wikipedia citation for that port now points back to Chen’s article, creating a neat circular reference that someone called out as a live example of the xkcd “Citogenesis” strip. Several commenters then jumped into the weeds of whether the squiggles actually worked well, with a split between those who find them indispensable and those who say modern autocorrect is broken and intrusive—one person even ranting that Word now flags “the” as a misspelling. There was also pushback about historical precedence: someone noted that ProWrite on the Amiga had real-time red squiggles before Word, and others debated the quality of AI-driven autocorrect versus the old squiggly system.

Extreme Heat conference cancelled due to extreme heat warning [comments]

338 points · 346 comments · www.lse.ac.uk · 8h ago

A London School of Economics conference on extreme heat governance was cancelled because the UK Met Office issued a red extreme heat warning. The thread seized on the irony immediately, with most of the discussion shifting away from the event's intended topic and into a sprawling argument about whether Europeans are being silly for not installing air conditioning. Australians and Americans brought up that 37–40°C is unremarkable where they grew up, but the counterargument was quick: humidity and building design matter more than raw temperature, and older European buildings make retrofitting AC expensive or legally impossible. Several people dug into wet-bulb temperature and acclimatisation, while others insisted this is a genuine mortality spike, not just discomfort, and that the UK's resistance to AC is a policy failure that's going to get worse as records keep breaking.

Madison Square Garden compiled a list of activists against facial recognition [comments]

300 points · 88 comments · www.404media.co · 18h ago

Madison Square Garden compiled a dossier on activists who opposed its use of facial recognition, which was included in a 45GB cache of data stolen from the company and leaked online. The HN thread focused heavily on the broader legal and ethical dimensions of using facial recognition to enforce trespassing bans at near-zero marginal cost—many argued this removes the natural friction that keeps such bans limited to serious cases. Several commenters pointed out that MSG's owner James Dolan has a long history of aggressive behavior, including banning entire law firms because one lawyer was litigating against the company, and that the venue pays no property tax despite being a de facto monopoly in New York. There was significant pushback against the idea that businesses have an unfettered right to ban people for any reason, with some noting that the Supreme Court's commerce clause reasoning for anti-discrimination laws could logically extend to banning businesses from retaliating against customers who exercise their legal rights. A few commenters also dug into the security implications, noting that storing facial recognition ban lists insecurely creates a serious privacy risk that dwarfs the original surveillance concern.

The worthlessness of Vitamin D is mildly exaggerated [comments]

284 points · 192 comments · dynomight.net · 15h ago

The linked article argues that while vitamin D isn’t the miracle supplement it was once hyped to be, the pendulum has swung too far: the evidence from randomized trials is weak but positive, and evolutionary biology suggests low-ish levels are worth correcting. The HN thread immediately zeroed in on the idea that blood vitamin D might just be a proxy for outdoor exercise or sunlight exposure, pointing to studies that find much stronger mortality reductions from sunlight (possibly via nitric oxide production) than from supplements alone. Several people who tested severely deficient reported dramatic personal improvements, but others pushed back hard, noting that excess supplementation is becoming a real problem — one doctor mentioned seeing more patients with toxic levels than deficiency, thanks to influencer-driven megadose advice. A strong undercurrent of the discussion was the importance of actually testing your levels before supplementing, with links to cheap direct-to-consumer lab tests, and a recurring comparison to how fish oil went through the same hype-then-debunk cycle.

AI's Affordability Crisis [comments]

282 points · 370 comments · blog.dshr.org · 16h ago

The article argues that AI companies like OpenAI and Anthropic have been massively subsidizing token usage to create demand, but are now forced to raise prices as they burn through cash—citing figures like OpenAI’s $38.5 billion loss and claims that companies are reining in AI use as costs spike 7x overnight. HN was sharply split: a vocal group immediately pushed back, arguing that API costs have actually dropped 50x over three years and that the article ignores dramatic efficiency gains in models and hardware, while others countered that falling prices don't fix the fundamental math of unsustainable capex and that the entire business model is a bubble. The thread also dove into the weird signal of deliberate typos in the article—some suspected the author left them in to prove it was human-written, sparking a meta-discussion about whether “proof of human work” will become a thing. A significant tangent emerged around open-source models and government bans, with many arguing that the frontier labs have already lost the coding war to cheaper, capable models you can run on a consumer GPU or cloud instance.

California AB 2047 makes 3D printers off-limits to students, educators, business [comments]

258 points · 180 comments · www.the3dprintingnerd.com · 9h ago

California’s AB 2047 would require all 3D printers sold in the state to include government-certified “firearm blocking” software, effectively banning most consumer and educational printers by 2029. The HN thread largely dismissed the bill as technically impossible—printers can’t distinguish a gun part from a chess piece—and pointed out that it criminalizes routine firmware tweaks that teachers and researchers depend on. Several commenters noted that California’s legislature has a history of passing performative gun laws that get vetoed or gutted in court, but also warned that New York already passed something similar and copycat bills are inevitable. The real split wasn’t over whether the bill is bad—everyone agreed—but over whether the out-of-state crowd gets to sneer at California’s regulatory zeal or whether the state’s sheer market power will drag the rest of the country into a 3D-printing dark age. A few side tangents dug into how most Americans can’t actually drive to another state to buy a printer, making the “just cross the border” argument hollow for the rural and poor.

Claude Tag [comments]

252 points · 168 comments · www.anthropic.com · 14h ago

Anthropic announced Claude Tag, a Slack integration that lets teams tag @Claude in channels to delegate tasks, with shared context, proactive updates, and async work—claiming 65% of their own product team’s code now comes from it. HN immediately questioned whether this is just a rebrand of their existing Slack bot, and several people pointed out it’s a direct shot at every Slack API startup out there. The multiplayer shared-context model got serious debate: some love the idea of a team-wide AI assistant, others worry about coworkers hijacking your session or leaking private info across channels, though Anthropic claims per-channel identities stay scoped. A strong chorus called this part of Anthropic’s “throw shit at the wall” phase, releasing products weekly that feel sloppy and unintegrated—like Claude Design and Claude Code not talking to each other—and criticized the lack of proper RBAC and audit logging for enterprise customers who aren’t on Slack. The pricing (rumored around $8k/month for enterprise) drew mixed reactions, with some calling it absurdly cheap for what it does and others scoffing.

Vulnerability reports are not special anymore [comments]

237 points · 126 comments · words.filippo.io · 8h ago

The article argues that vulnerability reports have lost their special status because LLMs can now find the same bugs as human researchers, making insight and confidentiality no longer scarce. The HN discussion overwhelmingly confirms this from the trenches: people running disclosure programs report a deluge of low-quality, AI-generated spam—going from 5 reports a month to 5 a day—and many are considering shutting their programs down entirely. Some pushback focuses on supply-chain attacks and dev-dependency CVEs, arguing that even “shallow” bugs can be dangerous if exploited in build pipelines, but the dominant sentiment is that the signal-to-noise ratio is broken and maintainers are exhausted. A few practical proposals surface—like requiring a small refundable deposit or banning repeat offenders who send slop—but the thread largely agrees with the author: triage and prevention are now the job, and treating every vuln report as a sacred obligation just doesn’t scale.

Meta Pauses Employee-Tracking Program Following Internal Data Leak [comments]

220 points · 140 comments · www.wired.com · 7h ago

Meta paused its employee surveillance program (tracking keystrokes, mouse movements, screen content) after a security lapse exposed the collected data to anyone inside the company. The thread latched onto the irony of the surveillance being undone by its own leak, but quickly split on what that means: most people expect Meta to just rebuild it with tighter access controls, since tracking performance metrics at scale is too entrenched to abandon. A vocal camp went further, using the leak to rehash arguments that working at Meta is a moral compromise—triggering a bitter back-and-forth about whether employees are truly stuck or just wearing golden handcuffs, with some insisting a remote job at a lower-paying company is always an option. The deeper takeaway wasn’t about the leak itself; it was whether this changes anything, and the consensus was no—the incentives to surveil are too strong, and the fix will be better access controls, not a rethink of the program.

Elevated error rate across multiple models [comments]

209 points · 256 comments · status.claude.com · 17h ago

Claude suffered an hour-long outage on multiple models and products, now marked resolved. The HN thread quickly pivoted from the incident itself to a broader debate about whether the claimed productivity gains from AI coding tools are real when services go down so often—several people crunched the uptime numbers and argued that 0.7-0.9% downtime, concentrated during working hours, effectively cancels out any net benefit. A split emerged between those who insist experienced developers can still code without AI or internet and those who say the baseline is gone forever, pointing to documentation atrophy and the impossibility of maintaining modern codebases manually. A long tangential argument broke out over the security of `curl | sh` installers, with people noting that Claude Code itself uses that method while criticizing a promoted alternative (pi.dev) for doing the same and then promptly erroring out itself.

The war on terror primed America for autocracy [comments]

203 points · 165 comments · archive.is · 5h ago

The linked article wasn’t available to this summarizer; from the discussion, it argues that the post-9/11 security state and wars paved the way for American authoritarianism. The thread mostly agrees that torture, mass surveillance, the Iraq invasion, and the TSA’s security theater were clear overreaches, but it splits hard on whether that overreaction was inevitable given the genuine shock of 9/11 — some call the fear manufactured or cowardly, while others defend it as understandable when hijackings were still a live threat and cockpit doors hadn’t been hardened. A huge chunk of the conversation derails entirely into a bitter dispute over the 1947 partition of India and Pakistan, sparked by a comment about JD Vance cozying up to Pakistan’s military junta, with people arguing over whether partition was a British-imposed disaster or a necessary separation that benefited India. The core point about the war on terror gets some pushback from those who note that earlier U.S. history was full of worse torture and less liberty, but the dominant tone is that the whole thing was a predictable slide into autocracy that many saw coming at the time.

Swift Package Index joins Apple [comments]

200 points · 66 comments · swiftpackageindex.com · 14h ago

The linked article wasn't available to this summarizer; from the discussion, the Swift Package Index has been acquired by Apple.

The HN thread quickly split between those worried Apple will wreck another good thing and those hoping this signals genuine improvement. The pessimistic side hammered on Apple's awful history with open source, developer identity verification (one blind developer detailed being locked out because a driver's license was the only accepted ID), and a policy that bans employees from contributing to open source outside work. Others pushed back, noting Apple has been open-sourcing more and that SPI should operate independently, though the counter was that even "open" Apple projects show contempt for standards. The conversation also got into the mechanics of "being Sherlocked" — a long history lesson on Apple cloning Watson into Sherlock — with relief that this time they bought instead of cloned, though some argued that's still effectively the same outcome. A smaller tangent debated whether languages need built-in package managers from day one, using Go and C# as examples of late arrivals that eventually unified the ecosystem.

Digital euro clears key hurdle as EU seeks to break free from U.S. credit cards [comments]

195 points · 311 comments · finance.yahoo.com · 15h ago

The article covers the European Central Bank winning parliamentary backing for a digital euro, aimed at cutting Europe's dependence on US payment giants like Visa and Mastercard, especially given geopolitical tensions. The HN crowd immediately split into two camps: one side sees this as a necessary sovereignty move, pointing out that your current bank account and card transactions are already tied to your identity and routed through US networks, so a European alternative is overdue. The other side dismisses it as a dystopian, centralized digital currency that nobody asked for, with fears about surveillance and digital ID hooks—though critics note that existing cashless payments are hardly private either. A surprising amount of the thread turned into a debate about credit vs. debit card usage in Europe versus the US, and whether the digital euro will actually solve anything when local systems like iDEAL and Wero already exist. There was also pointed pushback from people who understand the payments industry, arguing that Visa/Mastercard are just the network layer, not the card issuers, and that true independence requires building a new network, not just another digital wallet.

75% More Pedestrians Have Been Killed Since 2009. Giant Trucks and SUVs Are Why [comments]

190 points · 12 comments · www.thedrive.com · 14h ago

The Drive article points to the New York Times investigation showing that pedestrian deaths are up 75% since 2009, and the primary culprit is the shift to bigger trucks and SUVs with higher hoods and more mass. The HN thread mostly funneled into the original NYT discussion, but a few people pushed back hard: one commenter who claims to have been part of a large research organization says their studies found mobile device usage, not vehicle size, is the most significant causal factor, though they acknowledge the article’s 10% attribution to size is accurate. Others leaned into the arms-race dynamic, arguing that everyone buys bigger vehicles for perceived safety, then everyone else follows suit, and that we need a new license class for vehicles over three tons plus sensible headlight rules. The usual defensive jokes about daily-driving F350s for the occasional fence post also made an appearance.

Anthropic updates their terms to verify age or identity [comments]

188 points · 174 comments · www.anthropic.com · 12h ago

Anthropic quietly updated its privacy policy to require government ID and biometric data — including facial geometry templates — for age or identity verification on Claude. The thread immediately split between users who see this as a necessary safety measure for a paid service and those who called it a dystopian slide toward surveillance-state gatekeeping, with several commenters drawing direct parallels to China’s social credit system and arguing the US is speed-running the same playbook. Pushback came from people noting that identity checks for paid products aren’t new, but critics countered that the biometric scope and the fact that verification data won’t be deleted (citing a recent hack of a Discord age-verification vendor) make this a fundamentally different ask. A strong undercurrent argued that this is exactly why open-weight models must be the industry’s future — proprietary frontier models become tools for corporate and government control, creating an economic underclass unable to afford or access unvetted intelligence. The consensus among skeptical voices was that Anthropic’s move accelerates enshittification, while defenders mostly shrugged and said you can always run Qwen locally.

Don't verify email addresses by sending spam to them [comments]

172 points · 51 comments · milek7.pl · 11h ago

A blog post exposed that Pangram's email validation API doesn't just check if an address exists—it sends actual spam emails to the submitted address, complete with invisible filler text about magnetic domains to fool Bayesian filters. HN users were initially skeptical, with several calling it too insane to be real, but multiple people reproduced the behavior, getting similar weirdly-themed spam from burner domains. The thread eventually settled on the theory that a third-party validation service (likely ZeroBounce) is behind the spam, using it as a honeypot-detection tactic—Pangram's founder even showed up to say they had no idea and would investigate. A smaller faction argued this is simply a data-leak scheme, while others veered into a broader debate about email encryption and why financial institutions still send unencrypted PDFs.

Trains halted across Germany because of communication system problem [comments]

158 points · 150 comments · apnews.com · 10h ago

A nationwide failure of Deutsche Bahn's GSM-R digital communication system brought all trains in Germany to a halt for hours, leaving passengers stranded at stations. The HN thread immediately went to the usual place: this is Deutsche Bahn being Deutsche Bahn, with one person noting that for the company, this kind of outage is just "Tuesday." A sizeable contingent suspected Russian hybrid warfare, pointing to a previous Polish rail hack and recent sabotage incidents, but others pushed back hard, claiming word on the ground is it was a failed software update or an expired TLS certificate. The deeper discussion landed on three decades of underinvestment and the botched privatization model that left DB a state-owned "private" company too dysfunctional to maintain its own tracks, with comparisons to Switzerland's far higher per-capita rail spending and the UK's similarly cursed network rail story.

San Diego photologs from the 1970s [comments]

150 points · 48 comments · www.beautifulpublicdata.com · 15h ago

The post digs into a collection of 1970s San Diego street-level photos from the city’s transportation department — essentially pre-digital Street View, with pastel cars, wild signage, and a lot of steak-and-strip-club culture. Most of the conversation latched onto the observation that the world has lost its color and whimsy, with people arguing the shift to white/black/silver cars and computer-perfect signs is a genuine aesthetic loss, though a few pointed out that smog and leaded gas were less charming tradeoffs. The thread also got unexpectedly deep into San Diego urbanism: a bunch of locals confirmed that the infamous Les Girls club is still standing (and just got a new sign), then the discussion spiraled into zoning, Prop 13, and how California stopped building infill housing in the early ’70s — with one commenter in commercial real estate blaming Prop 13 for owners sitting on decrepit lots rather than developing affordable housing. There was also a minor detour into why the chain was called “Der Wienerschnitzel” instead of “Das,” and whether full-service gas stations still exist.

Wikipedia cofounder Larry Sanger blocked from editing Wikipedia [comments]

147 points · 190 comments · en.wikipedia.org · 20h ago

Larry Sanger, Wikipedia's co-founder, has been banned from editing the site, with his user page now sporting a block notice and a laundry list of radical reform proposals he'd been pushing. The thread quickly split between people who saw the ban as straightforward enforcement of Wikipedia's anti-canvassing rules—Sanger was accused of organizing off-wiki support to push his agenda—and those who took it as the latest proof that Wikipedia is run by a self-protecting bureaucracy of petty nerd-lords. Dozens of commenters piled on with bitter personal stories of trying to improve articles in math, chemistry, or transit, only to be hounded and reverted by entrenched editors who know every procedural loophole and will outlast any casual contributor. Others pushed back, arguing the complaints are mostly from people editing controversial topics or who don't realize they violated basic norms like citing sources, and that Sanger's own history—he left in 2002 and only returned last year to stir things up—makes the block look routine. The real takeaway: the conversation wasn't really about Sanger at all, but about whether Wikipedia has ossified into a system where the cost of entry is total submission to a handful of domain fiefdoms.