10 ms·
I don’t really think Google’s plan is that weird. And it would be amazing for decentralized networks, archiving, and offline web apps. Google can’t just serve n
by Spivak 6y ago
I don’t really think Google’s plan is that weird. And it would be amazing for decentralized networks, archiving, and offline web apps. Google can’t just serve nyt.com — they can serve a specific bundle of resources published and signed by nyt.com verified by your browser to be authentic and unmodified.
- pwdisswordfish2 6y agoIn what ways is this different/similar from "content centric networking"? https://m.youtube.com/watch?v=gqGEMQveoqg https://m.youtube.com/watch?v=gqGEMQveoqg (Google Tech Talk from Van Jacobsen on CCN many years ago)
- wmf 6y agoAMP is happening and CCN is not.
- pwdisswordfish2 6y agoDo you mean to say that is the only difference?
- wmf 6y agoNo, there are many differences but they don't matter. Since CCN is not economically feasible, none of the technical details matter.
- pwdisswordfish2 6y agoWhy is CCN not economically feasible?
- deleted 6y ago[deleted]
- domenicd 6y ago+1. The way I think about it is that signed exchanges are basically a way of getting the benefits of a CDN without turning over the keys to your entire kingdom to a third party. Instead you just allow distribution of a single resource (perhaps a bundle), in a crytographically verifiable way. Stated another way, with a typical CDN setup the user has to trust their browser, the CDN, and the source. With signed exchanges we're back to the minimal requirement of trusting the browser and the source; the distributor isn't able to make modifications.
- skybrian 6y agoIt seems like there is a risk that an old version of a bundle will get served instead of a new one by an arbitrary host? Maybe the bundle should have a list of trusted mirrors?
- gpm 6y agoAlternatively super short expiry times. It doesn't seem like it would be that concerning to have another site serving a bundle that was 5 minutes out of date. It doesn't seem like it should be too much load to be caching content every 5 minutes.
- deleted 6y ago[deleted]
- gregable 6y agoThere is a publisher selected expiration date as part of the signed exchange which the client inspects. The expiration also cannot be set to more than 7 days in the future on creation. This minimizes, but of course does not eliminate, this risk.
- xg15 6y agoIt also makes signed exchanges completely unusable for delivering packages offline. (E.g. the USB stick scenario) What a bummer.
- tyingq 6y agoThe AMP spec REQUIRES you include a Google controlled JavaScript URL with the AMP runtime. So technically the whole signing bit is a little moot, given that the JS could do whatever it wanted.
- gregable 6y agoThe same could be said of any CDN hosted javascript library. For example: jquery. There is an open intent to implement support for publishers self-hosting the AMP library as well.
- ComputerGuru 6y agoYou missed the required part.
- donaltroddyn 6y agoFor most JS served by CDN, you can (and should) use Subresource Integrity to verify the content. At least the last time I was involved in an AMP project, Google considered AMP to be an "evergreen" project and did not allow publishers to lock in to a specific version.
- gregable 6y agoLong term versions are now supported, so publishers can lock in a specific version. Publisher hosted copies are in the pipeline, as I referenced in the parent comment. My choice of verbiage was a bit confusing it appears.
- donaltroddyn 6y agoI don't think it's your wording that's confusing. You are contradicting the AMP documentation. AMP's documentation seems to indicate that the LTS is stable only for one month (new features released via the same URL each month), and so is not compatible with SRI (see https://github.com/ampproject/amphtml/blob/master/contributing/lts-release.md https://github.com/ampproject/amphtml/blob/master/contributi...) You can specify a version (ie, https://cdn.ampproject.org/rtv/somenum/v0.js https://cdn.ampproject.org/rtv/somenum/v0.js), but the AMP validator complains about that.
- dannyw 6y agoThe plan is bad because google currently tracks all of your activities inside AMP hosted pages site in their support article. Google controls the AMP project and the AMP library. They can start rewriting all links in AMP containers to Google’s AMP cache and track you across the entire internet, even when you are 50 clicks away from google.com.
- wmf 6y agoPublishers who use AMP were already allowing Google to track everything through either Analytics or Ads. Likewise, AMP pages are mostly accessed from Google search that's already tracked.
- robin_reala 6y agoAs a user I can choose to block GA, either through URL blocking or through legally mandated cookie choices in some regions (e.g. France). When served from Google I have no choice in the matter.
- gowld 6y agoIf you can block GA at the client, you can block google.com at the client, no?
- robin_reala 6y agoNot if I want AMP pages. (I mean, I don’t, but there are presumably people who do.)
- gregable 6y agoWhile that's theoretically possible, the library can be inspected and does not do these things.
- simion314 6y agoCould Google give specific persons different versions or is technically impossible?
- colordrops 6y agoWhy do they need a special extension though? What's wrong with DNS?
- gregable 6y agoSigned exchanges are an extension to digital certificates, such as used for TLS. This is independent of DNS.
- grey-area 6y agoThat's not why Google (the corporation) wants this to happen. This is not about technical capabilities but about power. They cannot be allowed to become the gatekeeper for the web.
- jacquesm 6y agoThey already are. The question is not how we're going to stop that from happening but how we are going to roll it back.
- nxnews 6y agoWhy would it be amazing for decentralized networks and offline web apps?
- remexre 6y agoIf I publish mycoolthing.com/thing, it could be mirrored over a P2P network as peer1.com/rehosted/mycoolthing.com/thing, peer2.com/rehosted/mycoolthing.com/thing, etc., in a way that would make it evident to end-users not familiar with the protocol that the content is from mycoolthing.com.
- tgv 6y agoAMP is of course not P2P.
- tyingq 6y agoI think the point is that signed exchanges ( https://developers.google.com/web/updates/2018/11/signed-exchanges https://developers.google.com/web/updates/2018/11/signed-exc...) could potentially be useful, if separated from AMP, and made an actually secure thing. Like, for example, the spec doesn't require specific Google controlled js URLS to be in the content.
- gregable 6y agoSigned exchanges is actually separate spec from AMP. The browser implements it independently. There is no requirement for AMP pages to use signed exchanges nor for signed exchanges to be AMP.
- mulmen 6y agoHow does centralizing content on Google from multiple sources improve decentralization? The web is already decentralized. That's why it is a web. AMP is a scourge. It's a bad idea being pushed by bad actors.
- amelius 6y agoGoogle is not a single server. Think of Google as a CDN.
- deleted 6y ago[deleted]
- oblio 6y agoSo it's decentralized because Google has multiple servers? And here I was, thinking that Google runs everything from a single IBM mainframe. What you're saying would be described as distributed... Not decentralized.
- HeWhoLurksLate 6y agoSeems to me like it's easy to forget there's a difference between those two..
- deleted 6y ago[deleted]
- eternalban 6y ago> How does centralizing content on Google from multiple sources improve decentralization? It actually makes perfect sense in Doublespeak. /s
- DougBTX 6y agoThey’re suggesting a web technology which would allow any website to host content for any other website, under the original site’s URL, as long as the bundle is signed by the original site. That could be quite interesting of a site like archive.org, as the url bar could show the original url. But AMP is a much narrower technology, I’d imagine only Google would be able to impersonate other websites, essentially centralised as you say. The generic idea would just be a distraction to push AMP. Everything would be so much better if the original websites were not so overloaded with trackers, ads and banners, then there would be no need for these “accelerated” versions.
- boomlinde 6y agoHow is it not weird that I see a domain name in the URL bar that has nothing to do with the domain I actually requested content from?
- jeffdavis 6y agoIt's completely moving away from the client/server model to something else. Perhaps that's a great thing to do, but it's not something to do quietly.
- mooman219 6y agoJust hearing about this from the thread, I'm getting a IPFS vibe from this. It would be interesting to see that tech get more native integration with the browser from this idea.
- deleted 6y ago[deleted]
- xg15 6y agoI agree, if we finally got a way to have working bundles on the web, that would be extremely useful. (And would also restore some of the capabilities of browsers to work without internet connection). It seems to me, a lot of the security concerns come from the requirements to make pages served live and pages served from bundles indistinguishable to a user - a requirement that really only makes sense if you're Google and want to make people trust your AMP cache more. I'd be excited about an alternative proposal for bundles that explicitly distinguishes bundle use in the URL (and also uses a unique origin for all files of the bundle).
- gregable 6y agoI believe the issue with this is that users already largely don't understand decorations in the URL. For example, the difference between a lock and an extended verification certificate bubble. Educating a user on what a bundle URL means technically may be exceedingly challenging.
- olingern 6y agoThe problem is ownership. Google is “stealing” or caching content for what they consider a better web. I don’t support ads but I also don’t support Google serving a version of the page that steals money from content creators. So, therein lies the problem: choice. I can imagine a future where amp is ubiquitous and Google begins serving ads on amp content. Luckily, companies have to make money and amp is not in most people’s or company’s best interests. If amp was opt-in only, this would be much more ethically sound.
- gregable 6y agoSigned exchanges guarantee that the content cannot be modified by the cache, such as ad injection. Google has never injected ads into any cache served AMP document (technically if the publisher uses AdSense, this is false, but that's not the point you are making). It's difficult to follow what definition of theft is being suggested. The cache does not modify the document rendering, it's essentially a proxy. In a semantic sense, this is no different than your ISP delivering the page or your WiFi router.