The Guardian (and likely everyone else) is reporting that AOL is killing off their instant messenger service. For those of us who never quite got the hang of IRC, AOL Messenger (not to mention MSN Messenger at the same time) was a truly fun way to chat with people we knew in an age before smart phones and SMS. And yes, my AOL screen name wound up becoming my default ID almost everywhere.
An article on AOL's website on Friday said AOL Instant Messenger will be discontinued on 15 December. The program will still function until then but after that, users won't be able to sign in and all data will be deleted. AOL says people with an aim.com email address will still be able to use it.
In a blogpost, a spokesman for AOL's parent company explained the platform's demise as the casualty of the evolving way people communicate.
"AIM tapped into new digital technologies and ignited a cultural shift, but the way in which we communicate with each other has profoundly changed," wrote Michael Albers, vice president of communications at Oath.
Launched in 1997, AOL Instant Messenger was at the forefront of what was called at the time the biggest trend in online communication since email.
I for one would happily trade in WhatsApp, Google Chat, and all of the others for a return to AOL Messenger.
Also at USA TODAY: RIP AIM: AOL Instant Messenger dies in December
(Score: 3, Insightful) by Aiwendil on Sunday October 08 2017, @09:57PM
No, not really, just have added another layer of abstraction.
Not somewhat, that is a hard server requirement right there. (ICQ did a similar thing actually, it tried connect directly first to serverprovided ip and if that failed it went via servers)
Yup, they solved it by using centralized servers :)
So, the solution for this to get to P2P is to add more servers (which means more points that will be breached).
So far havn't seen even a barely working solution in P2P setups (beyond obscurity).
On non-p2 a simple flooding protection or looking for repeated checksums tends to do the job.
Up until someone decides to ddos you, or just ping flood you...
But yeah, this point was a brainfart on my behalf.
VPN is a hefty latency (my ping times tend to be between 1.05 and 1.90ms on average to sites within my country - and yes, I notice the 145ms latency to soylentnews)
Ahh, the stuff that tends to be blocked at isp-level and route badly. :)
No, the issue is that the idea is trivial but the implementation hasn't been solved yet.
Oh, I also forgot - how to best solve it when someone has multiple clients for the same id? (For instance I right now have skype open on six devices for the same account, one machine is purely to gather logs)
(Quite frankly - so far modifying an ircd to share serverlists [with network id for each] would be a lot more useful. P2P servers makes more sense for ephermal stuff. Also could use pgp-signing to solve the irc-services problem that will arise)