<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technologist For Hire &#187; api</title>
	<atom:link href="http://www.nexdot.net/blog/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nexdot.net/blog</link>
	<description>An everyday attempt to stand out</description>
	<lastBuildDate>Tue, 09 Feb 2010 20:24:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1-alpha-15359</generator>
		<item>
		<title>Standards &amp; Data Portability</title>
		<link>http://www.nexdot.net/blog/2008/01/03/standards-data-portability/</link>
		<comments>http://www.nexdot.net/blog/2008/01/03/standards-data-portability/#comments</comments>
		<pubDate>Thu, 03 Jan 2008 15:04:19 +0000</pubDate>
		<dc:creator>Christian Flickinger</dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[DataPortability]]></category>
		<category><![CDATA[openmoko]]></category>
		<category><![CDATA[opensocial]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[w3c]]></category>

		<guid isPermaLink="false">http://www.nexdot.net/blog/2008/01/03/standards-data-portability/</guid>
		<description><![CDATA[Ah, my dreams will come true one day&#8230;. 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: OpenSocial (see my post here) DataPortability W3C Android &#038; the Open Handset Alliance OpenMoko Open APIs XML/RSS/Atom]]></description>
			<content:encoded><![CDATA[<p>Ah, my dreams will come true one day&#8230;. and <a href="http://dataportability.org/">http://dataportability.org/</a> is another step closer!</p>
<p>A few initiatives/groups/projects/technologies that I am in favor of, and everyone should check out, embrace, and eventually adopt:</p>
<ul>
<li><a href="http://code.google.com/apis/opensocial/">OpenSocial</a> (see my post <a href="http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/">here</a>)</li>
<li><a href="http://www.dataportability.org">DataPortability</a></li>
<li><a href="http://www.w3.org/">W3C</a></li>
<li><a href="http://code.google.com/android/">Android</a> &#038; the <a href="http://www.openhandsetalliance.com/">Open Handset Alliance</a></li>
<li><a href="http://www.openmoko.org">OpenMoko</a></li>
<li>Open APIs</li>
<li>XML/RSS/Atom</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.nexdot.net/blog/2008/01/03/standards-data-portability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s OpenSocial: Finally.</title>
		<link>http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/</link>
		<comments>http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/#comments</comments>
		<pubDate>Wed, 31 Oct 2007 02:41:46 +0000</pubDate>
		<dc:creator>Christian Flickinger</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[del_icio_us]]></category>
		<category><![CDATA[hi5]]></category>
		<category><![CDATA[highly_targeted_advertising]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[opensocial]]></category>
		<category><![CDATA[orkut]]></category>
		<category><![CDATA[plaxo]]></category>
		<category><![CDATA[social_bookmarking]]></category>
		<category><![CDATA[social_networking]]></category>
		<category><![CDATA[social_networks]]></category>
		<category><![CDATA[video_sharing]]></category>
		<category><![CDATA[youtube]]></category>

		<guid isPermaLink="false">http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/</guid>
		<description><![CDATA[Google is unstoppable. This Thursday, November 1, 2007, Google will launch OpenSocial (url goes live on Thursday); a set of API&#8217;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, [...]]]></description>
			<content:encoded><![CDATA[<p>Google is unstoppable. This Thursday, November 1, 2007, Google will launch <a href="http://code.google.com/apis/opensocial">OpenSocial</a> (url goes live on Thursday); a set of API&#8217;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.</p>
<p>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.</p>
<p>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.</p>
<p><span style="font-size:9px;">[Via <a href="http://www.techcrunch.com/2007/10/30/details-revealed-google-opensocial-to-be-common-apis-for-building-social-apps/">TechCrunch</a>]</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.nexdot.net/blog/2007/10/30/googles-opensocial-finally/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Told ya so&#8230; Facebook adds users.setStatus() API method</title>
		<link>http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/</link>
		<comments>http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/#comments</comments>
		<pubDate>Mon, 01 Oct 2007 11:03:56 +0000</pubDate>
		<dc:creator>Christian Flickinger</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[f8]]></category>
		<category><![CDATA[federated-status]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/</guid>
		<description><![CDATA[Welll, it appears that one month after Facebook asked me, and others, to remove my little cURL &#8216;hack&#8217; 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 [...]]]></description>
			<content:encoded><![CDATA[<p>Welll, it appears that one month after Facebook <a href="http://www.techcrunch.com/2007/09/06/facebook-opening-up-but-on-its-own-terms/">asked me</a>, and others, to remove <a href="http://www.nexdot.net/blog/2007/04/20/updating-facebook-status-using-php">my little cURL &#8216;hack&#8217;</a> for updating your Facebook Status, Facebook has finally implemented a <a href="http://wiki.developers.facebook.com/index.php/Users.setStatus">users.setStatus() method in their API</a>.</p>
<p>I originally posted my code and the ideas surrounding its creation and use on April 20, 2007. Five months later, Facebook decided to <a href="http://www.techcrunch.com/2007/09/06/facebook-opening-up-but-on-its-own-terms/">lay the hammer down</a>, 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.</p>
<p>Was this a move to open their platform more and to silence those who believe Facebook&#8217;s f8 is more of a &#8216;closed&#8217; 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.</p>
<p>And, as noted by <a href="http://www.muscetta.com/2007/10/01/facebook-implemented-a-usersetstatus-api/">Daniele Muscetta</a> (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 <a href="http://twittersweet.com/2007/9/30/integration-between-twitter-and-facebook-status/">TwitterSweet</a>.</p>
<p>So, good job Facebook&#8230; kind of. <img src='http://www.nexdot.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Updating Facebook status using PHP</title>
		<link>http://www.nexdot.net/blog/2007/04/20/updating-facebook-status-using-php/</link>
		<comments>http://www.nexdot.net/blog/2007/04/20/updating-facebook-status-using-php/#comments</comments>
		<pubDate>Fri, 20 Apr 2007 17:35:36 +0000</pubDate>
		<dc:creator>Christian Flickinger</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[idea]]></category>
		<category><![CDATA[mobile service]]></category>
		<category><![CDATA[status updates]]></category>
		<category><![CDATA[statuses]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.nexdot.net/blog/2007/04/20/updating-facebook-status-using-php/</guid>
		<description><![CDATA[I use Facebook as my 'social network of choice', and the means for updating friends of my status. The main reason is because most of my friends have no idea what Twitter is, nor would many of them use it. Everyone I know does have a Facebook account though, so it seems only natural that I use the medium which will give my updates the largest audience.

Although I do not use Twitter, I fully support it and love the idea of it.

Out of curiosity, I wanted to see if I could meld Facebook and Twitter. What I envisioned was a one-stop shop for updating my statuses across the internet.]]></description>
			<content:encoded><![CDATA[<blockquote style="border: 1px dotted #ccc; padding: 2px;"><p>
<strong>[<em>UPDATE</em>: October 01, 2007 @ 11:09am EST]</strong><br />
Facebook has <a href="http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/">officially implemented</a> a users.setStatus() method in their API. <a href="http://www.nexdot.net/blog/2007/10/01/told-ya-so-facebook-adds-userssetstatus-api-method/">Read more&#8230;</a></p>
<p><strong>[<em>UPDATE</em>: September 04, 2007 @ 7:21pm EST]</strong><br />
It is with great disappointment that I must make this announcement. Facebook has requested that I remove the code from my website. They have also contacted everyone else who has found my code and publicly mentioned that they are using it. I originally did not comply, but my Facebook account was disabled and legal action was about to be pursued.</p>
<p>I am saddened at this turn of events because the idea behind the code was to extend Facebook&#8217;s current service and fill in the gap that their API had. The API still does not provide a means for updating ones status.</p>
<p>To everyone who found my code useful, everyone who ported my code to various other languages, those who integrated my code into their projects, and those who believe in <a href="http://adrianspender.com/blog/2007/05/21/federated-status/" title="Drive Through...: Federated Status">Federated Status</a>, Thank You.</p>
<p>- Christian Flickinger
</p></blockquote>
<p>I use Facebook as my &#8216;social network of choice&#8217;, and the means for updating friends of my status. The main reason is because most of my friends have no idea what Twitter is, nor would many of them use it. Everyone I know does have a Facebook account though, so it seems only natural that I use the medium which will give my updates the largest audience.</p>
<p>Although I do not use Twitter, I fully support it and love the idea of it.</p>
<p>Out of curiosity, I wanted to see if I could meld Facebook and Twitter. What I envisioned was a one-stop shop for updating my statuses across the internet. To do this you would need something that can PUSH and ACCEPT updates. Twitter has an API that will ACCEPT updates, but nothing that will PUSH them. Facebook has an API that does not have any functions for status updates at all, but they do have status update RSS feeds. I want Twitter to be the top of my update tree. I want to update twitter (because of its SMS/Web/IM/API updating capabilities) and have everything else know about it. The API allows me to make a plugin for my IM client that could possibly throw my latest away message up on Twitter. SMS/Web/IM allow me to update twitter from wherever I am.</p>
<p>The problem with Facebook: You can only PULL status updates, and until now, you can not UPDATE them programaticaly. Searching google I quickly find <a href="http://www.designmeme.com/2007/03/22/twitterbook/" title="Twitterbook">a way to manually post my Facebook status to Twitter</a> and a post that <a href="http://www.srhaber.com/2007/04/02/twitter-and-facebook-status/" title="Shaun Haber: Twitter and Facebook Status" target="_blank">lays out the possibilities for facebook-twitter integration</a>.</p>
<p>Well, I do not give up that easy. I want a way to update Facebook without physically logging into Facebook. It can be done, and I found out how. Facebook has no status update API and their update box uses AJAX to post, so cURL is out of question&#8230; or so everyone thought! Facebook has a mobile service (<a href="http://m.facebook.com" title="Facebook Mobile" target="_blank">http://m.facebook.com</a>) that allows you to update your status and view your Facebook from a cellphone.  It looks the best on Windows Mobile devices (I have a Q), and works great on normal WAP browsers. This is the key to my facebook-twitter hack.</p>
<p>Facebook mobile uses a normal POST method for updating status. How cool is that? This means that it HAS to be possible to update your Facebook from a program. Using nothing but cURL (or, in my case, PHP with the cURL extension), you can update your Facebook status. What does this mean? This means that if someone wanted, they could easily keep their Facebook status synced up with their latest Twitter status. The code is below. Feel free to use it. Mentioning my blog/name would be greatly appreciated.</p>
<pre lang="php">
// Code removed at request of Facebook</pre>
<p>I have already created my first test mashup of Winamp &amp; Facebook, successfully displaying, in real time, the current song I was listening to in Winamp as my Facebook status. Anyone with some experience could easily use the above code to check Twitter and (if updated) push to Facebook. Happy mashing!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nexdot.net/blog/2007/04/20/updating-facebook-status-using-php/feed/</wfw:commentRss>
		<slash:comments>64</slash:comments>
		</item>
	</channel>
</rss>
