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?
To 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.
Did 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.
On your site you say you have "Google Analytics Integration" and you say it's seamless. I made a demo account but can't find the integration nor any documentation on it.
The back story is that we started as started as a B2B AMB product. We relied on another provider for data, then got hit with a bill one month that nearly bankrupted us. We ended up building our own system and pivoted to making this data more cost effective for others to access at scale.
Basically, there's still bits and pieces of old marketing material out there that needs to be removed and/or cleaned up.
9 comments
[ 3.8 ms ] story [ 33.7 ms ] threadBasically, we're addressing the community's feedback and providing general updates on the project. Open to any and all thoughts.
- https://techcrunch.com/2022/04/18/web-scraping-legal-court/ - https://en.m.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn - https://www2.staffingindustry.com/Editorial/IT-Staffing-Repo...
Legal has reviewed our approach in comparison, and we're good.
The back story is that we started as started as a B2B AMB product. We relied on another provider for data, then got hit with a bill one month that nearly bankrupted us. We ended up building our own system and pivoted to making this data more cost effective for others to access at scale.
Basically, there's still bits and pieces of old marketing material out there that needs to be removed and/or cleaned up.
It's one of the H2 headings just over halfway down the page.