3 ms·
You haven’t addressed the chief, highest rated comment in the original thread: what about the fact this dataset was generated by scraping LinkedIn in violation
by adastra22 3y ago
You haven’t addressed the chief, highest rated comment in the original thread: what about the fact this dataset was generated by scraping LinkedIn in violation of that site’s ToS, and the generates a liability?
- mfrye0 3y agoTo be frank, we and others interpreted that entire thread as resolved and didn't need addressing. Scraping is clearly a grey area of the law. This is all public data. - https://techcrunch.com/2022/04/18/web-scraping-legal-court/ https://techcrunch.com/2022/04/18/web-scraping-legal-court/ - https://en.m.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn https://en.m.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn - https://www2.staffingindustry.com/Editorial/IT-Staffing-Report/Jan.-5-2023/LinkedIn-ends-legal-battle-in-data-scraping-case https://www2.staffingindustry.com/Editorial/IT-Staffing-Repo...
- adastra22 3y agoDid you read your own links? The HiQ labs decision in favor of scraping was vacated by the Supreme Court and then settled. Not a clear cut case law, but definitely ended on LinkedIn’s terms.
- mfrye0 3y agoYes. This was because HiQ was creating fake accounts to scrape member profiles, which was deemed to be in violation of the TOS. Legal has reviewed our approach in comparison, and we're good.