[deleted]
Betrayed by LinkedIn
21–30 of 64 posts
Re: Betrayed by LinkedIn
#22I get this drupal error. -- PDOException: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction: DELETE FROM {semaphore} WHERE (name = :db_condition_placeholder_0) AND (value = :db_condition_placeholder_1) AND (expire variable_init [:db_condition_placeholder_1] => 112720946350f00b3f105ad8.99608950 [:db_condition_placeholder_2] => 1357908800.0644 ) in lock_may_…
Clearly they don't understand how to configure drupal.
Re: Betrayed by LinkedIn
#23It's sort of ridiculous how little information you can get from LinkedIn via their API. Case in point, I don't think you can get Twitter handles from even first-tier connections any more. I made the appropriate API calls, waved my hands, and all I got were empty values. The docs do clearly state that you should be able to download every Twitter handle associated with an account, so WTH? It looks like they've revoked…
well contact the company and ask for a partnership,you cant get stuffs for free forever.
Re: Betrayed by LinkedIn
#24I get this drupal error. -- PDOException: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction: DELETE FROM {semaphore} WHERE (name = :db_condition_placeholder_0) AND (value = :db_condition_placeholder_1) AND (expire variable_init [:db_condition_placeholder_1] => 112720946350f00b3f105ad8.99608950 [:db_condition_placeholder_2] => 1357908800.0644 ) in lock_may_…
Re: Betrayed by LinkedIn
#25Linkedin is behaving perfectly reasonably, it makes sense that for privacy reasons you want to restrict access to the work history of connections. Imagine someone you're connected to using linkedin on a recruiter's website giving them access their linkedin account. That recruiter now has full access to your work history, do you consider that acceptable ?
I would agree with you, but given that many LinkedIn profiles are public and discoverable when doing Google searches, with the work history included, I don't think this is an issue privacy, as those people wanted for their profile to be public. Anyway, a simple crawler would do the trick for public profiles.
The thread isn't talking about public profiles, rather profiles that your user account is privileged to access.
(Linkedin don't let you access public profiles via the API; but that's a separate issue)
Re: Betrayed by LinkedIn
#26Earlier quoted context omitted.
If you rely on a 3rd party for your business, then the 3rd party is in control of your company future. In that regard, its not about risk. Yes, using 3rd party API for your business model is risky, but thats a secondary effect. The major issue is than the future of the company, and any promises and investments done is completely dependent on that third-partys' whims. To some degree, your even in less control than if…
I just started reading "the signal and the noise" [0], and he talks about the difference between "risk" and "uncertainty": "Risk" is a known factor, something you can calculate with. Something might be risky (50% chance of failure) but at least you can calculate and reason about it. "Uncertainty" is "worse" because you can't easily reason about it. We often assign numbers to uncertain events anyway, but they might be…
Found a blog-post with that quote in its context:
http://unreasonable.is/opinion/entrepreneurs-are-scientists/ https://news.ycombinator.com/item?id=5042525
Re: Betrayed by LinkedIn
#27Earlier quoted context omitted.
Why do you think this? It's certainly riskier but there have been many successful companies that start out relying heavily on a 3rd party APIs.
If you have a business model that's based on a one sided relationship, then the chances of it going sour is significantly higher. Plenty of companies start out relying on 3rd party APIs and most of the time it's a happy relationship, but see what happened when the 3rd party needs monetise like Twitter did.
The scary thing is that most sites have such vital relationships, e.g. with TLD registries. Can you actually rely on nic.ly or nic.in keeping your domain safe forever?
Re: Betrayed by LinkedIn
#28I get this drupal error. -- PDOException: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction: DELETE FROM {semaphore} WHERE (name = :db_condition_placeholder_0) AND (value = :db_condition_placeholder_1) AND (expire variable_init [:db_condition_placeholder_1] => 112720946350f00b3f105ad8.99608950 [:db_condition_placeholder_2] => 1357908800.0644 ) in lock_may_…
Why would the code to view a discussion thread be so cumbersome in the first place?
Re: Betrayed by LinkedIn
#29Earlier quoted context omitted.
If you have a business model that's based on a one sided relationship, then the chances of it going sour is significantly higher. Plenty of companies start out relying on 3rd party APIs and most of the time it's a happy relationship, but see what happened when the 3rd party needs monetise like Twitter did.
The scary thing is that most sites have such vital relationships, e.g. with TLD registries. Can you actually rely on nic.ly or nic.in keeping your domain safe forever?
It's not so much one way with the TLD registers though, there's a formal business relationship where a price is agreed for a level of service (usually). Granted, a lot of the power remains in their court, but there's a two way relationship going on. The problem with the 3rd party API is for the most part it's all free, thus leading to the power remaining solely with the provider.
It's amazing how much businesses often depend on single sources for services, TLD's is a great example.
Re: Betrayed by LinkedIn
#30Yet another flawed business model based entirely upon the goodwill and co-operation of a bigger fish in the pond. Don't they know that bigger fish can swim away any time they want? Oh, and they might just turn around and swallow you. To further mix my metaphors - we have had "Cathedrals" and "bazaars" and now we have shacks leant against the city walls.
Of course, the "swallow you" option is what lots of these types of start ups both expect, and want.
"Hey we built this feature on your site, it's really cool. So, erm, want to buy us?"