amp/

vacuum tube amp

Someone has reached this website with a search for

https://genderdesk.wordpress.com/2018/06/19/ira-matetsky-and-cynthia-rapp-the-internet-tosses-up-more-nuggets/amp/

…which is basically “Ira Matetsky and Cynthia Rapp – the internet tosses up more nuggets” with “amp/” tacked on the end.

AMP is “an open-source library that provides a straightforward way to create web pages that are compelling, smooth, and load near instantaneously for users.” Its main use seems to be with mobile.

Wikipedia’s disambiguation page for “amp”, which for some reason is at “Amp” rather than “Amp (disambiguation)”, does not know anything about it.

What “amp/” does on Gender Desk is to display the text without the sidebar. I have no idea how the original link was generated, but it is easy enough to generate such a display just by adding “amp/” to the end of the shortlink.

For instance, yesterday’s piece on Saint Basilissa, which has lots of nice pictures of icons, lives at https://genderdesk.wordpress.com/2018/09/07/saint-basilissa/

Now, if you add “amp/” to that, as in https://genderdesk.wordpress.com/2018/09/07/saint-basilissa/amp/ you should see the whole thing in a wider format. It even gives the information “4-5 minutes” which is probably the reading time. Unfortunately it will still give you ads, but what can I say. It’s a free blog and “if you aren’t paying for it, you’re the product.”

Genderdesk with and without “amp/”:
saint basilissa with amp   saint basilissa without amp

It does seem to strip out some of the image formatting, for instance on some browsers it may just display the first image of a gallery, or none at all, so there are still a few bugs in it.

2 thoughts on “amp/

  1. Although it’s not visually obvious, the amp page has a number of significant differences in the code. Complex elements are deliberately omitted from the amp specification, which is probably why some incompatible elements don’t work. Of course all these changes are to make the page load faster on mobile.

    The way the page loads style elements is also changed to avoid render blocking, so it’s harder to design a website with AMP. A number of resource intensive CSS elements are disallowed entirely, see https://www.ampproject.org/docs/design/responsive/style_pages

    Although it’s built for mobile, it’s worth noting this is a Google product, and partly designed to fit into https://developers.google.com/amp/cache/ the Google AMP cache. And it has a large number of optimizations that make it easier for Google to crawl and display pages.

    The missing Wiki page about it is https://en.wikipedia.org/wiki/Accelerated_Mobile_Pages

  2. It’s probably not something I have to worry about then, unless I want to try to optimize the images, but I have to admit I find it fascinating and wish I could get a toe-hold into understanding it. I have no idea how many of my visitors are on mobile.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s