41–50 of 101 posts
I'll offer a weird but (I hope) valid alternative to the other great suggestions here: print the code of the static webpage on a piece of paper. Even better, archival paper [0], so it will really last a long time. In the future, anyone would be able to point a... smartphone, or a camera, to the paper, and instantly retrieve the webpage. An AI will ask them if they want to render the page using one of these very, very…
I doubt that people will know what to do with the "2D barcode" in 100 years. Someone who is willing to investigate will figure it out. But it is not something that will be convenient. I for example wouldn't know what to do with a barcode even today.
Ultimately you have to give a human direct responsibility for it; or in your case, a series of humans. I'd suggest you do buy a domain, but set up a legal/financial framework so that a long-standing law firm will keep up the payments for N decades (or for as long as the firm & its successors exist).
This is exactly the wrong advice, instead put your data on the blockchain, preferably Bitcoin, Bitcoin Cash or Ethereum. "Free" data storage for as long as the internet exists. Make the barcode to your transaction with the data, anyone with a brain and time can figure it out from there.
And make sure the Internet Archive indexes it. When people find old links that don't resolve anymore, IA is where they go.
Don't overthink this. Nothing lasts forever, but right now I'd say IA is the most likely repository to survive over the longest term, certainly in comparison to any for-profit company.
Ultimately you have to give a human direct responsibility for it; or in your case, a series of humans. I'd suggest you do buy a domain, but set up a legal/financial framework so that a long-standing law firm will keep up the payments for N decades (or for as long as the firm & its successors exist).
This is exactly the wrong advice, instead put your data on the blockchain, preferably Bitcoin, Bitcoin Cash or Ethereum. "Free" data storage for as long as the internet exists. Make the barcode to your transaction with the data, anyone with a brain and time can figure it out from there.
The big blockchains are robust, but I'm wondering if it's not impossible for them to not need the full blockchain at some point.
Posthaven is an option. https://posthaven.com/pledge
Ultimately you have to give a human direct responsibility for it; or in your case, a series of humans. I'd suggest you do buy a domain, but set up a legal/financial framework so that a long-standing law firm will keep up the payments for N decades (or for as long as the firm & its successors exist).
This is exactly the wrong advice, instead put your data on the blockchain, preferably Bitcoin, Bitcoin Cash or Ethereum. "Free" data storage for as long as the internet exists. Make the barcode to your transaction with the data, anyone with a brain and time can figure it out from there.
Ultimately you have to give a human direct responsibility for it; or in your case, a series of humans. I'd suggest you do buy a domain, but set up a legal/financial framework so that a long-standing law firm will keep up the payments for N decades (or for as long as the firm & its successors exist).
This is exactly the wrong advice, instead put your data on the blockchain, preferably Bitcoin, Bitcoin Cash or Ethereum. "Free" data storage for as long as the internet exists. Make the barcode to your transaction with the data, anyone with a brain and time can figure it out from there.
Oh ye of so much faith.
I'll offer a weird but (I hope) valid alternative to the other great suggestions here: print the code of the static webpage on a piece of paper. Even better, archival paper [0], so it will really last a long time. In the future, anyone would be able to point a... smartphone, or a camera, to the paper, and instantly retrieve the webpage. An AI will ask them if they want to render the page using one of these very, very…
> In the back of the book, I'd like to put a 2D barcode to send folks to a static webpage somewhere, maybe for further information, an update, text changes, etc.
How are you going to put the update/text change into the printed book? I think the point was tobe able to change the info when the books are already distributed.