content: Your are correct, but let's say that this entire process is first only workable for static websites, it still allows us to create a free distribution network of thousands of static websites. The options for the static websites could range from one time sync, scheduled sync or real time push sync (meaning, it's re-syncs every time the content is updated). Even if such as system as I just referenced above was created and that system was able to be shared across replication servers, it could easily be used as a video, images, news and blog hosting. Instead of us linking to videos on Youtube that later get taken down, people upload these videos to these distributed networks. A parsing tool could be added to websites to link to content hosted on these distributed services. For example, let's say you want to link to a video on Jewtube, you submit a Jewtube url which references the video, such as, https://jewtube.com/video/10003. These new links could be setup by redistribution servers and would look like an assortment of IP addresses as so, 138.32.0.3.50.5.75.10.38.223.36.13.1.74.96.32.63.133.231.55.9.0.2.44... and so on. The parsing tool Voat would use would simply choose one of the IP's from the list at random and if one was unavailable, it would attempt to connect to another and another and so on. The only way to stop that link from working would be to take down every single distribution server. Even then, a distribution server could have a thousand replicators but the link might only include 50 of them. Every generated link would be a different assortment of 50 of the 4,000. It would take incredible effort of the DDOS'ers and Jews in government to take them all down simultaneously, specially if people started setting up distribution servers all over the world. With all that said, it still wouldn't be impossible to set a service like Voat in such a system, here's how, First, yes, it would take a single website/database host to be able to have near real time commenting. A person wanting to host a site like Voat would have to have the money, hardware resources and live in an area with high speed Internet that allows for website hosting. I would need let's say 6 servers. 2 servers would be used to distribute content, 2 servers would be used to receive content and 2 would be used to store the database. The reason for 2 each would be redundancy. Next I would purchase 4 gigabit fiber connections, one for each incoming and outgoing server. Again, for redundancy. The 2 outgoing servers would constantly deliver updated content to the redistribution servers. The 2 incoming servers would constantly receive data from all of the redistribution servers. The 2 database servers would be used to process and store all the data. The trick would be to make sure you split your IP's between distributors in order to hide your public IP addresses. Give one set of distributors one IP address and another set another. That way if a Jewish honeypot was setup to disclose the actual public IP for a DDOS attack, it would hopefully only get one of the IP's and not the second one. Also, the idea of distribution is that you don't distribute to every server personally, you distribute to a few, then those replicate to others and so on. It's a chain of servers passing information through and then just a handful of servers actually passing information to the 4 servers actually running Voat. In many ways it would still be susceptible to being shut down, but it would be much more difficult than by today's standards. Right now, anyone in the Jewish chain can shut down a website, the webhost, the domain registrar, Google (by delisting), SSL cert company, or even places that protect you from DDOS attacks, such as what happened to that guy who hosted that pro white website. I'm not saying it would be easy and trial and error wouldn't be required for long term use, because they would obviously attempt to overload the system by flooding it with messages, but anti-spam tools could be created, even distributed lists of blocked IP addresses that are used for spamming attacks. None of these problems are much different than the same problems we face today though and are more about getting better at detecting spam than building a free, distributed, uncensored world wide web.