7 ms·
It's really unfortunate to see awful claims like "we are here to help build a better Internet and improving AMP is a huge step in that direction" that are blata
by ocdtrekkie 8y ago
It's really unfortunate to see awful claims like "we are here to help build a better Internet and improving AMP is a huge step in that direction" that are blatantly dishonest and harmful to the Internet being promoted by Cloudflare in this blog post. AMP is a horrible cancer the Internet is plagued with, and we keep being told it's great even though literally nobody wants it.
Claims like "Many of the sites we have spoken to get as much as 50% of their web traffic through AMP" ignore the fact that this is only true because it's been forced down our throats without our consent.
Anyone implementing an AMP-based technology which doesn't come with a way for users to decline to participate is actively harming the open web. I like Cloudflare and a lot of what it does, but I'm really disappointed in them today.
- snek 8y agoI can definitely agree here, It's really disheartening to see this. When I saw this headline I first thought it was Cloudflare using some sort of cool trick to redirect users back to the proper non-amp page, but was just met with disappointment.
- SquareWheel 8y agoCloudflare hosts their own AMP Cache. It seems reasonable they'd adopt this as well.
- AlexCoventry 8y agoIf you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? If AMP is federated, that's a lot less disturbing to me than my first impression.
- SquareWheel 8y agoI don't know the answer to those questions, but I'd be curious to know as well. Bing also hosts an AMP Cache if that's of interest to you.
- ocdtrekkie 8y agoGoogle can only serve data from Google's AMP cache. Bing can only serve data from Bing's AMP cache. So you can't, say, pick an AMP provider, your website gets hoovered up by each individual AMP cache and served to users coming from their respective networks. In short, only being in Google's AMP cache gets you good rankings on Google Search.
- lern_too_spel 8y ago> If AMP is federated, that's a lot less disturbing to me than my first impression. AMP is federated. Anybody who wants instant loading of AMP pages linked from their own pages can run their own AMP cache, as Bing and Baidu (among others) do. > If you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? Bing and Baidu running their own AMP caches doesn't affect their Google ranking. Why would it?
- gregable 8y agoLet me see if I can explain this a little better. Anyone can cache a signed exchange from anyone else. So, for example if you went and fetched a signed exchange from https://amppackageexample.com/ https://amppackageexample.com/ (or any other site that supports one, this is just an example), you could then serve that from your own server, more or less just like any other file (the less is that you need to set the right Content-Type header, but it otherwise works just like serving an image or a zip file). Then, if a user visited the URL on your site https://yoursite.com/cached-copy-of-amppackageexample.com/ https://yoursite.com/cached-copy-of-amppackageexample.com/ then the browser would display https://amppackageexample.com/ https://amppackageexample.com/ in the URL bar, as though that URL had 301 redirected, but without the extra network fetch. Google search does exactly this, just loading a cached copy of the Signed Exchange, and any other cache (or even any website) can do the same. So, if you publish a signed exchange, you are allowing all caches to do this, not just a selected cache. However, since the document is signed, absolutely no caches can modify the document or the browser will reject it and error handle (typically just making an actual redirect to your domain). I hope that helps to understand.
- AlexCoventry 8y agoYes, thanks for clarifying.
- SquareWheel 8y agoThanks for the explanation!
- panarky 8y ago> literally nobody wants it > as 50% of their web traffic through AMP > forced down our throats without our consent Who, precisely, is forcing publishers to use AMP?
- ocdtrekkie 8y agoGoogle is, by giving AMP-enabled pages preferential placement in Google Search results. If your business lives and dies by web traffic, it's not optional. Bear in mind, publishers hate AMP as much as everyone else: It forbids them to do what they want with their website. AMP is the technology nobody wanted and nobody asked for, users and publishers alike.
- panarky 8y ago> Google is, by giving AMP-enabled pages preferential placement in Google Search results That claim is gonna need evidence, and I've seen no evidence so far. Please provide it if you've got it. Google does prefer sites that are fast to sites that are slow, ceteris paribus. So if AMP sites are faster, maybe they get upranked due to performance, but not just because they're AMP. So if a publisher doesn't like AMP they don't have to use it, they just need to make their sites faster on mobile.
- tomp 8y agoI think you're conflating 2 things. User do want AMP-like technologies. I want the browser to restrict the publishers as much as possible (while keeping their sites "useful" for some definition of the word - static markup such as text, images and some background/styling is definitely useful) - I actively do that by preventing them from auto-playing videos, using adblocking, etc. However, Google-controlled AMP is a travesty. I don't want to view websites on Google. I want the original URLs, I want to be able to bookmark it and share it, I want to be able to go to the non-mobile website etc. Keep AMP, banish Google.
- altmind 8y agoUsers want fast loading speed, not specifically AMP. And quite often fast loading speed can be achieved by merely removing the bloat from your pages.
- zackbloom 8y ago[I work at Cloudflare] It's hard to build a great website, particularly one which works well on mobile. AMP as a web framework makes it easier. There's nothing about that value it which is intrinsically linked to any particular way of rendering AMP, a good chunk of the web would be better off building on AMP independent of Google. That doesn't mean every site should, there are developers and teams who are capable and willing to build great sites and we support their right to not have to use AMP. The need to use AMP-the-framework to get instant loading is hopefully a temporary one partially fixed by signed exchanges. The AMP cache is also made much less concerning and painful for users through the use of signed exchanges. By ensuring the content is what was provided by the origin we believe the Internet is becoming a more trustworthy place, opening the door to sites being able to be served from wherever they will be most performant.
- cphoover 8y agoI dunno all the amp sites I have visited have had terrible user experience IMO... Also for the longest time AMP had absolutely broken in-page search on mobile safari. If you believe in a web technology go through the process and champion a draft standard. It can start out as an experimental flag enabled feature or vendor prefixed feature before it is adopted as a web standard. But don't ram this shit down our throats... Also let's talk about the obvious business incentives for data collection both Google and cloudflare have for serving up AMP pages.
- ocdtrekkie 8y ago[I know, but thanks for disclosing. :)] The problem is, there really isn't an "AMP independent of Google", as Google's implementation is the only thing that matters, due to Search and Chrome. Supporting Google's proprietary fork of HTML is more or less supporting that entire structure, and it is inherently harmful. Whilst they have some notion of "governance" for the project, the plurality of participants are Google and they've confirmed that Google isn't really beholden to follow the project's governance with the implementations they put into their own products anyways. For the most part, AMP is a subset of HTML with proprietary tags, but could be easily implemented in normal HTML. The only reason to implement AMP is to format your website to be compatible with Google's demands for special treatment in Search. (A benefit that, while publishers may aspire for today, becomes increasingly useless as the entire Internet is forced over to the same proprietary format.) Various blogs have covered samples of how loading AMP is actually worse than loading their own websites in a lot of cases, but they're forced to implement it anyways because of that Google Search incentive. Surely the correct solution for mobile developers is to teach people to use restraint in piling on extra crud, not bootstrap some extra crud that prevents them from using any other crud. And essentially, from the responses here and in almost every previous discussion about AMP, and literally Twitter feeds made just to retweet examples of AMP hatred: Nobody wants this. Everyone who wants it is using it because they have no choice. It's forced on publishers to maintain competitiveness in search, and it's forced on users who have no way to decline. Probably what ground my gears the most about your blog, to be honest, is the cheerful, supportive tone for what is inherently a harmful technology that was implemented in a closed fashion. Compare to how FastMail acknowledged that they may have to support AMP for Email, whom I'm not upset with: https://fastmail.blog/2018/02/14/email-is-your-electronic-memory/ https://fastmail.blog/2018/02/14/email-is-your-electronic-me... If you have to do this for business reasons, tell us that, don't try and tell us AMP is good for the world, when we know it isn't.
- Kiro 8y ago> literally nobody wants it I can guarantee you that the majority of internet users like AMP. It's only developers and hardcore techies that don't.
- ocdtrekkie 8y agoHow can you "guarantee" this? First and foremost, the majority of Internet users don't like AMP, they just don't know what AMP is. Websites may behave strangely to them, and they just don't understand what's causing it. We, developers and hardcore techies, have the same problem, but we happen to know that the cause is AMP.
- Kiro 8y agoI presume you live somewhere with good internet connection. AMP is a life saver here and people first and foremost care about being able to load the page at all. So yes, they like AMP even if they don't know what's causing a page to load fast.
- dao- 8y agoSo if this is Google's motivation, they should just promote results that can load fast regardless of whether they use AMP. They have the means to do that but they don't want to, presumably because their motivation isn't quite aligned with users.
- JohnFen 8y agoMaybe, maybe not. But why doesn't Google do the one thing that would render this entire argument moot? Provide a mechanism that allows users to opt-out of getting AMP pages entirely.