Skimming the list, looks like most extensions are for scraping or automating LinkedIn usage. Not surprising as there's money to be made with LinkedIn data. Scraping was a problem when I worked there, the abuse teams built some reasonably sophisticated detection & prevention, and it was a constant battle.
In order to create the data source that LinkedIn's extension-fingerprinting relies on to work, someone (at LinkedIn*?) almost certainly violated the Chrome Web Store TOS—by (perversely*) scraping it. * if LinkedIn didn't get it from an existing data source
LinkedIn checks for 2953 browser extensions
161–170 of 263 posts
Re: LinkedIn checks for 2953 browser extensions
#162Earlier quoted context omitted.
The webpage would have to scan the entire UUID space to create this fingerprint, which seems unlikely.
Just have a database of UUIDs. Seems pretty trivial to generate and sort as it's only 16 bytes each.
Re: LinkedIn checks for 2953 browser extensions
#163Earlier quoted context omitted.
Just have a database of UUIDs. Seems pretty trivial to generate and sort as it's only 16 bytes each.
"Just" have a database, and then what? I can set up a database of all UUIDs very easily, but I don't think it's helpful.
Re: LinkedIn checks for 2953 browser extensions
#164Skimming the list, looks like most extensions are for scraping or automating LinkedIn usage. Not surprising as there's money to be made with LinkedIn data. Scraping was a problem when I worked there, the abuse teams built some reasonably sophisticated detection & prevention, and it was a constant battle.
In order to create the data source that LinkedIn's extension-fingerprinting relies on to work, someone (at LinkedIn*?) almost certainly violated the Chrome Web Store TOS—by (perversely*) scraping it. * if LinkedIn didn't get it from an existing data source
Re: LinkedIn checks for 2953 browser extensions
#165Earlier quoted context omitted.
Wont someone think of poor little LinkedIn, a subsidiary of one of the largest data brokers in the world?
Why frame what you are trying to say like that? Businesses of all sizes deserve the ability to protect their businesses from abuse.
Re: LinkedIn checks for 2953 browser extensions
#166Earlier quoted context omitted.
Do they respect my data? Why do they get to track me across sites when I clearly don't want them to but someone can't scrape their data when they don't want them to. Why should big companies get the pass but individuals not? They clearly consider internet traffic fair game and are invasive and abusive about it so it is not only fair to be invasive and abusive back, it is self defense at this point.
Because you signed up to a set of terms and conditions saying LinkedIn can use your data in this way
Re: LinkedIn checks for 2953 browser extensions
#167Re: LinkedIn checks for 2953 browser extensions
#168Re: LinkedIn checks for 2953 browser extensions
#169Does anyone know if Brave has any defense against this like Firefox does?
It doesn't seem like Brave's fingerprinting prevention includes extensions, so on my first pass I would say no.
Re: LinkedIn checks for 2953 browser extensions
#170I wrote a blog post recently about the technique used by LinkedIn to do extension probing, as well as other ways to do it with less side effects https://blog.castle.io/detecting-browser-extensions-for-bot-...