Does anybody know of a good article comparing dat, ipfs, and scuttlebutt? and optionally any other contenders? Including practical aspects, such as:
speed of the clients (e.g. copying same big file using each of those protocols),
disk storage overhead,
apps already built on them/supporting them (e.g. “dcp” seems to be a copy tool for dat, while scuttlebutt has some git sharing tool and a blogging app AFAIK, whereas ipfs has a public gateway IIUC).
I’m interested in reading more about it too. With ipfs you can trivially find out the IP address of the users that are seeding the content. There are ipfs cli commands to do it.
Dat, ipfs, scuttlebutt are all pull based. If I provide content on the network then I start off as the only seeder, then other users pull from me when they want the content. If I turn my device off before at least one other seeder has all the content then the content is unavailable until I turn it back on. How do you know when it’s safe to turn off the device? The general approach seems to be to set up a 24x7 server to seed the content or use a pinning service. Another issue with this, in my use of IPFS in the past, has been a thundering herd effect when initially announcing available data. If it’s popular anticipated content then a huge number of users will attempt to get the data initially but there’s only one provider and seeding drops to a crawl. Maybe this has been improved recently.
I like the Freenet approach where the data is pushed out into the network to multiple nodes. Once inserted the device can be turned off but the content remains out there. There’s a defined point where you know it’s safe to shut your node down, have nothing running anywhere, but users can still retrieve the content.
Does anybody know of a good article comparing dat, ipfs, and scuttlebutt? and optionally any other contenders? Including practical aspects, such as:
Here’s Dat vs. Scuttlebutt vs. ActivityPub: https://blog.datproject.org/2019/03/22/three-protocols-and-a-future-of-the-decentralized-internet/ — Not really benchmarks so much as different complementary roles they can play, potentially supporting one another.
Thanks! No ipfs unfortunately, but good read w.r.t. the others.
Here’s my term paper that I wrote about dat a couple years ago, if there’s interest: https://bernsteinbear.com/dat-paper/
lovely, thanks for sharing! looking forward to reading this
just read it, thanks for sharing! adding a link to this on the page
Cool! I’m glad you enjoyed.
This is interesting but has it has the same resilience and ip address security issues as ipfs and scuttlebutt.
Can you talk more about this?
I’m interested in reading more about it too. With ipfs you can trivially find out the IP address of the users that are seeding the content. There are ipfs cli commands to do it.
Dat, ipfs, scuttlebutt are all pull based. If I provide content on the network then I start off as the only seeder, then other users pull from me when they want the content. If I turn my device off before at least one other seeder has all the content then the content is unavailable until I turn it back on. How do you know when it’s safe to turn off the device? The general approach seems to be to set up a 24x7 server to seed the content or use a pinning service. Another issue with this, in my use of IPFS in the past, has been a thundering herd effect when initially announcing available data. If it’s popular anticipated content then a huge number of users will attempt to get the data initially but there’s only one provider and seeding drops to a crawl. Maybe this has been improved recently.
I like the Freenet approach where the data is pushed out into the network to multiple nodes. Once inserted the device can be turned off but the content remains out there. There’s a defined point where you know it’s safe to shut your node down, have nothing running anywhere, but users can still retrieve the content.
The article linked by @skyfaller seems to suggest that ssb does some kind of “[a]utomatic publication of content to your friends”?
I will be writing something up in a big blog post in a month or so but right now I can’t.