RE: https://infosec.exchange/@beyondmachines1/116340430386264988

The story here focuses on LinkedIn, who should definitely be held accountable for what they’re doing with our data, but the real question is “Why does Chromium allow this?”

If Chromium allows this, then anyone—not just LinkedIn—can do this.

Most certainly, Google already knows all of this if you use Chromium. Meta probably does this. I’m sure others do, too.

elle (@[email protected])

since that browsergate site about LinkedIn seems to be gaining traction I figure I should mention: - yes, LinkedIn does do what's being claimed (though, it's that it probes for *specific* extensions you're running, using features in chrome's API - it doesn't "search your computer") - it does seem to have been doing this since at least as far back as [2017](https://github.com/dandrews/nefarious-linkedin), and there has been intermittent reporting on it over the years - I'm fairly confident the copy on the site was generated by (or at least went through) an LLM, so idk that this site is the best way to spread the issue around edit: and as [someone else noted in the replies](https://not-brain.d.on-t.work/notes/akl6hp4gjqcp8d7h), looking through the list of extensions of scans for... they're [pretty much all "AI"/scraper/automation plugins](https://browsergate.eu/extensions/). so, should LinkedIn be doing this, or even *able* to do this in Chrome? no! but also, it does seem like the stuff they're scanning for is all extensions that shouldn't exist to begin with tbh edit 2: please see [this follow-up post](https://social.treehouse.systems/@vantiss/116342005257886265) which proves this is just a shitty campaign by people who made an addon called "Teamfluence" that got blocked by LinkedIn

Treehouse Mastodon
@webaware That’s sort of my point—and also that Chrome shouldn’t allow websites you visit the ability to see what extensions you have installed.