devlug.de is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Mostly using #Phosh on a #LibreM5 running #Mobian #trixie lately but also a #PinePhone running #Mobian #bookworm (with a trixie era kernel).
About 95% or more using the #Dino #XMPP client.
Mostly with WiFi but occasionally cellular data. Never with cellular voice calls or text.
Had tried Chats ages ago but the #OMEMO support was unreliable and there was no offline support at all. Lack off offline support was a total deal breaker for me.
Love phosh a lot, many thanks!
Designing top-down from the UI/UX is a good idea. It is, however, probably not a USP of Delta Chat. TTBOMK, at least #Conversations, #Dino and #Kaidan, have been developed with the same mindset.
But they do not share a common framework like Delta Chat. Everyone uses their own protocol implementation (in Java, Vala/C, and C++, repectively), which results in more work and potentially more bugs.
Im Blog-Beitrag vom Debian XMPP Team bekommt ihr dazu einige Informationen.
Was ist XMPP? 🤔
XMPP ist ein Internetstandard für Instant Messaging - ein Protokoll zum chatten und vieles mehr! ☝️
Hier 👇 geht es zum Beitrag:
https://xmpp-team.pages.debian.net/blog/2025/05/xmpp-debian-13-trixie-news.html
Meine persönlichen Highlights sind:
💫 Dino, upgraded from 0.4.2 to 0.5.0
💫 Gajim, upgraded from 1.7.3 to 2.1.1
💫 Profanity, upgraded from 0.13.1 to 0.15.0
💫 Prosŏdy, from 0.12.3 to 13.0.1
Vielen Dank an das Debian XMPP Team und die XMPP Projekte! 🙏 🙏 🙏
Viel Spaß beim chatten.
#Debian #Debian13 #Trixie #XMPP #Jabber #Chat #Messenger #Dino #Gajim #Profanity #Prosody #GNU #Linux
Dino 0.5 is out! 🥳
Dino now features improved file transfers and two completely reworked dialogs.
Release blog post: https://dino.im/blog/2025/04/dino-0.5-release/
#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