Re: [w3ctag/design-reviews] `Accept-CH` header is weird (#206)

Hey @igrigorik,

We discussed again at today's TAG call, and I remain confused (perhaps you can join a future call?).

There's a deep principle I'd like some clarity on: are we "too bloated" today? It seems the primary value is in reducing request header size, but only on the sites which don't use the values subsequently. This is very concerning! It seems that if we're at (or beyond) some theoretical limit about the total amount we can add, that the TAG should be providing strong guidance to feature developers to avoid new header information and perhaps be working to trim existing bloat back. If that's a cause we need to be signed up to, we'd love to know. 

Specifically, would love to understand if there's data that points to a general issue with header bloat and a calculus that describes how the `Accept-*` pattern helps, particularly given the extra round-trips that might be needed (e.g., for a redirect) to generate alternative body content for a top-level request.

Similarly, does the data suggest that we should be trying to consolidate `Accept-*` headers? If we're over our budget, would like to avoid opt-in-flag bloat.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/206#issuecomment-351204946