back
3 comments
> None of this is publicly available.

I received message on WhatsApp from someone claiming to be my LinkedIn contact, I asked how that person got my mobile number and was told my number is visible on my profile.

I didn't remember ever adding my number there, So I dug around to find that LinkedIn published my phone number to all my contacts when I uploaded it for 2FA (LinkedIn didn't have TOTP that time. You needed to have premium account to prevent it from being shown to contacts. I removed the 2FA until LinkedIn got TOTP.

LinkedIn IMO[1] has received far less scrutiny on its practices and content when compared with other social networks while having disproportionately large influence on professional life.

[1] https://news.ycombinator.com/item?id=27673024

Inferred salary is from salary estimates based on job titles. It isn’t tied to your personal data IIRC.

It’s likely that an API endpoint was found and all the data was siphoned off.

The same API that was used in the April breach.

https://restoreprivacy.com/linkedin-data-leak-700-million-us...

Even if you don't considered inferred salary directly tied to you as "personal data," surely you consider geo location personal data?

Also, aren't you even slightly outraged that you can't even download data that has been hacked and released into the wild?

Or outraged by the fact that you can only download data you have given directly to a service provider, but that the service provider will happily tell 3rd parties about your shadow profiles?

The geolocation in the response looks like the location you set in your LinkedIn profile.

Is there anything that shows that it’s your actual geo location when you access LinkedIn?

> Inferred salary is from salary estimates based on job titles. It isn’t tied to your personal data IIRC.

How do you know?

https://www.linkedin.com/help/linkedin/answer/4786/source-an...

>When we don’t have member-submitted data, salary insights are inferred using data between similar companies, job titles, location, and other job attributes.

With enough "job attributes", you can easily tie things down to an individual: who worked as <position> at <company> in <city> from <start_date> to <end_date>, doing <job_description> with <colleagues>?

Because you get salary insights when you look at job postings which means it’s an API endpoint.
Inferred salary would be useful for recruiters, perhaps they used recruiter accounts to scrape it?