How about Discourse Support Google AMP?

Some alternate viewpoints:

I don’t think AMP can be considered “open” technology. It’s a cunning scheme by Google, and other tech companies with resources to host AMP caches, to pillage/appify the WWW and divide the spoils.

It causes web publishers to lose control of their stack, because Google forces them to load a restricted version of the site on Google’s own servers (or the servers of one of their co-conspirators). It’s the end of server-side logs, because visitors never reach your server.

In the long run, the less control you have over your stack, the more at the mercy of those large companies web publishers will be. You end up sending your content onto their platform, and it is no longer really the open, decentralized WWW.

Google puts a back button on your site, so that visitors are more likely to go back to the Google SERPs than to explore deeper into your site (continuing this trend).

Signed HTTP exchanges spoof the URLs so that visitors don’t even know that they aren’t on your real website.

You have to load JavaScript from Google’s servers for it to be valid AMP.

If users don’t want to load Google’s JavaScript, the spec punishes them by forcing an absurd 8-second page loading time (not an exaggeration).

“Portals” are harmful to smaller publishers, because they allow large sites (that typically send traffic) to only show previews of the linked-to sites. It’s the new “can you open all external links in a frame?”

That’s part of the reason why it’s so bad. Google is not playing by the rules any more, and they are treating the Web as if it’s a Google product.

The only way Google can get people to use it is to strong-arm web publishers into adopting their format under threat.

AMP isn’t even faster than a hand-optimized page. Preloading-on-hover techniques (like in Gatsby.js) make loading pages as fast as an SPA, so I don’t think that the speed argument is convincing. It’s mainly about the business interests of some large tech companies that have the resources to host AMP caches.

A little extra traffic in the short term might sound attractive, but I don’t think it’s worth selling out the future of the Web. Also, I’ve read some comments from people who haven’t noticed much increase in traffic after implementing it. See also:

Sorry for the rant. Maybe Google will eventually win and all of our “websites” will become little more than pieces of content hosted on the networks of a few companies’ AMP caches, but I think that there is still a chance to stop it.

5 个赞

I am really glad that Discourse don’t consider to use AMP. With AMP users click a few times more to enter a website.

3 个赞

I have made a paid topic for anyone will to take this and do this as a paid project for me, [PAID] Convert discourse topics(forum) to Google AMP automatically

关于 AMP 的新信息:

总结来说,它声称谷歌欺骗出版商说采用 AMP 会提高加载速度,尽管该公司员工知道这只会提高“性能中位数”,并且实际上比出版商一直在使用的一些速度优化技术加载得更慢。它声称 AMP 页面为出版商带来的收入减少了 40%。投诉指出,AMP 的速度优势“至少部分是谷歌限制的结果。谷歌通过给非 AMP 广告人为增加一秒延迟来限制其加载时间,以便为谷歌 AMP 提供‘一个不错的比较优势’。”

4 个赞

此视频对Google AMP进行了精彩的总结,并解释了为什么它实际上并没有带来好处。

3 个赞

支持 AMP 不仅不必要地复杂化,而且实际上对您自己不利。

几乎所有我从那些声称了解 SEO 改进(除了最明显的方法)的人那里听到的说法,都像是彻头彻尾的骗局。唯一那些似乎想做完全违背常识的事情(例如,获取电子邮件地址并立即开始发送电子邮件,无需验证它是否属于他们以及他们知道如何输入)的人,是那些声称了解营销的人。(同样,有少数例外。)

3 个赞

在我开始专注于自己的项目之前,我曾在SEO领域工作过,有一些技术效果非常好,但这个行业充斥着骗局和江湖骗术。如果你聘请一家SEO公司,你可能会被敲竹杠,但如果你找到合适的人来做,或者学到足够的知识,这可能意味着一个项目成功与否的区别(尤其是在电子商务或旅游等行业)。偶然发现正确的公式是可能的,但系统地改进它要有效得多。

我相信这是真的,而且我曾与几位知识渊博的人共事过。其中一位我付了不少钱,而且不后悔。(尽管没有得到回报)

没错。

而且我相信也有一些人确实了解营销。我知道我对此并不了解(我在论坛上看到一些产品比cdck托管差得多,而且贵得多;我该如何向购买这些产品的人推销?),但客户的营销人员所做的事情似乎很疯狂。

(内部)搜索引擎优化 (SEO) 对此很有帮助。我会尝试让我的网站在谷歌上针对任何与启动和管理论坛相关的查询进行排名。大多数人会在开始之前做一些研究。如果他们不自己搜索谷歌,他们会在论坛上提问,然后其他人会搜索谷歌然后粘贴链接(进一步提高排名)。也许可以试试这项技术

1 个赞

新的 AMP 是“如果你 使用它,我们将在搜索结果中开始惩罚你”,也就是……

这很奇怪,因为这似乎是一场走向底部的竞赛,而获胜的唯一方法是静态 HTML 文件?:thinking:

4 个赞

那么 Discourse 会开始使用它吗(以防万一受到任何处罚)? :thinking:

关于我11月说过的内容,我再补充一下……

内容概要: 出版商正寻求摆脱 Google AMP。
https://www.wsj.com/articles/publishers-move-to-abandon-google-supported-mobile-web-initiative-11645725640

3 个赞

还有一个很棒的“新技术”——也适用于非 AMP 页面:
签名交换 (SXG)

1 个赞