At a certain bet size it would almost be self-fulfilling, heh, as one side would be very incentivized to keep at least that url working (buying the domain + hosting it if the page were to die)
In my mind, the part that is most likely to fail is "return an HTML document that still contains the following text." Nowadays, more and more "HTML documents" do not contain any content at all, just some JavaScript that is responsible for then fetching and displaying the content.
https://news.ycombinator.com/item?id=46139686
The part of this that's most likely to fail at some point is the "http://".
Now I'm a human slave copying text from web browsers to chat windows to get around JS rendering bullshit.
> A 301 redirect from www.longbets.org/601 to a different URL containing that text would also fulfill those conditions.
I assume this would cover the HTTP->HTTPS redirect scenario.
For the heck of it I confirmed "http://www.longbets.org/601" does in fact result in a 301 redirect to "https://longbets.org/601/". I suspected they might have used a 302.
Which is not, in my opinion, how things should be hosted on the Web.
Freenet had a different approach, even back in the early days (two decades ago). I interviewed Ian Clarke about it https://www.youtube.com/watch?v=JWrRqUkJpMQ
I wrote about it for years: https://community.intercoin.app/t/who-pays-for-storage-nfts-...
And recently I built Safecloud to be different: https://safebots.github.io/Safecloud/