https://ipfs.io/blog/24-uncensorable-wikipedia/
I think the biggest thing they're going to struggle with for adoption is their addressing system, which is brilliant from a technology point of view, but impossible to memorize for regular humans. Some sort of naming system (or, ideally, several such systems) needs to emerge I think, before the network will be properly usable by casual folks.
Here is an IPFS path to my blog: /ipns/jes.xxx/
No longer than the corresponding HTTP version: http://jes.xxx/
Of course, DNS isn't distributed or trustless, but if it can work with DNS it can work with the likes of Namecoin or ENS (https://ens.domains/).
Currently you need to prepend an IPFS gateway URL to the IPFS path in order for it to be backwards-comaptible with existing browsers (e.g. https://ipfs.io/ipns/jes.xxx/), but I don't think it will take too many years to get native IPFS support in browsers.
I'm really really excited by what's going possible already, and what's going to become possible soon, with IPFS.
> The tension/problem as I see it is this: we need distributed networks, where people run their own services, and are servers as well as clients, but at the same time a large proportion of people do not or cannot run their own services. Solving that problem seems key to me--have people act as servers without realizing it (maybe something like with torrents).
I think this is spot on. In case you haven't come across it already, IPFS is trying to do this, and already works today for many applications.
https://ipfs.io/
This talk is quite good if you have an hour to spare: https://www.youtube.com/watch?v=jONZtXMu03w