@kill_9_1 @pixelschubsi @farooqkz @treefit @delta

I'm sure, it is. So are #ejabberd and #prosody. You can easily run a #Jabber/#XMPP server on a very old #RaspberryPi.

@Langile

As someone who does not know Telegram and its features at all, I can only guess, that there is a #Prosody module for whatever usecase. There is a community module for almost everything! 🙂

Maybe ask in xmpp:prosody@conference.prosody.im?join or @prosodyim.

@debacle @stefan @vascorsd @gajim it's not easy to determine the "jurisdiction" of the bug - wether it's #Gajim or #Prosody (or maybe #Monal's unique, intermittent connectivity flakiness to connect to this MUC jumped in there awkwardly somehow?).

Each project will want convincing proof that the bug lies within their jurisdiction, before doing anything. I don't have the spoons to nail down the jurisdiction, which would mean trying to reliably reproduce the bug. The bug appeared only after 3 weeks of inactivity on the part of one laptop. It's hard to reproduce.

I'm grateful for all the hard work of the #XMPP community, but in the meantime, #DeltaChat is right there - one #flatpak install away. New account creation is a finger-snap. So far they've provided a bug-free experience to me, exceeding my expectations. The jury is still out if they can pull off trustworthy group chats. *Not an easy thing to do, when everyone is encrypting in a group chat;* notoriously challenging, and fraught with brittleness. I'll bet that's why your group chats are shrewdly not encrypted, @debacle

If you tile Gajim 2.1.1 and DeltaChat desktop side by side in #Debian, they sure look similar these days, both clearly taking strong design inspiration from #Discord (as they should, as Discord is still sadly the "incumbent", even with its ad-enshittification). BTW: #Element looks like Discord too.

I'm leery of crossing the line into dev territory here - or even software tester/debugger/bug reporter. I'm willing to install and maintain such a system, but it needs to be iron-clad-reliable to earn a lasting place amongst the other respectably reliable things I #SelfHost going forward.

@sbb @vascorsd

As the one who uploaded the #prosody package to #backports: Did you file an issue?

https://issues.prosody.im/

@prosodyim

@vascorsd I had something similar to that happen to me recently as well. I'm using a #prosody server, and I have my:

archive_expires_after = "5w"
... set in /etc/prosody/prosody.cfg.lua

Messages should be archived for 5 weeks.

Then messages sent in Gajim on one linux laptop were lost, when a second #Linux laptop who was subscribed to the same group, was turned off (absent from receiving messages) for 3 weeks. 2.75 of the 3 weeks worth of the group messages (where the laptop was turned off) silently never showed up, when #Gajim was re-opened on the second laptop.

This bodes very badly for me recommending XMPP to others. I now consider #DeltaChat to be a secondary choice, should something happen to #Signal (which is currently my privacy-respecting Messaging app goto).

Other clients who chatted in that same group, BTW: the latest stable #Monal in #iPadOS, and #Conversations in #Android

Prosody version is 13.0.0-1~bpo12+1, backend is sqlite, Gajim is 2.1.1. It was a private MUC, and OMEMO was used as much as possible.

#XMPP

@Monal @menel OK, I have a tough question, pertaining to notifications working properly in #Monal. After reading:
https://github.com/monal-im/Monal/wiki/Considerations-for-XMPP-server-admins
...it says: "Make sure that your server can talk Bidirectional to Monal's pushservers (s2s)". But what if I want to disable s2s (to avoid spammers), thereby having a private #prosody server for myself and my local users (who might use Monal)?

Is there some way to allow just enough s2s for Monal's notifications to work properly, but defederate from the other XMPP servers, to keep out spam?

#XMPP

#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?

My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*

So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.

Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": https://gultsch.social/@daniel/114012904576436518

It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird

Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".

(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)

#prosody #conversations #gajim #dino #snikket #monocles #monal

@daniel the two worst "footguns" I encountered when setting up #Prosody 0.12.3 in #Debian 12 were - you're not going to like this - enabling TLS, not STARTTLS (ruins upload.sampledomain.com capability), and trying to use SRV records (made an honest attempt, couldn't get it to fly).

These "footguns" wasted two brutally unenjoyable days of my life, until I scaled back these progressive wishes.

#XMPP

I made a simply Grafana dashboard to show some metrics of the Pimux.de XMPP server. Quite interesting to see the usage of my server varying during the day.

I’m still happy to see so many people using XMPP on a regular basis!

https://pimux.de/blog/pimux-de-server-statistics-dashboard

#Grafana #Prosody #XMPP #Pimuxde

Alt...

A Grafana dashboard with 6 panels. One of them shows two big numbers: 675 online users and 6090 registered users. The other 5 panels are showing a graph within 24 hours: size of file storage, about 23 GB. Online users between 600 and 1200. Registered users 6091 dropping to 6090. Client-To-Client connection for IPv4 and IPv6 and Server-To-Server Connections.