content: How to build a new, free, uncensored World Wide Web before 2019. No corporate advertising. No Jew CEO's regulating speech. No hosting fees. No domain names. No SSL's. Running a website is expensive and problematic. Under the Jew controlled Internet you have to purchase a domain name, purchase a SSL cert, pay for a web host, and pay to protect your website from funded DDOS attacks designed to eliminate free speech. At any time, your domain registrar, the company that provides your SSL cert, your web host and even your bank can decide to stop providing you services. Worse than that, search engines like Google can simply remove you from their search results like they did with 8ch.net. Something has been slowly changing behind the scenes that may now allow us to bypass all this Jewery and finally create an open and free World Wide Web of our own, Community Broadband. Publicly owned high speed fiber Internet access with a static IP is now available in my area with the option of 1000/1000Mbps Internet access (without any restrictions or caps) for $100/month. I don't know how wide spread this is, but I know it's spreading all over my state. Setting up a home web server for even a non-techie is pretty simple with a few guides. Then you create a guide for setting port isolation and forwarding using standardized open source router software like Tomato. The problem with the above setup is that most home users are stuck with much slower home Internet with terrible upload speeds (the very thing needed for web hosting), restrictions from their ISP saying they can't host a website, and dynamic (randomly changing) IP addresses. All websites are accessed by IP address, domain names are just pointers to IP addresses and not necessary for hosting websites. Step 1 - Home Web Servers: We create a custom stack using open source software like LAMP that will have both a beacon service and public key encryption. The beacon service will broadcast to trusted static IP's it's current dynamic public IP address, similar to how Dynamic DNS works. What this will allow for is anyone with a shitty dynamic IP Internet connection, a cheap router, something as basic/cheap as a Raspberry PI, a few command lines to install the software, and enough time to put together something as simple as a basic open source blog to host a website without restrictions for free. Step 2 - Online Directories: Anyone can use their home server to create an online directory website that will allow other home users to submit their site and content for review. If the person running the online directory likes their content, they accept their listing and it's published in their directory. Directory creators could even build their own search engines. To avoid the pitfalls of dynamic IP's, online directories would use an encrypted beacon service that would allow for updating dynamic IP addresses when necessary. Step 3 - Site replication: People like myself, who have access to cheap high speed Internet with static IP's and no restrictions on web hosting create replication services. A person with terrible Internet service who can't reliably host their own website, would submit their website to a site replicator who, after reviewing the content, would then replicate the website onto their own web server. Website replication could be set to sync on review or live sync, depending on how much you trust the person hosting the website. These kind of controls would be necessary to stop the Jewery of someone creating a regular website and then swapping out all the content for cheese pizza. A person could even replicate a site of replicates if the host allows it. For example, Joe works hard on keeping a replication site clean and functional with no dead links, but Joe's Internet service is limited. I trust Joe, so I setup a sync site that replicates all of Joes replications. The online directory beacons coming from websites would also include all the places that website is replicated and available. A website might be available from 4,000 different IP addresses, making things like DDOS attacks incredibly difficult since the original content creator has the ability to only share their IP address to the replicators. Step 4 - Distribution: Initially it would take some time to start building these directories and we would have to use the old web to get the process off the ground, but eventually we'll have directories of directories and we might even be able to come up with our own domain name services. This isn't about privacy or hiding people's identities. I'm not interesting in creating a new TOR or ".onion" type system. That system already exists. This is more about speech not being restricted and controlled by Jewish corporations. Anyone who hosts a website using their home IP address would be someone the police could locate if necessary, but it doesn't mean we couldn't bake in some level of anonymity for those who want to create content anonymously. A person could upload their website content through a private VPN to a host and then that host could choose to host the content or not. It would then be the responsibility of that host to make sure the content is legal and allow the content creator to remain anonymous. Nothing really different than our current system in those regards. Regarding software, I'm making possible suggestions when referring to things like Tomato, LAMP and Rasberry Pi's. I don't want this to turn into an argument for or against PHP or Apache, multiple types of software/hardware could be used, the only thing that must be agreed upon is a few standards that will allow this process to work. A process that would continually change just like any other technology. A final note, my ISP allows me to have up to eight 1000/1000Mbps connections at my house. Myself and many others in our situation could easily accept Bitcoin donations and host stacks of actual web servers for replication purposes. I could even see new businesses started where small residential offices are rented out, in these cheap high speed ISP areas, to do nothing more than replicate and host websites on this new open platform. For example, I could rent out some cheap offices downtown and have each office wired up with 8Gb's synchronous Internet connections that connect to stacks of replication servers. A few hundred people across the United States set these up and we'll be able to compete one on one with the big corporate sites. This distributed IP model would also make it extremely difficult, unlike now, to DDOS individual websites as they would have to DDOS thousands of replication servers simultaneously. Thoughts?