AOL Shuts Down 3rd Party IM Software? 236
David Gervais noted that AOL has begun shutting out third party IM software (among other things, breaking the Linux clones). Their error message is "AOL IMer Client: Gaim CVS Version.
09:24:11 AOL Instant Messenger: You have been disconnected from the AOL Instant Message Service (SM) for accessing the AOL network using unauthorized software." Can someone confirm this, or is Mr Gervais on something here? I've had several folks say they can get through just fine. Perhaps this is just a Gaim CVS bug? Update: 09/11 05:12 PM by C : Have tested AIM connectivity with Gaim v0.9.20 and Everybuddy 0.1.4 with no problems. Sorry for the scare.
if you like fat girls... (Score:1)
So don't use AoL! (Score:1)
How does AOL survive... (Score:1)
And now they sever another link between their clients and the outside world? I don't get it.
dynamo
Perspectrum - All possible views or perspectives on an issue.
Re:Um, AOL is a pay service, so 3rd parti IM == th (Score:1)
Re:Just fake the client name?! (Score:1)
We get enough buffer overflows by accident. I'm sure that setting one up intentionally shouldn't be too hard. ;-) And if everything else fails, just boycott the AOL protocol entirely and use ICQ or Yahoo instead.
-RickHunter
Re:Another reason for SIP (Score:1)
Maybe next time... (Score:1)
Re:The response (Score:1)
Rather takes the fun out of making the jump, now doesn't it?
--
Re:Their server, their right. (Score:2)
if they only want their client to talk to their server, they are entitled. This may suck for everyone in the short term,
certainly they are entitled to want that, but it is questionable whether they are legally entitled to have that, and doubly questionable whether they should be legally entitled to have that. Consider the telephone. It used to be that you could only connect a Bell telephone to the one company's circuits. Now you can connect any kind to a choice of servers, and the world is unquestionably a better place. The changeover required a change in the law and it took 100 years. That did suck for everyone, and lets not repeat it.
but alternatives will prevail if they stay closed.
Not necessarily. This industry, like the telephone, could be an example of a natural monopoly, in which case it takes active opposition/regulation to keep it open, cheap, and innovative.
Re:How will the FCC. SEC look on this? (Score:2)
Re:Just fake the client name?! (Score:1)
Re:False alarm? (Score:1)
Re:Their server, their right. (Score:1)
On the other hand, the sentiment is that spammers should not be allowed to send their junk mail to YOUR machine, because it is YOUR hardware.
Let's be consistent, shall we? Either you allow spammers access to your hardware, or you allow AOL to deny unauthorized access to their hardware.
typical, unfortunately (Score:1)
Re:Corporate Ethics (Score:1)
Am I a glassy-eyed libertarian? Not in any way. The community has a responsibility to itself and we should insist that AIM and services like AIM have open standards, and we should legislate, hack, clone, whatever to get there. I want to achieve the same "best" result you do, but I don't want to get preachy and moralize about it. There's nothing wrong with AOL's attitude, but we need to make sure they don't get what they want as it hurts us.
You idiots at Slashdot (Score:1)
Clarification: Two AIM protocols (Score:2)
Linux (Score:3)
AOL IM Linux Beta (Score:2)
AOL Instant Messanger Blockage (Score:5)
---
Rob Flynn
The question is... (Score:2)
How is AOL going to make money?
AOL thinks there are lots of ways to make money on messaging. One of their executives is quoted as saying that Instant Messaging is AOL's most important asset.
But clearly, they think they can only succeed if they control the client as well as the servers. And a route into their system where they don't control the client is apparently unacceptable to them.
repeats (Score:1)
Aol seems to be changing the authentication
a bit, maybe standardizing. Tried upgrading?
A new versiom of gaim showed up yesterday and
I'm not having any problems connecting.
So what, use the public protocol (Score:5)
As far as I know, however, only tik and tac use TOC. All the other stuff uses the half-working, mostly-broken, half-implemented FAIM implementation of AOL's private protocol. Is everyone just crazy, or what?
I don't blame AOL for breaking support for their private protocol. Just use the public one. Its there, it works. What's the big deal?
Re:The response (Score:2)
Reportedly, AOL has been talking about closing their TOC servers for a while now, and my guess is that they finally did that. Clients which use OSCAR (this includes everybuddy) are unaffected.
There's more info in the Everybuddy FAQ [everybuddy.com].
Please note that the above "facts" are all based on heresay and conjecture.
Re:This is BS (Score:1)
Yes, that's exactly it. Third-party clients bypass the ads and so they cost AOL money.
You're just going to have to accept the fact that this is AOL's technology and they have the right to exclude whatever they want.
Frankly, I don't understand the commotion. There must be open alternatives, so why not use those instead? Or do you really want to talk to people who like AOL? My email client automatically deletes all email from aol.com, because only lusers use AOL, so why would I want to talk to them anyway?
--
Re:What? Again? (Score:1)
Re:How will the FCC. SEC look on this? (Score:1)
Refrag
Re:Damn this is weird.. (Score:3)
Re:What do we expect? (Score:1)
Re:Wasant Aol... (Score:1)
No, this is true. (Score:2)
------------
a funny comment: 1 karma
an insightful comment: 1 karma
a good old-fashioned flame: priceless
Re:non-ad-showing clone clients (Score:1)
Re:Their server, their right. (Score:1)
On the cost of servers issue, I think bundling is in general a bad idea for consumers as it generally represents an attempt by a company to leverage some strength in order to gain share for some inferior product or to damage a legitimate competitor. As consumers we protect ourselves if we set up markets such that we are not faced with choices of bundles that include inferior products. So, the answer would depend on AOL's revenue model. If ads pay for the servers, then I'd be happy to require that clones run the same ads. If they're giving away the service in order to garner share, then AFAIC they've agreed to give it away.
Re:AOL IM Linux Beta (Score:1)
Re:Infrastructure (Score:1)
Well, this strikes me as somewhat amusing as I am running AIM for linux as we speak. Interested parties can check AOL's site [aol.com].
peas,
-Kabloona
Re:gaim from helixcode (Score:1)
---
Rob Flynn
Re:Just fake the client name?! (Score:1)
They do that, they'll slowly go back to being a network effectively isolated from the rest of the internet. And I don't think they want that. Remember that the internet routes around damage. AOL is coming closer and closer to qualifying as damage.
-RickHunter
What? Again? (Score:3)
why would they do that? (Score:1)
-lx
Stirring the pot :) (Score:2)
grrrrr (Score:1)
---------///----------
All generalizations are false.
Re:So use ICQ (Score:1)
That's exactly what I was thinking as soon as I saw this article. I think that maybe some people don't realize (or have forgotten), that AOL is "in charge of" ICQ now.
-B
benjones@superutility.net
Re:So don't use AoL! (Score:1)
ICQ being feature-bloated means I can do more shit than I can with AIM. Yes, there are a ton of features I don't use too, but some other people do.
As for standards-compliance, ICQ's servers have never blocked 3rd-party clients from communicating - they just made the separate client-to-server and client-to-client protocols a pain in the ass to both implement.
Not that it matters anymore, now that AOL is putting ads in ICQ... Anyone see a banner ad other than the stupid Network Solutions dot.com stuff yet?
Re:Why gaim was blocked. (Score:1)
---
Rob Flynn
Re: (Score:1)
Hmmm..... Hasn't this been done? (Score:1)
Re:How will the FCC. SEC look on this? (Score:1)
Granted, it was probably a ploy by MS et al to get a piece of the action, but AOL did not want to have any part of it.
And as it stands, I'm MUCH more afraid of the AOL/TW merger than Microsoft. At least with MS, there are feasible alternatives.
Buffer Overflow (Score:1)
Especially on a windows box, where every proggy runs as root, this would mean that any random script kiddie would have total control over a computer running AIM. That's a lost of people. Can anyone say "class action"?
Their server, their right. (Score:4)
Re:Linux, that's why (Score:2)
This means they will want to confine and control you. Make you use their product because others aren't compatible. TO talk to their users, you have to use their software and see their ads. Your information will get recorded by them, and sold to anyone willing to pay them the $ they ask.
If the AOL/TW merger goes through - expect to see TW Cable saturated with AOL ads (and you thought they were bad now!) - expect RoadRunner service to go down the toilet and for prices to rise. Expect MORE spam - not less. Expect the spam to come in MORE formats - email, on-screen, TV, etc...
AOL's philosophy has been to spam since the beginning. Spamming people's snail-mailboxes with disks, and later CDs - spamming their users with ads for products they could probably care less about - spamming TV stations with ads (sometimes that play 2-3 times in a row) to make sure you repeat their name in your sleep. It's a not-so-subtle form of mind control - and it's working on the masses. They believe ANYTHING that AOL tells them. "We respect your privacy" - BULL$#!^ - the only thing AOL respects is the almighty dollar - and they'll do anything to get it.
I'm off-topic now...let's get back on...
Linux clients made by 3rd parties don't display AOL's ads to users. They don't track the user's habits and report back to AOL. They don't do ANYTHING other than be a messaging client.
And thus AOL can make NO money off of them.
So AOL shuts them out. People can't use them - so they'll use the "official" AOL software that makes AOL money. At least, that's AOL's opinion on the matter.
The linux community, however, will probably not conform to AOL's wishes - reverse engineering will get the clients back into the system, and linux users will be happy and ad-free.
AOL will change their "authentication" checks again.
Linux clients will reverse-engineer them and get back in.
Lather, rinse, repeat. It's the same $#!^ that they pulled with M$'s messenger program - except now it's hitting closer to home.
Perhaps AOL... (Score:4)
The response (Score:4)
Nuts .
For those who don't know the historical reference, pop open the nearest history book and flip to the WWII section. =) All this means is that now we're going to change the version the software reports and recompile. w00t, big deal, hardly worth a post to /..
--
IRC to IM conversion. (Score:2)
Perhaps something like this will allow us to use IM clients without having to go through AOL's servers. Seems like a good alternative for me.
Although personally, I don't use a IM client of any flavor. I prefer real, live IRC (because I don't have any friends).
My GAIM is working fine! (Score:3)
---
Re:How will the FCC. SEC look on this? (Score:2)
What really makes me mad at the
IM is popular because it is nearly ubiquitous, and AOL made it that way, if you want to have a competing Open Source messaging system, go for it, just don't expect to see everyone you know on it. If you want to talk to those people, you need AIM to connected to AOL's servers. Its really *QUITE* fair.
Stop Your whinning.
flames may be trashed before sending them my way, because they will end up there once they get here anyway, so save the bandwidth, type up your complaints calling me a moron or whatever and
file it in
I think....therefore I am
Re:What's the big deal (Score:4)
Email is decentralized and works fine. (Score:2)
But look at the Email or WWW. THese are decentralized systems and thus can handle the load very easily. They distribute out the overhead to thousands of hosts. Or look at battle.net versus the clones.
The reason that AIM/ICQ are centralized and require a big machine is because they designed that way. They were designed so that they had a common and fixed chokepoint that the corporations cound control and exploit.
Design it differently: Design a protocol where a user has a name of and all messages are sent to that host automatically for that user. THat way you can decentralize it and handle hundreds of millions of users and billions of messages. It worked for email, where people send megabyte powerpoint presentations, it'll work for ICQ where people wrote 4 line messages.
Re:How will the FCC. SEC look on this? (Score:2)
Authorized software = !(free) (Score:2)
At first AOL's action seemed more than a little hypocritical to me in light of this, but then I noticed that, because of the presence of the actual AIM icon on the GUI, there must have been some sort of licensing fee paid to AOL by Lotus.
So I guess AOL just wants those licensing fees. I'm not saying this is a smart move on their part - there's plenty of ways to make money off the service without restricting the open clients.
Re:So don't use AoL! (Score:2)
ICQ is a piece of shit. Its official clients are buggy, feature-bloated, and even less standards-compliant than AOL's software. The only reason I use it is because I have some friends who still insist on using it. Everybuddy [everybuddy.com] manages to trim most of the fat, fortunately.
AOL Fighting for IM Standard (Score:3)
Conclusions made here ... AOL is full of it, they want to make sure that they aren't next on the Monopoly lawsuit list and they'll blow all kinds of smoke and whistles to make it look like they're for the community.
AOL wants to get on my side ... they'll release the OSCAR protocol, not just TOC.
Re:This is BS (Score:2)
You don't like it, use Jabber [jabbercentral.com]. Set up a server, promote it, spend your money on it, and get my grandma to use it.
aol copyright (Score:2)
this apparently is the reason nobody has really tried to ip spoof the aol network. besides the fact that all aol packets for clients are b-class private and all internal packets are a-class private net addresses. the spoofer would not only be facing the hacking charges but aol would dump enormous copyright charges against them.
Re:So don't use AoL! [ObJabberPost] (Score:4)
ICQ transmits your passwords plaintext.
Messages are easily spoofable.
There's no third-party extensability.
You can't run your own server (at least, not and communicate with the rest of the world).
There's no support for encrypted or signed messages.
And finally, it's controlled by a commercial entity. Don't want these things? Use jabber (www.jabber.org). Jabber is actually an XML-based protocol, so there are lots of differenct clients which conform. Since it's largely serverside, new clients (and clients for different platforms) are easy to write, and once a client has stabilized it very rarely needs upgrading (even to add features like ICQ compatability -- it's all done serverside).
Try Jabber. You'll like it. And if you don't, come back in 6 months and try it again.
Re:So don't use AoL! (Score:2)
Already been done. Check out Licq, Micq, GnomeICU, and a host of others, as well as (he said, modestly) the Jabber transport for ICQ.
Slightly off-topic comment to the "I don't think it would be hard..." remark: ICQ isn't a particularly easy protocol. It uses a combination of client-server UDP and peer-peer TCP that's tricky to get right. That also means that it's tough for one process to manage lots of ICQ connections, which is one of the reasons I'm rewriting icq-t...
Eric
--
Re:What's the big deal- even more dumb (Score:2)
...phil
I have a workaround (Score:3)
They just started looking for a client string in the network protocol. This is similar to the HTTP request header, or the MP3 stream ACK, or whatever. Find a copy of QuckBuddy (AOL's Java client), or if you're developing a client, change the name of the connect string so Oscar thinks it's getting a valid client.
GAIM links (karma whoring) (Score:2)
GAIM source tarball [marko.net]
All other types (RPM, DEB, etc) [marko.net]
- Bill
Well, try Jabber... (Score:2)
The current release is about stable enough for daily use, IMHO...
/joeyo
Re:What's the big deal- even more dumb (Score:2)
Here's to hoping AIM dies a horrible heat death and AOL users never realize there is a world beyond the AOL servers.
Re:The question is... (Score:2)
1) Ads - bombard users with ads for "Free AOL" and get more sheep to sign up for the online service priced at least $5 more than it's competitors. Later, they can sell ads to outside companies - with the promise of reaching millions of eyes.
2) Mindshare - The more people that use it, the more people that associate AOL with IM. This is an asset that shareholders like. Later they can start charging a fee (probably when micropayments take off) and figure they can make BOATLOADS of money.
Weird Gaim/AIM problem (Score:2)
This morning I was able to talk to her with Gaim, though.
Weird, eh? It looked to me like I was sending messages. No errors, but they just didn't get through.
I'm using v0.9.20.
---
Re: (Score:2)
Simple - move your network of friends off of AOL (Score:3)
If you want a IM provider that plays nice with linux, FreeBSD, MacOs and Windows, try Yahoo. I have been using their client for a few months on all of the above platforms and I'm very satisfied.
You have a choice, you don't need to feed the beast.
Re:Just fake the client name?! (Score:2)
Re:So what, use the public protocol (Score:3)
GAIM has used TOC since it started.
I am currently on AOL through GAIM using TOC and it works fine.
The reason why many clients are trying to support OSCAR (GAIM included) is because TOC cannot do everything that OSCAR can. For example, I can't send files to people (although I can receive them). Also, I can't seem to check away messages without actually sending the person a message and getting a reply (though maybe I'm just stupid there). There is a huge list of features that just don't work over TOC.
------
Whine, whine, whine. (Score:3)
This is one case where GPL'ed software isn't going to win out for at least a few years. Right now, a large IM system requires massive, massively-parallel directory and routing services, which require massive databases (read: not MySQL or Postgres 7) and massive servers with fast interconnect and low latency.
All of this costs money. If you open the protocol and the servers to all comers, where does that money come from? The GAIM team could build in support for AOL's ads, but the GPL would allow for patched or forked versions that strip out the ads. So it wouldn't do AOL any good to ask the GAIM team to support its ads.
For a bunch of Microsoft-skeptics, Slashdot readers are mighty easily swayed by Microsoft's PR spin on this. AOL isn't being anti-competitive by blocking 3rd-party clients. They're protecting a revenue stream that pays (they hope) for dozens of racks of expensive servers and millions of dollars in database licenses.Microsoft and Yahoo aren't fighting for freedom. They're fighting to convince naive courts that they have a "right" to strip out AOL's ads--on a service AOL is paying for in its entirety--and replace them with their own ads. If it goes to arbitration and MS and Yahoo are told they can make AIM clients as long as they give AOL's ads and ad-reporting mechanisms clear passage, you'll see MS and Yahoo lose interest in the whole idea mighty quickly indeed.
Massive peer-to-peer systems without central servers are a tough thing to do right now. Just ask the folks at Napster and the other filesharing projects. All of them are running clusters of independent servers. Sign on to Napster twice, and you'll see two sets of users and files.
When an equally massive, fully-distributed scheme for instant message routing and directory services becomes viable, those expensive central servers can go away, and so can the need for massive revenue. Seems to me something could be cobbled together out of a stripped-down version of OpenLDAP and ml.org-style dynamic DNS projects, so that any of your devices that are connected report their presence, and the lookups get farmed out over zillions of LDAP servers doing referrals.
By the time this happens, of course, text-based instant messaging may well be fading out in favor of IP telephony and videoconferencing, both of which all of the instant-messaging players are rolling into their clients as fast as they can.
Re:How will the FCC. SEC look on this? (Score:4)
Ok, so it's not "official" per se - but it's the best client out there. Unlike gaim it only needs tk/tcl to run so it will work on Solaris/BSD/Linux/Windoze/...
Mine works... (Score:2)
Jon
Re:AOL Instant Messanger Blockage (Score:2)
Re:Well, try Jabber... (Score:2)
There are, fortunately, a few libs, though they take some finding. Net::Jabber is in CPAN, but not on the sourceforge page. Jabberoo is available on its homepage, but not its sourceforge page nor as a download from www.jabber.org [jabber.org], ostensibly the development center. The dev doesn't appear to be terribly coordinated, though, judging by the traffic on the dev mailing list and the info available on the website.
There are a couple of Python modules available.. sorta.. but no documentation whatsoever.
There's Jabberbeans, for Java. I don't know anything about the state of that.
So is anyone actually using Jabber? What client are you using?
---
Sending files to other users using TOC protocol (Score:2)
<O
( \
XGNOME vs. KDE: the game! [8m.com]
How will the FCC. SEC look on this? (Score:4)
Of course, it's not like this will keep your friendly neighborhood hacker from releasing a patch to fix things...
The only way to fight this (Score:2)
Many many people have enough ability to use dial-up networking and configure Outlook or Eudora or whatever, and use ICQ. Once they see that life without AOL is actually better, they will switch. But it means you might have to take the time to educate someone a bit. Help them out. Once people with AOL feel "closed off" to their friends without it, there will be the demand from AOL's own customer base to implement access. They don't care about you on the outside. AOL doesn't win many customers from other ISP's, so you're not and never will be an AOL user. But they care about losing their existing customers. Once their users are ticked because their friends can't talk to them through IM, they will make AOL give in. AOL does listen to it's customers. They just don't listen to you. So make their customers do the work.
-------------
The truth is out th- oh, wait, here is is...
-------------
Uhm...who's crying? (Score:2)
But you're right - as long as we keep trying to piggyback on corporate shoulders, we'll always get bucked sooner or later. Hit up Jabber for IM. Use Vorbis instead of MP3. Use Icecast instead of Shoutcast. While it wasn't true a little while ago, there are now quality alternatives to a lot of the stuff we get used to that don't carry the weight and consequances of corporate decision-making. I used AIM progs to communicate with a pal. Now he'll communicate with me using Jabber. Big deal. No loss, and big gain - as long as these companies keep doing what they're doing, the Open Souce alternatives are going to win and there will come a time when these corporate companies are going to be all alone with no one to harrass... So, hurray AOL. Thanks for giving me the motivation to use Free (as in Free Speach) alternatives to your pathetic services...
Mike
Re:I hate to say it, but... (Score:2)
Greetings!
There's an alternative to avoid the banner ads: Use the Java version of AIM. That's what I use on all my boxes because it works great under *NIX, Windoze, and Mac.
Check the link out at: http://toc.oscar.aol.com/ [aol.com]. You can use this client with your existing AIM account, or you can create a new one and skip the software download step.
Cheers!
EI hate to say it, but... (Score:2)
I'm not trying to seem like an asshole here, but I doubt slashdot would appreciate it if someone came up with a way to mirror and allow posting of all their content without the banner adds to pay for the servers and bandwidth. (Yes, I'm aware one can simply use lynx, or turn off graphics, but the idea is still the same).
I personally love the AIM software. It allows you to communicate with AOL users cleanly and easily, and was what I needed to convince a family member to get off AOL and onto a generic local ISP.
AOL has provided this service to the public, which you would otherwise be paying $10/month for, for free. In return they request that you put up with some small banner adds. Doesn't seem like that big of a trade-off. And while I realize that the Linux version is still greatly lacking, it's understandable that they'd like to have money to support their expenses for the service that they're providing.
This kind of goes back to the discussion awhile ago on the EverQuest emulator. Verant spent the time, money, and effort, to develop their client and all the artwork, models, textures, and maps, with the intent that they would be used for their 10$/month game.
While I agree this issue is somewhat debatable, I don't think AOL deserves the bashing that it's going to recieve for this. THEY are the ones who are paying for this, not you.
non-ad-showing clone clients (Score:2)
What ever happened to Open IM? (Score:3)
America Online is committed to extending the benefits of instant messaging technology to as many consumers as possible.
This wouldn't annoy me so much if they didn't keep flip-flopping on their strategy. I suppose that since AIM won't make them any money, they're focusing on brand dilution issues instead.
--Pete
Re:Weird Gaim/AIM problem (Score:2)
I'm figuring it was an AIM bug myself. I had someone not receive a message again yesterday. They were disconnected from the network (physically), but not from AIM.
---
Re:Territorial Pissings (Score:2)
There's no one official Jabber client. You write your own client, it conforms to the standard, it's a Jabber client. Microsoft makes an IM client that conforms to the protocol spec? It's a Jabber client, and every bit as legitimate as everyone else's.
However, Microsoft can also go ahead and finish their current IM-standardization efforts -- when the RFC that they (and AOL, and whoever else) are working on is released, Jabber will add support for that too -- server side, though, so it will work with existing Jabber clients as soon as the server is updated. Nifty, no?
Re:bah (Score:2)
Let's say you run your own Jabber server outside the company firewall, and use ssh's tunneling support (one nice easy way).
If your company doesn't permit outgoing ssh connections, their sysadmin-types need a talking-to.
Re:Just fake the client name?! (Score:4)
...phil
Naw (Score:3)
Re:AOL Instant Messanger Blockage (Score:2)
Infrastructure (Score:4)
Refrag
From 0.10.0 source .. looks like gaim~=~aimwin32 (Score:2)
"en", 0x0004, 0x0001, 0x055};
Re:The response (Score:3)
Do you often have your nuts in your hand?
-thomas
"Extraordinary claims require extraordinary evidence."
False alarm? (Score:2)
::looks at GAIM::
::looks at Slashdot article::
::looks at GAIM::
::signs off::
::signs on::
::looks at Slashdot article::
::looks at GAIM::
::receives message through AIM::
Err... is anyone here actually having problems? Anyone? Please speak up if so. (I am not having any trouble at all.)
For the record, I am connecting through TOC.
------
Re:What's the big deal (Score:5)
With the proliferation of many different messenger systems, all those AIMers are going to be cut off from their friends who use MSN/Yahoo/ICQ. The motivation to use AIM diminishes as other messengers take off. So instead of AOL joining the community at large, they are creating a substantial, yet isolated community. It is a stupid mistake in the issue of a greater diverse internet. A smart move in the issue of keeping a captive audience. But in the end, they are just shooting themselves in the foot because if you are using AOL, you really don't need AIM to communicate to other AOLers but you will need another messenger to chat with your friends on MSN.
AOL just has a large enough ego to think these companies are clamoring to gain access to their herd of people. That may be partially true, but I believe it is more about these other applications trying to give their users as much versatility as possible, something AOL should think about.