You must log in or # to comment.
What if we use the extension (uBO) to block the scanning of extensions? /s.
Anyways, it’s for Chrome users:
The system responsible for this lives in some JavaScript code that LinkedIn runs in every Chrome visitors browser. The file is approximately 1.6 megabytes (it’s changed since browsergate’s analysis) of minified and partially obfuscated JavaScript.
That behaviour shouldn’t be possible in a browser that has its users interests in mind. The browser could limit the extentions websites could monitor for to a sensible amount. Or disable that feature at all. Or block fingerprinting by default by providing false data. But if you have the worlds biggest spy company building your browser, you will get a browser that spies

