4 ms·
I recently enabled privacy.resistFingerprinting in about:config (which basically is the configuration switch toggled by the UI described in this blog post). Ev
by muxator 8y ago
I recently enabled privacy.resistFingerprinting in about:config (which basically is the configuration switch toggled by the UI described in this blog post).
Everything went fine, until I noticed WhatsApp web becomes unusable, because it does not generate the initial QR code for establishing the session (to be fair, it flickers, which seems worse, as it smells of an active countermeasure on WhatsApp/Facebook part).
While I did I not have yet the time do dig deep into the specific technical reason WhatsApp may have to expose such a maddening behavior, I am inclined to think that this is more a policy choice.
If so, it's troublesome. We collectively as users arrived to the point of willingly give up the keys of our online communication to a few megacompanies. It's their infrastructure and their product, so they are in power of steering it in whatever direction it wants.
I see this as something that will increasingly become a political problem. As tech versed person, I see the responsibility for not doing enough about it.