<?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>Mobile • Local • Socialaim &#187; </title>
	<atom:link href="http://mobilelocalsocial.com/tag/aim/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobilelocalsocial.com</link>
	<description>Mobile, Local, Social and Search is here. It&#039;s one ecosystem. The future of communication is now.  MobLoSo discusses these topics &#38; other Tech News.</description>
	<lastBuildDate>Fri, 21 Oct 2011 21:39:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Social Wars: Aol Teams Up With Facebook</title>
		<link>http://mobilelocalsocial.com/2010/social-wars-aol-teams-up-with-facebook/</link>
		<comments>http://mobilelocalsocial.com/2010/social-wars-aol-teams-up-with-facebook/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 14:23:24 +0000</pubDate>
		<dc:creator>Matthew Baron</dc:creator>
				<category><![CDATA[aol]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Chat]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Social Wars]]></category>
		<category><![CDATA[aim]]></category>
		<category><![CDATA[aol instant messenger]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[google buzz]]></category>
		<category><![CDATA[ichat]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[MSN]]></category>
		<category><![CDATA[Yahoo!]]></category>

		<guid isPermaLink="false">http://mobilelocalsocial.com/?p=733</guid>
		<description><![CDATA[Aol has announced that it will team up with Facebook to link Facebook Chat with Aol&#8217;s chat client, AIM. This is largely in response to yesterday&#8217;s announcement by Google of it&#8217;s new social networking service, Google Buzz, which looks to expand into territory held by Facebook and Twitter.  While Aol gains little from it, Facebook [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-734" title="Social Wars" src="http://mobilelocalsocial.com/wp-content/uploads/2010/02/chat-e1265811745332.jpg" alt="" width="571" height="494" />Aol has announced that it will team up with Facebook to link Facebook Chat with Aol&#8217;s chat client, AIM. This is largely in response to yesterday&#8217;s announcement by Google of it&#8217;s new social networking service, Google Buzz, which looks to expand into territory held by Facebook and Twitter.  While Aol gains little from it, Facebook gains some small amount of chat functionality as AIM is still a very viable chat platform.  What is puzzling is that this announcement is so late in the game.</p>
<p>AIM is not much to look at.  It is a monotasker (to borrow the word from Alton Brown) and not a pretty one.  It is available for Mac, but is largely unused because iChat, which has the advantage of being both pre-installed and located on the default Dock, uses the AIM chat protocol.  On the PC front, AIM has steadily lost ground over the years as all-in-one IM clients took over.  Chat wars haven&#8217;t been a big thing for years, when Yahoo! and Google (which launched Google Talk soon after GMail) and Microsoft and Aol (then AOL) each jealously guarded their chat protocols to prevent interoperability.  The upshot was inconvenience for the user.</p>
<p>MSN Messenger still exists but only as a casualty of the Chat Wars (much like MSN).  Yahoo! Chat still boasts a hearty user base.  And Google and Aol have had an uneasy detente for the past several years, with interoperability in the chat window in GMail as well as in Apple&#8217;s iChat.  But now with Google moving once again into the Social Networking field, old truces may fall and new alliances like Aol and Facebook form.</p>
<p>Let us not forget that Google is also in some very nasty fights against Apple and Microsoft.  Google&#8217;s Nexus One looks to unhorse the iPhone (that has yet to be seen).  It is working on an OS called ChromeOS which would naturally go against OSX and Windows.  And speaking of Windows, Google also has its own browser to fight Internet Explorer (Microsoft) and Safari (Apple) available for Windows and in beta form on Mac, where Safari holds a lot of traction.  On the Search front, Google is fighting against Microsoft&#8217;s Bing!, which, it should be noted, could in theory be supplemented if and when Microsoft manages to buy out Yahoo!</p>
<p>So there sits Google, fighting battles on too many fronts to name and starting more fights of its own.  As I&#8217;ve previously stated, I&#8217;m not a fan of AIM by any stretch and giving it Facebook functionality won&#8217;t make me want to install it on my Mac.  However, this is a prime opportunity for Apple to ride in on a white horse and do a deal with Aol and/or Facebook to add Facebook to iChat.  I&#8217;ve been a Mac user (I use all platforms) for over four years.  Since then, I&#8217;ve felt that the iChat UI is simply the best-looking interface for chat.  I&#8217;ve used Pidgin, Adium and even Trillian years ago.  But, pixel for pixel, iChat works nicest.  On the iPhone, BeeJive, in my opinion a must-have app, works so nicely in no small part because it uses the iChat UI.</p>
<p>The Aol/Facebook alliance provides a unique opportunity for several companies, each fighting their own battle with Google, to strike a blow.  Aol can update not just its client but its protocol to allow for multiple instances to run (opening GMail won&#8217;t knock out your iChat connection).  Facebook can give its users another reason to keep a Facebook tab open by having AIM right there.  Apple can get some more pixels from the press by updating a program that is starting to gather dust.</p>
<p>These are all some minor things that Google&#8217;s adversaries can do to maybe get Google to rethink its expansionist ideas.</p>
]]></content:encoded>
			<wfw:commentRss>http://mobilelocalsocial.com/2010/social-wars-aol-teams-up-with-facebook/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>It&#8217;s Time To Kill AIM And Pay SMS</title>
		<link>http://mobilelocalsocial.com/2010/its-time-to-kill-aim-and-sms-plans/</link>
		<comments>http://mobilelocalsocial.com/2010/its-time-to-kill-aim-and-sms-plans/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 15:00:59 +0000</pubDate>
		<dc:creator>Matthew Baron</dc:creator>
				<category><![CDATA[AT&T]]></category>
		<category><![CDATA[Chat]]></category>
		<category><![CDATA[Texting]]></category>
		<category><![CDATA[aim]]></category>
		<category><![CDATA[aol]]></category>
		<category><![CDATA[aol instant messenger]]></category>
		<category><![CDATA[buddy list]]></category>
		<category><![CDATA[data plans]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[mobile phones]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[text messages]]></category>
		<category><![CDATA[text plans]]></category>
		<category><![CDATA[verizon]]></category>

		<guid isPermaLink="false">http://mobilelocalsocial.com/?p=343</guid>
		<description><![CDATA[Both AIM and SMS, two technologies of the 1990's, have run their course. In an age of Androids and iPhones, why should we only be able to have a chat program running in one place? Why should we have to pay to text?]]></description>
			<content:encoded><![CDATA[<p><a href="http://mobilelocalsocial.com/wp-content/uploads/2010/02/6a00e5501aaa24883400e553c0be188833-800wi.jpg"><img class="aligncenter size-full wp-image-344" title="Text Messaging" src="http://mobilelocalsocial.com/wp-content/uploads/2010/02/6a00e5501aaa24883400e553c0be188833-800wi-e1265122637600.jpg" alt="" width="572" height="380" /></a></p>
<p>Generally speaking, I have a variety of chat programs open at any given time on a variety of platforms. At home in the evening, I usually have my media server (which doubles as an internet terminal) on, as well as my MacBook Pro.  The chances are that there is a GMail window open on either the server or the Mac.  Additionally, I have iChat almost always running on the Mac.  On top of that, on my iPhone, I&#8217;m usually running BeeJive.  As a result, I usually get a few error messages associated, not with not knowing how to run a computer, but with running too many instances.  The biggest offender is AIM (AOL Instant Messenger), which, as anyone with multiple GMail instances open knows, bugs the user with alerts that there are multiple AIM instances running.</p>
<p>AIM is a classic piece of Nineties tech.  It launched in 1997 and quickly became the dominant chat program, displacing ICQ (pronounced &#8220;I Seek You&#8221;).  AIM would link to your AOL Buddy List, meaning that if all you wanted to do was IM people, you didn&#8217;t have to run AOL.  Several features were added over the years (file sending, photo sending) but, honestly, except for less than a half-dozen new features and a long-delayed UI updating, AIM now looks like AIM then.  iChat within a year of its 2003 launch, was touting AIM compatibility.  At the end of 2007, ten years after AIM&#8217;s launch, Google was touting AIM compatibility in Google Talk.  And open-source programs like Adium and Gaim also have AIM compatibility.  The question is why?</p>
<p>AIM is stale.  Compatibility is sketchy at best with the frequent inability to file send between AIM clients (file-sending between iChat and AIM is a crap-shoot).  But most irksome is the chronic notifications of multiple instances.  In 1997, a household probably had one computer and that computer was connected to the internet via either 2-wire or 4-wire telephone cable on a 56k baud connection.  Now, more than a decade later, a household may have upwards of a half-dozen connections to the web when you factor in mobile phones.  Discouraging multiple instances is a dead concept on a dead platform made by a dead company.  And yet AIM is a zombie of the internet.  It should be dead and it won&#8217;t die.</p>
<p>Texting is a product of the Nineties, as in it began in 1990 and slowly grew throughout the decade.  Twenty years after its birth, it is the most widely used mobile data service worldwide.  And yet it is still constrained to 160 characters.  Now, we have mobile chat clients on our smartphones.  The iPhone has BeeJive (if you haven&#8217;t installed BeeJive, do it; it&#8217;s worth the $10).  Android, not requiring app-store approval, also has a variety of chat programs; so does BlackBerry.  Texting, it seems, is no longer all that relevant.  In a smartphone world, it&#8217;s dead tech.  We&#8217;re still using only 160 characters and, most of all, we&#8217;re being charged through the nose for the privilege of it.</p>
<p>And in a cruel instance of gouging the customer, AT&amp;T is now requiring people with certain phones to also have a text plan too.  This is simply absurd.  It&#8217;s bad enough that customers get gouged when it comes to texting (the actual cost is negligible).  But to force dead tech on customers, that&#8217;s egregious.</p>
<p>It&#8217;s time for these zombies to be put down.  To AOL &#8211; either actually overhaul the AIM protocol or sell it to someone who will.  I&#8217;m sure that Google would be happy to take it and your Buddy Lists off your cold, dead hands.  And to AT&amp;T (and it&#8217;s evil step-sister Verizon), start giving away texting for free to people with smartphones with unlimited data plans.  I know there are unlimited texting plans that you can buy but a smartphone shouldn&#8217;t need an SMS plan.</p>
]]></content:encoded>
			<wfw:commentRss>http://mobilelocalsocial.com/2010/its-time-to-kill-aim-and-sms-plans/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

