goffi
Joined 11 years ago
Joined 11 years ago
Anyway, there is a discovery mechanism, and clients do adapt the version used by peers, so there is no incompatibility. Kaidan choose for a while to have only OMEMO:2, because resources are limited and they were going for the latest version first, but resource are limited for everybody, and it took times for others to implement OMEMO:2 too.
NLnet/NGI did (and still does) gave financial support on several XMPP projects (including mine, huge thanks to them), and, curiously, when there is money to help, implementations happen. That's problem nb 1 with XMPP: lack of financial resource.
() GUI (notably web UI) is being reworked, not stable yet, but the CLI is pretty solid.
I've proposed a specification for SFU hosting (check https://bloggeek.me/webrtcglossary/sfu/ if you don't know what's a SFU), and wrote a component based on the excellent Galène SFU, as well as client implementation (in Libervia) as part of a NLNet/NGI grant (https://nlnet.nl/project/Libervia-AV/).
XMPP council (disclaimer: I'm a council member for the current term) asked me to some modifications and to re-propose, which I'm about to do. I couldn't find the time so far (cause I'm working on ton on stuffs), but will go back to it very soon.
To sum-up: this is very much worked on.
Also note that Libervia is using a backend/frontends architecture with a D-Bus API, you can use it to make your own frontend with any language you like.
For UI there is https://github.com/kivymd/KivyMD for Material design on top of Kivy.
And the team is nice (I've met some of them at PyCon or FOSDEM).
The framework is pleasant to use, and there is a descriptive language, kv, which is really great.
Cross compiling may be painful though (I did it for Android) and the app loading time is a bit long, but it's working.
Some things may be missing in comparison to big frameworks such as Qt, there is no WebView for instance, and accessibility is unfortunately not as good.
It's overall a very good project and it's a pity that it's not more known and used.
I'm using XMPP for chatting of course, but also for blogging (my blog is XMPP based), A/V calls, events organization, file sharing, photo albums sharing, as a remote (with ad-hoc command, I've even built an specific UI to control MPRIS supporting player). I'm building an agenda, a forum, a generic list tool (TODO, shopping list), and other stuff.
I'm using Snikket to host a small server for family and friends, with accompanying mobile clients.
I've also built an XMPP <=> ActivityPub gateway (soon to be released, but dev version is already available), so my blog is accessible from any AP supporting client, and I can access the AP ecosystem (including events as seen in Mobilizon).
There is Slidge IM if you wanna talk to legacy network such as Signal, Whatsapp, Telegram, Discord, Mattermost, Steam, Skype, Facebook Messenger, Matrix, VoIP.ms.
There is Biboumi if you wanna talk to IRC.
There are old and new email gateways on the work (I'll be working on one myself).
XMPP is used in many fields (from healthcare to games), you can have an idea at https://xmpp.org/uses/instant-messaging/ but I have the feeling that this list is not up-to-date and is incomplete. I think that it's used in Fornite for instance.
So yeah, we may not be the best for marketing, and we not have as much resources as we should, but XMPP is still well alive and kicking!
edit: Fornite is actually mentioned at https://xmpp.org/uses/gaming/ .
Note: I'm very involved in XMPP, and the author of the latter XEP.
Edit: forgot to mention that it's also available to ActivityPub thanks to the XMPP <=> AP gateway (that I've authored too)