Gajim 2.4.4 has been released! 🎉
This release comes with link previews 🖼️ and many improvements for macOS
.
Thank you for all your contributions ❤️ Let us know what you think!
Support Gajim's development: https://liberapay.com/Gajim
Lead dev of Libervia project (https://libervia.org), XMPP, Free Software and politics.
Développeur principal de Libervia.
| Libervia | XMPP |
| Python |
@John_Livingston je suppose que c'est utile pour transmettre les dossiers entre médecins. Mais ça ne devrait pas être chez le prestataire (surtout en clair), ça devrait être chiffré de bout en bout, segmenté, et avec un système costaud de permissions (style ABAC).
Là ce genre de données exposées, je ne serais pas étonné que ça fasse des suicides ou autres drames.
Gajim 2.4.4 has been released! 🎉
This release comes with link previews 🖼️ and many improvements for macOS
.
Thank you for all your contributions ❤️ Let us know what you think!
Support Gajim's development: https://liberapay.com/Gajim
I wanted to test Playwright on my Arch Linux, but that software is a pain to install (which is rare on Arch), even with the AUR package. It's built for Debian-based distributions, and installing dependencies is a mess.
I was thinking about using Debian in a chroot, then I remembered the Distrobox project, which uses Podman with deep integration. This was a perfect use case for it, and it works super well. Kudos to the people involved!
I'm deploying this morning on https://mov.im/ the biggest architectural change since 2014: multi-sessions workers 😳
This means that Movim is moving from a one-session = one process architecture to multiple-sessions per PHP process. This will greatly reduce the RAM consumption and database connections while having negligible impacts on the global performances 🚀
I am testing 4 sessions/worker at the moment, so a -75% RAM usage but we might do more sessions if things runs great ✨
A new daemon command allows you to have a nice overview of the worker and sessions 👀
Oh and I'm deploying from my local train in the middle of the French Alps 😸🚞⛰️
@650thz Hello. MESH group calls are supported by at least Libervia, Dino and Movim (multiparty with small number of participants, without server support). And conference calls using a SFU (i.e. server support for large number of participants) has an experimental implementation in Libervia, and Movim is willing to do the same.
I (Libervia dev) am also working on specification for SFU on XMPP.
Note also that Jitsi is XMPP based (but with its own non standard implementation).
Tonight's Spaces status:
- Numerous stability fixes ✅
- Notifications are properly working ✅
- Admins can set admin/member role to the Space users ✅
There is still some notifications feature to be done... and stability improvement and I think I'll be good to merge a first preview of the Spaces in Movim 👀 Interested to try it out ?
I repeat that everything done so far works on a standard #ejabberd #XMPP server without any specific hack. It is just very basic MUC + Pubsub XMPP put together so it should work "out of the box" (minor a small config to declare where the Spaces are created) to work ✨
Stay tuned 😸!
OK so e2ee contact are implemented in Libervia, only in the CLI for now. Here are 2 screenshots:
- in the first one contacts are retrieved and rendered for the terminal. We can see contacts and groups IDs and that they are encrypted (which is optional but default).
- in the second one we see what is stored on the PEP service, so what your XMPP server admins can see, an encrypted blob.
This is highly experimental.
Did you know that PeerTube supports XMPP (Jabber) for live chat? It is not built into the core Peertube software, but the "peertube-plugin-livechat" allows administrators to bridge PeerTube live chats to XMPP servers, facilitating moderation and allowing users to join chats via XMPP clients.
@Amgine I'm grateful to the people who worked on those project. That some of them were paid by Google is a detail, it would have been done in other conditions otherwise, but still done. The result is open standard, not tied to any company.
Most of the web techs/specs are nowadays made by private companies, in particular Google, too.
Anyway, yes Jingle (XEP-0166) is the base of any feature involving direct connection when possible (A/V, direct file transfer, etc).