Multiwriter Dat could power the next Web (Video + blog post)
@bob @aral the video demonstration at the site fails to show the power of the underlying distributed filesystem? - where and who gets to set the servers that carry the data? or everynode carries all data like the blokchain?
or for private use/at home/work in a multiserver setup, what is the main advantage? does it imply efficient copies, ie if one of the nodes are taken down? if there is a better intro URL to these concepts or if you have answer pls let know.
@0x3F @alanz @aral Thanks to GSConnect by Andy Holmes and the KDE Connect team :) https://ar.al/2018/08/02/crafting-a-continuous-client-desktop-mobile-experience-on-linux-with-gsconnect/
@fabricedesre @aral There is none in the protocol per se as far as I know. Jim's example uses Automerge if I remember correctly (https://github.com/automerge/automerge). As does Peter van Hardenberg's PixelPusher (https://medium.com/@pvh/pixelpusher-real-time-peer-to-peer-collaboration-with-react-7c7bc8ecbf74)
I love multi writer DAT, it's truly amazing technology.
I currently use it with TiddlyWiki. Share the link with my devices and some friends and we have a shared notebook/wiki for the courses we share.
unfortunately though, i still go through an https gateway:
id love to learn how to turn something like this into a "pure" DAT app.
@anish Yeah and I don't see that changing soon, sadly. Mostly because the major browser makers – Google and Google-funded Mozilla – are surveillance capitalists. They could add native Dat support tomorrow but instead Mozilla will placate the community by allowing extensions that three developers install. Apple could do this with Safari but I wouldn't hold me breath. Best chance is other FOSS browsers but then you get into the issue with penetration numbers again…
And yet, so much potential :)
@aral I really like the idea of DAT, and a lot of the tech, but my first experience with it involved a significant amount of time fiddling with firewall settings on a Windows machine. I never did get it to work (save for turning the firewall off) so that was the end of my DAT experience.
I hope they can sort this out because it's going to be hard to hit mainstream adoption otherwise.