>server-side rendering
Oh, that's shiny new technology. Call me when we have 3d buttons back.
A new AMP update shows how it can infiltrate every corner of the internet
71–80 of 93 posts
Re: A new AMP update shows how it can infiltrate every corner of the internet
#72Earlier quoted context omitted.
But AMP sites pretty much require you to get out of the AMP site to work properly. Closing a pop up is no harder than that.
I'm all for bashing AMP but I can't remember a single time I've had to get out of AMP to get it working. Do you have any examples?
Try reading a thread on an AMP search result from reddit. Most of the comments will be missing.
Re: A new AMP update shows how it can infiltrate every corner of the internet
#73Earlier quoted context omitted.
I think the parent's point is that desktop sites are often good enough even on mobile. Mobile sites, on the other hand, seem to often lack in functionality.
But most purely desktop sites, are in fact, not anywhere close to good on mobile. A good test is: do you need to zoom in and then pan horizontally to be able to read the content?
Reddit is the main site I use on my phone and I certainly use it in desktop mode all the time. I even use Google in desktop mode very often, because desktop mode lets me select arbitrary dates in results, whereas the mobile page gives me a limited selection.
Re: A new AMP update shows how it can infiltrate every corner of the internet
#74Earlier quoted context omitted.
Website authors opting in to letting another server serve content "as" their own domain isn't anything new: it's what CDNs do. The Signed Exchanges standard is actually a huge step up because the website authors get to cryptographically sign their content. With normal CDNs, if the CDN is malicious or gets hacked, the CDN is free to serve modified content on the original domain.
> Signed Exchanges standard is actually a huge step up Signed exchanges is considered harmful by Mozilla.[1] * * * [1] https://mozilla.github.io/standards-positions/
"Harmful" is a rather poor summary of [their actual position][1], which is closer to "this is a big change and we don't know what kind of effect this will have, so we're going to wait and see":
> There is a lot to consider with web packaging. Many of the technical concerns are relatively minor. There are security problems, but most are well managed. There are operational concerns, but those can be overcome. It’s a complex addition to the platform, but we can justify complication in exchange for significant benefits.
> [...]
> Big changes need strong justification and support. This particular change is bigger than most and presents a number of challenges. The increased exposure to security problems and the unknown effects of this on power dynamics is significant enough that we have to regard this as harmful until more information is available.
I think that's a reasonable position. I certainly wouldn't summarize it the way they did though.
[1]: https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5s...
Re: A new AMP update shows how it can infiltrate every corner of the internet
#75Earlier quoted context omitted.
for example the mobile version of facebook, doesn't let you see messages. The desktop one does and works fine.
I've been able to see/send messages from the mobile site recently actually. I might finally be able to remove the Messenger app from my phone as well.
Me too. I think I was using fb with the mbasic.facebook.com URL.
Re: A new AMP update shows how it can infiltrate every corner of the internet
#76I'm confused. The title of this article isn't at all supported by its content. The entire thing can be summarized as:
> Google rolled out a new feature that allows AMP to use server-side rendering (SSR), boosting performance for sites that adopt the technology across their entire domain.
Followed by a dozen paragraphs arguing why AMP is bad, with no further mention of server side rendering or why it "shows how [AMP] can infiltrate every corner of the internet". Is there anything new here, or is this just another rehash of the same arguments we've been having about AMP since the day it was released?
Re: A new AMP update shows how it can infiltrate every corner of the internet
#77Re: A new AMP update shows how it can infiltrate every corner of the internet
#78Earlier quoted context omitted.
They are building another monstrosity to be able to masquerade as your entire domain. But it is optional , of course /s
Website authors opting in to letting another server serve content "as" their own domain isn't anything new: it's what CDNs do. The Signed Exchanges standard is actually a huge step up because the website authors get to cryptographically sign their content. With normal CDNs, if the CDN is malicious or gets hacked, the CDN is free to serve modified content on the original domain.
[deleted]
Re: A new AMP update shows how it can infiltrate every corner of the internet
#79ah that's nothing. Wait until google launches accelerated desktop pages
And then accelerated shopping results. And then accelerated signups.
Re: A new AMP update shows how it can infiltrate every corner of the internet
#80I think that the mobile trend was blown way out of proportion. I very often find myself clicking on the 'Browse desktop version' button when browsing a so-called 'mobile-friendly' version of a site. Is the look of the website really more important than the content and functionality? For me, it's not. This is just another example of a big tech monopoly imposing their highly opinionated ideas on billions of people. Als…
I dont even think people complained about mobile articles being slow. Sure , there are many bad cases where sites autoplay videos etc. but it’s equally bad in their desktop version (where s the amp there?). A few seconds to load an article on mobile is normal, considering that reading the article will take entire minutes. The probability of needing 1-2 seconds per page applies only when someone is skimming through multiple pages for research. The possibility of doing that on mobile is small, and these are users you dont want visiting your site anyway. Imho google built a honeytrap and is going to get away with murder because, when they will be fined for this, it will be already too late.
I hope developers wake up to this reality. Since that is not going to happen, i hope they abuse amp as bad as they abused html , rendering it useless