My perception is very much along the lines of what @anjacks0n responded: dat has a focus on end user apps, IPFS on storage. But, it’s kind of hard to be sure when not being directly involved.
-
-
There was a discussion at some point about why Dat couldn’t easily use IPFS as the storage layer… Ah I was thinking of this https://github.com/ipfs/faq/issues/119 … and the referenced https://github.com/datproject/docs/blob/master/docs/faq.md#how-is-dat-different-than-ipfs …
1 reply 0 retweets 1 like -
Different layers on "the stack" maybe? Would be nice to have a table to compare. That link seems to be Dat-promotional.
@juanbenet gave another (now 2+ y/o) perspective (https://github.com/ipfs/faq/issues/119 …) that anticipated some intersection via IPLD. Any updates on Dat vs. IPFS,@IPFSbot?1 reply 0 retweets 2 likes -
Replying to @machawk1 @anjacks0n and
Here's
@jimpick comparing Dat and IPFS: https://youtu.be/EwZ-CcxaG6s?t=1168 … At 24 mins Jim talks about how IPLD could be used to model Dat.2 replies 0 retweets 3 likes -
One thing that I like in Dat is the notion of a repository as a unit of sharing. I believe people who say it (dat) could be built on top of IPFS, but I feel like that kind of misses the point a bit.
1 reply 0 retweets 1 like -
Replying to @ibnesayeed @edsu and
#Dat is also good in tracking version history & has optimizations in place for that. In the#DWebSummit I had a chance to talk to some people behind Dat about its potential use in#IPWB as a backend, but what I learned from them made me realize it's not suitable for that purpose.1 reply 1 retweet 1 like -
Replying to @ibnesayeed @edsilv and
Hmm, there's not much preventing you from sharing WARCs (and CDX files) with Dat is there?
2 replies 0 retweets 1 like -
Replying to @edsu @ibnesayeed and
No, and I think
@IlyaKreymer was thinking along similar lines, using a standard sub-folder layout. Might struggle with a domain crawl?2 replies 0 retweets 1 like -
Replying to @anjacks0n @edsu and
Yep, that's the idea. With Dat, the entire directory structure need not be synced at once (or at all!), only relevant portions (eg. index), and not all web archiving use cases are about globally deduplicating 'content-addressable chunks of bytes' ;)
1 reply 0 retweets 5 likes
I think certainly both Dat and IPFS can have different benefits for web archiving. Important to keep in mind that modern web pages often have a different content hash on each reload, eg. 'curl https://www.nytimes.com/ | md5sum' a couple of times (and that's even before cookies)
-
-
Replying to @IlyaKreymer @anjacks0n and
That was the crux of
@phonedude_mln's presentation at#cni18f last week re:calculating fixity of web archives, "You cannot replay twice the same archived page"https://www.slideshare.net/phonedude/blockchain-can-not-be-used-to-verify-replayed-archived-web-pages-125618706?qid=46f9851d-f947-4c8a-b010-0363f28e8875 …0 replies 6 retweets 7 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @IlyaKreymer @anjacks0n and
Maybe related? I’ve got a little mad science experiment where I’m implementing hypercore storage on IPFS... so the choice between the two projects might not be black and white... :-)
0 replies 1 retweet 4 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.