Just pushed a new protoXEP for implementing Remote Control in #XMPP, along with an accompanying implementation in #Libervia!
This is exciting, as it enables not only Remote Desktop, but also controlling devices without video feedback - like using your phone as an ad-hoc touchpad, laptop keyboard to control a Single-board computer, or making automation scripts, and more!
It's designed to be extensible, with plans to add clipboard sharing and gamepad input. Thanks to #NLnet for their support!
My current AV grant is consuming all my time, making it challenging to progress on other topics.
Feel free to work on microblogging XEPs: as long as they're compatible with #Movim and #Libervia - it will with the gateway, at least for body. Reactions and likes require XEP-0470, not yet implemented in Movim.
AP DMs are converted to #XMPP chat messages, so they should work with Converse and other clients out of the box.
@ejabberd#Libervia implements it for Pubsub (both in the Pubsub service and in the client part), but not yet for messages. I could probably easily add it, at least in the CLI frontend. Something to add in my (long, too long) TODO list :)
For instance to send an announcement for servers supporting XEP-0133:
li ad-hoc run "<http://jabber.org/protocol/admin#announce>" -f subject "Maintenance in 30 min" -f announcement "$(<~/announces/maintenance_30.txt)" -S
Check the doc linked above, it's explained there. Ask me if you have questions.
Curious how none of the coverage of this launch mention that the app isn’t actually open-source (though they pretend to be an open-source project), which makes all of their claims of “end-to-end encryption” worthless...
@Samsy@arbocenc#XMPP can run bridges (called "Transports" or "Gateways" in XMPP terms) since the early ages. And nowadays, there are modern ones with tight integrations: #Slidge being a flagship (including a #Matrix gateway), and I'm myself working on ActivityPub gateway and soon a email one with #Libervia. #Cheogram is also working on SMTP gateway. And #Biboumi is the flagship #IRC gateway.
#Libervia now supports SCRAM-SHA authentication. Previously relying on outdated Twisted #XMPP mechanisms, we experienced incompatibilities with recent servers like #Snikket. This issue is resolved, and Libervia can now operate with up-to-date Snikket instances.
Hmm, after having #nextcloud run on my #rpi for a bit I noticed I really don't need it. (Because the video chat just doesnt work as it should).
Maybe I'll just reset the rpi again and focus on some leaner system.
Maybe I'll try with #xmpp this time. Have to check if that has good voice and screenshare options right now. And maybe a web interface.
I haven't really done anything with that for a decade.
🚀 Just pushed the #WebRTC Data Channel Signaling implementation to #Libervia! In this case, it features a different workflow compared to usual Jingle File Transfer methods, with separate browser and #GStreamer implementations 💻
It's a great addition, allowing direct P2P file sending (where possible) from any device to any other one (like a CLI/Desktop frontend sending files directly to a remote browser). I look forward to enhancing the UI/UX! #NLnet#XMPP#PeerToPeer 🌐
After #GUI, I've now pushed implementation of a #TUI output in #Libervia#CLI frontend, which shows A/V call video streams directly into your terminal! It's using #Kitty or #iTerm2 image protocols, or #Unicode half-blocks (thanks to #termimage)
I'm not aware of any other CLI tools doing something similar (#XMPP or not). It's not as useful as GUI, but it's quite fun :)
I've just pushed the implementation of a GUI for calls in the CLI frontend of #Libervia
That means that you have a full-featured #Qt GUI accessible quickly from your #terminal to make or receive your #XMPP calls. Can also be useful to compensate for clients missing A/V calls.
@aresti#Libervia (I'm the lead dev) CLI frontend supports state of the art #XMPP encryption (OMEMO legacy - the one used in most clients -, OMEMO:2, and OX).
I believe that some other CLI tools do support OMEMO legacy too, maybe xmppc?
It has become among the most popular open messaging protocols, but it remains a scalability nightmare.
It's literally the Blockchain of messaging. Its current state is given by the sum of the whole chain of events received since t=0. It's a brittle append-only ledger, and any modifications you do to it are very likely to break it.
Do you have a huge 100GB database and you want to clean up old stuff? Sorry, you can't. There are some non-official solutions for compacting the events, but they're all likely to break your db - and none worked so far in my case.
Do you have users on your instance that entered a busy room on matrix.org? Then you'll get all the join/leave events of that busy room on your db, with no way of deleting them, and nothing to do unless your users exit those rooms.
Did you start your instance by toying with the default SQLite backend, and now that it's become big you want to move to Postgres? Sorry, no official guides provided, only unofficial procedures scattered across a bunch of blogs.
Do you want to change the name of your server? Sorry, you can't. All the events are tightly coupled to your server name. The advised solution is to simply start a new instance.
Such a rigid and brittle implementation shouldn't have become an open de facto standard without much questioning about its poor design decisions.
At the very least, some official tools must be provided to enable admins to compact events. If the size of the database is guaranteed to increase indefinitely, then entry barriers against self-hosting are only going to increase.
📢 My talk "How I've Built a Web Frontend for a Federated Communication Tool with #Brython" from the #Python devroom at #FOSDEM2024 has just been released! Thanks to everyone who attended and a special shoutout to the #FOSDEM organization team for their incredible work. Check it out here:
@Polychrome@debacle FYI, #Libervia was built from the ground up with multiple frontends in mind. If you want to create your own interface, you can do so in any language/framework you like, focus on the UI/UX and let the backend handle #XMPP and many other things.
I'm stabilizing the front-end API for this release to encourage third-party front-ends.
There is a major outage on my server, https://libervia.org, my blog at https://goffi.org , and associated services won't be accessible probably for a few days. My email service is also down, so if you need to contact me, please use XMPP at goffi@jabber.fr for now, thanks! #Libervia
This project will not only convert normal messages but also transform mailing lists into #pubsub based forums. It includes UI/UX enhancements on Libervia, end-to-end encryption, and advanced handling of attachments.
The federation model of #ActivityPub is based on random chance. Yes, being on a larger instance increases your chances that you can see all replies in a thread but it doesn’t guarantee it.
@pavot It's one of the goal of #Libervia (I'm the main dev). It works on desktop (natively), on the web, and there is an Android port but it's not yet usable. Windows and Mac OS version are planned, and iOS would be doable, however I'm not sure about the possibility to publish AGPL on Apple Store. It also has a TUI and a CLI frontends.
I've just pushed A/V call commands to the #CLI frontend of #Libervia. I believe that it's the only #XMPP CLI to date with calling capabilities (make and receive calls).
Automattic buys Beeper for $125MM, launches closed-source "privacy" app (techcrunch.com)
Curious how none of the coverage of this launch mention that the app isn’t actually open-source (though they pretend to be an open-source project), which makes all of their claims of “end-to-end encryption” worthless...