Technologist For Hire » api http://www.nexdot.net/blog An everyday attempt to stand out Tue, 09 Feb 2010 20:24:03 +0000 en hourly 1 http://wordpress.org/?v=3.0.1-alpha-15359 Standards & Data Portability http://www.nexdot.net/blog/2008/01/03/standards-data-portability/ http://www.nexdot.net/blog/2008/01/03/standards-data-portability/#comments Thu, 03 Jan 2008 15:04:19 +0000 Christian Flickinger http://www.nexdot.net/blog/2008/01/03/standards-data-portability/ Ah, my dreams will come true one day…. and http://dataportability.org/ is another step closer!

A few initiatives/groups/projects/technologies that I am in favor of, and everyone should check out, embrace, and eventually adopt:

]]> http://www.nexdot.net/blog/2008/01/03/standards-data-portability/feed/ 0 Google’s OpenSocial: Finally. http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/ http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/#comments Wed, 31 Oct 2007 02:41:46 +0000 Christian Flickinger http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/ Google is unstoppable. This Thursday, November 1, 2007, Google will launch OpenSocial (url goes live on Thursday); a set of API’s that allow developers to interact with ANY social network that chooses to participate. What does this mean? It means that in order to access Orkut, LinkedIn, hi5, Plaxo, and other currently participating social networks, a developer only has to learn one API: The OpenSocial API. This reduces the cost and time associated with developing applications against a social network, and also opens the doors for new/existing social networks to give access to their data via the OpenSocial API.

The internet needs more standards and APIs. The things that differentiate the 200 different clones of an original idea, also clutter and confuse the internet. If the clones worked together, to form a network, everyone could choose their niche clone, and still enjoy content from the rest of the clone-network. For example: Youtube clones. If all Youtube clones worked together on a standard API, they could aggregate all of the videos, comments, and users together to form one large Video Sharing Network. Another example: del.icio.us clones. If all del.icio.us clones worked together on a standard API, they could aggregate all of the bookmarks, tags, comments, ratings, and users together to form on large Social Bookmarking Network. Google is giving the tools for one large Social Networking Network to exist.

Next, once there is an OpenAPI for each form of web2.0 product, we need a central OpenAPI that links all of those APIs together. Then we will have one global network, filled with tags, and users, and sharing, and stalking, and a lot of highly targeted advertising. Everyone will be happy, and the internet will implode.

[Via TechCrunch]

]]> http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/feed/ 3 Told ya so… Facebook adds users.setStatus() API method http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/ http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/#comments Mon, 01 Oct 2007 11:03:56 +0000 Christian Flickinger http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/ Welll, it appears that one month after Facebook asked me, and others, to remove my little cURL ‘hack’ for updating your Facebook Status, Facebook has finally implemented a users.setStatus() method in their API.

I originally posted my code and the ideas surrounding its creation and use on April 20, 2007. Five months later, Facebook decided to lay the hammer down, after many people had already implemented, ported, optimized, and whored my code. Now, one month after that, Facebook has an official API method for updating your own status.

Was this a move to open their platform more and to silence those who believe Facebook’s f8 is more of a ‘closed’ platform when compared to other service providers with APIs, a move to implement something that they obviously forgot about so they would look like less of a loser, or an honest move towards helping the federated status initiative? Either way, I am glad that the API method now exists.

And, as noted by Daniele Muscetta (a new friend of mine, and Facebook F8 Developer), it has already been picked up and implemented in a project that echoes that of my original vision of Twitter->Facebook over at TwitterSweet.

So, good job Facebook… kind of. :)

]]> http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/feed/ 4