Investigate impl Link as header

[sublimator]

WICG/webmonetization#19 (comment)

[sublimator]

https://developer.chrome.com/extensions/webRequest#event-onHeadersReceived

[sublimator]

@adrianhopebailie @sharafian

Do we want this only for images/videos/etc ? In other words non documents ?
It would definitely be more performant and much simpler if we do it that way.

The webRequest.onHeadersReceived api has an option to declare what types of resources you want to monitor, e.g.:

    this.api.webRequest.onHeadersReceived.addListener(
      listener,
      { urls: ['<all_urls>'], types: ['media', 'image', 'object'] },
      ['responseHeaders']
    )

And what about cross site embedding monetized resources ?
If they are monetized, what would the equivalent of <iframe allow="monetization"> be ?
How to specify that this is "allow"ed ?

[adrianhopebailie]

My thinking was that we update the spec to allow a website to return a link header instead of putting the link tag in the HTML. So it would only apply to the root document but I guess that could expand in time.

The value of putting it in the header is that it's not subject to any client-side manipulation through, for example, other extensions.

[sublimator]

ah right-right yeah! that makes sense I was thinking “for media types that aren’t html” then nesting and it seemed a bit much forgot the basic “server only“ case yeah, shrug on whether it’s worth the perf hit and extra permission