互联网与文化theregister.co.uk
在 Google AMP 杀死网络之前杀死它
Kill Google AMP before it kills the web
2017 — 2020，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
2017年 The Register 的文章批评 Google AMP：它本可成为轻量网页标准，但谷歌通过缓存和托管内容控制分发，把内容集中到自家平台，威胁开放网络的竞争与发布者主权。
为什么经久不衰：AMP 争议延续多年，今天关于平台权力、内容托管和开放网络的讨论仍与它直接相关。
HN 评论精选
AMP 让谷歌成为内容的单一入口，应以排名惩罚代替强制标准。
自谷歌推出 AMP 后，我强迫自己改用 Bing。我并不是更喜欢 Bing，但我更不喜欢谷歌成为我获取内容的单一来源。我希望我访问的网站能控制自己的内容，并且能方便地被链接。谷歌如此无情地推动 AMP 应受谴责，这不只是偷链接，还让谷歌变成“互联网”。AMP 本可以成为一个标准，实际上它大多只是常识（好的轻量 HTML/CSS/JS）。谷歌不该强加于用户和创作者，而应降低违规者的页面排名。作为用户和工程师，另一件让我恼火的事是它又多了一个维护点，多了一个糟糕且被忽视的体验。AMP 页面坏掉时，我有时还到不了非 AMP 版本。我不怪开发者，只怪谷歌制造了这个烂摊子。
rubyn00bie查看英文原文
Ive forced myself to use Bing since google introduced AMP. Do I like it better than Google? No, I don't. But! I like not having google become my single source of content more than I dislike the slight drop in quality as a result of using Bing. I like the sites I go to, to have control over their content and being able to easily link to them. I think it's reprehensible for google to push this so relentlessly and beyond simply stealing links it makes google into the "internet." This (AMP) could easily be a standard, in fact it's mostly just common sense (good lightweight HTML/CSS/JS). Instead of Google forcing its way on users and creators it could just lower the page rank of the offenders. One other thing about AMP that pisses me off as a user and an engineer is it's one more place to maintain meaning one more shitty neglected experience. As a user I hate it when AMP pages are broken and I somehow can't get to the non-AMP version. I don't blame the developers because we have enough on our plate. My anger is solely directed to google for making the damn mess in the first place.
标准化子集可接受，但谷歌托管内容威胁竞争，内容应留在发布者站点。
理论上我不介意有一个更标准化的网页子集：内部结构一致、渲染快速。但让谷歌加载这些结构化内容并托管在自家平台上是个糟糕的主意。内容应该留在发布者的网站上。把太多内容集中在一处对竞争很危险。实践中也有实现问题，比如文章里提到的那些。
richdougherty查看英文原文
In theory* I don't mind the idea of having a more standardised subset web page that has a consistent internal structure and that renders quickly. However, having Google load this structured content and host it on its own platform is a terrible idea. Content should remain on the publisher's site. Putting too much content in one place is dangerous for competition. * In practice there are implementation problems too, e.g. those mentioned in the linked article.
AMP 是谷歌走向不提供链接、直接回答查询的中间步骤。
别担心，AMP 只是谷歌终极愿景路上的过渡步骤：直接用一个事实、一段摘录或知识图谱数据表来回答所有搜索查询，这些信息从你的内容中提取，而且根本不提供任何 URL。
DebtDeflation查看英文原文
Don't worry, AMP is just an interim step on the path to Google's ultimate vision, which is to answer all search queries directly with a fact, passage, or knowledge graph datasheet, using information it extracted from your content and without providing any url at all.
AMP 在去中心化网络中引入私有单点故障，方向错误。
基本上整个网络没有单点故障，除了 DNS，而连 DNS 也是去中心化的。那面对这种情况你该怎么办？——显然要引入一个私有服务形式的单点故障。
jacinabox查看英文原文
Basically the whole web has no single point of failure, with the exception of DNS, and even that is decentralized. So what do you do with that?-- obviously introduce a single point of failure in the form of a private service.
历次讨论
同类还值得读
如今电脑上几乎所有操作在感知上都比 1983 年更慢（2017）
Almost everything on computers is perceptually slower than it was in 1983 (2017)
2017 年的推文串认为，尽管计算机硬件比 1983 年快得多，日常操作的感知速度却常常更慢：启动、界面响应和网络应用被层层抽象、动画、后台检查与网络依赖拖累。
互联网与文化上首页 5 次 · 2017–2020twitter.com网站肥胖危机
The Website Obesity Crisis
Maciej Cegłowski（idlewords）的经典演讲文稿《网站肥胖症危机》，批评现代网页越来越臃肿：动辄数 MB 的 JavaScript、追踪脚本和广告，把本可以轻…
互联网与文化上首页 5 次 · 2016–2021idlewords.com编辑精选亚马逊那本标价 23,698,655.93 美元的苍蝇书
Amazon’s $23,698,655.93 book about flies
博文讲的是亚马逊上一本关于果蝇的二手书被标到 23,698,655.93 美元。
互联网与文化上首页 5 次 · 2011–2022michaeleisen.org浏览器 User-Agent 字符串的历史
History of the browser user-agent string (2008)
2008 年的经典文章用戏谑的“创世纪”口吻，讲述浏览器 User-Agent 字符串如何从简单的标识演变成层层叠加的伪装：浏览器为了绕过按 UA 分发的网站检测，纷纷把自己伪装…
互联网与文化上首页 5 次 · 2012–2022webaim.org编辑精选最后的问题——艾萨克·阿西莫夫
The Last Question - Isaac Asimov
阿西莫夫最著名的短篇科幻小说《最后的问题》的在线全文。
互联网与文化上首页 5 次 · 2009–2019multivax.com编辑精选