Author here, thanks for your comment, "cool" is what I aim at.
>without anyone on those services knowing I’m using an XMPP client
Slidge acts in a way that (should) make it impossible for your contacts to know you are not using the official app. However, since some services are OK with alternative clients, Slidge does not necessarily tries to hide its "identity". For services that are less tolerant about it, I wrote a quick documentation page with advice about how to avoid triggering their "security" alerts (mostly because they'll see connecting from a data center, unless you host at home): https://slidge.readthedocs.io/en/latest/user/low_profile.htm...
Group messaging is definitely the next big feature I want in Slidge. There were part of Slidge's first iteration, but I decided to postpone them since it was too ambitious for a start. I really want direct messages to work well, and the code to be maintainable enough before I (re)implement groups. You can help by setting up slidge on your server and bug reporting. ;)
>without anyone on those services knowing I’m using an XMPP client
Slidge acts in a way that (should) make it impossible for your contacts to know you are not using the official app. However, since some services are OK with alternative clients, Slidge does not necessarily tries to hide its "identity". For services that are less tolerant about it, I wrote a quick documentation page with advice about how to avoid triggering their "security" alerts (mostly because they'll see connecting from a data center, unless you host at home): https://slidge.readthedocs.io/en/latest/user/low_profile.htm...
Group messaging is definitely the next big feature I want in Slidge. There were part of Slidge's first iteration, but I decided to postpone them since it was too ambitious for a start. I really want direct messages to work well, and the code to be maintainable enough before I (re)implement groups. You can help by setting up slidge on your server and bug reporting. ;)