> most idea i have seen, like a tor browsing, is focusing on changing fingerprint and not so much on making fingerprint non-unique.
Not sure if I exactly understand what you're trying to say here, but the Tor
Browser itself certainly focuses on making its users' fingerprints identical.
At least it's the only browser I know of that passes fingerprint tests
(Panopticlick and friends) with JavaScript enabled.
I would guess that the amount of people who care about which keyboard layout
they use, don't use the local keyboard layout, and require appropriate labeling
of keys (i.e. don't touch type) at the same time isn't that high. I can imagine
how annoying it must be to be in that group, though.
I still wonder how that detection thing works. My custom Firefox setup with
requests proxied through Tor passes as the TBB, but copying the same request as
a curl command somehow doesn't.
Yeah after years of suffering from reCAPTCHA I'm somewhat thankful for
hCaptcha. It is still annoying (especially Cloudflare's integration which
seems barely compatible with the Tor Browser's cookie and circuit management),
but at least I don't have to switch exit nodes twenty times just to have a
chance of my solution being accepted (like with reCAPTCHA).
I normally use the Kanji draw [1] application which is also surprisingly good at
recognizing what I'm trying to input. Not nearly as forgiving as Google's
solution [2], which I sometimes have to fallback to, but usually it works if I
can at least roughly guess what the official way of drawing a character is and
check for inexact matches. Plus it's FOSS.
[2]: "Note that this will NOT work - at all - if you don't know basically how
to draw kanji. If you just draw something any old way that looks like it, it
certainly won't be recognised."
Well the Hungarian one feels like somebody took every single word in the essay
and replaced it with the first result from a rather small dictionary.
Google Translate produces a better translation (which is of course still
awful), but I have a feeling that the one in question was made by an earlier
version of Google Translate as well.
I don't really get the outrage, I've always been perfectly fine being addressed
by the government and other organizations without the diacritics in my name. In
fact I far prefer that to their placement being mixed up by human error (or a
wrong diacritical mark being used, etc).
And this is exactly why I enabled the global "Disable JavaScript" option in
uBlock Origin. The frustration these popups constantly cause far outweighs the
slight annoyance of having to re-enable JS for some websites (and you can ask
uBO to remember those anyways).
I believe that these conventions (at least for dates) are indeed the most
practical for their respective languages.
Take for example "October the third, two thousand nine" (10/3/2009, MDY). In German
one would pronounce this as "der dritte Oktober zweitausendneun" (3.10.2009, DMY).
In Hungarian "kétezer-kilenc október harmadika" (2009. 10. 03., YMD). All of these
pronunciations reflect the order numerical dates are written: using any other
convention would simply make them less natural to pronounce.
Now it is certainly not unheard of that the order of pronunciation also changes
(see the British "the third of October"), but changing language is a lot harder
in some cases impossible without breaking grammar than changing written
numerical representations.
Not sure if I exactly understand what you're trying to say here, but the Tor Browser itself certainly focuses on making its users' fingerprints identical. At least it's the only browser I know of that passes fingerprint tests (Panopticlick and friends) with JavaScript enabled.