Enabling the distributed web

Lots of folks have been echoing the idea that the way the Internet operates now, is a serious problem for the future of the web. Not least of all because, despite its decentralized and open roots (seriously, read that one), the Internet has become a place of centralized giants and information monopolies. But it’s not all bad news. First, the Internet does work pretty well, and second, we can make it better. And that’s exactly what the fine folks behind the Interplanetary File System (IPFS) aim to do. Their vision? A peer-to-peer hypermedia protocol to make the web faster, safer, and more open.But what exactly does this mean? At its core, IPFS is a versioned file system that manages objects and facilitates storing them, while also tracking versions over time. IPFS also accounts for how those files move across the network (via protocols), so it is also a distributed file system. A key piece of the distributed web puzzle, and the topic of today’s post, is content addressing. How you actually refer to files and objects within the system. But first, what’s wrong with the Internet?

This is a companion discussion topic for the original entry at https://blog.textile.io/enabling-the-distributed-web/