<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.kai-mai.com">
<channel>
 <title>Kai Mai&#039;s Blog - Take Back the Web - Nodes for api</title>
 <link>http://www.kai-mai.com/tags/api</link>
 <description>Nodes containing the tag api</description>
 <language>en</language>
<item>
 <title>To Twitter:  Stop Replying on Developers Building Features using Your API.  Take Control of Your Own Destiny</title>
 <link>http://www.kai-mai.com/node/186</link>
 <description>&lt;p&gt;
Twitter is famous for its openness on its API and have a lot of tools built by 3rd party developers. But many 3rd-party tools are built/abused to add automated spammy tweets, robots to Twitter.
&lt;/p&gt;
&lt;p&gt;
Last month, Twitter engineer Alex Payne tweeted “If you had some of the nifty site features that we Twitter employees have, you might not want to use a desktop client. (You will soon.)&amp;quot;
&lt;/p&gt;
&lt;p&gt;
I&#039;d love to see the niffy site features!  Twitter&#039;s web UI is just way too simple.  Example: Where can I follow conversations(aka: thread of retweets, replies) on a tweet?
&lt;/p&gt;
&lt;p&gt;
Twitter should surely use its $160 million funding to beautify its web presentation and blow away all the 3rd-party clients(whoever builds its entire business model on features that are core to Twitter should have seen this day coming).
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/84&quot;&gt;api&lt;/a&gt; &lt;a href=&quot;tags/124&quot;&gt;twitter&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">api</category>
 <category domain="http://www.technorati.com/tag">twitter</category>
 <pubDate>Tue, 23 Mar 2010 22:23:23 -0700</pubDate>
</item>
<item>
 <title>The Next Battle Field between Yahoo &amp; Google &amp; Microsoft: Email 2.0</title>
 <link>http://www.kai-mai.com/node/167</link>
 <description>&lt;p&gt;
Yahoo has already been working on &lt;a href=&quot;http://developer.yahoo.com/mail/&quot;&gt;Yahoo Mail Platform&lt;/a&gt; to allow 3rd-party developers to write &lt;a href=&quot;http://gallery.yahoo.com/mail#&quot;&gt;applications&lt;/a&gt; enhance Yahoo Mail experience. 
&lt;/p&gt;
&lt;p&gt;
&lt;a href=&quot;http://www.xobni.com/&quot;&gt;Xobni&lt;/a&gt; has been enhancing the Outlook experience.  I don&#039;t know what&#039;s the reason of MS not buying Xobni.  But Xobni has everything that Outlook and email services ought to have.
&lt;/p&gt;
&lt;p&gt;
Today, Google rolled out new Gmail Lab features to allow &lt;a href=&quot;http://mashable.com/2009/03/18/gmail-youtube-previews/&quot;&gt;preview of youtube, flickr, picasa, Yelp contents&lt;/a&gt; whenever they detect relevant links in your emails.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/70&quot;&gt;application&lt;/a&gt; &lt;a href=&quot;tags/84&quot;&gt;api&lt;/a&gt; &lt;a href=&quot;tags/177&quot;&gt;platform&lt;/a&gt; &lt;a href=&quot;tags/295&quot;&gt;email&lt;/a&gt; &lt;a href=&quot;tags/299&quot;&gt;gmail&lt;/a&gt; &lt;a href=&quot;tags/346&quot;&gt;yahoo_mail&lt;/a&gt; &lt;a href=&quot;tags/347&quot;&gt;xobni&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">application</category>
 <category domain="http://www.technorati.com/tag">api</category>
 <category domain="http://www.technorati.com/tag">platform</category>
 <category domain="http://www.technorati.com/tag">email</category>
 <category domain="http://www.technorati.com/tag">gmail</category>
 <category domain="http://www.technorati.com/tag">yahoo_mail</category>
 <category domain="http://www.technorati.com/tag">xobni</category>
 <pubDate>Wed, 18 Mar 2009 23:14:24 -0700</pubDate>
</item>
<item>
 <title>Yahoo! Search BOSS API FAQs</title>
 <link>http://www.kai-mai.com/node/149</link>
 <description>&lt;p&gt;
I am a big fan of &lt;a href=&quot;http://developer.yahoo.com/search/boss/&quot;&gt;Yahoo! Search BOSS API&lt;/a&gt; as it empowers users to leverage Yahoo&#039;s search&#039;s crawler and indexes to develop applications without spending a huge amount of money on infrastructure/bandwidth!  Google, do you know what I mean?
&lt;/p&gt;
&lt;p&gt;
As an observer on &lt;a href=&quot;http://tech.groups.yahoo.com/group/ysearchboss/&quot;&gt;the active Yahoo! Search BOSS API mailing list&lt;/a&gt;,  I document the Yahoo BOSS API&#039;s limitations which I over-hear on the mailing list: 
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; API fees and Monetization
&lt;ul&gt;
&lt;li&gt; Yahoo is going to &lt;a href=&quot;http://developer.yahoo.com/search/boss/fees.html&quot;&gt;charge fees on API usages beyond a certain limit&lt;/a&gt;.
&lt;/ul&gt;
&lt;/ul&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/84&quot;&gt;api&lt;/a&gt; &lt;a href=&quot;tags/152&quot;&gt;search&lt;/a&gt; &lt;a href=&quot;tags/281&quot;&gt;yahoo_boss_api&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">api</category>
 <category domain="http://www.technorati.com/tag">search</category>
 <category domain="http://www.technorati.com/tag">yahoo_boss_api</category>
 <pubDate>Fri, 12 Dec 2008 23:35:19 -0800</pubDate>
</item>
<item>
 <title>The Importance of Web 2.0: Public API for Ad-Hoc Application Integration</title>
 <link>http://www.kai-mai.com/node/64</link>
 <description>&lt;p&gt;
There have been lots of articles/blogs written on &lt;a href=&quot;http://en.wikipedia.org/wiki/Web_2&quot;&gt;Web 2.0&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Here is my take on it:
Web 2.0 comes with richer, more responsive user experience.  But behind the theme, it really drives the &lt;a href=&quot;http://en.wikipedia.org/wiki/Semantic_Web&quot;&gt;semantic web&lt;/a&gt; adoption although people may not have realized that.  When you have a web application that updates part of its view (a web page) instead of reloading the whole page or directing to a brand new page, the web application mostly gets the DATA(not the view) from a server and updates the view with the new data.  A crucial feature of any web 2.0 application is that it opens a API for getting the application data.  Like it or not, the API is public because it&#039;s exposed through HTTP regardless whether developers behind it indent to have it as a pubic API.  People can easily use some tools to analyze HTTP requests to reverse-engineering the API.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/82&quot;&gt;web2.0&lt;/a&gt; &lt;a href=&quot;tags/83&quot;&gt;semanticweb&lt;/a&gt; &lt;a href=&quot;tags/84&quot;&gt;api&lt;/a&gt; &lt;a href=&quot;tags/85&quot;&gt;mashup&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">web2.0</category>
 <category domain="http://www.technorati.com/tag">semanticweb</category>
 <category domain="http://www.technorati.com/tag">api</category>
 <category domain="http://www.technorati.com/tag">mashup</category>
 <pubDate>Wed, 12 Apr 2006 21:41:12 -0700</pubDate>
</item>
</channel>
</rss>

