Omg, looking at the user agent client hint proposal, it is a nightmare of complexity! For such a trivial thing, you will now have dozens of headers. And one of

Omg, looking at the user agent client hint proposal, it is a nightmare of complexity! For such a trivial thing, you will now have dozens of headers. And one of the force of user agents string was the fact of not being "fixed" in term of format but to allow unexpected evolution. The issue with it that worth to be solved is just the mountain of lies with browser not assuming their id but having to list all their ancestors. Also, again something that itch my brain with a new case of Google controlled info: <<Note the word "secure" in the paragraph above, and the SecureContext attribute in the IDL: these client hints will not be delivered to plaintext endpoints. Non-secure HTTP will receive only the reduced User-Agent string, now and forever.>>