I am very sorry for you to need to cope with this:

the best option for private chatting TODAY when it comes to #security, usability/user-friendly, #resilience, #digitalindependence and #freedom is #DeltaChat a chat app that uses #SMTP + #IMAP at its backbone, not your favorite "perfect" chat protocol, you don't need new better protocols, you need tools that actually work for the people

#xmpp #matrix #simplex #signal

@adbenitez It's easy to say that one doesn't need better protocols after those better protocols have become so ubiquitous that you don't even realize how you're using them yourself.

Apple APNS and Google FCM use #XMPP technology to deliver push messages instantly. All the other messengers listed (#Signal, #Element, #DeltaChat) thus use XMPP technology. Everyone uses XMPP, but when it is about marketing, suddenly XMPP is not necessary.

@pixelschubsi @adbenitez new protocols are fine. The point may rather be that contrary to popular nerd belief protocols are only one part of an effort. What distinguishes #deltachat from #xmpp is that one is a cross-platform mass-user focused app with a consistent UX across the platforms and using standards under the hood, while the other is a set of specs with many different implementations and UX approaches on the various platforms, and sometimes tenuous compatibility between them.
@delta @adbenitez consistent UX, except when not.
@pixelschubsi @delta @adbenitez
It's not listed as an official client implementation
@darkcat09 @delta @adbenitez Official client implementation of what? Chatmail website also lists a lot of implementations with largely different UX: https://chatmail.at/clients
Chatmail: Clients

Chatmail provides FOSS infrastructure for interoperable, secure, speedy and reliable end-to-end encrypted messaging. Check out clients as Arcane Chat, Bots or Delta Chat today!

@pixelschubsi buddy, you are completely missing the point

yeah, sure anyone can create 3rd party clients that are not feature-complete, but you can always point people to the official Delta Chat client and that is something that exists stable in all platforms, you don't have such stable cross-platform client in XMPP

besides, even the most simple of the demo client has a backup format that is compatible across all clients and it is possible to move from one client to another, in XMPP this doesn't exist, you can't export a backup from Conversations and import it in Gajim, etc

nor can you recommend the same app for desktop, android and Apple users

more importantly: even the most basic of clients have the same audited encryption etc. than the official client, in xmpp you can often end up even without any encryption at all, and super easy to disable it, it is such a bizarre thing not even worth keep talking about, chao

@darkcat09 @delta

@adbenitez @darkcat09 @delta Again, you are comparing Delta Chat (software) with XMPP (protocol). That makes no sense.

Of course I can't recommend the XMPP app for desktop, Android and Apple, because there is no XMPP app. None. Zero.

There are just apps that use the XMPP protocol, typically among other protocols. And DeltaChat is technically such an app (via APNS and FCM). Just like DeltaChat is an app that uses IMAP and SMTP protocols.

@pixelschubsi @adbenitez @delta
But can you recommend a specific XMPP client with a really good UX both for mobile and desktop which would have consistent UI on both platforms?

@darkcat09 @adbenitez @delta How about DeltaChat, which, as I just explained, is technically using XMPP (at least on Android and iOS).

I mean, I also firmly believe that "good UX both for mobile and desktop" and "consistent UI on both platforms" are actually mutually exclusive, because to have a good UX, you need to use platform-specific UI patterns, so it can't be consistent.
That's why I consider the DeltaChat UX on desktop pretty bad, but I guess you're a believer so I'm not going to fight.

@pixelschubsi @adbenitez @delta
Yes, i can recommend such a client implementation in case of Delta. The official one. https://get.delta.chat

And pls stop pretending every messenger is using XMPP.
I answered you in the thread above that GCM doesn't use XMPP anymore, they introduced a new HTTP v1 API back in 2017, deprecated the legacy API in 2023 and removed it in 2024.
Moreover, push notifications never were a main feature of a messenger. Messages are sent over a different protocol which XMPP doesn't have any relation to.
@pixelschubsi @adbenitez @delta
I don't know about Apple, but the point that it's not the main feature still stands

@darkcat09 @adbenitez @delta
The HTTP API is for submission (how your server sends the message to their server, what SMTP does in email world), it's not for how the receiving client receives those messages from the server (what IMAP does in email world), that's still XMPP.

Tell your friends about your cool messenger where push notifications are not a feature (they will only know about new messages when they open the app). They are going to love it.

@pixelschubsi
You missed the word. "Not the main feature"
@pixelschubsi
Please provide any sources. I can't prove nor disprove that GCM still uses XMPP for receiving. And i'm not going to reverse engineer google services for that
@darkcat09 the developer of @microg said so. As microG did all that reverse enginner of google services, I guess they're right.
@pixelschubsi @microg
Oh, ok, thanks for clarification 
(Still would be great if you provided a link to any source but ig i can search it by myself)

@darkcat09 @microg I found these port and hostname lists from Apple and Google

https://firebase.google.com/docs/cloud-messaging/network-configuration?hl=en
https://support.apple.com/en-ph/102266

Port 52xx are known to be used for XMPP. mtalk.google.com is for Google Talk, which was using XMPP (but access was closed to third-party clients in 2022)

Configure your Network for FCM  |  Firebase Cloud Messaging

Configure your network to allow traffic to and from Firebase Cloud Messaging.

Firebase