<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Raising the Dial Tone</title>
	<atom:link href="http://jbordeaux.com/raising-the-dial-tone/feed/" rel="self" type="application/rss+xml" />
	<link>http://jbordeaux.com/raising-the-dial-tone/</link>
	<description>with John Bordeaux</description>
	<lastBuildDate>Fri, 04 May 2012 22:52:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=9295</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: More Friday Link Love with Strawberries</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-117592</link>
		<dc:creator>More Friday Link Love with Strawberries</dc:creator>
		<pubDate>Wed, 14 Mar 2012 19:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-117592</guid>
		<description>[...] John Bordeaux continues to wow me with his writing and &#8216;Raising the Dial Tone&#8216; definitely fits the bill. Yes, you&#8217;ve read blog posts talking about social media [...]</description>
		<content:encoded><![CDATA[<p>[...] John Bordeaux continues to wow me with his writing and &#8216;Raising the Dial Tone&#8216; definitely fits the bill. Yes, you&#8217;ve read blog posts talking about social media [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Card</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-3006</link>
		<dc:creator>Twitter Card</dc:creator>
		<pubDate>Fri, 12 Jun 2009 23:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-3006</guid>
		<description>[...] on a Friday night!) but for now I&#8217;m going with this twitter card as a way to get my social media dialtone for now. To make you&#8217;re own, just edit the source at twitter.com and crop to fit. Or, if [...]</description>
		<content:encoded><![CDATA[<p>[...] on a Friday night!) but for now I&#8217;m going with this twitter card as a way to get my social media dialtone for now. To make you&#8217;re own, just edit the source at twitter.com and crop to fit. Or, if [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-229</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 24 Feb 2009 18:28:43 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-229</guid>
		<description>Tony,
  Excellent points, thank you.  I guess my question is this:  by leveraging existing web (and SMS) protocols and providing an open API - is Twitter in fact achieving a dial tone without requiring (and in fact building on) the standardization work that went before?  

jb</description>
		<content:encoded><![CDATA[<p>Tony,<br />
  Excellent points, thank you.  I guess my question is this:  by leveraging existing web (and SMS) protocols and providing an open API &#8211; is Twitter in fact achieving a dial tone without requiring (and in fact building on) the standardization work that went before?  </p>
<p>jb</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tony joyce</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-228</link>
		<dc:creator>tony joyce</dc:creator>
		<pubDate>Tue, 24 Feb 2009 18:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-228</guid>
		<description>Something is missing in the transmorgification from pre-WW2 party lines to the mid-60&#039;s dial tones, which was an intensive effort on standardization that accompanied, and accomodated, the market growth at the time.  A large body of standards were developed under the cognizance of the old Bell System monopoly, and subsequently internationalized by the ITU.  Back in those old days the customers were generally shielded from the details; and they probably didn&#039;t care.  At least until the advent of the Princess phone (DTMF), non Bell service (original Worldcom?) and the antitrust breakup of AT&amp;T.
  I don&#039;t know that the owners of the Web were ever as interested in &quot;standardization&quot; as the phone company was; there have always been more web providers, more browsers and more applications than there were phones.  Not only have standards been lacking, but the continued profusion of APIs and mashups and interfaces suggest the standards bodies are falling further and further behind.
  Im afraid that the divergance will continue, for it would take the combined weight of major market players, Twitter plus Google plus Facebook plus others, to take on the standards challenge to  get us to a decent digital dial tone.  The odds are pretty long IMHO.</description>
		<content:encoded><![CDATA[<p>Something is missing in the transmorgification from pre-WW2 party lines to the mid-60&#8217;s dial tones, which was an intensive effort on standardization that accompanied, and accomodated, the market growth at the time.  A large body of standards were developed under the cognizance of the old Bell System monopoly, and subsequently internationalized by the ITU.  Back in those old days the customers were generally shielded from the details; and they probably didn&#8217;t care.  At least until the advent of the Princess phone (DTMF), non Bell service (original Worldcom?) and the antitrust breakup of AT&amp;T.<br />
  I don&#8217;t know that the owners of the Web were ever as interested in &#8220;standardization&#8221; as the phone company was; there have always been more web providers, more browsers and more applications than there were phones.  Not only have standards been lacking, but the continued profusion of APIs and mashups and interfaces suggest the standards bodies are falling further and further behind.<br />
  Im afraid that the divergance will continue, for it would take the combined weight of major market players, Twitter plus Google plus Facebook plus others, to take on the standards challenge to  get us to a decent digital dial tone.  The odds are pretty long IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: more on Twitter &#171; Villanova Executive MBA</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-207</link>
		<dc:creator>more on Twitter &#171; Villanova Executive MBA</dc:creator>
		<pubDate>Sat, 21 Feb 2009 14:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-207</guid>
		<description>[...] John Bordeaux raises the dial tone with [...]</description>
		<content:encoded><![CDATA[<p>[...] John Bordeaux raises the dial tone with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael miller</title>
		<link>http://jbordeaux.com/raising-the-dial-tone/comment-page-1/#comment-205</link>
		<dc:creator>michael miller</dc:creator>
		<pubDate>Sat, 21 Feb 2009 13:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://jbordeaux.com/?p=233#comment-205</guid>
		<description>Despite the discontinuous jump from phone-to-browser metaphor, I wouldn&#039;t necessarily agree that the user interface has disappeared. The numeric keypad is probably the single most researched and best understood interface in existence. And with back end phone trees we&#039;ve even managed to extend it&#039;s utility considerably, if not to our entire satisfaction - it is now more difficult than ever to get a real person on the other end of a phone...</description>
		<content:encoded><![CDATA[<p>Despite the discontinuous jump from phone-to-browser metaphor, I wouldn&#8217;t necessarily agree that the user interface has disappeared. The numeric keypad is probably the single most researched and best understood interface in existence. And with back end phone trees we&#8217;ve even managed to extend it&#8217;s utility considerably, if not to our entire satisfaction &#8211; it is now more difficult than ever to get a real person on the other end of a phone&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

