How LinkedIn exfiltrates extension data from the browser

Re:How LinkedIn exfiltrates extension data from the browser by luckylion on Tuesday June 18, 2019 @12:49PM (#20215092)

That's easy: LinkedIn should simply ask for permission. "Hey, you're about to submit a support request. Can we quickly check your browser for a few plugins that are known to cause trouble?"

"Is that plugin installed" is also a terrible "protection" against scraping.

[ Parent | on HN ]

Re:How LinkedIn exfiltrates extension data from the browser by codezero on Tuesday June 18, 2019 @12:49PM (#20215108)

Yeah, that's reasonable, I think it's much more likely to be an arms race w/ contact scraping extensions than a support issue.

[ Parent | on HN ]

Re:How LinkedIn exfiltrates extension data from the browser by luckylion on Tuesday June 18, 2019 @12:53PM (#20215152)

Probably, but tbh, it sounds like a bad way to combat scraping, much like blocking curl user agent strings.

Looking for access patterns that are typical for automated usage are a much better answer - and not publicly showing email addresses to everyone, of course.

[ Parent | on HN ]