Notes

4582 sparkline

Saturday, August 24th, 2019

I’m dubious of this proposal. I just don’t think a nice bag can offer the kind of companionship you get from an animal.

I’m dubious of this proposal. I just don’t think a nice bag can offer the kind of companionship you get from an animal.

Replying to a post on remysharp.com

❤️

Reading Skyfaring by Mark Vanhoenacker.

Replying to a tweet from @tobie

If only Google Search had a similar model.

As it stands, the AMP team gets to offload the unfairness of the format’s privileged position onto the search team, while maintaining the appearance of open source and good governance for AMP.

Replying to a tweet from @cramforce

Replying to a tweet from @cramforce

You won’t recommend me for a Product Manager job at Google?

My dreams lie in tatters before me.

How about a position on the AMP advisory committee? I’m hoping fascists like me aren’t barred.

Replying to a tweet from @cramforce

Never once did I claim that using AMP would result in fewer clicks for publishers.

It’s exactly because AMP is guaranteed to work this way—while nothing else will—that makes the situation unfair.

Publishers have no choice but to use AMP.

Replying to a tweet from @cramforce

But only for AMP pages.

No other framework gets this treatment.

No other web pages—no matter how fast—get this treatment.

Any wonder that developers are resentful of AMP?

Replying to a tweet from @kryshiggins

You are not alone:

https://baymard.com/blog/deemphasize-install-app-ads

During our testing “Install App” banners were the direct and sole cause of several abandonments of some of the world’s largest e-commerce websites.

Replying to a tweet from @cramforce

You’ll notice that I never once said that AMP is a ranking factor.

I said AMP is unfairly privileged in Google search results …because AMP is unfairly privileged in Google search results.

That’s a real shame for AMP-the-format.

Replying to a tweet from @adactio

Replying to a tweet from @cramforce

AMP as often cited is not a ranking factor

This is the kind of semantic chicanery I’m talking about.

AMP pages are pre-rendered by Google. Regular (fast) web pages are not.

The Top Stories carousel appears above other results.

Replying to a tweet from @cramforce

Publisher value enabled by AMP?

Publishers are using AMP because they have to, not because they want to.

If AMP weren’t treated differently to other frameworks, we could assess its true value.

Replying to a tweet from @adactio

Also: holding this position apparently makes me a fascist.

(still shaking my head over that one)

Replying to a tweet from @cramforce

To understand my position, start with the position “one framework shouldn’t be unfairly privileged in search results” and then extrapolate from there. That is the fundamental disagreement.

(I think I’ve made that pretty clear, right?)

Picture 1 Picture 2 Picture 3

Beach scenes.

Florid.

Florid.

Replying to a tweet from @davegehring

According to Godwin’s Law, the discussion stopped here:

https://twitter.com/cramforce/status/1164693853032439810

Replying to a tweet from @jensimmons

Hint away! …But also, please charge your phone’s battery.

Friday, August 23rd, 2019

Replying to a tweet from @rem

Ooh! Colour me intrigued!

Gonna blog about it?