HN Debrief

The original URL for this prediction will no longer be available in 11 years (2011)

  • Infrastructure
  • Web
  • AI
  • Developer Tools

The post resurfaced a 2011 Long Bets wager about whether typing a specific URL into a browser or a command-line tool would still return the promised text after 11 years. In 2026, the page still resolves, largely because longbets.org now issues a 301 redirect from the old HTTP URL to an HTTPS page, and the original bet text explicitly allowed that. That made the wager look almost solved by careful wording rather than pure infrastructure luck.

If you care about durable links, treat them as a product requirement with redirects, tests, and static exports, not as something your stack will preserve by accident. Also assume the hardest part is institutional continuity and funding, not DNS or HTML.

Discussion mood

Mostly amused and slightly cynical. People were impressed that the URL still works and that the bet anticipated redirects, but the dominant mood was that web permanence depends on human commitment and money, not elegant protocol design, and that many old promises survive only as long as someone cares enough to keep them alive.

Key insights

  1. 01

    Static exports beat heroic maintenance

    Flattening retired sites into plain HTML turns a fragile application into a cheap artifact. That changes the preservation problem from ongoing software maintenance to little more than domain control and object storage, which is why old forums and one-off sites can survive for decades after their original CMS is gone.

    When a product, blog, or docs set becomes historical rather than active, add a static export path before the original stack rots. Make this part of shutdown or migration planning, not a rescue project years later.

      Attribution:
    • mg #1
    • kimos #1
    • dmitrygr #1
  2. 02

    The hard part is succession

    Broken links usually come from incentives and continuity failures, not missing redirect rules. If a startup dies, a manager wants the old thing deleted, or the maintainer dies without leaving access and instructions, the URL disappears even if preserving it would have been technically trivial.

    Put domains, hosting, credentials, and redirect ownership into documented operations and estate planning. If no one specific is responsible after a reorg, acquisition, or death, assume the links will die.

      Attribution:
    • vasco #1
    • fragmede #1
    • joshspankit #1
    • troupo #1
  3. 03

    Browser policy can break archival promises

    A durable URL is no longer just a server-side contract. Browser moves toward HTTPS-first behavior and harsher treatment of plain HTTP can make an old address fail from the user's point of view even when the server still responds and redirects correctly. That means client software becomes part of link longevity.

    Do not rely on legacy HTTP entry points staying acceptable forever. Preserve canonical HTTPS URLs now, and test archived links in current browsers as well as with raw HTTP tools.

      Attribution:
    • JoshTriplett #1 #2
    • ywain #1
    • kijin #1
    • tredre3 #1
  4. 04

    Long Bets itself shows link rot

    Some older Long Bets entries appear to be gone, including innocuous ones that do not look legally sensitive. That undercuts the idea that the site is a stable archive and reinforces the point that even institutions built around long-term preservation still lose content or fail to keep it addressable.

    If a page matters, do not trust the original host as the only archive. Keep your own snapshots and submit important material to public archives while it is still online.

      Attribution:
    • pinum #1
    • mmahemoff #1
    • CSMastermind #1
  5. 05

    Turing test bets reward persona design

    The examples people raised, from ELIZA and PARRY to modern LLM prompting, all point the same way. A system can score well by narrowing the role, acting young or unstable, or avoiding substance. That makes the benchmark easy to game and weak as evidence of intelligence.

    Be skeptical of demos or headlines that frame chatbot success as a milestone in intelligence. Ask what persona, prompting, and evaluation setup made the result possible before treating it as a capability jump.

      Attribution:
    • DonaldFisk #1
    • andai #1
    • Someone #1
    • derdi #1
    • sublinear #1

Against the grain

  1. 01

    Behavior may be the only test that counts

    Judging intelligence or consciousness by internals sets a standard we do not use for other people. If a machine becomes genuinely indistinguishable from a human under prepared, expert scrutiny, then refusing to credit the result starts to look like special pleading rather than a serious scientific distinction.

    Keep some humility about claims that present architecture alone settles questions of mind. If your product or policy depends on human-machine distinction, plan for cases where behavior is good enough to erase the practical difference.

      Attribution:
    • wasmperson #1 #2
  2. 02

    Big stakes can preserve the page

    A public wager about URL survival is not a neutral observation of web decay. At high enough stakes, the existence of the bet itself creates an incentive for someone to buy the domain, keep hosting alive, or patch the redirect, which makes the prediction partly self-fulfilling.

    When evaluating forecasts about infrastructure durability, check whether the forecast changes the incentives around the outcome. Public commitments can become preservation funding in disguise.

      Attribution:
    • 9dev #1
    • matsemann #1

In plain english

301 redirect
A permanent HTTP response that tells browsers and tools that a page has moved to a new URL.
CMS
Content Management System, software used to create and manage website content.
curl
A command-line tool for fetching URLs and inspecting web server responses.
ELIZA
An early 1960s chatbot that used simple pattern matching to mimic conversation.
HTML
HyperText Markup Language, the standard markup language used to structure web pages and rich email content.
HTTP
Hypertext Transfer Protocol, the basic web protocol used to request pages and other resources.
HTTPS
Hypertext Transfer Protocol Secure, the encrypted version of HTTP used by most modern websites.
JavaScript
The main programming language used to add behavior and interactivity to websites.
LLM
Large language model, a type of AI system that generates and edits text by predicting likely next words from patterns in training data.
PARRY
A 1970s chatbot designed to simulate a person with paranoid beliefs.
Turing test
A thought experiment proposed by Alan Turing in which a machine tries to appear human in conversation.

Reference links

Web permanence and URL design

AI and Turing test references

Related commentary and prior discussion

Decentralized hosting and permanence