@kas@enotty.dk, @freemor@freemor.homelinux.net (re: finger) That’s another neat thing about twtxt, it totally independent of any transport layer. ipfs, zeronet, finger, as long as the protocol has an url we could follow the ressource.

There are so many alternatives like ipfs or scuttlebutt, but i fear that we loose the simplicity of the old protocols. That in my mind is the main attraction of twtxt.

So, last #txtnish update for today: It supports subscribing to ipns:// and can publish your twtfile to ipfs. puh

looked over IPFS - looks interesting - will give it a try to see how many other people are already using it.

http://ipfs.io/ I want to learn more - bookmark

But publishing takes a long time, maybe I fork a detached subprocess to handle that. Mhh. You’ve been warned. #ipfs

Next task: Fetching twtxt files from ipfs without using the public gateway. And pinning subscribed files would be great #ipfs

Publishing to #ipfs now works reliable in #txtnix. You can find me at /ipns/QmZxsWLdxMcpb34qXtDyFAVtUDDm9Fp2G24NSjS8fGWBWY/twtxt.txt

But boy, ipfs name publish really takes its time to find other nodes #ipfs

#txtnix now has minimal support to add and publish files with IPFS. Subscriptions shouldn’t be too hard either.

Testing the ipfs backend … nothing to see!