Quote:
Originally Posted by xxxjay
I thought about this a lot and this is my conclusion. Google is a publicly held company. It is the officers fiduciary responsibility to make that company grow every year. What Google can be taking in on search is basically maxed out. They aren't going to sell X% more adwords to satisfy investors.
Google is now primarily in the INFORMATION BUSINESS...
https://cloud.google.com/bigquery/
The big reason they want to move to the https encryption is because they will among the few people with the keys.
 |
That's interesting only if it can take Google's own transactional data provided to you, (i.e.; the encrypted search strings with keywords from Google-Analytics , ) and then you could correlate the paths (transactional analysis) to your specific URI's.
Data Mining with nosql is old hat already AWS cloud has had this service for a few years now -- Google is just playing catch-up with some added value code availability.
https://cloud.google.com/datastore/
https://cloud.google.com/prediction/
https://cloud.google.com/s/results?q... ocs%2Fpython
In any event, this has nothing to do with the mantra for https.
- OAuth, SSO and other sign-ins should be in https
- ecommerce activities should be in https
- in https ONLY the path and parameters are encrypted -- server addresses are in plain text
https does prevent DNS *spoofing in most cases*
https://www.ssllabs.com/ssltest/
check your (or your bank's) https^