HN user
Gasoline is 100 times more energy dense than a battery. The Tesla roadster adds 800 lbs to the lotus elise upon which it is built. Batteries have a long way to go.
Rural areas rely on dial up internet
community.letsencrypt.org
Is secured with Comodo.
Left to their own devices, people would never upgrade. This is a security risk for MS. (Win 8 support ends January 2018). Chrome was championed for auto updating, and now all browsers do the same. Web apps can auto update whenever they want. Mobile apps auto update. Why shouldn't operating systems?
In North Texas some (< 10%) of these large high school football stadiums generate positive revenue.
http://www.dallasnews.com/sports/high-schools/football-news/...
New keypairs would be generated on the client every time you join a chatroom. Another member of the chatroom sends you the shared_key encrypted by your public key. Server knows nothing, stores no keys. Keys exchanged between users.
Javascript crypto is still a problem though: http://matasano.com/articles/javascript-cryptography/
When you re-download the codebase on every use, there is no way to ensure integrity of the code. This is the reason cryptocat ships as a chrome extension, because it is downloaded once. Even with these issues, I'd take javascript crypto + open source over nothing (or just SSL).
I only feel safe using end-to-end encrypted chatrooms. Currently, niltalk can read every message. At the very least, AES encrypting messages by the chatroom's password will reduce reliance on SSL. But it really should use public key crypto for a key exchange between users. This is what's done by other disposable chatrooms:
https://ephemeral.pw/chat/ (Also written in Go)