Slashdot Mirror
The America Online Protocol Revealed
Gods Misfit writes "The America Online protocol(Connecting, Logging In, Joining Chats, etc..) has remained a mystery for most of its life. The only way one could log into their AOL account was via the AOL software. A few months ago, some people set out to break down the AOL protocol and open the door for alternative America Online software. This document is the result: The AOL Protocol.
A sign on example for Visual Basic programmers has been written and is available here." I suspect a fair number of people never try Linux or one of the BSDs because they're moderately happy with AOL as an ISP, and switching OSes would mean switching ISPs at the same time. A shame that AOL doesn't make this kind of information more easily available.
Not everyone can read .wri, a .txt and/or .pdf would be nice.
As much as I dislike AOL, I understand many people like it. I'm glad that one more proprietary thing has been broken to help people. I just hope this doesn't make AOL accounts any easier to hack into, as I've heard. I don't know the exact nature of AOL's login process, so does anyone have any idea what the chances this can be used as a malicious hacking tool are?
Two things are infinite: the universe and human stupidity, though I'm not yet sure about the universe. - A Einstein
Wouldn't this be considered illegal under the DMCA, since they reverse engineered AOL's proprietary protocol? If AOL had meant for it to be public, then they would have put it out themselves.
I suppose there might be a handful. A small handful. Not "a fair number".
How long until they make an arbitrary change that breaks all the "new" clients? While I don't understand why they'd care (the customer is still, in theory, paying for the service), the fact that they've kept it secret for so long makes me wonder if they'll let this slide. Not to mention their annoying policies regarding the AIM client (how many times did they break everybuddy?)
Send your friends messages of love at fuck-you.org
...was keeping AOL users ON Windows? Now they can spread....
OtakuBooty.com: Smart, funny, sexy nerds.
Considering AOL wasn't exactly thrilled with "Unauthorized" versions of their messaging software (Jabber) I wonder how long it will take them to have a stroke over this.
BRENT ROCKWOOD, EST'd 1975
I wouldn't try AOL even with my own customizable "protocol". I'm quite happy with a local provider.
It's not AOL that's keeping me from trying Linux on the desktop - it's that my fiancee needs to use the PC as well, and she has enough trouble with Windows... (okay, that and the games)
You find this humorous, centurion?
Does this mean a stronger, better, more annoying version of AoHell will be released?
AOL on Linux.
Isn't that like having a red neck teach physic's at MIT?
guvf vf zl fvt
Seriously, I don't know why whenever something gets posted on /., the sentiment "Finally! Now the average user will use Linux!" has to be used. The simple fact is that the average user isn't savvy enough to use it, and there is a large group of users who ARE savvy enough to use it, but find setting it up to be a big headache.
America Online isn't going to be Linux's killer app.
(ducks behind asbestos wall)
Uh, AOL runs on linux also, think Gateway kitchen device, think Playstation 2. It's there, it works, they've shipped. You just can't download it yet.
But I would go as far to say that the type of people who like computers very simple, and very task oriented wouldn't want to install Linux on their desktop for more than one reason.
1) maybe AOL
2) their computer likely came with windows and installing a new OS is beyond their skills
3) linux desktops are still not dumbed down enough. Come on, TiVo is easy to use, my playstation 2 is easy to use, why is my computer so hard?
Joseph Elwell.
I suspect a fair number of people never try Linux or one of the BSDs because they're moderately happy with AOL as an ISP, and switching OSes would mean switching ISPs at the same time. A shame that AOL doesn't make this kind of information more easily available.
Probably very few people using AOL would consider playing with *nix. If you're playing with other operating systems, you've probably already outgrown AOL. You're not burning ISOs from Redhat that you downloaded via AOL/dialup. If you're on AOL, you're happy and content and most probably don't want to be switching ISPs or playing with a new OS. Besides, just because you're on a new OS, doesn't mean you have to get rid of your M$ partition and AOL as your dialup. People can explore the goodness of *nix on that old computer in the closet they feel bad about donating to the Salvation Army.
The AOL protocal was a nice reverse engineering hack. Nice work fellows. AOL didn't make it more freely available because it was a proprietary technology. They'd prefer to keep it to themselves or license it out.. otherwise they would have used a published standard.
=steve
--- rapper/producer/bachelorette party stripper
when you have to use aol's software to log in to aol, you have to look at the ads and crap that they want you to look at. aol is just one large, happy advertisement. with the possibility of being able to log into your aol account without having to use their software, they'll lose some of that advertising exposure, which means that yes, they will have kittens over this. whee.
"Why is all this crap here?" -- 4-year-old Brandon
More technical info about AOL can be found here.
A shame that AOL doesn't make this kind of information more easily available.
This reminds me of the same sort of complaint found in a recent Slashdot article on Microsoft. Do you really think AOL/Time Warner wants this type of information spread around so they can lose subscribers?
It's not a shame, it's good business sense.
I like fire ants. They are very spicy!
Why?
WHen you use their client, they control eveything you see. What you can do. Think - they could force commercials or ads down yoru throat (and they will). If its opened up, you know people will just chose not to accept them.
The protocol will change very soon. :)
I suspect a fair number of people never try Linux or one of the BSDs because they're moderately happy with AOL as an ISP ...
Let's face it, the reason that AOL and Linux don't mesh isn't because there's no AOL-Linux interface. It's because people who use AOL use it for a reason - it's got a happy, friendly, push big rainbow colored buttons, don't-cut-yourself safety-scissors interface. Love 'em or hate 'em, it's what they do well - an interface so simple that even grandma can use the demon box.
Linux is still, even in its most user-friendly form, a system that requires you to get some dirt under your fingernails while you use it. It's still a power-user OS.
There just simply isn't a big overlap between the types of people who use AOL and the types of people who traditionally run Linux.
If it ain't broke, it doesn't have enough features yet.
Actually, it doesn't surprise me that they don't make it available. If they release that information, they lose an edge they have on joe average as an entry level computer user. How many times have you talked to someone who wanted to show you something that was on the 'internet' and in reality, it was something that was on a section of AOL? AOL has done a really good job of making a 'controlled' section of the internet we're they control the information. By having only one style of software they have more control also. Would YOU just want anything to connect to YOUR server and have authorization privleges? Of course AOL is very much based on server side scripting, and a butchered version of html. All aol sections are addressed with an aol://xxxx:xxxx:asdgfsadgas type link... a mix of alphanumeric strings, etc. Essentially it's THERE style of html distributed through a browser.
But in the end the bottom line is profit. You don't want to allow people to get onto the internet where you can't 100% control what the first thing they see is. AOL gives the illusion to first time joe averages that it IS the internet. My mom spent months on AOL without even using the actual internet and she thought she was on the internet. It's marketing genius. You control their access, you control the way content is shown, you give them places to spend their money and control the ways they communicate. Everyone does it the same way, so everyone is having a similar version of their own experience...
The AOL designers aren't dumb IMHO, sure it's not the service that I want as my ISP, but when it comes to marketing, they know what their doing...
For awhile they were going to make it so you could use them as a 'traditional' isp using Dial-up, but I don't think that anything really ever came of it.... I guess AOL users just like hearing 'WELCOME, YOU'VE GOT SPAM, (I MEAN MAIL)...'
[Something witty and intelligent should have appeared here.]
{Traicovn}
They fear that the change they make will kill their expensive toy and force them to go talk to a more computer literate friend who will once again berate them for using the most expensive ISP with the worst service.
I suspect that this doocument will be the source from which nasty new AOL hacks will be based. And now that it is out it is in very immature hands.What this will do. (maybe) is covered by point 8
Not that it matters to me because I don't use AOL
I used to have a cool sig, back when I cared
I don't know about the ISP protocol, but people have cracked the AOL Instant Messenger protocol, so you can use AIM in Linux (along with various other protocols, it's fantastic). It's called Gaim, and it's available over at Sourceforge (link here). Happy chatting!
"Now gluttony and exploitation serves eight!" - TV's Frank
So who is ever go to put time into this? Anyone who can write something like this is probably not interested in dialing up to AOL, and the 'ease-of-use' folks who can't write it probably appreciate the AOL interface.
Other than hacking into AOL for the fun of it, this is pretty useless. It's a good blow for the cause of open protocols and file formats.
I suppose there might be a market for a simple AOL client, for those who use it for portable internet access.
Public recognition of Visual Basic as a programming language by the /. crowd! Millions of Microsoft programmers, no longer afraid to talk about work at cocktail parties!
Woot w00t w007.
I wonder if this could be used to make a login script for my sisters AOL DSL account. You have to login to AOL before you can use any tcpip...the modem says it is connected though.
Why does my sister use AOL DSL...? I dunno. But she's an air traffic controller in the US Navy so I will forgive her for now.
In my opinion, logging on and enjoying AOL's so-called services was never 1/10 of the problem as their stupid crappy propritary mail system.
Back around 1996 or so, I was part of an AOL beta program that released a MAPI interface for AOL mail servers. IE, you could add the AOL mail server to your Outlook config and download your AOL mail right into Outlook.
Of course, the AOL exec freaked out when they considered how many eyeballs their advertisers would lose if everyone uninstalled the AOL client and kept their mail via Outlook. So the program was canned, and I was unfortunately too short-sighted to save a copy of that MAPI tool before the area was closed down.
Ever since, I've been trying to get my sister/parents/grandparents off AOL. Not to mention that AOL never supported Windows NT because they couldn't figure out how to install their stupid AOL Adapter TCP shunt thing. So for years my relatives were forced to run a crappy 16-bit (Win 3.11) version of the AOL client for the sole purpose of checking e-mail.
AOL's mail service is terrible but a lot of people don't want to change their e-mail addresses. If you really want to do a great services to help newbies move beyond their AOL shackles...please, I implore you:
A) Reverse engineer the AOL mail protocol so that external programs can at least READ AOL mail (sending, unsending, and AOL custom features are optional)
B) Reverse engineer the AOL mail database (local copy of stored mail) so that it can be imported into another program.
Even after I got a couple family members to switch over to Hotmail, they still have to use the AOL client to read their old mail. It's that or save it all as flat text and lose all the important header information.
Also, a bonus to reverse engineering the AOL mail database would be the ability to sync mail with your Palm. The AOL client for Palm is 400KB and can only dial-up, not sync.
Please post reply if you know of any project working on the AOL mail/database formats. Thank you!
- JoeShmoe
-- I wonder which will go down in history as the bigger failure: the War on Drugs or the War on Filesharing
A shame that AOL doesn't make this kind of information more easily available.
A large amount of AOL's income is from advertisements. You're bombarded by them from the second you sign on, in every window you open, till you sign off. Salon might have adopted the mandatory ad viewing my friend, but they didn't invent it. AOL has been using these for years. Subscribers are forced to view several ads of "special offers" before they can even begin to navigate through the "service." It's like playing Where's Waldo trying to find the Close button on some of these windows. AOL doesn't want third parties designing software to be used on their networks because it would be detrimental to their advertising income. Fewer members using their software translates into fewer eyes viewing their ads, which reduces the value of their ad space. It's a safe bet that AOL will do everything in its power to ensure that people continue to use its software.
https://www.eff.org/https-everywhere
As a single person without children I've never had any desire to use AOL, but I know lots of AOL users. There is at least one good reason to use AOL. Years ago internet access was $20/month and that gave you one email account. Meanwhile, AOL gave allowed you to create many accounts. Which is the better choice for a family with several children? One account shared between mom, dad, and all the kids, multiple accounts with some (possibly outrageous) surcharge per POP account, or one AOL account with lots of screen names?
Even now, most ISPs will give you a couple of POP mailboxes for $15-$20/month, but few if any provide the ease and convenience of creating new "screen names" that AOL provides. Try telling a 12-16 year old girl that she can't change her screen name to avoid some pre-pubescent geek who's harrasing her via email.
Here is the simplified version of the protocol:
void AOL()
{
while(connected)
{
send_advertisements();
monitor_browsing_habits();
monthly_fee++;
if(bandwith_to_spare)
send_internet_data();
}
return;
}
Life is the leading cause of death in America.
A bunch of clone clients have been trying to get hooks in for years to no constructive end because AOL actively tried to BLOCK other clients from connecting. If I remember correctly Jabber and MSN had it working for a while until AOL forced them out by altering the protocol. Most lately I believe they've been doing it with executable checksums. We might have figured out the protocol, but theyre just going to change it up again as soon as foreign clients start connecting in large numbers.
Some old coverage of this can be found at ZD. Theyve got a whole site called "InstantMess" that talks about how AOL refuses to discuss an open format because they want to lock users into their app.
Recently Trillian (www.trillian.cc) has succesfully done it. I think they got around it by using whatever method the JAVA aol clients (AIM express, Quickbuddy).
Id love to see an open standard, but without AOL on board its useless. Its sad really - that the unwashed masses are dictating the standard for the rest of us.
I can't wait for the first Linux-client. Why?
The only thing about AOL that's worth anything are the chatrooms. Unlike IRC, you can actually meet real, low-self-esteemed, fat chicks who'll put out for anyone willing to pretend to listen to them whine about how no one likes them.
I'd better stock up on condoms and twinkies, big dog is gettin' let out of the house...
If you were me, you'd be good lookin'. - six string samurai
Why couldn't you set up a linux gateway? Get your local ISP (or university service) set up roomie's Winbox with a tcp/ip card with linux as default gateway. Then install/setup AOL with 'Bring your own access' or whatever they call it. Heck, he can even save $2 per month that way.
Jesus was all right but his disciples were thick and ordinary. -John Lennon
(710)123-4567 is my phone line.
(456)123-4567 is an AOLnet dialin. Numbers mutilated to protect the guilty, of course. A few years and many many area code splits ago, we were all one code. More than a few lusers are confused by Windows' concept of "dialing location" and area code settings, and apparently more than a few of them are AOLers.
I get silent phone calls all the time, sometimes several in a row. Without fail, if I answer with a carrier, they connect.
Sometimes if I send "login:" they talk back. I've never bothered to get farther than that.
I've long dreamed of hacking up a barebones AOL emulator, just enough to push them a page that says "You dumbass, your area code settings are fux0red!" and then play some fart noises before dropping them.
Yeah, this is gonna rock. Not only do I get to fuck with their heads, but I get a free supply of AOL l:/p: pairs delivered to my desktop! Never know when those might come in handy.
Even though AOL is not targeted at the Unix/Linux user. There could be good reasons why a Unix/Linux guy could want or need to use AOL.
1. There are many kids out there who want to learn Linux and are allowed to setup a duel boot systems. But their parents are paying for AOL as an ISP and will not switch. So not at least they can switch the os and pay for one ISP.
2. Emergancy Internet connection. Every once in a while your Internet connection goes down at the ISP level and you need a quick short term internet connection. Hay AOL give 1000 hours free internet for a month. And if you like me there are hundreds of those CDs with trial passwords around. It is tempoary free internet. Hey it may suck but it is better then nothing.
3. Simular to #2 many new computers come with a year of Free AOL. You got the computer at a good price why pay for an other ISP when you can get AOL for free for a year.
4. AOL only services. AOL has some services that other ISPs dont have. Although they are ways around them but sometimes they may be covient.
5. The @AOL.com E-mail address. Those are easy to remember for most people (becasue they use AOL). And with the e-mail they can find your IM name quicker.
I dont directly use AOL (I use RoadRunner own by AOL/TimeWarner) nor do I ever want to use AOL. But I just wanted to state they there are reasons why a UNIX/Linux person would want access to AOL. and they are people who can use Linux who dont care much about the proper geek way, they just want a good OS, or just to try something new. To say that All AOL users are Unix Ilerate or will always be that way is a gross overstatement.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
There is a work-around to AOL's proprietary email protocol. I think it's called e-netbot, and it works by connecting to AOL webmail, and downloading messages into Outlook Express. The program itself uses Internet Explorer components.
A Linux user logging into AOL would be like an MIT professor showing up on Springer.
Here is the file in PDF, rather than "write" format:
P rotocol.pdf
http://www.flyingbuttmonkeys.com/mirrors/The-AOL-
Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
There are not any.
The protocol may be protected by copyright, patent, or as a trade secret.
Reverse engineering of methods described in copyrighted material is legal.
Reverse engineering of trade secrets is legal.
Reverse engineering of patented inventions is illegal.
Bypassing copyright protection schemes through reverse engineering is illegal.
Reverse engineering protocols is similar to what the SAMBA team does already - of the NTFS team, or the VFAT team, or the HFS team etc...
Because this isn't directly a copyright issue.
The DMCA makes breaking a copy protection mechanism illegal.. which this isn't.
Yes, this is very, very good. That's a very smart idea. Seeing as how AOL caved to the pressure to have a webmail system, it seems only logical that someone would rip apart the HTML and figure out all the FORM POST commands necessary to fill in the proper boxes on AOL's mail page.
http://www.enetbot.com/ for those also curious.
Pity it's $20 shareware, but this is very good. That takes care of request A from my post...now can any clever soul provide a solution for converting/importing previous mail?
- JoeShmoe
-- I wonder which will go down in history as the bigger failure: the War on Drugs or the War on Filesharing
This has nothing to do with instant messaging.. it's about the actual AOL signon procedure.. not AIM.
And trillian rocks.... to be sure. Needs some UI work.. some stuff you really have to hunt for. Needs proxy support.. and needs file transfers to work properly.. but otherwise, it's superb.
Of course, I can see why AOL doesn't want people doing this - I used this mainly as a tool for migrating to POP3! I would check AOL email once in a while, and whenever there was anything other than spam (rare) I would reply to it from my POP3 account.
sulli
RTFJ.
- Because I'm a poor college student who's parents are still on AOL. Why pay for a second ISP when there's one available? Linux isn't a solution for them, but if I could dial up from the Linux Box in my room (Linux on the second cheap computer? I have the second cheap computer!), that'd make my life simpler.
- Who wants to reboot to a Win/9x partition, connect, DL kernel patch, reboot to linux partition... etc...
- Remember that AOL offers a nation wide network. So these days, that's nothing new. But think about moving every few years, and doing this six years ago. Want to hunt up a new ISP every time you move?
- If you've managed to keep an ISP (and e-mail address) for a few years, would you want to go through the hassle of chainging? There are alot of long time AOL users who cling to AOL just to keep their e-mail addresses. As they grow more comfortable with their computer they may even grow towards Linux. Being able to keep your ISP would make that decision easier.
It's not about converting windows users to Linux because now they can keep AOL (though I think you may see some of that). It's about letting power users simplify thier life. (Single ISP for both the kids running windows and parents running linux (or the other way around!))Another possible effect could be an "Offical AOL For Linux". Which would be easier and less stressful in the long run, continually fighting off the third party connections, or writing an offical port to get people away from third party connection software?
If I can't see it in Lynx I'm not interested.
How many self-respecting Linux users would want to use AOL? Granted, there is a small appeal in saying "Hey i got AOL to work on Linux," but I imagine it would sorta wear thin after a minute or 2.
My other sig is funny!
Better be careful. AOL may consider any unauthorized use of their servers as computer trespass - even if you are an AOL subscriber. (They can say via license "you are only authorized to use our servers using OUR software.")
Thus, this information is aiding and abetting computer trespass. Slashdot and the authors may be liable retroactively under the new terrorism legislation (depending on the scope of the hacking provisions) with mandatory life sentences for giving aid to terrorists.
By advocating an open AOL client for linux, given AOL's licensing terms, you are trying to change intellectual property policy, thus are "trying to change government policy through computer trespass" under the PATRIOT act, USA act, or whatever they are calling it now.
While this scenario seems crazy, keep in mind that this is literally within the scope of (some versions of) the terrorism legislation.
Conclusion: "You've got jail!"
The better alternative would be an operating system that supports secure and easy to setup multiuser operation. This will also make sure your kids can't read any of the files you don't want them to see, etc. If the setup were simple enough, as an added bonus control of the computer would move back from the kids to the parents. Things like restricted use of games and restricted software installation don't have to be hard to use, they just happen to be.
Multiple e-mail adresses are not a serious problem, as there are so many freemail offers and anyway your local ISP might also want to offer "subaccounts," if it were easy enough for average users to setup so they won't call tech support all the time.
Is any such operating system available? Unfortunately not. Windows XP, from what I have seen so far, is simple to use and setup, but horribly insecure (e.g. non-password protected users with admin rights are created during setup) and tries to force you into using Passport, Digital Rights Management etc. Linux, on the other hand, is secure, but much harder to setup and maintain. There are also only very few games available. Mac OS X might be an option, but Macs are quite expensive for a family computer, and as with Linux, few games are available.
Sig (appended to the end of comments I post, 54 chars)
/dev/aol anyone?
You're absolutely correct. Not only do they have a captive audience, but they have an audience about whom they know a lot about.
So, if the problem is "we can't use AOL from Linux, etc", then why don't they fix it? What's really stopping them from putting together a cross-platform Java (heck, or even C-based) GUI? That way, at least no one has an excuse to work around them.
I do think they'll be forced to stomp on anyone producing other implementations of their client. Long-term though, it's not a battle they can win (especially if Linux does start getting used more by average/non-technical users).
Please mod this post only if you think others should/n't read this. I have enough ego^H^H^Hkarma. Thanks!
So, here's the premise. AOL isn't available on Linux or BSD, therefore people who are happy with AOL but considering switching to Linux/BSD would not switch, because AOL isn't available.
There's just one problem. How many AOL users are even aware of the mere EXISTANCE of Linux/BSD? The people who use AOL when there are other options available are the same types of people who use Windows simply because that is what is loaded onto their computer when they bought it. The vast majority of AOL users aren't going to bother to find out whether other OSes would be good for them, considering that they haven't bothered to see whether ISPs are better.
-Jenn
3-6 months - someone actually writes a fully functional OpenAOL client that people are willing to use.
+ 2-3 months - AOL figures things out, issues cease and desist letters, starts blocking OpenAOL clients.
+ 1 week - OpenAOL figures out new protocols (return to previous step as needed while Lawyers OpenAOL users)
+ ??? months - AOL finally wins in a DMCA case that no one cares about because by this time everyone is using DSL and realizes that AOL and is another weight throwing mega-corp.
Note: AOL will probably blow a LOT of money fighting this too, that's why this is so humorous to me... I look forward to seeing ideas like this show up on rtmark.com.
Hammer of Truth
The AOL protocol described is a modification of the old (1984) PlayNet error-correction and data communication protocol I devised (with some input from Steve Bohram, but it was mostly my design based on the Tannenbaum networking book).
CRC-16 was used because modems (300 baud) didn't have any error correction, and we could use tables to process the data 16 bits at a time without using too much memory or CPU (the servers were 12MHz 68010's).
Packets all ended in hex 0D because we were using Telenet and Tymnet X25 dial-in pads in line-buffered mode, because we were charged by the packet. We also munged the other fields to avoid 0D (that may be gone now). Also, they were limited to 256 byte lines; thus the length byte instead of something longer.
Bytes 6 & 7 (which the author doesn't understand) are sequence numbers used in the sliding-window error-correction protocol.
The two-character ASCII prefixes were the actual message types for data packets, and were the input to a multi-tasking state-machine language. EM for example was (IIRC) part of email, perhaps to turn on the 'MAIL' icon. (I forget all the codes, I'm afraid).
Z on the front seems to be an AOL addition.
I was at PlayNet from Feb '84 to Feb '86 (when we declared bankruptcy). AOL licensed the PlayNet software from us for a song when we were running out of money, and rebranded it QuantumLink (and made minor mods, many of which we did for them).
PlayNet ran out of money in Feb '86, though the service continued to remain up for the 1500-3000 subs for another year or two.
PlayNet got a cut of AOL gross revenues until they finally wiggled out of it right before launching America Online (a port of the software to the PC with considerable enhancement), at which point PlayNet's bankruptcy was closed.
The servers were Stratus fault-tolerant machines, and as of 3 years ago they were still using them.
They didn't manage to change the 10-character limit on usernames until a few years ago. That limit was because of the 40-character width of the C64 screen, a ',' between each name, 16(?) characters for the room name plus a space, and we wanted N (12? 15?) users in a chat room. The result was that there were 10 characters available for the username.
The algorithm in AOL for selecting usernames that resulted in JohnQ12345 was also part of the old PlayNet (server) software. Also the default initial passwords for "marketing" accounts (i.e. the free disks) of "word-word" is another thing thought up over lunch at PlayNet that still hasn't changed.
Many things have been added & changed - but far more than I ever expected remains the same. I figured they'd dropped the ECC protocol ages ago.
-- Randell Jesup
Well AOL the company isn't so hot because they didn't give away this information. However the main reason that AOL stinks as an ISP is because in order to connect you have to load this enourmous hog of a program into memory. With a normal dial up isp you use dial up networking, and with a NIC you load nothing. If we could write a very small program that simply connects to aol and establishes an internet connection, that would be fantastic. People could still use AOL, but it wont suck, as much.
The GeekNights podcast is going strong. Listen!
My family were AOL users for a year or two, long enough ago that we used the DOS-based interface. We didn't stop, either, until after I got a dialup University account and they got a commercial PPP account in 1995.
I've been using Linux since 1997. Perhaps the current crop of AOLers would also require a couple years "transition" period, but that doesn't mean it won't happen.
I keep hearing people say that the reason there are no alternate AOL clients is that AOL changes the protocol if it decides people are using alternate clients. However, as far as i can tell, the only way AOL can see what client you are using is through the identification packet that is sent during logon. If the client is designed to properly fudge the identification, AOL would never know, and in fact they'd think you were using a plain old AOL client.
Can someone please tell me if i understand this properly?
Beware of he who would deny you access to information, for in his heart he dreams himself your master.
This spec could be terribly useful for anyone who wants to write a program to migrate a user's e-mail (or even their settings, etc.) to a new service.
Or better yet -- think about this: with this spec, an AOL module could be written for fetchmail. Suck down the mail from that old AOL account and deliver it via SMTP. Cool, eh?
Tired of FB/Google censorship? Visit UNCENSORED!
Reverse engineering of patented inventions is illegal.
Could you explain this one? Patent law makes it illegal to make use of someone else's patent as your own, but I don't see how looking to see how it works would be illegal. Especially since patents are published anyway.
Huh? I'm not sure how you can do this. If AOL sends out some big nasty M$ patch as it's update, what are you going to do? I suppose someone could set up a rig to automatically update observed protocall from an official and updated AOL client. If they then set up a Deb, everyone could get the updates as a chron job. Whew! What a lot of trouble for AOL's dinky client.
For some reason, I still give AOL $10/month. It's a junk mail account until I get a reasonable TOS that will let me serve my own mail. It get's about 30 spams/day, and is utterly useless for real mail, despite AOL anywhere that actually lets me read it. The only AOL software I have is AIM. Will they ever see the light?
Friends don't help friends install M$ junk.
Back in 1995, Claris introduced Emailer, a Mac e-mail client application that could retrieve AOL mail, along with many other kinds of mail accounts. Development was continued on it for about 3 years or so, but it became an orphan when Claris became Filemaker, Inc and divested itself of non-database products. It was neglected and finally end-of-lifed by Apple in November 1998 at version 2.0v3. Most of the team that created it went on to develop Outlook Express for the Mac, which does not do AOL mail because AOL decided to stop licensing out the protocol. I can only assume that AOL realized they could make more money by forcing everyone to use their shitty built-in mail client and bombarding them with paid advertisements the entire time, than by licensing out the protocol to other software companies creating clean, elegantly-designed mail clients.
Six years later, Emailer still works great on Mac OS 9.x, and the original developers do not believe it should break under OS X. I still use it (as do a lot of people) and I still think it's the best mail client I've ever used, because it doesn't do HTML mail. Nothing but pure, speedy text.
~Philly
Grossly overlooked in all the posts I've seen so far is the fact that this also will allow you to write a new AOL server. So you could piggyback on AOLs carpet bombing of free CDs by having people just dial up a new number, and get GnuAOL.
To purchase it is not like spending money but rather it is an investment in the future in a blow against the empire
I recently ran across a site that archived the the old SIDDs music from Quantum link and had a Window s player available to play them.....
This document reveals the "secret" protocol of AOL version 2.5. Version 2.5 was released eons ago. The protocol has probably changed a lot since then, since AOL's current client is on version 6.0.
In addition, this document must be eons old as well. Who claims this is a new document? Why would anyone bother with deciphering AOL version 2.5 at this point? This is ancient info.
If you want more info from other sites, just use this google search.
I loved Q-Link. Maybe it was because it was the first online community I was involved in, but I suspect it had more to do with the community itself. It was small (relative to today's standards), and populated with mostly honorable people. I spent most of my time playing chess, but recognized a surprising portion of the usernames in most of the chat areas. No virtual communities have come near it since. The closest today are well-moderated IRC channels, but these are too small. On the other hand, AOL is too big, rooms don't have consistent community and there are 5 trolls or lurkers for every good person.
I've expended a lot of thought about what led to this type of community, free of trolls and the seedy quality of most chatrooms. I think it came from a couple things:
1. It was new to those participating. We hadn't learned to abuse anonymity.
2. The size was right. IRC channels are too small, while the scale of IRC servers or AOL itself is too large.
3. We paid a buttload for the service. At $3.60/hour the bills racked up quick. No one would pay that today, but it sure kept the idiots out.
It would be nice if someone started an AOL type community that required an application to join, capped its membership numbers (~5000), did not provide anonymity and charged a fee. I doubt it could be profitable, but it might be very refreshing.
Funny how hours after it's released and posted on /., the AIM server (that I connect to at least) is down...
Pity it's $20 shareware
Why is it a "pity" that someone can try to earn a living by writing useful computer software? Should talented programmers write software for free and earn a living by flipping burgers or selling drugs? You should be damned glad that he's made a useful package and is only asking $20 for it.
This whole "all software should be free" crap is really annoying the hell out of me. If someone wants to give away the software that they write for the good of some community, that's very noble, but that doesn't mean that everyone should. I have found that most of the people in the "free software movement" are actually a bunch of leeches that just want to get something for nothing. They don't write software and are frequently just computer users. They give nothing back to the community. But they are the first ones on the FTP site when any new piece of free software hits the platters.
If you like the package, pay the guy $20. Then send him an e-mail thanking him for making it available for such a small price.
Patent law allows the patent holder to prevent anyone from using the patented invention for the purpose of one of the patent claims.
If you do not know how an invention works, and you invent something to do the same thing, you may or may not need the patent holder's permission to use it. If it uses the same invention described in the patent, you need permission.
MY main reason for using AOL is portability in terms of geography. I recently moved ~100 miles,a dn will likely be moving again soon. Until I'm fully settled, at which point I'll probably spring for DSL of some flavor if I can get it, AOL provides an easy way to get online where ever I land, no down time beyond plugging myself in.
-={(Astynax)}=-
"Darkness beyond Twilight"
You ask, why is it a pity?
Because I'm trading one piece of proprietary software for another. Let's say AOL does something to break eNetBot (like they did to MSN Messenger several times)...well I will be SOL if eNetBot Inc. can't fix it in a timely fashion.
Contrary to what you may think, I don't have a problem with someone making money off this piece of software. But can't I still be allowed to lament the fact that the underlying information isn't available? Compare this eNetBot thing to what the original article was about.
Original article is a document explaining how the AOL protocol is formatted, as well as some basic functions to demonstrate usage. Five out of five stars. eNetBot doesn't explain anything but offers me an alternative to the piggish AOL client for e-mail. Nice, but still only four out of five stars. Thus, my pity comment.
I'd much prefer a website that went something like "here's how to write your own interface to access your AOL Mail via the website...oh by way if you're interested I've already written one and you can have it for $X".
- JoeShmoe
-- I wonder which will go down in history as the bigger failure: the War on Drugs or the War on Filesharing
As I stated in my original post, it is a noble thing to release "free" software. But that does not make anyone who chooses not to some kind of right-wing, establishment, capitalist pig. Most of the people who release shareware get an occasional small check in exchange for hours of development time. That's hardly puts them into the same boat with Microsoft.
While there are many good arguments in favor of open source software, some of which you make, the main appeal to many people is that they get something for nothing.
I suspect a fair number of people never try Linux or one of the BSDs because they're moderately happy with AOL as an ISP, and switching OSes would mean switching ISPs at the same time.
You show me five people who say the only thing stopping them from using Linux is AOL, and I'll show you three people who are lying and two who are probably trying it anyway.
Which is all well and good, but it doesn't explain why reverse engineering patents would be illegal.
Patents protect an invention. It does not matter if you think of the same invention independently - you still need permission from the patent holder. That is how patents work.
Copyright protects expression, so if you can implement a method described in a copyrighted work without using the expression, it is legal. This is an appropriate interpretation for most software reverse engineering. If you do not use the source, you are always fine.