flori_ava_star:~:cursor_blinking: :made-with-estrogen: (@star)

@kkarhan @gajim @pidgin Because what you're asking for is a Herculean task.

Plattforms like XMPP and IRC were and are designed to be open. They are made with the intent in mind, that a single developer can read through the specification and build software for and with it.

Plattforms like Discord were never made with this intent in mind. They were started as many people getting paid to be as productive as possible with building something, and "improving" it. They break APIs so rapidly, that to maintain a Discord client library to maintain Discords pace in changes and breakage is no easy feat already, to say the least. Discords HTTP API has 10 versions. And they do not do semantic versioning, nor do they do any kind of active change log keeping, nor do they provide ANY details on the User-Targeted API (only the bot API). In the same version 10:

- Discord completely changed user identifiers from the # based system to @ based usernames
- Discord introduced MLS encrypted voice traffic and implemented that whole system
- Discord changed the client permissions list in a way that affected an existing permission in a backwards-incompatible way, which, I think, was a first for them

In ONE version! In THE SAME version! And they always do this, forever, for every version!

Got that? Okay. Now rinse and repeat, we still got WhatsApp, Signal, Slack, Teams and Telegram to take care of. /hyp

Like, of course, some of these providers, i.E Telegram and Signal, do much better at this than Discord. But still, this is a HUGE task. And you have to keep all of this up-to-date, because they do not care that much about backwards incompatible breakage, unlike your typical IRC enthusiast.