ua-client-hints VS ethical-ad-client

The Client Hints specification covers a lot of this already - https://wicg.github.io/ua-client-hints/#content-adaptation-u... ... DPR, width, and viewport-width are already available in some browsers. Hopefully other hints will be available soon.

I encourage you to review the decision making and engage in the discussion here: https://github.com/WICG/ua-client-hints

chrome is starting to implement UA-CH, which splits up user agent info into individual headers sent by the client: https://wicg.github.io/ua-client-hints/

As a Firefox/FreeBSD user occasionally annoyed by this nonsense, but not being knowledgeable about modern web standards evolution, I wonder if https://wicg.github.io/ua-client-hints/ will fix this by killing User-Agent headers.

ua-ch might reduce the amount of data browsers send, though it's gonna take a while to move away from regular user agents: https://wicg.github.io/ua-client-hints/

There is a JS companion to this proposal that splits up the information in a similar way

https://wicg.github.io/ua-client-hints/#interface

We do support publishers using an API directly, and running none of our code.

Our ad client is also open source, and pretty simple: https://github.com/readthedocs/ethical-ad-client -- we have publishers who use a published version with Subresource Integrity, but you can also just host the JS yourself if you want.

Yea, we are planning to do a blog post on it, but the total overhead is in the 10's of KB. Just a single JS file, and an image. All open source: https://github.com/readthedocs/ethical-ad-client