ua-client-hints VS hosts-blocklists

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

https://github.com/notracking/hosts-blocklists seems dead. https://raw.githubusercontent.com/DandelionSprout/adfilt/master/LegitimateURLShortener.txt should work except the regex rules.

had the same issue, was caused by notracking

Unfortunate that the map is on your simpleanalytics.com site. NextDNS tells me it is blocked by the notracking list: https://github.com/notracking/hosts-blocklists

Here is a project that attempts to do that