<?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: Beta No More for Windows Live Messenger 8.1</title>
	<atom:link href="http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/feed/" rel="self" type="application/rss+xml" />
	<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/</link>
	<description>Technology News</description>
	<lastBuildDate>Mon, 23 Nov 2009 16:18:25 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MetaMan</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87564</link>
		<dc:creator>MetaMan</dc:creator>
		<pubDate>Thu, 01 Feb 2007 02:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87564</guid>
		<description>Here&#039;s an easy fix for all of the companies. Pick a protocol (one universal protocol), and then make it so that all of the IM clients use that protocol for basic, unformatted text. Then, have each of the companies build a proprietary layer on top of the base protocol, to allow things such as formatted text, file sharing, and video and voice chat, but so that only users of the same service could use it. That way, they would not be inconveniencing users if they absolutely had to text each other, but they would be offering an incentive to use their service.

In fact, this could actually be a very good marketing scheme. Let&#039;s say person A uses Google Talk, and person B uses AIM. Persons A and B would both be very excited and happy when they found out that their two clients would be cross-compatible. After a while, though, they would both become thoroughly annoyed because they could not, say, share files. Then, they would have to decide on which client to both use in order to have that compatibility, and would then decide based on the clients&#039; merits. Whichever client they chose would then have one more member. And, since it would be easy for them to switch over to the other client if that other client suddenly became so much better, it would then be possible for one client to grab the majority of users after a major release. The client&#039;s popularity would then slowly decrease over time as other clients released their new versions, but would spike again as the client released its next version. Theoretically, if none of the clients were ever released around the same time, all companies involved could make a lot more money. Something to think about.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an easy fix for all of the companies. Pick a protocol (one universal protocol), and then make it so that all of the IM clients use that protocol for basic, unformatted text. Then, have each of the companies build a proprietary layer on top of the base protocol, to allow things such as formatted text, file sharing, and video and voice chat, but so that only users of the same service could use it. That way, they would not be inconveniencing users if they absolutely had to text each other, but they would be offering an incentive to use their service.</p>
<p>In fact, this could actually be a very good marketing scheme. Let&#8217;s say person A uses Google Talk, and person B uses AIM. Persons A and B would both be very excited and happy when they found out that their two clients would be cross-compatible. After a while, though, they would both become thoroughly annoyed because they could not, say, share files. Then, they would have to decide on which client to both use in order to have that compatibility, and would then decide based on the clients&#8217; merits. Whichever client they chose would then have one more member. And, since it would be easy for them to switch over to the other client if that other client suddenly became so much better, it would then be possible for one client to grab the majority of users after a major release. The client&#8217;s popularity would then slowly decrease over time as other clients released their new versions, but would spike again as the client released its next version. Theoretically, if none of the clients were ever released around the same time, all companies involved could make a lot more money. Something to think about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87558</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 01 Feb 2007 01:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87558</guid>
		<description>@CoryC: I just don&#039;t think the companies like to work together. Honestly, I&#039;m still in awe that Microsoft and Yahoo managed to work together to get their messengers working together. I guess sometimes competition outweighs consumer benefits.</description>
		<content:encoded><![CDATA[<p>@CoryC: I just don&#8217;t think the companies like to work together. Honestly, I&#8217;m still in awe that Microsoft and Yahoo managed to work together to get their messengers working together. I guess sometimes competition outweighs consumer benefits.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CoryC</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87557</link>
		<dc:creator>CoryC</dc:creator>
		<pubDate>Thu, 01 Feb 2007 00:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87557</guid>
		<description>&lt;div id=&quot;commentquote&quot;&gt;&lt;a href=&quot;#comment-87554&quot;&gt;MetaMan wrote:&lt;/a&gt;&lt;blockquote&gt;If only they finally made &lt;a href=&quot;http://tech.cybernetnews.com/2006/12/22/when-will-google-talk-work-with-aim/&quot; rel=&quot;nofollow&quot;&gt;AIM and Google Talk cross-compatible&lt;/a&gt;.&lt;/blockquote&gt;&lt;/div&gt;

I wonder when these companies will realize that inter-op will benefit everyone.  AOL, Microsoft, Yahoo, and the other should stop see the other guys as competition and o fined a way the leverage each other to their own benefit. 

Let&#039;s face it, most of us have a preference on messenger clients are not going to switch just because a friend of our uses a different one.</description>
		<content:encoded><![CDATA[<div id="commentquote"><a href="#comment-87554">MetaMan wrote:</a><br />
<blockquote>If only they finally made [<a href='http://tech.cybernetnews.com/2006/12/22/when-will-google-talk-work-with-aim/.' rel='nofollow'>tech.cybernetnews.com</a>]</p></blockquote>
</div>
<p>I wonder when these companies will realize that inter-op will benefit everyone.  AOL, Microsoft, Yahoo, and the other should stop see the other guys as competition and o fined a way the leverage each other to their own benefit. </p>
<p>Let&#8217;s face it, most of us have a preference on messenger clients are not going to switch just because a friend of our uses a different one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MetaMan</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87554</link>
		<dc:creator>MetaMan</dc:creator>
		<pubDate>Wed, 31 Jan 2007 23:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87554</guid>
		<description>&lt;p&gt;If only they finally made &lt;a href=&quot;http://tech.cybernetnews.com/2006/12/22/when-will-google-talk-work-with-aim/&quot;&gt;AIM and Google Talk cross-compatible&lt;/a&gt;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If only they finally made [<a href='http://tech.cybernetnews.com/2006/12/22/when-will-google-talk-work-with-aim/.' rel='nofollow'>tech.cybernetnews.com</a>]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashley</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87534</link>
		<dc:creator>Ashley</dc:creator>
		<pubDate>Wed, 31 Jan 2007 20:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87534</guid>
		<description>Your welcome  :D</description>
		<content:encoded><![CDATA[<p>Your welcome  <img src='http://cybernetnews.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay</title>
		<link>http://cybernetnews.com/beta-no-more-for-windows-live-messenger-81/comment-page-1/#comment-87525</link>
		<dc:creator>Ajay</dc:creator>
		<pubDate>Wed, 31 Jan 2007 19:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://tech.cybernetnews.com/2007/01/31/beta-no-more-for-windows-live-messenger-81/#comment-87525</guid>
		<description>Thanks for the link Ashley :)</description>
		<content:encoded><![CDATA[<p>Thanks for the link Ashley <img src='http://cybernetnews.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
