I'm pretty sure 8.8.8.8 is Google's DNS service. You can set it manually, if you really want to, and have them be the ones to translate the web addresses you type in (like www.google.com) and connect you with the server via IP on the backend. You can also use 1.1.1.1 for CloudFlare's DNS service. Could be whatever datacenter they're using routes through Google, or uses Google fiber as their backbone.
How do you avoid it? A handful of companies own everything, and they're all evil. What's he going to do, build his own worldwide network? You could do something with TOR and the deep web but that has it's own problems.
I'm pretty sure 8.8.8.8 is Google's DNS service. You can set it manually, if you really want to, and have them be the ones to translate the web addresses you type in (like www.google.com) and connect you with the server via IP on the backend. You can also use 1.1.1.1 for CloudFlare's DNS service. Could be whatever datacenter they're using routes through Google, or uses Google fiber as their backbone.
What I don't understand is why he didn't post the files encrypted and checksummed long before now, so only the key needed to be released.
This is why I think this is a big larp.
The odds that however many TB of data could be successfully released in this way after the DMS triggered are pretty much 0.
The Blockchain idea is cool but seems like too much data to store on a Blockchain. The whole Ethereum Blockchain is only 500GB
Oh well...
How do you avoid it? A handful of companies own everything, and they're all evil. What's he going to do, build his own worldwide network? You could do something with TOR and the deep web but that has it's own problems.
then they wd track down the physical location of your little indie server and blow up the building