A few weeks ago, this pop-up from the "AOL System Msg" started to appear when logging into AOL Instant Messenger using client version 4.8; the last one that didn't require Internet Explorer and worked on Windows 95:
"Hello. The version of AIM you’re using is going away as of November 30th. To continue using AIM, please download the latest version here."
I initially called bluff on this, since AOL had pulled stunts like this a few times before. Today, however, it finally happened: AIM 4.8 will no longer connect to the service.
Now, I'm not going to say that this is of much practical significance. The AIM network is practically a ghost town these days, and I all but ceased using it three years ago simply because none but one of my acquaintances ever use the service anymore. If I'm surprised about anything, it's the fact that AOL still exists at all! Still, I'm a bit miffed: AIM worked so well for so long, it needed a lot less overhead than whatever passes for online chat today (Skype? SMS texting on smartphones? Having a Facebook window open 24/7?), and I'm sad to see one more relic of the Win95 age slip away.
I also suspect that this incompatibility is artificial. If AOL had truly changed its protocol, I would expect AIM 4.8 to time out altogether instead of connecting and throwing me off. As it stands, the client will verify the login, "Starting Services" will appear, and the buddy-list window loads for a split-second...before I'm logged out again and have an AIM message from "AOL System Msg" thrown in my face. I assume that to connect, the server does a "handshake" with data in the client's "proto.ocm" file. Would it be possible to hack this to spoof a more recent version and get 'ole 4.8 working again?
(Incidentally, AIM's ICQ 2002a cousin still works and connects; though I never knew anyone who used ICQ to chat in the first place.)