3 ms·
The big problem with the LinkedIn API is that the ToS are pretty harrowing. Who knows what they'll do to you if you succeed in using their (extremely valuable)
by aditya 16y ago
The big problem with the LinkedIn API is that the ToS are pretty harrowing.
Who knows what they'll do to you if you succeed in using their (extremely valuable) data set: http://www.readwriteweb.com/archives/linkedin_platform_pros_and_cons.php http://www.readwriteweb.com/archives/linkedin_platform_pros_...
- shyamster 16y agoThanks for the link...just read the terms and it does not look encouraging.
- yesimahuman 16y agoRight, and you have to be logged in through OAuth to get anything out of the API (As far as I can tell, please prove me wrong though), which really diminishes the value you can get out of the platform as a third party.
- bjonathan 16y agoHi, can you explain your PoV ? How OAuth diminishes the value ?
- yesimahuman 16y agoOAuth requires a user to be logged in, which is fine if that is the type of service you are running. If you want to search LinkedIn like you might twitter, you are out of luck if you want to do it through the API. And even if you do have a service that OAuth fits, the TOS is scary enough to avoid it.
- d78g 16y agoIndeed. We had four ideas for apps. None are compatible with their ToS. Calling it an open API is a bit unfair. It is only open from a technological perspective, not from a legal perspective. Plus, they have all sorts of bans on scraping, etc. They say users own their own data, but if their users use any tools to try to get their data, they block the tools.... It's too bad, because there are a lot of great things that could be built.