Frequently Asked Questions
A user on MSN Messenger can speak to someone using Yahoo! Messenger, and that same person can also be speaking to someone that's using AOL Instant Messenger or MySpaceIM (once they're implemented of course :P). It's all one central service. They near-seamlessly interoperate, even if their original services didn't operate that way.
Modern and retro protocols alike are going to be supported. You can see what clients we currently support on the Supported Clients page.
For the retro protocols, of course, Crossmsgr acts as a full revival service for the clients that used them.
Because of the nature of this project, it's experimental, so keep that in mind. And also, it's still in Alpha. There are going to be bugs. If you find them, please report them!
All components of Crossmsgr are open source and available on our two Git organizations, available here and here. This includes all client side and server side components.
Contributions are greatly welcomed.
This also helps if Crossmsgr is ever in a position where services have to shut down, ensuring that the clients we support are not lost forever. After all, that's what real preservation is :P.
You can enable these manually while making your account, or later on in your account settings.
We will never beg for donations, or paywall any functionality of the service, ever. Crossmsgr is and will remain 100% free to use, no strings attached. No selling your data, no ads, no paywalls.
If our financial situation becomes so dire that it's either paying rent or keeping the servers online, then we may open donations. However we don't see it ever getting to that point. Hosting fees are manageable right now.
We run banner and text ads for projects and websites that we think are cool + user suggestions, but these aren't for monetary gain. We do not, and never will run "proper" ads on the service, site, or anywhere.
If you're on Windows XP - 7, make sure only TLS 1.0 (and/preferably 1.1/1.2 if available) are enabled, and update your root certificates. You can do the latter by installing Legacy Update. It'll also make Windows Update, activation, and other things work again.
If you're not using Windows, follow the equivalent steps for your operating system.
One more thing for Windows XP users: Service Pack 3 is seemingly required for HTTPS connections to our web server to work. Make sure that is installed as well.
If all else fails, try WebOne with our configuration file.
To make interoperability work between these two types of clients, we do this as a workaround.
We send out notifications to all connected users notifying them of this, as well as a countdown to when the server actually goes down.
Once it's complete, you'll be able to sign back into Crossmsgr.
Maintenance periods are going to be common for now while the server is still in active development.
If you run into a false positive, please contact us with all details; mention what filtering/antivirus/firewall software you use, and the specific affected domain(s). Preferably, also link us to where we can file a dispute/false postive report with the creator of the software.