The idea here is to force infrastructure providers (hosts, especially) to provide customers with free certs, by default, so that *everything* is encrypted. The web should have been HTTPS-only from the start, we can see in hindsight.
-
-
Replying to @waldojaquith
We want to shut down MITM attacks (airlines and Comcast both do this routinely), stop making only super-secret things HTTPS (which reveals somebody to be doing something sneaky—that’s bad), and stop assuming that people do and don’t need to read confidentially.
2 replies 1 retweet 5 likes -
Replying to @waldojaquith
Has a ton of drawbacks in complexity and manageability.
1 reply 0 retweets 0 likes -
Replying to @clintsharp @waldojaquith
It’s really a shame that absolutely terrible practices like Comcast’s are driving us to encrypt inane traffic to avoid tampering. There is otherwise very little technical or business justification for needing to encrypt someone’s personal blog for example.
2 replies 0 retweets 0 likes
I really agree with @davewiner on this subject.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.