Live data from Hacker News

AMP: the missing controversy

ferdychristant.com

61–70 of 143 posts

Re: AMP: the missing controversy

#61
post #18

Earlier quoted context omitted.

Am I reading the article right: the browser preloads resources from amp pages from the search page? That's going to be hard to fix in an HTMLLite sorry of way.

HTTP/2 servers can preload (if they choose).

Preload is different from push.

Re: AMP: the missing controversy

#63
post #37

Earlier quoted context omitted.

I disagree with your defeatist message and I consider it harmful if spread. Individual action is the foundation of our entire social system. It is not "useless" by any measure. I don't want to use AMP in email so I'm not going to. It's just that easy. What are you doing and what do you suggest the rest of us do? Is voting with our wallets not a thing any longer?

And how productive do you think "voting with our wallets" can be for a product we don't pay for from a company with more money than all of us combined?

Probably at least slightly more productive that literally voting in actual elections.

Re: AMP: the missing controversy

#64
post #63

Earlier quoted context omitted.

And how productive do you think "voting with our wallets" can be for a product we don't pay for from a company with more money than all of us combined?

Probably at least slightly more productive that literally voting in actual elections.

If I had a solution I'd be telling you about it I assure you. I'm just saying that vote with your wallet and put your faith in the market is also not a solution in this case.

Re: AMP: the missing controversy

#65
post #48

Earlier quoted context omitted.

Me too, but ultimately this will mean not using services that decide to implement AMP. Most services will just see one or two weird customers creating issues for them. Also, unless you complain, they'd have to check their server logs, to even notice the deliverability issues. You can just as well receive the e-mail and just complain if it's AMP only, or they don't pay attention to the plaintext part, causing issues f…

A 501 return will cause an email bounce, so the sender will know that it has been refused. If you for example use "501 5.6.1 AMP format email messages not supported, please use a mail system that doesn't use AMP" then the sender will get that as the reason the mail was not sent.

I know, but AMP will be used mostly for automated email, and I'm not holding my breath many services that send me e-mail check their mailserver logs, if they even know such a thing exists. Bouncing to no-reply address will not help much either. And I need to receive e-mail from services I've registered to anyway, that's why I whitelist anything sent to a random email address that I assign to each service.

Better to just complain over channels where someone is actually listening.

Re: AMP: the missing controversy

#66
post #39

"Something only Google is capable of, because it is the only entity in the world controlling the most important information portal: search." How is Google the only search engine? A different one is literally a click away. This just doesn't pass as an argument.

I have a website. How can I get all my visitors from a search engine other than google with "literally a click"?

I can’t. 95% of my visitors will come from Google. As result, I’ll have to accept whatever demands Google makes.

Re: AMP: the missing controversy

#67
post #3

Earlier quoted context omitted.

I think the best thing to do is just be the kind of online citizen you want to see. It may be small but it is something you can do yourself. I will be looking for a way to move my online identity away from Google to something I control more directly. I am also going to try replacing my social media activity with email. The web is already decentralized, we just need to use it.

I closed my G Suite account today because of Google’s announcement of AMP for Email. Luckily I didn’t have a huge Google presence in the first place beyond email which is easily IMAPed over to another server. Takeout allowed me to extract the rest: my docs as ODF, YouTube subs as RSS and contacts as ICS. If anyone’s interested I wrote up my investigation into potential replacement mail services: http://www.robinwhitt…

Another option is simply sign up for a shared hosting account. You'd get all of the features you're looking for and more for equal or less money.

Re: AMP: the missing controversy

#68
post #37

Earlier quoted context omitted.

I disagree with your defeatist message and I consider it harmful if spread. Individual action is the foundation of our entire social system. It is not "useless" by any measure. I don't want to use AMP in email so I'm not going to. It's just that easy. What are you doing and what do you suggest the rest of us do? Is voting with our wallets not a thing any longer?

And how productive do you think "voting with our wallets" can be for a product we don't pay for from a company with more money than all of us combined?

You're "voting with your data," which for a company like Google is essentially the same thing. If you don't hand them data, they can't monetize it.

Re: AMP: the missing controversy

#69
post #60

Only thing I can't figure out is why is anyone buying into it in the first place? Has the publishers not learned anything from Facebook taking their content and readers hostage? Sure, it gives you traffic boost in the beginning, but sooner or later it will force you to play by their rules and generate content for them .

If I had a choice between going out of business sooner (not using AMP) or going out of business later (getting screwed by AMP one day), I'd choose later.

Re: AMP: the missing controversy

#70

We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…

How about we create client-side plugins for each of the major platforms that people can use to detect the AMP mime-type and automatically mark as spam? Email reputation is a huge concern for senders and if there were enough people using the plugin it would poison the entire thing and may deter senders from using AMP entirely.

Now, for the web AMP I have no idea...

Post reply on HN