Most of my friends are on stovepiped chat systems now. It's really annoying because chat providers have pretty much stopped providing third party APIs anymore so you have friends spread across Signal, Telegram, Whatsapp, Tencent, WeChat, iMessage, and whichever chat system Google is using this month.
I seriously miss the days when all of them would be in the same app no matter what service they were connected through.
So, aside from Jabber, IRC, and the AIM TOC protocol (which was the weaker version — we used OSCAR, which was not open), we had to reverse-engineer most of the protocols, and keep up-to-date with changes. Often these services actively tried to block us, and we would spend weeks or months working around their changes. Yahoo was notorious for this.
It's not entirely different than the current situation, in that regard, but there was also less security baked in on the older services, and much of the protocols were in plain text.
While I'm out of the IM game (gaim?) these days, I'd be very interested in any modern attempts to reverse-engineer these modern services, and whether the pushback from companies would be any different.
Well, sadly there's the fact that Discord has finally pulled out the official laser beams for the alternative client scene, such that Cordless recently called it quits: https://github.com/Bios-Marcel/cordless
Ripcord (https://cancel.fm/ripcord/) doesn't seem to be giving any indications that it no longer works, but ¯\_(ツ)_/¯ (and probably for fairly large values of ¯\_(ツ)_/¯ too)
My computer is generally only able to handle one Chromium-based HI I EAT ALL YOUR RAM AND GPU, so I basically treat Discord like email as a result of the no-3rd-party-app policy. Given that the Discord "app" is just Electron, it'll get in a fight with the poor thermal design of my laptop in exactly the same way on the website does.
This being said, it's very difficult for me to argue loudly against the position they're, because it's complicated.
Discord has scaled to the point where "13 year old skiddies who like pulling legs off spiders will use any alternate clients they find [which don't include anti-spam protection] to send a {server,reputation}-destroying level of spam" is having a more measurable impact than "we need to maintain equality of access". I suspect that extremely strong management vision+competence would be necessary to prioritize this - as things stand right now, it's incredibly easy to deprioritize because the vast majority of people using Discord either have minimally-viably decent machines appropriate for playing games or completing actual day jobs.
> It's really annoying because chat providers have pretty much stopped providing third party APIs
They never provided third party APIs. The work of developing a unified messaging client was in getting around the ways in which they tried to stop you from interfacing with their system, and responding quickly when their countermeasures updated.
We haven't seen a change in the behavior of chat providers; we've seen developers give up on trying.
Not true. Many protocols were open (even one of the AOL protocols), and also security basically didn't exist back then, almost everything was based on trust and obscurity.
I was surprised to find many of the newer chat systems supported by Pidgin plugins: Discord, Facebook, LINE, Signal, Skype, Slack, Telegram, WeChat, WhatsApp.
There’s different limitations for some. Facebook Messenger is only one on one. I’m in as many group chats as one on one so it doesn’t help. I’ll have to check the WhatsApp one. If that works well, that would be pretty nice.
I seriously miss the days when all of them would be in the same app no matter what service they were connected through.