#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": gultsch.social/@daniel/1140129…

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 Gultsch

2025-02-16 09:41:01

Absolutely nobody knows what an XMPP address is, so just go ahead and call it a:

#XMPP #Conversations_im #Jabber