<?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: Here Comes Trouble: Hypertext to Hypercomm</title>
	<atom:link href="http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/</link>
	<description>The Business of Technology</description>
	<pubDate>Sun, 23 Nov 2008 00:53:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862977</link>
		<dc:creator>Daniel Berninger</dc:creator>
		<pubDate>Mon, 25 Feb 2008 19:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862977</guid>
		<description>&lt;p&gt;Aswath:&lt;/p&gt;

&lt;p&gt;We agree devices represent the key to change as demonstrated in the case of cellular (e.g. iPhone, Android, etc).  The question remains what we do while waiting for interesting SIP devices.  I believe there exists opportunity on the plumbing side of the equation to enable cool apps that do not necessarily require the SIP iPhone equivalent.  The elimination of telephone numbers represents one idea of where we might find these cool apps.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Aswath:</p>
<p>We agree devices represent the key to change as demonstrated in the case of cellular (e.g. iPhone, Android, etc).  The question remains what we do while waiting for interesting SIP devices.  I believe there exists opportunity on the plumbing side of the equation to enable cool apps that do not necessarily require the SIP iPhone equivalent.  The elimination of telephone numbers represents one idea of where we might find these cool apps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint Boulton</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862948</link>
		<dc:creator>Clint Boulton</dc:creator>
		<pubDate>Mon, 25 Feb 2008 15:28:25 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862948</guid>
		<description>&lt;p&gt;Daniel:&lt;/p&gt;

&lt;p&gt;Your post is interesting, but I'd love to hear some specifics. What apps today currently enable hypercomms? Please shoot me an e-mail and maybe we can set up time for a call today.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Daniel:</p>
<p>Your post is interesting, but I&#8217;d love to hear some specifics. What apps today currently enable hypercomms? Please shoot me an e-mail and maybe we can set up time for a call today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat Moore</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862881</link>
		<dc:creator>Pat Moore</dc:creator>
		<pubDate>Sun, 24 Feb 2008 23:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862881</guid>
		<description>&lt;p&gt;Social Networks (Facebook, LinkedIn, etc.) will not be successful in this regard until they change their ToS.&lt;/p&gt;

&lt;p&gt;Why? Facebook's ToS states that accessing your Facebook account is a "privilege" that Facebook can revoke arbitrarily at any time, without any sort of "due" process concept. Also Facebook, et.al. maintain what is entered is "theirs" to do with what they want.&lt;/p&gt;

&lt;p&gt;Without this kind of protection, how many intelligent users will really trust social networks with all the knowledge of how to access their friends?&lt;/p&gt;

&lt;p&gt;Right now you might not bother to remember your friends' phone number because your phone does. Even if your carrier cuts off your service you still have your friends' contact information.&lt;/p&gt;

&lt;p&gt;What happens if Facebook does the same?&lt;/p&gt;

&lt;p&gt;Even if you believe in the "I am too small to be noticed and affected" principle... would you / should you take the risk?&lt;/p&gt;

&lt;p&gt;Not me....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Social Networks (Facebook, LinkedIn, etc.) will not be successful in this regard until they change their ToS.</p>
<p>Why? Facebook&#8217;s ToS states that accessing your Facebook account is a &#8220;privilege&#8221; that Facebook can revoke arbitrarily at any time, without any sort of &#8220;due&#8221; process concept. Also Facebook, et.al. maintain what is entered is &#8220;theirs&#8221; to do with what they want.</p>
<p>Without this kind of protection, how many intelligent users will really trust social networks with all the knowledge of how to access their friends?</p>
<p>Right now you might not bother to remember your friends&#8217; phone number because your phone does. Even if your carrier cuts off your service you still have your friends&#8217; contact information.</p>
<p>What happens if Facebook does the same?</p>
<p>Even if you believe in the &#8220;I am too small to be noticed and affected&#8221; principle&#8230; would you / should you take the risk?</p>
<p>Not me&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aswath</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862810</link>
		<dc:creator>Aswath</dc:creator>
		<pubDate>Sun, 24 Feb 2008 01:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862810</guid>
		<description>&lt;p&gt;I have two (but related) major disconnect with you. The first is in all your posts you touch on the need for a different kind of device. But you do not go far. You go great distance dissing incumbent telecoms, but do not challenge IP Communications community to build end devices. Not only that you seem to tolerate the industry that is building the Middle. I cam only imagine the day when you as CEO of FWD issuing an RFP for a phone in the form factor of a cordless phone that uses Internet connectivity for "signalling" independent of whether the media goes over PSTN or IP. After all pulver.com issued an RFP to motivate the industry to agree on a single version of SIP and a wideband codec. So it can call for a "computer-less" computer phone. (Tap on the shoulder - don't go for a wifi phone, DECT is much better. It allows both PSTN and VoIP. The current version includes wideband codec.)&lt;/p&gt;

&lt;p&gt;The other disconnect is with your conclusion that we have to wait for all of us to agree on banning telephone numbers. I think if we make available devices like I mentioned previously, then those that want to avoid using phone numbers can go ahead with the help of such devices. The whole world will follow in due course. We all love Internet; one unique characteristic of Internet is that people did "The" way in a corner and if it is a good way, it slowly got adopted universally. Why can't we try that for voice? Why do we start to think differently?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I have two (but related) major disconnect with you. The first is in all your posts you touch on the need for a different kind of device. But you do not go far. You go great distance dissing incumbent telecoms, but do not challenge IP Communications community to build end devices. Not only that you seem to tolerate the industry that is building the Middle. I cam only imagine the day when you as CEO of FWD issuing an RFP for a phone in the form factor of a cordless phone that uses Internet connectivity for &#8220;signalling&#8221; independent of whether the media goes over PSTN or IP. After all pulver.com issued an RFP to motivate the industry to agree on a single version of SIP and a wideband codec. So it can call for a &#8220;computer-less&#8221; computer phone. (Tap on the shoulder - don&#8217;t go for a wifi phone, DECT is much better. It allows both PSTN and VoIP. The current version includes wideband codec.)</p>
<p>The other disconnect is with your conclusion that we have to wait for all of us to agree on banning telephone numbers. I think if we make available devices like I mentioned previously, then those that want to avoid using phone numbers can go ahead with the help of such devices. The whole world will follow in due course. We all love Internet; one unique characteristic of Internet is that people did &#8220;The&#8221; way in a corner and if it is a good way, it slowly got adopted universally. Why can&#8217;t we try that for voice? Why do we start to think differently?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862802</link>
		<dc:creator>Daniel Berninger</dc:creator>
		<pubDate>Sat, 23 Feb 2008 23:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862802</guid>
		<description>&lt;p&gt;Aswath:&lt;/p&gt;

&lt;p&gt;The IP address and telephone numbers work fine to identify hardware, but they do not belong in the UI flow.&lt;/p&gt;

&lt;p&gt;Click-to-call sets up a call one leg at a time and bridges the two legs.  Your device rings and you pick it up.  No need to dial anything (assuming you are sitting in front of a computer.)&lt;/p&gt;

&lt;p&gt;Absent a computer, I imagine a voice recognition implementation of the old operator mode.  Pick up - "Call Tom" ...Tom's phone rings.  Social networks help in this regard by providing a finite set of names the voice recognition must identify.&lt;/p&gt;

&lt;p&gt;People can devise more interesting ideas, but the prospect for change seems limited until we agree on a goal of banning telephone numbers.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Aswath:</p>
<p>The IP address and telephone numbers work fine to identify hardware, but they do not belong in the UI flow.</p>
<p>Click-to-call sets up a call one leg at a time and bridges the two legs.  Your device rings and you pick it up.  No need to dial anything (assuming you are sitting in front of a computer.)</p>
<p>Absent a computer, I imagine a voice recognition implementation of the old operator mode.  Pick up - &#8220;Call Tom&#8221; &#8230;Tom&#8217;s phone rings.  Social networks help in this regard by providing a finite set of names the voice recognition must identify.</p>
<p>People can devise more interesting ideas, but the prospect for change seems limited until we agree on a goal of banning telephone numbers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aswath</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862797</link>
		<dc:creator>Aswath</dc:creator>
		<pubDate>Sat, 23 Feb 2008 21:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862797</guid>
		<description>&lt;p&gt;Daniel:&lt;/p&gt;

&lt;p&gt;Can you give us a hint on the architecture that will get rid of telephone numbers? After all the IP network architecture hasn't gotten rid of IP addresses and MAC addresses. Aren't they comparable?&lt;/p&gt;

&lt;p&gt;On another tack, GC provides click-to-call capability. There is an architecture that allows users to avoid phone numbers if they agree to give up on the 12 button phone. You keep teasing us about this particular point and I am waiting for you to openly implore the industry to adopt capable (dare I say "intelligent") end-points. Better yet an announcement that FWD will utilize is architecture. I hope some day soon I will read such a post uner Here comes Trouble banner.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Daniel:</p>
<p>Can you give us a hint on the architecture that will get rid of telephone numbers? After all the IP network architecture hasn&#8217;t gotten rid of IP addresses and MAC addresses. Aren&#8217;t they comparable?</p>
<p>On another tack, GC provides click-to-call capability. There is an architecture that allows users to avoid phone numbers if they agree to give up on the 12 button phone. You keep teasing us about this particular point and I am waiting for you to openly implore the industry to adopt capable (dare I say &#8220;intelligent&#8221;) end-points. Better yet an announcement that FWD will utilize is architecture. I hope some day soon I will read such a post uner Here comes Trouble banner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862792</link>
		<dc:creator>Daniel Berninger</dc:creator>
		<pubDate>Sat, 23 Feb 2008 21:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862792</guid>
		<description>&lt;p&gt;Michael,&lt;/p&gt;

&lt;p&gt;GrandCentral does offer click-to-call from the address book, but it still needs to create more distance from telephone numbers.  The whole premise still revolves around a telephone number albeit a single telephone number.  The world needs an architecture that makes the telephone number disappear.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>GrandCentral does offer click-to-call from the address book, but it still needs to create more distance from telephone numbers.  The whole premise still revolves around a telephone number albeit a single telephone number.  The world needs an architecture that makes the telephone number disappear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862783</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 23 Feb 2008 17:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862783</guid>
		<description>&lt;p&gt;Seems to me you've this is the direction Google is going with their recent purchase of GrandCentral. When the addressbook fully integrates with gmail, we'll be a long way down the path you suggest.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Seems to me you&#8217;ve this is the direction Google is going with their recent purchase of GrandCentral. When the addressbook fully integrates with gmail, we&#8217;ll be a long way down the path you suggest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aswath Rao</title>
		<link>http://gigaom.com/2008/02/23/here-comes-trouble-hypertext-to-hypercomm/#comment-862779</link>
		<dc:creator>Aswath Rao</dc:creator>
		<pubDate>Sat, 23 Feb 2008 16:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11584#comment-862779</guid>
		<description>&lt;p&gt;We have implemented many of the ideas and features suggested in this post and is operational for about a year now. What is more, it is architected so that it can be distributed as well. Look for some major step forward during Von.x.&lt;/p&gt;

&lt;p&gt;GigaOm may have decided that it was not worth writing about this, but slowly and surely we will be noticed. :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We have implemented many of the ideas and features suggested in this post and is operational for about a year now. What is more, it is architected so that it can be distributed as well. Look for some major step forward during Von.x.</p>
<p>GigaOm may have decided that it was not worth writing about this, but slowly and surely we will be noticed. :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
