<?xml encoding="ISO-8859-1" version="1.0"?>
<!-- OPML generated by OPML Editor v10.1a8 on Mon, 03 May 2010 21:20:45 GMT -->
<opml version="2.0">
	<head>
		<title>scripting.com</title>
		<dateCreated>Mon, 03 May 2010 20:55:39 GMT</dateCreated>
		<dateModified>Mon, 03 May 2010 21:20:45 GMT</dateModified>
		<ownerName>Dave Winer (Larry King)</ownerName>
		<ownerId>http://www.scripting.com/</ownerId>
		<expansionState>1, 11</expansionState>
		<vertScrollState>1</vertScrollState>
		<windowTop>238</windowTop>
		<windowLeft>333</windowLeft>
		<windowBottom>756</windowBottom>
		<windowRight>1152</windowRight>
		</head>
	<body>
		<outline created="Mon, 03 May 2010 20:56:34 GMT" text="Response to Matt's important post about the Twitter API">
			<outline created="Mon, 03 May 2010 20:56:40 GMT" text="&lt;img src=&quot;http://images.scripting.com/archiveScriptingCom/2010/05/03/ninja.gif&quot; width=&quot;150&quot; height=&quot;224&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named ninja.gif&quot;&gt;Matt Mullenweg, the founder of Automattic and the lead dev on WordPress, has written an &lt;a href=&quot;http://ma.tt/2010/05/twitter-api/&quot;&gt;important post&lt;/a&gt; about the Twitter API. Lots of interesting observations and more than a little telegraphy here! Well-worth a careful read."></outline>
			<outline created="Mon, 03 May 2010 20:57:38 GMT" text="The conclusions:"></outline>
			<outline created="Mon, 03 May 2010 20:57:49 GMT" text="1. The Twitter API had a &lt;a href=&quot;http://www.scripting.com/stories/2009/12/17/howOpenStandardsAreCreated.html&quot;&gt;chance&lt;/a&gt; of becoming a defacto standard, but it didn't happen, for a variety of reasons."></outline>
			<outline created="Mon, 03 May 2010 20:58:08 GMT" text="2. It sounds like there's a WordPress client coming from Matt's company (unless there already is one that I'm not aware of) that works similarly to the Twitter clients."></outline>
			<outline created="Mon, 03 May 2010 20:59:00 GMT" text="3. It sounds more and more like Matt sees Twitter as competition. Or maybe this is wishful thinking on my part."></outline>
			<outline created="Mon, 03 May 2010 20:59:22 GMT" text="As a founder of this market, and someone who has the ear of most of the participants, I'd like to make a recommendation."></outline>
			<outline created="Mon, 03 May 2010 21:01:05 GMT" text="1. You have to support twitter.com, and this means working with whatever changes they make to the Twitter API. At this point they have the most users and the most influential users. Not supporting twitter.com, for most of the client developers, seems like it's not an option."></outline>
			<outline created="Mon, 03 May 2010 21:02:48 GMT" text="2. You should also support an open protocol, and by open I mean replaceable and simple. I explained that in &lt;a href=&quot;http://www.scripting.com/stories/2010/05/02/replaceable.html&quot;&gt;yesterday's post&lt;/a&gt; in response to Chris Saad's piece. There really only one way to go here, and that's a &lt;i&gt;good&lt;/i&gt; thing -- RSS 2.0 as the format, and its &amp;lt;cloud&gt; element to add the realtime component. It's decentralized, doesn't depend on any of the BigTechCo's, and isn't owned by anyone. It also isn't controlled by the W3C or IETF, which means it cannot be &lt;a href=&quot;http://www.google.com/search?q=define+corralled&quot;&gt;corralled&lt;/a&gt; by the BigTechCo's. It's easy to support, doesn't require a massive R&amp;D budget and is not a moving target, and &lt;i&gt;cannot become&lt;/i&gt; a moving target. "></outline>
			<outline created="Mon, 03 May 2010 21:05:25 GMT" text="You must have a route-around of the dominance of the big vendors if the smaller independent and open source projects are to have a chance in the market."></outline>
			</outline>
		</body>
	</opml>
