Live data from Hacker News

Did iOS 15 kill Google AMP

lapcatsoftware.com

61–70 of 85 posts

Re: Did iOS 15 kill Google AMP

#61
post #55

I'm an AMP noob but why would someone block AMP pages?

My experience on iOS: scrolling feels wrong because it is non-native (different inertia and velocity), reader mode stops working, and if for whatever reason I want to share original link that won't be easy.

Re: Did iOS 15 kill Google AMP

#62
post #45
post #41

Earlier quoted context omitted.

Why is this a regression in iOS? Changing the user-agent string is not a regression.

As in, a change/feature added to the rendering/javascript engine caused an regression.

Except AMP still loads in Safari 15 if you spoof the User Agent, per TFA.

Re: Did iOS 15 kill Google AMP

#63
post #49
post #12

Earlier quoted context omitted.

How does apple relay affect AMP?

Apple uses their own IP address when accessing sites to protect privacy: https://support.apple.com/en-us/HT212614 Maybe the majority of iOS 15 traffic coming from Apple servers instead of individuals is causing trouble with Google's current AMP implementation somehow, so they check the iOS 15 user agent and disable it? IMO more likely Google just has a user agent whitelist or regex that misses iOS 15 and AMP was just…

Majority of Private Relay traffic comes from Cloudflare and Fastly. That's one of the relay's privacy features: the server don't know where the client comes from.

Re: Did iOS 15 kill Google AMP

#64
post #27

Earlier quoted context omitted.

> Apollo is not the defacto reddit client. Reddit's own app is. Reddit's is the official client. > Defacto: in fact, or in effect, whether by right or not I think in this case the validity of the word "defacto" depends on your sample population. Apollo is very popular (and a fantastic reddit client, I wish there was an equivalent for HN) but I can't imagine it's marketshare is anywhere close to even 50%. Among tech e…

Reddit pushes the official client hard from the mobile website. I'm sure its marketshare is huge.

I hope the marketshare of the official client is at the very least high enough to prevent them from crippling APIs so third-party clients are gimped, like Twitter has done.

God forbid they add a token limit

Re: Did iOS 15 kill Google AMP

#66
post #62
post #45

Earlier quoted context omitted.

As in, a change/feature added to the rendering/javascript engine caused an regression.

Except AMP still loads in Safari 15 if you spoof the User Agent, per TFA.

"regression" doesn't have to mean "totally broken". maybe it's a little laggy. Maybe it breaks in certain edge cases.

Re: Did iOS 15 kill Google AMP

#67
post #60

My suspicion, having worked at google for a while, is that this is a parser / version eligibility bug. Someone probably put the list of major versions where this is supported, and 15 was not there :) Things like this happened every new ios release. Going from 9->10 was a problem for example because regex used was limiting major version to single digit etc.

Also AMP it's disabled for Firefox on Mobile (Android)

Re: Did iOS 15 kill Google AMP

#68
Side note:

Does anyone have a decent link that explains exactly what AMP is to someone non technical? (Bonus if it explains why its bad, but I think I was able to at least get that part across)

I have been trying to explain multiple times but I am continuing to realize that there is certain terms that I just "know" and don't really know how to translate.

Re: Did iOS 15 kill Google AMP

#69
post #68

Side note: Does anyone have a decent link that explains exactly what AMP is to someone non technical? (Bonus if it explains why its bad, but I think I was able to at least get that part across) I have been trying to explain multiple times but I am continuing to realize that there is certain terms that I just "know" and don't really know how to translate.

Techcrunch usually has this type of articles: https://techcrunch.com/2018/02/13/amp-for-email-is-a-terribl...

Since this is site is usually read by C-levels and some VC's, the language is less technical but somewhat editorialized.

Anyway AMP is bad because it proposes an Internet without the freedom to push dynamic content (JavaScript, webassembly, etc...), cached at "google servers" for fast delivery but with features specifically built so Google Analytics and others can keep working, it doesn't solve anything that a good css style wouldn't solve plus content creators lose control of their data.

Post reply on HN