Is it possible to set it as default on iOS/Android somehow? AMP really frustratingly breaks link sharing, and I'd like to totally avoid it.
Is it possible to set it as default on iOS/Android somehow? AMP really frustratingly breaks link sharing, and I'd like to totally avoid it.
!g search query
Leads to https://encrypted.google.com/search?hl=en&q=search%20queryOf course, this also works if you type this query in at duckduckgo.com
Edit to add: I guess it is a matter of time before amp pages also appear on the encrypted subdomain; another incentive to switch to DDG now.
Many years ago, Google Search existed only on http:// and schools used filters to block searches that they didn't like. Then Google shipped https:// for search on www.google.com, upset the schools because they could no longer block just some searches, then moved encrypted search to encrypted.google.com so that the entire domain could be blocked: https://cloud.googleblog.com/2010/06/an-update-on-encrypted-...
>1. Clicking on an ad:
> - https://google.com : Google will take you to an HTTP redirection page where they'd append your search query to the referrer information.
> - https://encrypted.google.com : If the advertiser uses HTTP, Google will not let the advertiser know about your query. If the advertiser uses HTTPS, they will receive the referrer information normally (including your search query).
>2. Clicking on a normal search result:
> - https://google.com : If the website uses HTTP, Google will take you to an HTTP redirection page and will not append your search query to the referrer information. They'll only tell the website that you're coming from Google. If it uses HTTPS, it will receive referrer information normally.
> - https://encrypted.google.com : If the website you click in the results uses HTTP, it will have no idea where you're coming from or what your search query is. If it uses HTTPS, it will receive referrer information normally.
[0] http://security.stackexchange.com/questions/32367/what-is-th...
You used to have to use that domain to run searches over HTTPS. Google's enabled that for all users now, so it's kind of obsolete -- but apparently it still behaves a little bit differently?