biboumi

> and supports bridging to other types of networks which aren't matrix-based https://sr.ht/~nicoco/slidge/ Turn any XMPP client into that fancy multiprotocol chat app that every cool kid want. > Signal, Telegram, Discord, Steam, Mattermost, Facebook, Skype https://spectrum.im/ Spectrum is an open source instant messaging transport. It allows users to chat together even when they are using different IM networks. https://github.com/louiz/biboumi Biboumi is an XMPP gateway that connects to IRC servers and translates between the two protocols. It can be used to access IRC channels using any XMPP client as if these channels were XMPP MUCs. ------ I'm using all of those daily to connect to all my other accounts, Slidge is the most modern one and is having lots of features ported to the modern XMPP extensions.

Ofcourse if i (or anybody else) would write a chat protocol today i would make changes. But i'm not even sure if i would abandon xml. I'm in the same boat as you and think xml is too verbose and all that other stuff but i've recently programmed some xmpp projects and i came to the conclusion that xml actually realy does work well. And i didn't even use a library like sleekxmpp because i wanted to know everything. I'll just say: good luck designing something that'll be able to grow for 20 years and still work today. You can realy feel where the X in XMPP comes from. I have to mention the Conversations people. For me they are a big reason why i use xmpp. It's not only the client which is very good, but the stuff like http-uploads fix some very real problems in very little amount of code. Also once axolotl-xmpp works and prosody 0.10 is rel