content: Definitely the right direction, but if I was going to show off the abilities and power of distributed public web hosting I wouldn't show it from a traditionally hosted website using a Youtube video. His website should have been a link to a website using the technology he is showcasing and should have featured hundreds of links to people using the system. Otherwise, it's just a website showcasing a theoretical product that no one, including IPFS, seems to be actively using. The process of setting up the initial website for the 9-5 factory worker who just wants to bitch about the government is going to have to be multitudes easier to set up as well. Ideally, the best solution would be to make modificati  ffa  ons to the Tomato router firmware that allows it to become an optional web hosting device. Almost all modern routers already have web hosting built in, as that's the main way of accessing and controlling a router. So not a stretch by any means. There are also cheap and simple products out there designed to host websites from home, such as Synology. Something as simple as this, a person goes to a website and reads the instructions to update their firmware on their router to the Tomato product. Once updated, a person logs into their routers web server page and clicks on a link that says, "Create website". A few more options appear like "Blog", "News", or "Photo Gallery". They pick one and setup a simple web site and for extra storage plug in a USB flash drive into their router. Once the website is setup, a new link appears on the router's web page, "Publish Website". They click the link and the router scans for known online replication directories. The user then has the option to choose which directories they want to submit their website to and whether they want a one time sync, push sync (content changed), or live sync. They then wait for the people running those directories to review and either accept or deny their website. If they accept, the user will see which websites accepted to replicate their website and will be able to go and view the content themselves. The replication process could be kept simple as well. A person downloads a custom image with all the necessary replication software and installs it on a server. They setup and register their beacon with other directories and wait for requests to come in from people who want their content replicated.