5 ms·
Doesn't https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/ https://amphtml.wordpress.com/2018/01/09/improving-urls-for-... address one of th
by bryanlarsen 9y ago
Doesn't https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/ https://amphtml.wordpress.com/2018/01/09/improving-urls-for-... address one of their two demands?
- bagacrap 9y agoThat is a great article because it sheds light on actual technical reasons for the current behavior. The original article is pretty light on technical details of how to achieve their suggested goals, which is weird because it assumes the user knows/cares about URLs, and that is probably only true of those with more tech savvy.
- wmf 9y agoThe letter is undated so it could be old and I'm sure they'd prefer if URLs get fixed immediately rather than in a few years. Update: So after Google announces that they're fixing AMP, some people decided to write a letter demanding that Google fix AMP? I guess the next step will be to retroactively take credit for Google's changes.
- ZoomStop 9y agoIt's on GitHub also and looks to be from today: https://github.com/amp-letter/amp-letter.github.io https://github.com/amp-letter/amp-letter.github.io
- strict9 9y agoNo, it's recent. (last update 2 minutes ago) https://github.com/amp-letter/amp-letter.github.io https://github.com/amp-letter/amp-letter.github.io
- temp-dude-87844 9y agoThe letter seemingly dates to 2018-01-09 [1], with the earliest non-content commit, which doesn't include the letter's body, on 2017-11-10, the same day as the domain's registration. I agree it's poor form to not include an origination date in the document itself. [1] https://github.com/amp-letter/amp-letter.github.io/commits/master https://github.com/amp-letter/amp-letter.github.io/commits/m...
- thedz 9y ago1. H2 2018 2. Relies on a "web standard" that Google is pushing and is implementing in Chrome (and so far, I think, only confirmed to be in Chrome)
- deleted 9y ago[deleted]
- jyasskin 9y agoWe're expecting to follow roughly the same path that SPDY (eventually HTTP/2) took: iterate on some early versions in Chrome to get experience while the format goes through the standardization process, and eventually remove those in favor of the standardized version. You can follow the IETF part of the process at https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-01 https://tools.ietf.org/html/draft-yasskin-http-origin-signed....
- untog 9y agoIn theory it does, but there are a lot of open questions there (including whether Apple will implement it). I'd say the search engine placement is the bigger of the two issues anyway, as it clearly shows Google putting their thumb on the scale.
- niftich 9y agoNo. In fact, the solution detailed in that article accomplishes the exact inverse of one of the letter's demands. While the letter wants third-party content not to be surfaced in a wrapping viewport that downplays the fact that it's actually Google's AMP Newsreader, the recent AMP announcement details a planned change where emerging tech [1] will be used to make the URL appear as if the content was directly loaded from the distant origin, because the content being served has been digitally signed by that origin and its serving has been delegated to Google akin to how a run-of-the-mill CDN is delegated the authority to serve content for a domain that's 'spiritually' owned by someone else. However, the recent AMP announcement does address a very frequent complaint about AMP. Just one that's at odds with the one the letter is requesting. [1] https://github.com/WICG/webpackage https://github.com/WICG/webpackage
- Ajedi32 9y agoIf the content has to be signed by its true origin, does it matter who's technically serving the content? There could be privacy considerations I suppose, but the standard addresses that already: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.6 https://wicg.github.io/webpackage/draft-yasskin-http-origin-...
- bobfunk 9y agoTo me the proposal there is arguably even scarier than what AMP is doing now. It requires changing browsers, to let people distribute Google Hosted Apps on their own domains (as long as Google approves). Sites distributed in this way will get preferential treatment by Google. This is essentially an App store model, similar to Google Play, and the really big danger is that we end up in a place where you either distribute (and host) your website through Google's AMP registry, or you're not actually on the web (in the same way that distributing your Android app as an APK outside of the Play store is not a realistic distribution channel). I hope Firefox, Safari and Edge will resist this.
- jopsen 9y ago> you either distribute (and host) your website through Google's AMP registry As long as anyone can setup their own AMP-like cache and build a search engine similar to Google, that also supports preloading... then I'm not sure it so bad. The proposal GP refers to has a lot of use-cases, it basically makes caching of HTTPS by third-parties possible. At-least to some extent.
- stfwn 9y ago> As long as anyone can setup their own AMP-like cache and build a search engine similar to Google, that also supports preloading... then I'm not sure it so bad. Yes, anyone could build a cache. But can anyone build a cache that can compete with Google's absolutely massive infrastructure and pile of money, not to mention the reach they already have with search? I'd say this is not a discussion on the level of ‘can you build a better product and win from a giant company?’, more like ‘can you build a planet and get everyone to move there?’