LinkedIn's Surveillance Scope: Are They Scanning Your OS or Just Peering into Your Browser Sandbox?
The core accusation is that LinkedIn engages in deep, invasive data collection, specifically alleging it scans for installed software and monitors the entire array of user Chrome extensions. This process triggers immediate concerns regarding data legality and opaque data sharing practices.
The debate splits on technical grounds. Commenter 'git' argues the scanning itself constitutes an illegal, non-consensual search of personal hardware. Counter-arguments claim the scope is limited; 'makotech222' suggests the scanning stays within the 'browser sandbox,' while 'BCsven' notes browsers already reveal basic extension metadata to the web.
The community consensus points to a profound lack of trust. While some users advocate for technical evasion—such as 'Crozekiel' recommending WebKit or Firefox derivatives—the weight of opinion confirms deep skepticism regarding any corporate platform accessing this level of user system detail.
Key Points
Scanning installed software without explicit permission is an illegal search.
Strongly argued by 'git,' asserting that platform necessity does not excuse illegal data grabs.
Alleged scanning is technically confined within the 'browser sandbox.'
This technical mitigation was offered by 'makotech222' to define the limits of data collection.
WebKit or Firefox derivatives can bypass Chrome-specific scanning.
Reported by 'Crozekiel' as a viable method to avoid specific invasive tracking mechanisms.
The risk of tracking is not limited to LinkedIn; it's the entire ecosystem.
A broader warning from 'git' that multiple fingerprinting systems are at play regardless of the scanner.
Using privacy browsers and VPNs on Linux offers a concrete defense layer.
Actionable advice provided by 'decaptcha' for minimizing data exposure.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.