Live data from Hacker News

Google proposed Web Bundles could threaten the Web as we know it

ghacks.net

71–80 of 84 posts

Re: Google proposed Web Bundles could threaten the Web as we know it

#71
post #68
post #64

Earlier quoted context omitted.

This feels like such a weird stance. I can’t imagine someone saying something to the effect of “I don’t want my DNS records just circulating without my control.” This isn’t like AP giving CNN republishing rights, this is getting a magazine from the stand at the convenience store rather than having going to the Condé Nast corporate HQ. Like it’s your site, exactly as it would be if it was delivered by your server just…

DNS is not content. HTTP caches were always problematic from a business perspective. Great for downloading large binaries (installs) but problematic when they don’t expire as expected, or if content needs to change for contractual reasons.

Tell that to cloudflare.

It's not like you're forced to cache things if it doesn't work for your business case.

Re: Google proposed Web Bundles could threaten the Web as we know it

#72
post #69

Earlier quoted context omitted.

Assuming that the third party in this scenario is distinct from the party serving the bundle, they wouldn't be involved in the TLS/QUIC connection, right? So it seems like a third party wouldn't even know that their resource was delivered, unless the party delivering the bundle notified them, or their script makes a separate request to their own server. (And those are options already, so AFAIK bundles wouldn't give t…

In the scenario, the third party is the advertising broker, Google, who are also the entity serving the signed bundle.

Yeah, I think this is a compelling argument, but also, it's a decent argument against using Google Search itself, is it not? They can almost certainly already correlate a click on a search result on google.com with the Google Ads subrequest from the target page.

And, on the other hand, the fact that web bundles are signed and can be delivered by any origin means that a privacy-focused user agent could try to fetch the bundle indirectly via some privacy-preserving CDN - essentially DoH for web bundles. If you are about to load a site via some known web-bundle host (like https://www.google.com/amp/ probably), try sending a request to some Cloudflare Workers setup or something first.

Re: Google proposed Web Bundles could threaten the Web as we know it

#73
post #68
post #64

Earlier quoted context omitted.

This feels like such a weird stance. I can’t imagine someone saying something to the effect of “I don’t want my DNS records just circulating without my control.” This isn’t like AP giving CNN republishing rights, this is getting a magazine from the stand at the convenience store rather than having going to the Condé Nast corporate HQ. Like it’s your site, exactly as it would be if it was delivered by your server just…

DNS is not content. HTTP caches were always problematic from a business perspective. Great for downloading large binaries (installs) but problematic when they don’t expire as expected, or if content needs to change for contractual reasons.

I mean you’re the one who gets to decide how long the signature is valid for just like you can choose your TTL in DNS. And a malicious cache can’t continue to serve stale content because browsers will reject it. You get a hard guarantee that your TTL will be respected.

Re: Google proposed Web Bundles could threaten the Web as we know it

#74
post #67
post #64

Earlier quoted context omitted.

This feels like such a weird stance. I can’t imagine someone saying something to the effect of “I don’t want my DNS records just circulating without my control.” This isn’t like AP giving CNN republishing rights, this is getting a magazine from the stand at the convenience store rather than having going to the Condé Nast corporate HQ. Like it’s your site, exactly as it would be if it was delivered by your server just…

It's not weird to reject arbitrary complexity. The most important issues is the 'lack of value' - not anything else. Complexity compounds to imbue cost geometrically, we don't need stuff 'because', we need stuff that solves real problems.

For sure, but the big value prop is better speed and less load on your own servers when your content primarily comes from Twitter, Google, IG, Facebook, Reddit, etc. Small sites can use this to not need a CDN and avoid the hug of death.

If it doesn’t come with a benefit to you then it’s all good.

Re: Google proposed Web Bundles could threaten the Web as we know it

#75
post #72
post #69

Earlier quoted context omitted.

In the scenario, the third party is the advertising broker, Google, who are also the entity serving the signed bundle.

Yeah, I think this is a compelling argument, but also, it's a decent argument against using Google Search itself, is it not? They can almost certainly already correlate a click on a search result on google.com with the Google Ads subrequest from the target page. And, on the other hand, the fact that web bundles are signed and can be delivered by any origin means that a privacy-focused user agent could try to fetch th…

This would be like opera turbo (and similar from other browsers), but with fewer privacy concerns, so it's not even new design space.

Re: Google proposed Web Bundles could threaten the Web as we know it

#76
post #29

Fyi... Web Bundles and Signed HTTP Exchanges are confusing topics so I think it's worth reading 2 previous threads with comments from 2 Google employees (spankalee, jefftk) [1]. One may still choose to discount their explanations because they may be biased sources but I still think everyone should try to understand what they're saying. Hopefully, being familiar with the technical details will elevate the discussion s…

[deleted]

Re: Google proposed Web Bundles could threaten the Web as we know it

#77
post #29

Fyi... Web Bundles and Signed HTTP Exchanges are confusing topics so I think it's worth reading 2 previous threads with comments from 2 Google employees (spankalee, jefftk) [1]. One may still choose to discount their explanations because they may be biased sources but I still think everyone should try to understand what they're saying. Hopefully, being familiar with the technical details will elevate the discussion s…

> Hopefully, being familiar with the technical details will elevate the discussion so people who disagree can point out specific and concrete technical flaws Asserting that an elevated discussion should center only on technical flaws and disagreements is a myopic way to look at a topic. There’s more to the web than the technology used to power it. How a technology is used, and what it enables (good or bad) is an appr…

I agree that how tech is used & what it enables is a good discussion.

I think folks interested in this topic should get a basic education.

I resend starting with intents & desires the project started with, by reading the ietf draft of the use cases,

https://tools.ietf.org/html/draft-yasskin-wpack-use-cases-01

Re: Google proposed Web Bundles could threaten the Web as we know it

#78
post #27
post #7

Earlier quoted context omitted.

Yes because heavy pages clog their crawlers. Of course they are not following their advice (neither does FB)

And I don't really understand why they don't follow their advise. Saving a single byte on Google front page can potentially save terabytes of bandwidth. I know the idea of "developers are expensive, hardware is cheap" but when you serve trillions of search queries, hardware is worth considering. The 8 MB you get don't come from nowhere, there is a server somewhere sending them to you. And improving user experience fo…

This actually gets back to the issue of web bundles. Google doesn't have to worry about the 8 MB because they have an extensive CDN, but smaller sites have to save every bit because they are being charged for it. If Google can leverage its CDN to serve the smaller sites, everyone wins.

Re: Google proposed Web Bundles could threaten the Web as we know it

#79
post #8

I think their idea is to combine that with signing the bundles, so a page from www.someserver.com can be served by anyone, aka Google. I guess this would mean Google can serve all content on the web. There seems to be a strong urge in Google to cut the connection between then endpoints of the web and become the central authority. Make all traffic flow through their machines. Let no information arrive at the endpoints…

Part of what excites me is that it decentralizes where assets have to come from. Yes it means Google can serve stuff, which will help some all operators at who knows exactly what cost of privacy.

But what absolutely electrifies me is that I can share content with other people: even in an offline scenario I can give then a webbundle with a site if the site supports it, and the friend's browser can crytographically check everything out, & trust that the bundle is from the bundler.

> Right now, requests on the web are kind of p2p.

Today's web is decentralized, because there are many domains. But there is little peering among peers: everything is client-server.

This, imo, enables a much more p2p web. It enables a distributed web. Where even if an endpoint is under attack, the web can go on. Where folks who fall over the edge (go offline) can still operate. But yes, seems likely Google intends to be a rather large peer among this newly distributed web.

I recommend the IETF draft of use cases for getting a taste of what WebBundles is for, which hints at this new distributed architecture, by way of describing characteristics a WebBundled web has,

https://wicg.github.io/webpackage/draft-yasskin-wpack-use-ca...

Re: Google proposed Web Bundles could threaten the Web as we know it

#80
post #79
post #8

I think their idea is to combine that with signing the bundles, so a page from www.someserver.com can be served by anyone, aka Google. I guess this would mean Google can serve all content on the web. There seems to be a strong urge in Google to cut the connection between then endpoints of the web and become the central authority. Make all traffic flow through their machines. Let no information arrive at the endpoints…

Part of what excites me is that it decentralizes where assets have to come from. Yes it means Google can serve stuff, which will help some all operators at who knows exactly what cost of privacy. But what absolutely electrifies me is that I can share content with other people: even in an offline scenario I can give then a webbundle with a site if the site supports it, and the friend's browser can crytographically che…

We might not disagree much. IDK. I think there's something right about what you saying, but I seek clarification. I ask for your patience in thinking outloud with me (and my schizoposting); I'm someone who isn't as skilled as you are with computers. Despite my ignorance, I am a person deeply concerned with p2p-ness. I'm delighted to see your argument, and I appreciate your perhaps contrarian perspective here.

Google is evil, and if we need to wrestle about that, I will. I'd like to see your red-team skepticism about their intentions and your attempt to consider how this may be a trojan horse or a false-compromise. Google is famous for making moves that look neutral or even good from many angles that are ultimately centralizing power in the hands of capitalists. With good reason, we should doubt why they are doing this. It does appear that the core intuition (if I understand correctly) in WebBundles //can// be used to improve decentralization of information power, but I suggest we should paranoically imagine how it may be exploitable by Google (that is our duty here).

I have some limited experience and a ton of skin in the game on this one. For several years, my wiki has had some of the properties of a prototype of a WebBundle, including an attempt at enabling cryptographic verification (https://philosopher.life/#Cryptographic%20Verification). My goal is to emit one huge all-inclusive html file with the signature wrapped around it (I sign and push/sync up to every minute). This enables me to distribute my wiki across many networks, even sneakernets, without losing one of the fundamental keys to my voice. I'm a second-class citizen on the internet compared to a large corporation, and I have to be able to effortlessly abandon or accept the losses of rented end-points (I really don't own my domain, access-point, or server...they are merely rented: I do own my private key though). In some sense, I have the opportunity to agnostically treat the methods of distribution as a lame middlemen pipeline (what we always hoped the internet infrastructure would really be). I give up my ability to control how my wiki is distributed in some sense as I enable anyone to pass around the signed wiki as a proxy. I happily lose the ability to check whether or not I want to send my signed wiki to any individual in many cases, and I lack interactive control of a session; it feels like I become a far more passive participant of the web, being incentivized to provide the read-only information valuable to ML and disincentived from relying upon dynamic real-time exchanges. I appreciate being able to prevent people from putting words in my mouth while also enabling users of my wiki to acquire and run the site offline, as they see fit, with maximum privacy and anonymity.

There's the context I have. From what I can tell, from a grassroots p2p practice, the reason that the signature "works" is because a user has maintained an old copy of the wiki or even just the public key that they do trust. They've chosen by hand to trust it's me that signed it. I'm not convinced that Google intends to maximize the automation and decentralization value of that kind of verification. It seems an incidental possibility at best (perhaps there's their quasi plausible deniability in seeking a monopoly).

They aim to be more than merely a very large peer, and I'm begging you to question that more openly with me. This feels like a disruptive feint only seeking decentrality in name. Perhaps their move weakens the powers of many web infrastructures that would otherwise continue to centralize, but I think they will continue to attempt to take over whatever power vacuums arise in that space (I assume they can see how to make money off this far better than I can too). When I see, for example, Dat become a first-class citizen of Chrome and when I see them empower client-side archiving, search, and moderation to users of their infrastructure (while taking Firefox and web standards off the leash), I'll begin to believe they intend to enable a p2p web. For now, I see them building an AMPed blackhole walled-garden where they aim to be the root server of trust and authority on what is salient while allowing the highest paying bidders to have degrees of access or control over our data, minds, and lives.

Post reply on HN