I noticed around 1:30 AM EST today, December 15, 2017, that AOL Instant Messenger had disconnected for the last time, apparently right on schedule.
I have been signed into AIM since it became available to non-AOL subscribers in the late 90s, but really, I preferred ICQ, and only started to use AIM more regularly as ICQ lost popularity. Then as Messenger began to surge in use, AIM became a secondary client with those few contacts who still used insisted on using it. In more modern times, I delegated both ICQ and AIM to multi-service software, at this moment, that is Trillian.
Unlike Messenger, I never considered AIM itself that important, it was just a tool I used to communicate to others. Although I’m particularly fond of Emily is Away and its sequel, I felt the software was fairly generic and didn’t offer that much.
When the announcement arrived of AIM’s shut down this past October, I went through my AIM contacts, reading through the screen names of friends that have long since added me on other messaging platforms, plus the endless sea of friends of friends with whom I hadn’t spoken to in over a decade. How would I preserve this list of people? Then I realized I already had, and a lot more.
Originally using AIL and then DeadAIM, any AIM conversations from the year 2001 onward were automatically saved, lovingly preserved in HTML, complete with “Direct Connect” assets, as well as the original AIM colouring, and other formatting fully intact. This archive comprises 8446 files and takes up 345MB of space, hardly anything for what I consider priceless data.
Unlike other communication mediums, even other electronic ones, instant messaging has a huge advantage of being easily saved and preserved. What I have found worrisome of late is that the more modern instant messaging tools are mobile-centric and lack easy logging capability and even worse, have limited options to allow third-party software to do this job for you (aka DeadAIM or Messenger Plus!).
In doing some research for this post, I was pleased to discover that work has been done to try and mitigate this problem (note: I have not tried most of these), for example, tg-export (Telegram), DiscordChatExporter, and WhatsApp Export. Additionally, Google Takeout or Facebook’s “Download my data” will provide archive file(s) of their respective chat services. However, despite being recently updated, Microsoft’s Privacy Dashboard still has no way to export your Skype conversations. A significant problem if you’ve been upgraded to the non-Classic versions of Skype, or are using the built-in Windows 10 application, as they have no local conversation store. Still, with all of these options, they require manual, regular updates to keep your archive current, as well as some degree of trust if the conversations are stored on the server.
After reflecting on AIM’s shutdown today, it seems that when instant messaging services shut down, it’s not about the software, it’s really about the communication and the memories you made while talking to others. When you have those memories preserved, you have the ability to re-visit them whenever you want, regardless if the service is still running or not.
So, the next time you use any instant messaging tool, be sure to consider if you have a way to preserve those conversations, because no service will last forever but your archived instant messaging logs will.
A final note for those interested, my Messenger Plus! logs currently stand at 37,165 files/1.36GB.
Exactly two weeks since the last Messenger server twinkled out of existence comes the announcement of “New Skype“. See Skype’s promotional video below:
At present, this is only an announcement and the software has not yet been released. However from what is shown in the video, I have a few questions, observations and opinions already.Are there any (MSN or Windows Live) Messenger features?I generally evaluate new messaging clients by comparing them against Messenger’s standard set of features. Based on what we know so far, I don’t see any sign of New Skype of backgrounds, custom emoticons, custom fonts, nudge, status (presence), or voiceclips.
It does appear you can set a background colour (and gradient!) for the text of an individual message reminiscent of the background colour functions in the modern versions of Messenger Plus!. However, it’s not entirely clear if this feature expands to allowing you to change the colour of the actual text. In the screenshots, a background colour swapped the font colour from black to white.
Winks (called Stickers) do exist in New Skype and are animated, as well as the normal expected GIF support and Skype’s own “Mojis”.New Skype appears to have a Snapchat stories-like Highlights feature for material you want to share with all your contacts for a seven-day period. Of course, this stories feature is the latest variant of what was once Messenger 2009’s “What’s new?” pane as well as 2011/2012’s social pane.Will all the problems be fixed?
Although I haven’t had a lot of exposure time to the iOS version of Skype, I have had quite a lot of time with the Android version and its whole slew of reliability and performance problems. From time to time, I’ve resorted to uninstalling Skype on my phone because of weird glitchy behaviour that has made the phone unusable or drained the battery. I do hope a lot of these issues have been ironed out since they’ve taken steps to drastically change the client. Additionally, Skype recently ranked as using the most mobile data in comparison to other mobile messaging clients, and hopefully that has also been improved.
Why so much white?
Everyone I have shown the promo video to has had the same immediate reaction I did – there’s just way too much white space.
It reminds me of Office 2013’s attempt at white everywhere in its default theme, which was also unpleasant
Particularly on phones, I can’t think of anyone who wants to be blinded by a mobile screen first thing in the morning or replying to a message late at night in the dark.
Although I would prefer a dark background option, I rather like the look of the current mobile Skype. It retains the classic Skype colour and fits in with whatever native operating system it’s on.
Will it be compatible with current Skype?
I would assume yes, but it’s not explicitly mentioned anywhere. I find it a bit weird that I would have to consider such a question, but Yahoo! had no qualms in completely eliminating its existing Yahoo! Messenger service/contact lists last year in favour of the “new Yahoo! Messenger”.
What about the desktop version?
As part of the announcement is Windows and Mac versions. I do wonder if the Windows version will be yet another variant of Skype. At present, there are two Skype Windows versions – the classic Win32 version you download from the website and the new Universal Windows version (excluding Skype for Business versions as that operates on local servers or Office 365). At the very least, I would assume New Skype to also be written for the Universal Windows Platform (UWP).
I use the Win32 version of Skype, primarily because it does have a (albeit limited) API that ties in with my headset’s software, notifying the headset base of calls, allowing a button on the headset to answer calls and an LED to let others around me know I’m in a call with someone. On top of that, the Win32 version provides a local message history spanning all the way back to my first main use of Skype, I can log into multiple accounts at once and particularly important, my taskbar icon for Skype lights up when I get a message (a feature not available in Universal Windows applications at present).
I don’t think any of the features in New Skype would be compelling enough to lose such valuable features from the classic version of Skype.
Overall, this update appears to be an attempt to “keep up” with the other modern messaging services today and less about trying anything particularly new or interesting. When the New Skype does get released in some form, I’ll do another comparison.
For now though my advice to the Skype team is simple, please, please, please provide a dark theme option.
It is with a heavy heart that I announce that Messenger Reviver 2 has come to an end.
On May 18th, 2017 Microsoft shut down the last Messenger server, preventing Windows Live Messenger from being revived any further.
MSN Messenger first came online July 22, 1999 making public access to the servers available for a total of 17 years, 9 months and 27 days. In the 2000s, Messenger dominated the instant messaging world, being used for text, voice, video, remote assistance, game invitations, and enjoyed both for business and personal use. Massive communities and long-lasting relationships were formed around all around the world on Messenger-related websites and tools like mess.be and Messenger Plus! Even today, despite hundreds of new messaging applications, still no client has yet to match the features and customization options of Windows Live Messenger.
I originally got involved with the Messenger community back in 2001 as part of the Windows XP beta “Associate Experts” program, and quickly became a Microsoft MVP for Messenger, a position I held for over 10 years. After Messenger officially “shut down”, I released Reviver to continue making Messenger connect to the Microsoft servers, and that has continued for over four years, with 98 versions of changes and fixes. The original versions of Reviver only required a small adjustment to Messenger itself, but later on DNS servers, proxy servers and even modifications to Windows itself were needed to keep Messenger working. I also expanded into versions on OS X/MacOS for Messenger:Mac and Adium, as well as aMSN. It’s been quite a ride!
Previously, I have not taken donations for my work but as this is the end of the Messenger Reviver 2 chapter, I feel comfortable now putting out my PayPal tip jar for any who feels Reviver has been useful to them over the years.
Back in 2015 when it first appeared that the Messenger servers might not be available for much longer, I recorded a video of myself going through all the available versions of Messenger discussing and comparing the various features as well as telling some stories about the software. I present it to you below or you can watch it on YouTube:
Although you can no longer use Messenger with the public Microsoft servers, you can continue using the older versions of Messenger on a new private server called Escargot. You can find contacts to add on this forum topic.
You have a several options to continue to communicate to your contacts on what was formerly known as the .NET Messenger network. Of course, you can use Skype, but also Miranda-NG, Pidgin with EionRobb’s, SkypeWeb plugin, or SkypeWeb with other libpurple-compatible clients like Bitlbee. You can also use the web-versions of Skype at https://web.skype.com or on https://outlook.com.
A final version of Messenger Reviver 2 is now available that you can download as a memento which retains all the original features you can explore or even just open it up to play around with the Easter eggs.
If you have looked at the Reviver About screen previously, you would have seen many important people who made Reviver possible when it was first released. For the final release, I’ve also added the people who have been vital over the years I have been supporting and working on Reviver, and I would like to thank them here too: Emil, John, Tasos, Dean, Petri, Jeff, Mariano, Esteban, Peri, Alexis, dx, Jacko, Javier, and Raul, thank you for your friendship, endless discussions about Messenger, many late nights and supporting me and my projects.
Additionally, I would like to thank Patchou for creating Messenger Plus! Plus! was the cornerstone of the Messenger community for many years, indispensable for adding missing vital Messenger features and responsible for many relationships and careers for so many people. Furthermore, I’d like to thank wtbw for always being available for reverse engineering assistance and pointers.
Thanks to Valtron for building the new private Messenger server and giving Messenger continued life.
Finally, a special thanks to all of you who have been users of Messenger Reviver 2 for so long. You have made this journey a great and memorable part of my life and I greatly appreciate all the kind words and support over the years. Please stay in touch! You can reach me on the new Escargot server by adding the user email@example.com, on Skype by adding trekie, my website, the forum, or here on this blog.
I think it’s appropriate to end with my favourite wink, the UFO, which can be both a hello and a goodbye.
At approximately 15:45 UTC, the Messenger bn2 servers have stopped responding. Investigations are still underway but you will be unable to connect.
You will receive the following possible error codes: 80072efd, 81000306 and 80072efd 81000301.
If you are still signed in, do not sign out or you will not be able to sign in again at the moment.
EDIT: Scanning through IP ranges hasn’t found a suitable replacement, Butterfly Messenger and the Windows 8.0 client do not appear to be working either. Skype is still working.
EDIT 2: Also of note, if Messenger cannot be restored, all focus will shift towards the Escargot server and continuing its development. Visit the forum for discussion and contacts to add.
EDIT 3: After more scanning and hoping, there’s no sign of the public Messenger server. Unfortunately this means, Messenger Reviver 2 support will have to end. If you haven’t already done so, please read my final Reviver 2 post as I’ve tried my best to pay tribute to a great messaging client and service.
What a dizzying four years, but Messenger is still (mostly) usable. Unfortunately more features such as groups (with a workaround) have stopped working, and conversion to Office 365 on Hotmail has caused a multitude of contact list issues, even for Skype-based Messenger users.
In case you haven’t been watching the forum, recently the ever awesome valtron has put up a Messenger Protocol server for older versions of Messenger as the Microsoft server stopped accepting older clients back in 2015. Give it a try!
At what is no surprise to anyone, the Windows Essentials have disappeared from the Microsoft servers.
I did prepare for this situation for Reviver use and the Essentials installer files have been saved. However, this does mean that installing Messenger for the time being will now be a larger download at 100MB.
Additionally, not all the languages will be available for the next few hours, if there is one you are in need of right now, please let me know in the comments and I’ll move it up in queue. All languages are now available.
This afternoon Microsoft account based services like Messenger, Skype, Xbox, Outlook.com and others are experiencing intermittent issues.
In Messenger you’ll get error code 81000395 when you try to sign in. Additionally when you do sign in, contact lists may be incomplete.
Just keep trying and it should eventually allow you to sign in.
In the heyday of Messenger’s popularity, I had very little reason to use any of the other instant messaging services on a regular basis, because (almost) everyone used Messenger!
However, today’s XKCD comic expresses my current situation perfectly:
To further explain, here’s a screenshot of the messaging section of my taskbar.
There’s at least nine applications for instant messaging, not counting that some connect to more than one chat service. Within each application, I tend to have a completely different group of contacts, and some are used more so for audio, group, or exclusively text communication.
Although over time I’ve become more accustomed to knowing which contact is trying to talk to me on which application, and the required CPU and memory usage for each application hasn’t been too noticeable in general usage, searching for information can be quite difficult as the message history for each contact usually can only be searched within the application or service itself (or virtually not at all, Google Hangouts).
Recently Microsoft has shown that they are working on a feature (called My People) for Windows 10 that would pin contacts to the taskbar instead of individual applications. The feature has been delayed and may not work with existing desktop applications (which should be the subject of another article), so this may or may not help the situation.
Messenger on its own originally supported both the .NET Messenger Service/Windows Live and AOL Instant Messenger, and you can still see the basis of this if you hover over a contact in Messenger 2012 (look for the Networks: heading).
Additionally, Messenger originally supported a full API back in the 90s to allow others applications to fully communicate through Messenger without evening opening the program. This was quickly abused and scaled back slightly but the API is still usable and was made use of in tools like Messenger Plus!, Outlook, Outlook Express and others. Almost no instant messaging applications support this level of control now.
I’m curious how many messaging applications others use, so I’ve made a poll on the forum where you can indicate which applications you actively use on your PC.
If you use Windows 10, no doubt you have updated to the Anniversary Update (Version 1607, build 14393) which has a built-in Skype app called Skype Preview.
After using Reviver to revive Messenger on the new version of Windows, you may notice that Messenger will tell you you’re signed into multiple locations with the same device name.
This will happen if you use your Microsoft account to sign into Windows and the Skype app will automatically make use of your Microsoft account to sign you into the .NET Messenger network.
The biggest problem with this is that you’ll remain signed into Messenger, even if you’re signed out of Messenger or your computer is off as the Skype app operates on the Microsoft servers. Additionally, even if you use Messenger to force the Skype app to sign out, the app will eventually sign you back in again on its own.
Thankfully you can choose to sign out of the Skype app and use the real Messenger client exclusively. To do so, just head over to the Start menu and click on the Skype Preview tile (or find it on the applications list under S).
When the Skype app opens, choose the hamburger menu button in the top corner and then choose your name at the bottom.
You’ll then find a Sign out link under your name and info, clicking on the link should sign you out and then close the Skype app automatically.
Now you’ll only be signed into one location.
Signing out of the Skype app has been maintained through the insider builds, so you should hopefully only need to do this once. You can always start the Skype app and sign in again if you would like to try the app at a later time.
As I don’t believe the software or servers for DeltaSync are a component of the new foundation of Outlook.com (Outlook Web Access), it’s not clear how long DeltaSync will end up staying around.