41–50 of 64 posts
I 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_…
I 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?
I 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_…
google cache: http://webcache.googleusercontent.com/search?q=cache%3Ahttp%...
As a LinkedIn user, I'm actually relieved that they're considering my privacy. And with regards to the API behaving like the web page, there's a big difference to me between a machine scraping my data and a human looking at my profile (one might just be interested, the other is trying to use me for something).
Giving/finding you a job?
I 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.
They modified their API to be more sensitive to users' privacy concerns. There is nothing inherently wrong with a company respecting its users' privacy.
The complainant is understandably disappointed, but he is wrong in suggesting that an API is a contract that the host company can never change. Changing an API can be part of improving your product, and that seems to be the case here.
It seems these days that companies like LinkedIn, Twitter, Google, Facebook, etc, not only do not have any real forms of support, you can't even purchase a support contract if you wanted. Also, they don't have the professional courtesy to maintain their APIs to ensure backwards compatibility, unlike companies in the past.
I'm not sure why people would invest money and time into integrating with products that don't offer some level of formal support, as well as backwards compatibility. If you have no contracts and no stability with your underlying service provider, you are completely at their mercy. This means that any and all apps based on Facebook, Twitter, LinkedIn, etc are suspect, and anyone who does business with companies like Twitter and LinkedIn who are notorious for screwing over their developer community by changing things willy nilly, is basically stupid. The only development use case is if their goal is to create a popular app quickly, and then exit quickly. If they intend to create a product/company with a long-term vision, they are completely at the mercy of these companies.
This is the risk of building your business on somebody else's platform; there's always a degree of sharecropping involved, and in this realm, landowners are not bound to any law. I wonder how many "big" startups will offer APIs from now on. Many API-friendly services (delicious, twitter) have changed their stance, and Google didn't even want to release an API for G+. Many "new" APIs are basically useless, as companie…
The "tale" of many of the big startups you mentioned is that they still can't figure out how to effectively monetize their platforms. For instance, if you look at Twitter, they made a huge push to get the developer ecosystem to fill in holes Twitter itself couldn't cover; the end result being a growing community and revenue streams Twitter got nothing from. Seeing this, I think Twitter came to the belief they needed…
As a LinkedIn user, I'm actually relieved that they're considering my privacy. And with regards to the API behaving like the web page, there's a big difference to me between a machine scraping my data and a human looking at my profile (one might just be interested, the other is trying to use me for something).
> the other is trying to use me for something Giving/finding you a job?
I generally don't like things tied in to my social networks. This is not because I don't think they are useful, it is because I don't have long-term trust in the companies doing them.
It'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.
- LinkedIn collects a ton of user data, and had some idea to monetize it
- clever developer has a different idea about the same data, uses the API to achieve it
- users love developer's app, and they stay on LinkedIn because they love all the ecosystem apps
- maybe LinkedIn gets jealous and implements their own version. This is fine, if they don't break any laws, or cut off the original service for no real reason
Partnership sounds like some Facebook-Zygna type relationship. That seems like a really high barrier to entry. If you look at a service like Wolfram|Alpha, they're doing it right by putting reasonable restrictions on API use, and saying up front "license this commercially, contact us". This is a win-win: WA makes money, you're a real customer with bargaining power. Throwing a half-assed api out there for anyone to use, whinging about not making any money, then revoking bits piecemeal is not good for anyone.
1. Your writing seems to lose a certain quality online, maybe stick to prose? L'etranger was very good.