If You Can Decentralize the Internet, Mozilla Has $2 Million For You (cnet.com)
Mozilla and the National Science Foundation want a new internet. And they want it to be free and accessible for everybody. From a report: They'll pay $2 million for it. On Wednesday, the two organizations issued a call to action for "big ideas that decentralize the web" as part of the "Wireless Innovation for a Networked Society" challenges. The challenges include getting the internet to communities off the grid, with proposals like a backpack with a computer and Wi-Fi router inside.
https://freenetproject.org/ Those guys are already trying to do it. It is fully decentralized and private. It is very slow, and consumes huge bandwidth, but it works. The real concern here is the lack of choice when it comes to ISPs. They control the last mile, which almost everyone MUST lean on if they want to be on the internet. Break up the monopolies/duopolies and most the problems Mozilla wants to solve evaporates.
Mozilla isn't trying to decentralize the internet. The challenge with the money involved is either to deploy access to places that have none OR deploy BETTER access to places that have lousy access.
NEITHER OF THOSE IS "DECENTRALIZATION."
SSL is now completely free via let's encrypt.
Let's Encrypt requires a fully qualified domain name (FQDN) under a well-known top-level domain (TLD), not an IP address in RFC 1918 space or a name under a made-up TLD such as .local or .internal. So do all other CAs whose root certificates are included in Mozilla NSS, as a FQDN is one of the Baseline Requirements adopted by the CA/Browser Forum.
Domains are cheap.
Cheap enough for every head of household to buy and to continue to renew in perpetuity? Because buying a domain is the only way to get a certificate for hosts on your LAN that visitors' devices will trust, and a certificate is the only way you're going to satisfy the "Secure Contexts" requirement for recently introduced JavaScript APIs.
Free ones are available.
Namely?
If you're referring to subdomains offered by dynamic DNS providers, these providers have to be on Mozilla's Public Suffix List (PSL). If a domain isn't already on the PSL, and 20 other users of subdomains under the same domain have obtained certificates in the past week, Let's Encrypt will deny you a certificate, citing its rate limit policy. If a domain is on the PSL, each subdomain gets its own separate rate limiting bucket of 20 certificates per subdomain per week. In addition, submissions to the PSL must be made by the dynamic DNS provider as a pull request through GitHub.com, and use of GitHub.com requires running proprietary software written in JavaScript on your computer.