<?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>Coffee on the Keyboard &#187; api</title>
	<atom:link href="http://coffeeonthekeyboard.com/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeeonthekeyboard.com</link>
	<description>by James Socol</description>
	<lastBuildDate>Mon, 30 Jan 2012 17:56:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/>		<item>
		<title>The Thing About Twitter</title>
		<link>http://coffeeonthekeyboard.com/the-thing-about-twitter-585/</link>
		<comments>http://coffeeonthekeyboard.com/the-thing-about-twitter-585/#comments</comments>
		<pubDate>Mon, 14 Mar 2011 00:29:11 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://coffeeonthekeyboard.com/?p=585</guid>
		<description><![CDATA[The thing that bothers me most about Twitter&#8217;s API announcement is that very few of the most useful features of Twitter were actually their ideas. Hashtags. Retweets. Location. Search. Lists. Conversation view. Inline images and links. Short URLs. The entire mobile user experience. All of these appeared in user behavior or other clients or other [...]]]></description>
			<content:encoded><![CDATA[<p>The thing that bothers me most about <a href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c82cd59c7a87216a?pli=1">Twitter&#8217;s API announcement</a> is that very few of the most useful features of Twitter were actually their ideas.</p>
<ul>
<li>Hashtags.</li>
<li>Retweets.</li>
<li>Location.</li>
<li>Search.</li>
<li>Lists.</li>
<li>Conversation view.</li>
<li>Inline images and links.</li>
<li>Short URLs.</li>
<li>The <em>entire mobile user experience</em>.</li>
</ul>
<p>All of these appeared in user behavior or other clients or other apps first, and Twitter picked them up into their clients, or bought the client outright.</p>
<p>I&#8217;m <em>for</em> picking up features from clients. I think it&#8217;s fantastic: a feature can be effectively tested among a small group via a niche client and if it&#8217;s compelling and popular, well, you may want to steal it for the whole userbase—or not, of course.</p>
<p>The comparison that sprang to mind was the <a href="https://addons.mozilla.org/firefox/">Firefox add-ons ecosystem</a>. Something can start as an add-on (say, <a href="http://www.azarask.in/blog/post/tabcandy/">Tab Candy</a> or <a href="https://addons.mozilla.org/firefox/addon/personas-plus/">Personas</a>) and if it&#8217;s popular and a compelling feature, sometimes it gets picked up into the product (<a href="http://support.mozilla.com/en-US/kb/what-are-tab-groups">Panorama</a>, <a href="http://www.getpersonas.com/">Personas</a>). Other times (<a href="http://getfirebug.com/">Firebug</a>, <a href="https://addons.mozilla.org/firefox/addon/adblock-plus/">Adblock Plus</a>) it is incredibly compelling but not for everyone, and it doesn&#8217;t. (Or, in the case of Firebug, some of the ideas, if not the implementation, were <a href="https://developer.mozilla.org/en/Using_the_Web_Console">picked up</a>.)</p>
<p>The point of all that, to borrow a phrase from <a href="http://twitter.com/JeffChausse">Jeff Chausse</a>, is that thinking you will &#8220;inevitably make better apps [is] <a href="http://twitter.com/JeffChausse/status/47088363081179136">epic hubris</a>.&#8221;</p>
<p>If 90% of user access to Twitter is through official clients, like they claim, then they are overstating the threat of &#8220;fragmentation&#8221; of the user experience, and doing so in a way which discourages anyone else from trying to do better, or simply different. (Unless, of course, they aren&#8217;t putting any technical teeth behind it, but in that case why say anything at all?)</p>
<p>Considering how much of the current Twitter experience was invented outside the company, it seems like this is indeed epic hubris.</p>
<p><em>NB: As all content on this blog, this post is my personal opinion and should in no way be construed as representing my employer.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://coffeeonthekeyboard.com/the-thing-about-twitter-585/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Widget l10n</title>
		<link>http://coffeeonthekeyboard.com/widget-l10n-230/</link>
		<comments>http://coffeeonthekeyboard.com/widget-l10n-230/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 04:36:43 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[Code]]></category>
		<category><![CDATA[i18n]]></category>
		<category><![CDATA[l10n]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://coffeeonthekeyboard.com/?p=230</guid>
		<description><![CDATA[I spent some of today working on bringing a couple of WordPress widgets up-to-date (Better Search and Most Comments) only to discover there is a new widget API. I guess I haven&#8217;t been paying attention. I&#8217;ll probably start some 2.0 branches tomorrow to take advantage of the new API. I wish I didn&#8217;t know how [...]]]></description>
			<content:encoded><![CDATA[<p>I spent some of today working on bringing a couple of WordPress widgets up-to-date (<a href="http://jamessocol.com/projects/better-search-widget.php">Better Search</a> and <a href="http://jamessocol.com/projects/most-comments-widget.php">Most Comments</a>) only to discover there is a <a href="http://codex.wordpress.org/Widgets_API#Developing_Widgets_on_2.8.2B">new widget API</a>. I guess I haven&#8217;t been paying attention.</p>
<p>I&#8217;ll probably start some 2.0 branches tomorrow to take advantage of the new API. I wish I didn&#8217;t know how many people don&#8217;t keep their WordPress installations up to date, so I wouldn&#8217;t care about backwards compatibility.</p>
<p>At least both widgets got nice new, and functional, internationalization (i18n) code and new localization (l10n) files.</p>
<p>And BSW got a good feature update, incorporating some suggestions from <a href="http://mjml.de/">Marco Jung</a>, who is also, kindly, doing a German localization, and a few of my own. The built-in search widget has stepped up it&#8217;s game, and fixed the thing BSW was originally designed to fix (no widget title) so I have a higher bar to clear to justify the name &#8220;<em>Better</em> Search Widget.&#8221;</p>
<p>I&#8217;ll write up the new features tomorrow.</p>
]]></content:encoded>
			<wfw:commentRss>http://coffeeonthekeyboard.com/widget-l10n-230/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

