3 ms·
I switched to 30d because with browser update cycles "all time" is kinda useless, imho. > Content language 31.51% en-US,en;q=0.5 This is a default Firefox. I
by wink 7y ago
I switched to 30d because with browser update cycles "all time" is kinda useless, imho.
> Content language 31.51% en-US,en;q=0.5
This is a default Firefox. I didn't change anything. Surely there's probably only Chinese that has more users of this language?
I'm not even an American or in the US... (all time it was just below 30%, not teal-colored, but already orange..)
Also why is the JS result for Content language 35.40%?
Whereas my list of plugins is 46.2% (higher value seems better) - but I'm absolutely sure there's at least one uncommon one among them...
Hardware concurrency 16 is really interesting, 3.32%, probably all fellow Ryzen users.
TLDR: Surely there are some of those properties where it absolutely makes sense to avoid the uniqueness, but others seem a bit like bullshit metrics.
But on the other hand, my user agent (OS+Browser) = 7.37% is a really good sign for me. I find this a very, very high percentage. (Ok, it's Win10+Firefox, but still...)
- 1_player 7y agoAgreed, some of those stats are questionable. A basic Microsoft Edge installation with en-GB content language header has a similarity ratio of 0.18% -- really? Java enabled: true -- 0.26% Java enabled: false (on Brave) -- 8.75%
- wolco 7y agoThey make sense. en-GB would start below 5%, having en-GB on edge means someone would have to be using edge (under 1%) and not on the mobile for a mobile first site. Keeping a current java version enabled is difficult. Each browser update, each java update disables java by default now. Could be a small Brave sample size.
- kelnos 7y agoI fired up Chrome (I'm a Firefox user too), and for content-language it showed "en-US,en;q=0.9" (FF is q=0.5), so I guess each language is broken down into a few buckets.