ua-client-hints
webappsec-permissions-policy
Our great sponsors
ua-client-hints | webappsec-permissions-policy | |
---|---|---|
13 | 5 | |
575 | 391 | |
2.3% | 0.3% | |
4.4 | 6.9 | |
25 days ago | 18 days ago | |
Bikeshed | Bikeshed | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ua-client-hints
-
Website Fidelity
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.
- UA Gotta Be Kidding
- Példátlan leállás jöhet a neten, és nem is lesz egyszerű megoldani
-
Version 100 in Chrome and Firefox
I encourage you to review the decision making and engage in the discussion here: https://github.com/WICG/ua-client-hints
- W3C User Agent Client Hints
-
Google Chrome Update will cause Big Issue For 2 Billion Users
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/
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
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.
- W3C User-Agent Client Hints ( SEC-CH-UA-* HTTP Headers)
-
Mozilla tests if 'Firefox/100.0' user agent breaks websites
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/
-
Mozilla alters stance on User-Agent Client Hints from “non-harmful” to “harmful”
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
webappsec-permissions-policy
-
Smart Move, Google
Thanks for the docs. The examples (2 & 3, https://github.com/w3c/webappsec-permissions-policy/blob/mai...) seem to me to say that search.google.com can’t grant location permissions to an iframe if the parent was forbidden them, but I didn't find an explicit example for what happens if the iframe domain already got permission previously.
As you say the UI for requesting in this case would be weird, and this seems like a big security hole to me, but I can’t see a bit of the spec that explicitly forbids (though I only scanned the doc.)
-
Amazon is blocking Google’s FLoC
there is apparently no way to define a default disable either, so to turn off all the random features, the header becomes huge.
https://github.com/w3c/webappsec-permissions-policy/issues/1...
What is happening in w3c?!
-
Optimise your site - Addressing recommendations from securityheaders.com
This took a fair bit of investigation. I'm not convinced that it's the most well-documented header, in terms of the properties that you can set. Effectively, this is a list of values that determine which permissions are allowed for this website. Given I don't need access to location, camera, microphone or accelerometer. I did have issues finding consistent documentation on this one, so ended up having to combine the Feature-Policy documentation from MDN as well as the permissions policy examples from w3c.
-
User-Agent Client-Hints, take 2
Since Chrome v84 the Chrome team has had a few set backs which has resulted in some changes. In addition, the feature policy header, for delegating the client hints to third parties, has changed name to Permissions-Policy.
What are some alternatives?
web - Pi-hole Dashboard for stats and more
ichnaea - Mozilla Ichnaea
chromium-legacy - Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+
OsmAnd - OsmAnd
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
webappsec-feature-policy - A mechanism to selectively enable and disable browser features and APIs [Moved to: https://github.com/w3c/webappsec-permissions-policy]
evercookie - Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
ethical-ad-client - Ethical Ads JavaScript client
stylelint-no-unsupported-browser-fe
hosts-blocklists - Automatically updated, moderated and optimized lists for blocking ads, trackers, malware and other garbage
notrack-blocklists
webcompat-addon - Hotfixing the web, one Intervention at a time.