Since this is being posted fucking everywhere with the same sensational headline that makes it look like linkedin is jumping out of the browser to scan your actual filesystems, here’s an exerpt from the site linked:

The Attack: How it works
Every time you open LinkedIn in a Chrome-based browser, LinkedIn’s JavaScript executes a silent scan of your installed browser extensions. The scan probes for thousands of specific extensions by ID, collects the results, encrypts them, and transmits them to LinkedIn’s servers. The entire process happens in the background. There is no consent dialog, no notification, no mention of it in LinkedIn’s privacy policy.

It’s enumerating the browser extensions you have installed.

Qubes as a daily can be pretty cumbersome with a steep learning curve, but once you get the hang of it it’s a very unique modular kind of experience, and a pretty good way to safely(ish) use one machine for many things - certainly much more so than any of the main linux distros. If you’re interested in security, worth checking out!

Linux hobbyist for 20+ years, pro for 6+. Fedora for workstations, proxmox for hypervisors, and rocky for servers is my usual personal recommendation. Beyond that, secureblue (a hardened downstream of fedora atomic) with heads firmware is a fantastic daily driver if you’re into that kind of thing.

Started with debian sarge way back in the day, currently using secureblue and qubes with fedora vms for most work, with a debian htpc on the side. For servers, I’m mostly debian-based on hardware (a bunch of proxmox machines at various sites and debian-based raspberry pis everywhere), with mostly redhat-based vms. Some alpine and freebsd baremetal and virtual machines sprinkled in here and there for flavor where they fit right.