Google kicks itself out of its own cache when serving AMP pages Google’s come up with a way to kick itself out of URLs served to mobile devices from its cache, an effort that will mean pages from around the web no longer score an unwanted google.com address. URLs appear to come from Google thanks to the Accelerated Mobile Pages (AMP) project the company championed. Like so many Google …
On Android you can simply switch your search engine to encrypted.google.com (go to that site, search for something once, then go to chrome settings, set search engine, and pick encrypted.google from the list).
I'm not sure why that would need a separate app.
"Ubl wrote that Google hopes to implement its work in the second half of 2018, by adding some new bits to the WebKit browser engine and helpingforcing other browser-makers to adopt it"
TFTFY
Once again, Google leading the web down the proprietary, good-for-google path under the claim that it makes things "better for everyone".
As opposed to Apple's laughable attempts to get its notch accepted in CSS?
No. It's the exact opposite of that. That's trying to get something added to a standard, not 'adding it to the most common thing' and hoping inertia will drive it's adoption.
Think more MS in the 90s or Apple and their -webkit extensions in the 2000s.
No. It's the exact opposite of that.
Is it fuck: Apple has already made the changes to its own code and is now post facto trying to get them included in the standard. Apple only works on Webkit when it wants something new hence the lack of support for WebP or service workers and lots of other stuff. And then there's the ban on other rendering engines on IOS.
Google’s Tech Lead for the AMP Project, Malte Ubl, offered a third reason in a Tuesday post in which he wrote that current arrangements meant removing the Google.com URL would have let publishers know what readers were keen on before they visited sites, a privacy no-no.
El Reg probably needs to explain that URL you visit is also told about the URL you've just come from, hence the third reason quoted above. Effectively, the URL you visit from goggle can decode the google URL and decipher what you searched for hence the privacy issue. Removing the google amp prefix and making it seem like you visited the URL fresh enhances users privacy.
Google amp most likely increases page visits but like net neutrality is probably skewed in favour of the big outfits.
.. of course if webmasters actually bothered to code their own websites for the functionality they need rather than pulling in some huge library of code, that they only need a fraction of to do something that the end user probably doesn't want... then we wouldn't need AMP in the first place!
I guess other reasons are if you want a higher pagerank then you need AMP, if you want analytics on Google's AMP cache then you probably need Google Analytics, and if you want advertising on your AMP page then you probably need AdWords. I'm guessing at the last two, but if true it would answer my question above.
Lock-in fun for all the family.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
