Yeah, the source I used is browsergate.eu. I do a lot of developing in the dev tools (browser fingerprinting protection tool on the same site) and so I was looking at the dev tools for linked in and saw the extension enumeration a few weeks ago. I didn't realize that's what was going on, but there was a repository from a few years ago that started tracking this. There's a HN link somewhere... nefariouslinkedin I think it was called.

Then, I saw the browsergate story drop on mastodon and thought "no way," lo-and-behold, there's a lawsuit in the works for it.

I found the audit to be a bit dense and hard to read, this is a response to that. I

I did do my own independent audit, though. Sorry, I just checked back today and was not expecting this to get the traction it did.

That's what I mean, this article has its own audit, it's not a dupe of the other