Linkedin API is or is not for delevopers?

October 17, 2007

I must say that I’m really surprised… I own a blog about LinkedIn and particularly about the future of LinkedIn and how new features and new ideas for LinkedIn could not only benefit LinkedIn company but also and QUITE more important LinkedIn users.

I also must say that I’m kind of a developer and I’m waiting for LinkedIn API to launch some little online application that would make LinkedIn experience better.

Why am I writing then? Well, I write about the future of LinkedIn just for fun, not to make money. I’m building that “test” addin application just for fun and not for money, I’m doing that in my free time so hearing that LinkedIn will open only to approved company sounds really sad (even though they approve me in the future or not) but also very hard and painful.

I mean… I definitely won’t wait for an approval… I definitely won’t wait for they keeping some part of any of my possible revenue because it will my work. If I build a great application by using their API, they will also win, because people and more people, and more traffic, and more and more things can be done in their website, so if I win they win… BUT.. if I lose with my application that uses LinkedIn API, I lose money and time and they lose NOTHING. So, this is not fare at all…

Providing an open API for developers (as they announce some time ago) means really to be OPEN, and this is not being OPEN AT ALL. If that happen I will definitely try to move to Facebook, XING, Marzar or whatever other business social network that works in an open way.

Web World is looking forward to be open and I won’t be part of an “open to just some approved companies” website. I will definitely do my dev staff and blog staff and spend my free time in another thing… (I’m writing at same time I’m thinking) or do I have to be paid by LinkedIn because I’m giving them some ideas (even though they probably don’t read my blog :D) that they could transform to earn money from that. Or even they share their revenues with us (users): I mean.. they earn money not only because of linkedin website service but also because of us that enter, use and navigate the website and provide them with traffic, information and lot more…

Sorry for this “no positive at all” vision but as a free time LinkedIn add-in developer and blogger about LinkedIn I’m really not happy…


Linkedin strategy for upcoming "not so open" platform

October 13, 2007

I’m back at blogging after two weeks approximately with some “possible” not good news for developers and people that are waiting Linkedin’s API.

Why? Well.. Reading I found an interesting post about a New York times’ article about Linkedin strategy for the upcoming API.

I guess all can be resumed to the next phrase:

“We have no interest in doing it like Facebook with an open A.P.I. letting people do whatever they want,” Mr. Nye said.

Mr. Nye is the chief executive of Linkedin, so he has the power to the decide the future of linkedin.

“So LinkedIn will have to approve any company that wants to tap into its system. Mr. Nye says he is looking for two kinds of applications. First, there are deals that enable LinkedIn members to tap into their connections in other places, for example, while using applications like Second, some applications will be allowed to add features to LinkedIn’s own site. Mr. Nye offered, as an example, a module connected to a trade show or conference that integrated travel planning and other features.”

On June 24th they mentioned they will open to developers… and they are just openning to some companies not to developers at all…

What can I say?… I have no words…

As a resume.. It looks like they are building a “not so open” platform.

Facebook is extending APIs to compete with Linkedin

September 3, 2007

Some months ago Facebook publish APIs to become a great (or very great) and amazing social network where people not just only communicate their selves using Facebook functionality but also to extend it and use it the way they want.

On the weekend I saw one post at insidefacebook (here) talking about new APIs to stay on top and to start competing with the still “uncertain” linkedin API and also with the biggest Facebook Application: Slide.

The two new API methods are:

    * friends.getLists
    * friends.getListsMembers

    Those two methods let developers build Facebook Applications that get access and clasify people in many ways…

    Based on these method names, “Friend Lists” could be buddy lists that you might use to organize your friends. For example, “Work Friends” or, say… “Top Friends”.

    Why these methods are Linkedin related? Well, Justin Smith at his post at mentioned:

    This will be a welcome change for everyone whose LinkedIn networks have migrated to Facebook. Consequently, this could mean accelerated LinkedIn attrition: per-Friend-List privacy settings could substantially decrease the need of many to actively maintain their LinkedIn accounts as well.

    As a conclusion, Facebook is working really hard, not only in making its API more and more powerful each day, but also to stay on the top of social networks. And they are doing quite well!!!!

    Maybe, before Linkedin API is ready, we have some more Facebook API’s methods to have Linkedin functionality completely inside their website.

    Writing a blog post with Windows Live Writer Beta

    August 28, 2007

    Today I was looking for some information about a Microsoft Product I need for my work and I find something I didn’t know: Windows Live Writer Beta.

    I’ve just tested it and everything works ok. It looks really nice and it’s very comfortable because it provides to bloggers the chance to manage (write, edit and delete) blog posts into a win application.

    Live Writer Screenshot 1I still don’t find the way to test grammar check and things that Microsoft Office offers. Maybe it’s not available on this Windows Live product but in that case, users can add an add-on with that functionality. Anyway , it uses Blogspot, WordPress and Typepad API to get all the information on our blogs so we can feel just like if we were in the web interface.

    The best issues:

    • Web Preview option gives us an immediate preview of the post into the website.
    • User Interface
    • Manage multiple blogs
    • HTML Editor

    Live Writer Screenshot 2I think in this web world we are living now, this is a really interesting application that give us all the flexibility and facilities to blog on our own desktop. They also provide an API so developers can extend it (just like Facebook but in Windows Apps) and plugins (add-ons like Firefox) so each user can use Live Writer application just the way and with the things each want.

    Here is the Download link and some product information here and here.

    Hope you find this as interesting, useful and amazing as I did.

    By the way, this post have been written with Windows Live Writer 😉

    Linkedin is hiring a developer network manager for their API

    August 27, 2007

    I just saw on Mashable a three days old post titled: “LinkedIn Seeks Warrior to Fend off Facebook“. It looks like Linkedin is looking for a new Developer Network Manager…

    We are looking for a developer network manager who is part developer, part product manager, part marketer, part evangelist and, perhaps most importantly, can see how to take a nascent program and make it huge. This person can communicate the technology, encourage partner relationships, and set up communication vehicles that help make people successful at developing using LinkedIn APIs.

    • Work with product management and development to define and prioritize new APIs and supporting technologies.
    • Plan and execute the marketing and communications around the API program.
    • Establish a new developer program from the ground up, including all communication, partner, and developer support mechanisms

    The job posting is here so anyone in the San Francisco Bay Area (no relocation available) interested can apply…

    I would love to get that position but I’m in Argentina and also I guess they are looking for something with quite big experience for that position… so, I hope anyone here would be interested in that…

    MMLGF 3: Exporting information and generating alerts from LinkedIn Groups

    August 24, 2007

    Making websites with APIs and Feeds has its sense. When providing an API anyone could build great services over the website existing platform achieving benefits for themselves (offering new services for users on the existing website) and the existing website (promoting it). By providing Feeds, not only website’s information and data could be exported automatically by software components but also, and more important, could be read and used offline or at least, being disconnected from the source website.

    Feeds give websites the chance to export information and consume external services automatically. Feeds consumers (web applications like or and especially Feed Readers like Google Reader, or desktop feed readers like BlogBridge) let users a way to consume different website and applications information without going into websites but also, in some cases, exporting the information to see what they want or need.

    As I mentioned in a previous post applied to Question and Answer section, filtering and combination of feeds is also very useful when thinking about LinkedIn Groups (or this “LinkedIn Groups” idea I have in my mind). But, wouldn’t be better for users to have Feed Exportation of specific user’s queries they need or want inside Linkedin, instead of going offsite with feeds URL and make that “filter and combine” onto other website?

    Using Feeds from users’ queries and adding advanced search functionality to LinkedIn Groups would let find and export information like:

    • Questions from a whole Group
    • A particular thread (A Question and its answers)
    • A Threads list where some users had asked or answer (yourself, one of your connections or someone you just want to know what he is talking about).
    • Queries results I talked about on MMLGF #2 to get questions or threads:
      • Matching specific keyword search.
      • Asked/answered by your connections.
      • Popular threads.
      • Asked/answered today.
      • Asked/answered by some people you are interested in.
      • Tagged by you before.

    But, feeds are not everything… we can think about receiving alerts into email inbox, LinkedIn inbox or even directly to our mobile phone. That way, we can be offline but completely online all the time reading feeds into our feed readers from specific queries we want and receiving some alerts into many different ways…

    Definitely, with all this, LinkedIn Groups will be great!!!

    This is post #3 of the (M)aking the (M)ost of (L)inkedIn (G)roups (F)unctionality (MMLGF) Series.

    (M)aking the (M)ost of (L)inkedIn (G)roups (F)unctionality (MMLGF) Series…

    August 16, 2007

    As I mention last week I will start writing a series of blog posts I named: “Making the Most of LinkedIn Groups Functionality” or just MMLGF. I know MMLGF is difficult to say but I can’t find a best name 🙂

    I haven’t written too much of it but I’m open to hear from things you‘d like to improve or change at LinkedIn groups functionality. I mean, this guide is not at all a guide about bad things on LinkedIn groups now, but a guide about what it will be great to have and use on them.

    MMLGF 1: Features that LinkedIn Groups must have

    MMLGF 2: What we need to get and find on LinkedIn Groups

    MMLGF 3: Exporting information and generating alerts from LinkedIn Groups

    MMLGF 4: Showing your LinkedIn Groups activity at your public profile

    MMLGF 5: Accessing your LinkedIn Groups from your LinkedIn home page

    MMLGF 6: Making Connections with LinkedIn Groups members

    MMLGF 7: LinkedIn Groups activity included on Linkedin Search

    MMLGF 8: Exporting your LinkedIn groups activity (Blogging?)

    MMLGF 9: Linkedin Groups Privacy and Visibility

    MMLGF 10: LinkedIn Groups API

    I’ll be waiting your comments, ideas and thoughts about LinkedIn Groups and this MMLGF post series.