I’m following the development of the hyper-protocol [1] former: DAT-protocol for quite some time now.
I do like the characteristics of that system. It’s based on peer to peer distributed data stores.
So if I do like the content enough, I am able to “seed” [2] it. Which means I am providing infrastructure, for the content, that is valuable to me, so it can stay “alive”. Since I want to quote it, I do have an interest in the original contents availability.
With that type of system we can have both. The original author of the content gets better infrastructure redundancy and I can be assured, that my link stays valid. … at least as long as my content
So I have to find someone, who is also interested in my content. … May be the “internet archive”.
Yes, that’s how IPFS works too, and what #fission is built on.
However, you can’t use DNS based links in any of these systems, which was was your original worry.
You could use an ipfs:// protocol link as one example, which is the content address of the HTML file etc of the article being linked to.
I know of some systems that submit bookmarked links to the Internet archive, in order to have future redundancy, as a more Web2 / DNS based example.
And of course dedicated bookmarking tools like Pinboard which will archive articles for paid accounts.
For read only TiddlyWikis, experimenting with running IPFS on your own computer and serving it yourself is a great experiment to run. The IPFS desktop app makes this pretty simple.
Paul Frazee, the developer behind the DAT-based Beaker Browser is now working on Atek, a personal distributed cloud, with nodes designed to be hosted on a Raspberry Pi behind a home firewall. It can host Node.js apps, so looks straightforward to use for TiddlyWiki hosting:
