Live data from Hacker News

How LinkedIn betrayed a 5-man startup

thenextweb.com

21–30 of 65 posts

Re: How LinkedIn betrayed a 5-man startup

#21
Same goes for Facebook or any other big company. If your application depends on them heavily, then they can shut you down with the flip of a switch. If you're not making them money directly, they won't care either. I make the distinction between big and small companies here because if you depend on a small company, there's a lot more chance of opening a dialog and working out some kind of arrangement.

That said, to not hinge the entire outcome of your company on another company is, I feel, business 101. Doing so is a very high risk.

My feelings go out to the guys who started the company though...mistakes or not, it would truly suck to see all your hard work flushed down the toilet.

Re: How LinkedIn betrayed a 5-man startup

#22
post #12

If your product is completely dependent on a third-party API or service in order to function you really only have two possible exits: 1. Get bought out by the company implementing the API 2. Get shut out by the company implementing the API This should serve as a cautionary tale: never place the fate of your company in the hands of someone whose interests may not align with yours.

Excellent point.

Corollary: when the other company is figuring out how generous of an offer they need to make for choice #1, they know that your next best alternative is choice #2 (for $0).

Re: How LinkedIn betrayed a 5-man startup

#23
post #8
post #3

Earlier quoted context omitted.

What does "iterates" mean in context? "Pealk has been in contact with lawyers in the event that LinkedIn iterates its own version of the app" I can't tell if it's misused or I'm missing something.

In this context it can basically mean "improves". It comes from a recent trend in software development called Agile where new features are added in short cycles e.g. week called an iteration.

In that case, wouldn't it be "iterates on its own (…) app"?

Re: How LinkedIn betrayed a 5-man startup

#27
post #24

"pealk" is a stupid name. I'm not even interested in learning about your product if you named it something stupid. What is it with web start-ups and stupid names?

I don't think that's constructive to the discussion. While I agree the name is a bit strange in english maybe it's not in France where the startup is based?

Re: How LinkedIn betrayed a 5-man startup

#28
I just don't get all the hand wringing. You are not entitled to unlimited use of another company's data. They can shut you off at any time for any reason. And if you build your company around someone else's API, an essential part of the business plan is preparing for the day when the API-providing company takes notice of what you're doing and evaluates your use of their service, with the expectation that they may shut you down if you threaten them.

If your only response to this is "go cry to various small tech publications", then you're doing it wrong.

Re: How LinkedIn betrayed a 5-man startup

#29

Hi, author here, don't usually [ever] comment on my own work here - but am interested to hear if other devs have had similar or contrasting experiences working with LinkedIn.

In your post, you say "After news of the API cut off, LinkedIn got in touch to suggest a possible trip to its San Francisco HQ" - IIRC, LinkedIn's HQ is in Mountain View, not San Francisco.

[deleted]

Re: How LinkedIn betrayed a 5-man startup

#30

Hi, author here, don't usually [ever] comment on my own work here - but am interested to hear if other devs have had similar or contrasting experiences working with LinkedIn.

I have an issue with your wording.

"Getting free data via LinkedIn's API" != "Working with LinkedIn"

Post reply on HN