8 ms·
Ok. Let's take your claim at face value. Can you explain how to accomplish content blocking with WebBundles? For example, adblockers?
by RonanTheGrey 6y ago
Ok. Let's take your claim at face value.
Can you explain how to accomplish content blocking with WebBundles? For example, adblockers?
- spankalee 6y agoThe work exactly the same. They don't even need any modification, as far as I understand. That's what I'm trying to point out by saying that WebBundles adhere to the current request/response model - they just preload a bunch of responses so you don't need the network round-trip. See the section I already linked: https://wicg.github.io/webpackage/draft-yasskin-wpack-bundled-exchanges.html#name-load-a-response-from-a-bund https://wicg.github.io/webpackage/draft-yasskin-wpack-bundle... An extension that can modify requests and responses still can with bundles. In fact, it should be easier to identify and block individually address resources out of a WebBundle vs the transpiled bundle out of WebPack, et al.
- Vinnl 6y agoJust coming across this now, but since you seem to know a bit about this: can a tracker blocker prevent the preload requests from being sent in the first place, or alternatively, is it the case that the preload requests do not allow whoever initially serves up that content to track who has been loading it?
- RonanTheGrey 6y agoThis seems like an advanced form of what service workers do, or am I misunderstanding? Provided that adblock/content block functionality wouldn't be impacted, I can provisionally get behind this. It would certainly make my life as web developer easier.
- nitrogen 6y agoOne of the reasons to block content selectively is to save bandwidth on metered connections. Does a WebBundled site have to also provide separate resources, or is there some way for this bandwidth to be saved for those who need to save bandwidth?