The article assumes that this SSL-on-by-default change is for the only 1 reason: To prevent sites from knowing what you searched for to find them.
On the other hand, I assumed it was all the privacy and security vulnerabilities that go along with not using SSL, and they were doing it to protect the consumer. It's already been an option for a while, allowing those who truly care to test it out. This just changes it to be the default.
I don't think the author is right about Google's reasons, and I don't think it's a particularly logical leap, either.
Comments
The article assumes that this SSL-on-by-default change is for the only 1 reason: To prevent sites from knowing what you searched for to find them.
On the other hand, I assumed it was all the privacy and security vulnerabilities that go along with not using SSL, and they were doing it to protect the consumer. It's already been an option for a while, allowing those who truly care to test it out. This just changes it to be the default.
I don't think the author is right about Google's reasons, and I don't think it's a particularly logical leap, either.