Slidgetastic news, my friends: more gateways, more contributors in the XMPP gatewaying world!

SlidgeQQ

Thanks to William Goodspeed, slidgeqq now exists. If you need to chat with residents of the Tencent QQ walled garden, you can try right away with the containers for amd64 and arm64 available on the codeberg container registry.

To connect to the Tencent QQ network, you will need to run a LLOnebot (or another compatible QQ client) to expose a OneBot11 WebSocket API endpoint for slidgeqq. As this is the very first release, initializing large friend lists and group rosters may take some time. You may also want to clean up media storage regularly, as it can grow quickly—especially if you are part of large groups. Once that’s done, however, it runs fast and provides a surprisingly complete experience.

Currently supported features include: direct messaging and group chats; bidirectional message retraction; sending and receiving replies, images, videos, and voice messages; and more.

Matridge got a whole lotta love

Thanks to the relentless efforts of WhyNotHugo, matridge received both user experience and code quality upgrades. With dedicated commands, it is now possible, directly from your XMPP client, to accept an invitation to a Matrix room, join a room by its Matrix ID, change your Matrix password, or remove devices from your Matrix account.

Soon(ish), slidge commands will not only be exposed only on the gateway component JID, but also on the JIDs of the room and contact puppets. We should find some good use for this in Matridge, hopefully getting it closer to a fully-enough featured Matrix client.

Spaces? 🧑‍🚀

Server-side spaces (now supported by Movim 😱) should be part of the slidge 0.4.x series. A work-in-progress pull request details the roadmap for this feature to land in slidge core. This will no doubt benefit Slidcord to expose a better UI for discord servers. Slidge-whatsapp will also use it to map WhatsApp communities, and matteridge for Mattermost teams.

Slidge needs YOU to grow the family further

We have more and more people hanging out in the chat rooms; this is great: slidge was always meant to be a community-owned thingy. We welcome contributions of any kind, be it by helping out other users in the support room, opening tickets to report bugs and suggest improvements, making this blog better, or anything you feel like doing, really. Join our community of bridgers, the more, the merrier!