4 ms·
Yeah, related! I haven't looked extensively into NDN, still need to sink into it, but good thing Van Jacobson's doing it! :) Contrast points: IPFS is an implem
by _prometheus 12y ago
Yeah, related! I haven't looked extensively into NDN, still need to sink into it, but good thing Van Jacobson's doing it! :)
Contrast points: IPFS is an implementation at the leaves of the network (rather than calling for routers to change initially), can be mounted as a filesystem, maps to the web (string paths as URLs), and provides a Merkle DAG data model.
- ilaksh 12y agoI don't see how its fundamentally a different concept. Named-data networking is a loose category of proposals, doesn't necessarily need routers to change. Obviously you can't tell that other guy what to do but if IPFS doesn't inform that other effort then I think they are going to be wasting time. Anyway I hope you will very seriously look at the various different approaches to NDN (with several different names) as a loose category and consider attempting to recruit from or merge with or interface with other efforts (there are many similar systems) and possibly expanding the scope a little if necessary. We really do need a new internet. Also what do you think of operational transformations, do they relate in any way to IPFS or future IPFS capabilities?
- _prometheus 12y agoYeah, I'm all for consolidating efforts. I'll be looking into NDN more. Though there's only so many minutes in a day-- if you can help me figure out who's great there to talk to, drop me a line juan@ipfs.io (other than Van Jacobson, ofc. will go talk to him at some point.) On OTs: yep! you can implement OTs on a merkle dag trivially, so you can build files from OTs. So! apps can use OTs as first class data structures and store directly onto IPFS.