Sorry, off-topic, but as a fan it really bugs me that graphic halfway down appears taken without attribution from Hyperbole and a Half. http://hyperboleandahalf.blogspot.com/
You know it's become a huge internet meme right? http://www.google.com.au/search?q=x+all+the+things&oq=x+... .
Should All Web Traffic Be Encrypted?
21–30 of 136 posts
Re: Should All Web Traffic Be Encrypted?
#22Earlier quoted context omitted.
> is definitely stored in plain text in the googlesphere have a source for that?
By definition, since Google can index email and mine it for keywords, they have access to the contents of it, which makes it isomorphic to plaintext.
Re: Should All Web Traffic Be Encrypted?
#23Re: Should All Web Traffic Be Encrypted?
#24Funny that https://stackoverflow.com/ certificate is not valid.
To be fair, Jeff Atwood recently left Stack Exchange (amicably, of course): http://www.codinghorror.com/blog/2012/02/farewell-stack-exch...
or... have i been working on this bug for way to long?
Re: Should All Web Traffic Be Encrypted?
#25I use the EFF's Firefox addon called "HTTPS Everywhere". It has a list of websites that have HTTPS enabled, and whenever your browser is directed to the plain-HTTP version, it will go to the HTTPS version instead. https://www.eff.org/https-everywhere A useful (but tbh kinda annoying) companion addon is the HTTPS Finder. It checks to see if the website you're currently browsing also has an HTTPS version, and will add…
Then you can go into Preferences > Advanced after some browsing, and you'll see a list of all the good sites found. You can create HTTPS Everywhere rules directly from there, without ever being annoyed during your normal browsing.
Re: Should All Web Traffic Be Encrypted?
#26Earlier quoted context omitted.
> is definitely stored in plain text in the googlesphere have a source for that?
By definition, since Google can index email and mine it for keywords, they have access to the contents of it, which makes it isomorphic to plaintext.
Re: Should All Web Traffic Be Encrypted?
#27Earlier quoted context omitted.
By definition, since Google can index email and mine it for keywords, they have access to the contents of it, which makes it isomorphic to plaintext.
That's not the same thing though. Plain text is a security risk because users tend to reuse passwords. If it's hashed then that wouldn't be the case, even if they can mine it or whatever.
Re: Should All Web Traffic Be Encrypted?
#28Earlier quoted context omitted.
By definition, since Google can index email and mine it for keywords, they have access to the contents of it, which makes it isomorphic to plaintext.
That could be done on the client side, reading the text on the page, like I assume they do for every other AdSense-enabled page.