← Oct 11Monday, October 12, 2026 · all daysOct 13 → · today »
1.Fingerprints are the new cookies(royfish.dev)
739 points by royfish 2 days ago | 364 comments | permalink
tl;dr: Browser fingerprinting—using hardware and software signals like GPU, CPU, fonts, audio processing, and canvas rendering—can uniquely identify users across sessions without cookies, VPNs, or incognito mode. Google, after years of delaying third-party cookie deprecation, now permits fingerprinting in its ad products, making it the de facto successor to cookies. Only Brave, Tor, and Mullvad Browser offer meaningful engine-level defenses; extensions and Firefox's protections help but can ironically make you more identifiable by being rare.
HN Discussion:
  • ↑Browsers should gate high-entropy APIs behind user consent to prevent fingerprinting
  • ↑JavaScript is the root problem; it gives sites too much power and should be restricted by default
  • ↓Fingerprinting is overhyped and impractical commercially; IP addresses still do most of the work
  • ~Spoofing or having a generic fingerprint may be more effective than trying to be unfingerprintable
  • ~The real issue is tracking/consent law and third-party advertising, not the specific technology used
2.Total Annihilation, rebuilt for modern computers(nanolathe.gg)
670 points by jttnr 2 days ago | 253 comments | permalink
tl;dr: Nanolathe is an open-source, MIT-licensed 2.5D RTS engine that reimplements Total Annihilation via clean-room research, with native builds for Windows, Mac, and Linux plus a browser demo of the original three missions. It features a modern GPU renderer (with light, glow, and 2× art) alongside a Classic mode, and supports single-player campaigns, skirmish, Survival, and online multiplayer using game files you supply from GOG, Steam, or original CDs.
HN Discussion:
  • ↓Beyond All Reason is a superior existing spiritual successor to Total Annihilation
  • ↓Spring engine already provides similar clean-room TA reimplementation, questioning this project's value
  • •Someone is building a similar modernization effort for Supreme Commander instead
  • ↓The project has poor documentation and error messages, other open source alternatives seem better
  • ↓Supreme Commander and Planetary Annihilation are more legitimate successors to TA
3.Cartographers of North Korea (2019)(cartographers-nk.wonyoung.so)
315 points by edent 2 days ago | 66 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Fascination with contributors' motivations for mapping North Korea on OSM
  • ↑Appreciation for OSM as a valuable collaborative internet resource
  • ↑Praise for the article's design, layout, and readability
  • •Sharing related content like tourist videos and documentaries about North Korea
  • ↓Criticism of the article's interactive format, preferring a traditional article
4.Terence Tao: Math 2.0 [pdf](teorth.github.io)
556 points by Anon84 2 days ago | 540 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↓Tao's cancer/mechanism example is misinformed; much of medicine and engineering works without full mechanistic understanding
  • ↑Tao accurately captures the grief and disruption mathematicians feel as AI solves long-standing problems
  • ↑Tao's framing of math as a shared 'codebase' that AI fails to contribute to elegantly is insightful
  • ↓Tao focuses too much on current AI limitations and avoids confronting the future obsolescence of human mathematicians
  • ↑Context matters: Tao is broadly pro-AI and is thoughtfully exploring how human work will evolve
5.The gap in shared understanding of LLM capability is widening(twitter.com)
681 points by albertzeyer 2 days ago | 1000 comments | permalink
tl;dr: LLM capability awareness splits sharply across a funnel: ~75% of people barely use them, ~20% treat free-tier chatbots as a slightly better Google, ~0.2% (mostly in math/code) see agents complete weeks of work from a prompt, and a few thousand insiders witness swarms of agents doing mega-projects, zero-days, and novel science. The gap is widening due to problem ambition, LLMs' jagged strength in digital/verifiable domains, and tiered access. The result is that most of the public sees "derpy chatbot" while a tiny sliver experiences a near-vertical capability curve—simultaneously.
HN Discussion:
  • ↑Agrees that non-tech workers underestimate LLM capability and automation risk to their jobs
  • ↓Questions why AI companies don't market these capabilities if the gap is real
  • ↓Author is lost in marketing hype and ignores why LLMs only work in narrow domains
  • ~The gap exists only because LLMs work on machine-verifiable tasks, not a true capability divide
  • ↓Economic realities like token pricing and lack of business ROI undermine the vertical capability narrative
6.Passkeys are a trap(nonfunctional.substack.com)
1030 points by laurex 2 days ago | 541 comments | permalink
tl;dr: Passkeys, pushed by the FIDO Alliance, bundle many different credential types under one confusing name, and the standard includes "remote attestation" — a feature that lets websites verify you're using approved hardware, software, and OS. While attestation isn't widely enforced yet, the author warns it could eventually be used to lock users out of alternative operating systems, custom browsers, or self-written software, undermining user control. The recommended alternatives are TOTP (authenticator apps) for convenience or hardware security keys like YubiKey for high security without OS-level lock-in.
HN Discussion:
  • ↓Attestation concerns are overblown since it's not actually enforced in practice
  • ↑Passkeys lack portability and tie users to specific devices, validating concerns
  • ↓Article misses that passkeys work well in password managers and offer great UX
  • ~The alarmist tone and title undermine the article's legitimate points
  • ↑Remote attestation is a genuine freedom threat worth sounding alarms about
7.So, you’d like to sell your print issues of The Onion?(theonion.com)
371 points by mooreds 2 days ago | 61 comments | permalink
tl;dr: The Onion is seeking print copies of specific back issues to fill gaps in its archive, primarily from 1988-1991 and 2008-2013, along with scattered issues from other years. Issues are identified by volume and issue numbers on the front page, and must be clean and readable. Interested sellers can submit details via a Google Form, with the understanding that sold issues become permanent property of The Onion.
HN Discussion:
  • ~Title should better reflect that The Onion needs fan help filling archive gaps
  • ↑Nostalgic reminiscing about picking up print issues in various cities
  • ↑Potential sellers checking their old collections to possibly contribute
  • ↓Skepticism about the framing, questioning if issues were stolen or dramatized
  • ↑Learning new facts about The Onion's history and supporting current management
8.NYC's "Click to Cancel" rule is now in effect(nyc.gov)
587 points by gregsadetsky 2 days ago | 318 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~Rule won't stop companies like Adobe from using cancellation fees as loopholes
  • ~Good rule but skeptical about NYC's enforcement follow-through
  • •Similar legislation is spreading to other jurisdictions like the EU
  • ↑California's version has worked well, hoping for federal adoption
  • ↑Shady cancellation tactics by companies make this law necessary
9.IRCv3(ircv3.net)
407 points by basilikum 2 days ago | 347 comments | permalink
tl;dr: IRCv3 is a working group developing backwards-compatible extensions to the IRC client protocol, building on RFC1459/RFC2812. Shipped features include SASL authentication, server-side message timestamps (for better bouncer playback), account tags, instant away notifications, and message grouping. In-progress work covers standardized account registration, chat history access, automatic STS-style secure connection upgrades, Unicode nicks/channels, and client avatars.
HN Discussion:
  • •Nostalgia for older chat apps like ICQ with better UX than modern options
  • ~IRCv3 protocol changes are nice but client-side improvements matter more
  • ↑Actively experimenting with IRCv3 features like persistent chat history via Ergo
  • ↓IRCv3's many optional extensions cause fragmentation and inconsistent user experiences
  • ↑IRC/IRCv3 is a viable, preferable alternative to Discord for communities
10.3rd Yandex Cloud Data Center Was Hit(status.yandex.cloud)
626 points by defly 3 days ago | 774 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Strike is justified retaliation for Russian attacks on Ukrainian infrastructure
  • ↑Celebrating the attack as deserved consequence for Russia's war
  • ↑Promoting donations to Ukrainian volunteer funds to support the war effort
  • •Reflecting on how data centers becoming targets will drive decentralization and fortification
  • •Sharing supporting data/links about the outage without taking a stance
11.I paid people to try and follow my README(shkspr.mobi)
415 points by edent 2 days ago | 203 comments | permalink
tl;dr: The author paid people €25/hour to screen-share and think aloud while following his project's README, uncovering numerous blind spots like broken links, unexplained jargon, bad section ordering, and unfunny jokes that confused readers. He iteratively updated the docs after each session, spending about €150 total, and argues this beats using an LLM to simulate users because real humans provide authentic frustration cues and unique perspectives.
HN Discussion:
  • ↑Writing docs is hard due to author bias; even personal READMEs become incomprehensible quickly
  • ↑READMEs commonly fail to explain what the software actually does, confirming the article's findings
  • ~This is just rebranded usability testing or QA work, nothing novel
  • ↓AI agents can effectively supplement or replace human testers for doc testing
  • •Documentation should be treated like code with proper tooling and processes
12.I'm sorry, but you still have to think(itsallaboutthebit.com)
435 points by drogus 2 days ago | 181 comments | permalink
tl;dr: DHH's AI-generated Rust, Elixir, and Go rewrites of Campfire produce misleading comparisons because the LLM made different implicit trade-offs (backwards compatibility, Redis vs in-process queues, sync vs async locks) across languages, and the benchmarks only measured throughput. Deeper testing reveals the Rust version drops 99% of notifications under load due to a small broadcast channel capacity, while Elixir's unbounded mailboxes trade memory and latency for delivery—neither is strictly better. The takeaway: language choice doesn't automatically solve concurrency problems, and you still need to understand code, failure modes, and trade-offs.
HN Discussion:
  • ↑AI-generated low-quality work is cheap to produce but expensive to debunk
  • ↑LLM translation worked here only because humans already did the hard thinking
  • ↑Developers should still read code and understand systems rather than abdicate to AI
  • ↓Worrying about understanding code echoes outdated concerns like distrusting compilers
  • ~Shipping half-understood code is fine for low-value features to save energy
13.LineageOS 24(lineageos.org)
447 points by timschumi 3 days ago | 182 comments | permalink
tl;dr: LineageOS 24 is out, based on Android 17, released ahead of schedule thanks to prior refactoring work. Highlights include a new image editor (Canvas), Material Design 3 Expressive updates across core apps, browser-based WebUSB flashing tools at flash.lineageos.org, a completed accessibility audit, and commonized SoC kernels for maintainers. Devices with Linux kernel 4.4/4.9 will remain on 22.2 only, while 24.0 launches with a large roster including Pixel 4 through Pixel 10 series, recent OnePlus, Xiaomi, Samsung Galaxy S20–S23, and Sony Xperia devices.
HN Discussion:
  • ↑Appreciation for LineageOS extending device lifespan and keeping phones from landfill
  • ↑Excitement about the new generic bare-metal target enabling Android on laptops/PCs
  • ↓Frustration with hardware-specific issues like broken GPS or poor camera quality on LineageOS
  • ~Lineage should improve device recommendations and clarity around supported new devices
  • ↓Lineage needs stronger privacy/security controls to compete with GrapheneOS
14.A Remote Employee Refused 160 Webcam Photos a Day. Her Employer Fired Her(inc.com)
272 points by bhrlady 2 days ago | 188 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Surveillance is a pretext for soft layoffs or forcing return-to-office, not productivity
  • ↑Storing invasive employee surveillance data creates serious privacy and liability risks
  • ↑Such invasive monitoring violates human rights and should be illegal, as European precedent shows
  • ↑Employer may be violating disability accommodation laws given the employee's health condition
  • ↑Productivity should be judged by outcomes, not screen time or webcam presence
15.The tilde in your PATH may not be your HOME(disconnect3d.pl)
247 points by arusekk 2 days ago | 176 comments | permalink
tl;dr: Using `export PATH="$PATH:~/.local/bin/"` (with quotes) in your shell config doesn't expand `~` to your home directory—instead, it literally adds `./~/.local/bin/` to your PATH, which can be a security risk since binaries placed in that relative path will be executed. The fix is to use `$HOME` instead of `~`. You can audit your setup with `echo "$PATH" | grep -- '~'`.
HN Discussion:
  • ~Just don't quote the tilde; the issue stems from unnecessary over-quoting habits
  • ↑Avoid tilde in scripts entirely and use $HOME instead
  • ↑Bash's quoting/escaping rules are absurd and not worth learning
  • ↑Shells should have a strict mode to validate PATH entries and prevent such issues
  • ↓The problem would be obvious since the PATH entry wouldn't work in the first place
16.Nitter: Update Oct 10th seeking funding and legal help(nitter.net)
470 points by ForHackernews 2 days ago | 247 comments | permalink
tl;dr: X Corp. sent cease-and-desist letters in August and September 2026 demanding permanent takedown of Nitter instances and its repository. The project's maintainer (zedeus) now says earlier claims about having legal representation were based on false assurances, and Nitter currently has no legal counsel. He is seeking lawyers, organizations, and donations to fund a legal defense.
HN Discussion:
  • ↑X is weaponizing legal system to chill legitimate speech and projects
  • ~Nitter likely cannot operate legally and hosters face real legal risk
  • ↑Frontends like Nitter are important and worth funding despite legal issues
  • ↑EFF/FSF should help and fair use defenses may apply
  • •Questioning what Nitter is and its purpose
17.Google told to halt work on datacentres in Finland over environmental concerns(theguardian.com)
445 points by heyimada 2 days ago | 170 comments | permalink
tl;dr: Finnish authorities have ordered Google to halt construction on two datacentres in Muhos and Kajaani after the company cleared over 500 hectares of forest without completing required environmental impact assessments. The sites, part of a €13bn Finnish datacentre expansion, were reportedly reduced to "sand" through tree removal, topsoil stripping, and road construction. Google acknowledged it "fell short" of its standards, while conservationists blame an "overheated" datacentre market and under-resourced municipalities for the systemic oversight.
HN Discussion:
  • ↑Google's non-apology deflects from the fact they violated legal obligations, not just internal standards
  • ~The cleared 'forest' was actually a monoculture plantation, not pristine nature
  • ↑Data centers should be forced to use brownfields rather than clearing natural land
  • ↑Proposed fines will be trivial to Google and fail to deter future violations
  • •Finland's economic desperation makes it permissive toward environmentally damaging investment
18.The RAM shortage is bringing back DDR4(theverge.com)
292 points by 1potato 4 days ago | 315 comments | permalink
tl;dr: Facing severe DDR5 price hikes (a 32GB Corsair kit now runs $620 vs. $260 for DDR4), Intel and AMD are reviving support for older DDR4-compatible platforms. Gigabyte announced new motherboards for Intel's LGA 1700 socket, with new compatible CPUs expected in early 2027, alongside similar moves for AMD's AM4 platform tied to the Ryzen 7 5800X3D relaunch. The shortage may persist for years, making decade-old memory tech a viable option again.
HN Discussion:
  • ↑Parallel ecosystems already exist using decommissioned server parts and older RAM standards
  • ~DDR5 prices will drop in ~24 months as new fab capacity comes online
  • ↑AI demand has cannibalized consumer memory supply, making shortages predictable
  • ↑DDR4 is still perfectly adequate for most consumer use cases
  • ↑Chinese manufacturers like CXMT ramping up older-tech production will reshape the market
19.2D Vehicles(patkerr.co.uk)
621 points by Michelangelo11 6 days ago | 118 comments | permalink
tl;dr: In 1996, the author wrote a 2D rigid-body physics simulation in GFA BASIC on an Atari ST that became the vehicle system in the original Grand Theft Auto. For its 30th anniversary, they've recreated it in JavaScript ("Motion Lab") with playable Car, Ship, and Brick modes. The post details the design: a proper rigid-body core with torques (uncommon in games then) layered with a deliberately simplified, non-physical tyre model that applies velocity-proportional resistance along and across each wheel's heading to produce convincing car-like handling.
HN Discussion:
  • ↑Appreciation for the historical significance and nostalgia of GTA 1/2 car physics
  • •Related references to other foundational 2D driving/physics models and games
  • ↓Criticism that the blog post's diagrams are poor and lacks explanation of design reasoning
  • ↑Praise for the prototyping approach and value of simple 'toy' physics
  • ↑Personal struggles replicating similar 2D vehicle physics, highlighting the achievement
20.A city-building game in which the city would prefer you didn't(housing.over.pizza)
542 points by JumpCrisscross 3 days ago | 195 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Shares similar satirical game ideas about bureaucracy and development obstacles
  • ↑Praises the game as fun gallows humor reflecting real building difficulties
  • •Discusses real SF housing policy and potential solutions like SB 79
  • ↑Suggests SF actually wants restrictive housing policies by design
  • ↑Extends the critique to other contexts like UK's HS2 infrastructure obstruction