I'm testing #PeerTube after a while for light integration with #Libervia and really pleased with what I see! Clean UI, lots of features, easy to use - great work by @Chocobozzz, @Framasoft, and the entire contributing team. Plus, there are a ton of plugins available! I'll be exploring the API to see if deeper integration is possible, it would be neat. #selfhosted#XMPP#videos
https://snikket.org/blog/snikket-hosting-launched/
"We believe that the ideal online communication network is larger than any single organization, and that it should offer people freedom and choice. That’s why we built #Snikket on open standards (#XMPP) and everything we produce is open source, so that people can inspect it and run it themselves."
I'm early in my XMPP journey, but I'm currently working on a few chatbots to get a server to what I'm calling "Discord Parity"
As I understand XMPP and have my webhook bot configured is that the bot is a user that joins a room and simply is always passively listening.
Something I've noticed in the logs is that the bot receives the xml for all activity.
This includes the plaintext communications of people.
I haven't gotten to the step of setting up OMEMO encryption for the bot and this might quell my concerns for this bot which just forwards data into the chat.
More concerning is a planned interactive bot. Since it will be waiting for commands it must listen for messages, but I don't want it snarfling all messages up.
At this stage, I think our data is better stewarded and secured by us than Discord, but it's something I'm thinking through and would love to here from any XMPP folks in the fediverse.
@jeremiah You don't have to listen to commands in the same group-chat. For example the bot could be configured in a separate 1:1 chat and only post into a group-chat. Another neat option is to allow configuration via ad-hoc commands and forms. A recent example for such a bot can be seen here: https://slixfeed.woodpeckersnest.space/posts/slixfeed-news-bot/#xmpp#jabber
Disroot è un server con sede ad Amsterdam che offre anche servizi #XMPP con cancellazione di tutti i dati dopo un mese dall'archiviazione. Offre anche bridge per comunicare con Matrix e IRC.
If you are curious and courageous, and run #Debian testing or unstable, you might like to try the latest snapshot of #Gajim by @gajim. It features message replies and message reactions.
Expect bugs! This is not a release version, but a snapshot. It's called "experimental" for a reason.
echo "deb https://deb.debian.org/debian/ experimental main" | sudo tee /etc/apt/sources.list.d/experimental.list
Likely a result of recent Slack shenanigans, the pressure on the matrix.org server is a good reminder of why I should just run my own #matrix instance. It also just adds to my appreciation of how much nicer it is to run and use #xmpp.
@art_codesmith With a literal interpretation, "everyone" didn't - #XMPP is still actively used by many people, knowingly or unknowingly. Some people use interoperable XMPP services such as Snikket or one of the many public XMPP providers. Others self-host (Snikket, Prosody, ejabberd, etc.). And many more use it unknowingly via WhatsApp, Zoom, MoyaApp, etc.
The problem with the latter services is that they don't interoperate with others, but the EU's DMA regulations are aiming to change that.
Instant messaging is more complicated than you'd think. Sending a message from one device to another seems simple, but it's hard; especially on mobile. NAT, Firewalls, smartphone battery optimisation are all technical challenges, but then you also got user expectations. Users expect to see the same messages in the same order on every device. They want to be able to send photos, files, locations, voice messages and much more. On top of all that, full end to end encryption is a must have nowadays. Especially if you let average people run their own servers.
Matrix seems overly complex, but once you attempt to reinvent it, you end up with the same level of complexity.
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!