The current state of #XMPP iOS clients certainly leaves a lot to be desired. But I'm very excited about the rate of progress recently.
We now have a growing number of people making it their mission to ensure XMPP gets the first-class iOS experience it desperately needs.
Make sure to provide the developers feedback. If you find a bug that isn't reported, or that you could provide additional insight into, that is a really helpful way to contribute to improving the future of XMPP on iOS.
We can do this! 😎
@mattj Join a MUC, get spammed, because there's a.) no filtering (I canot say don't push for MUC) and b.) no deduplication (if someone didn't specify an id on their message, I'm SOL)
Not sure where deduplication comes in? The client would just ask for messages since whatever the last one it saw was.
I find this platform tricky for real-time technical discussions... if you want to chat, feel free to reach out!
@mattj The problem is that you get both, MAM and the MUC giving you the last N messages. If any of them does not have an id, the client doesn't know how to dedup.
Modern clients don't ask for "the last N messages" but use MAM with IDs and/or time ranges instead.
If, however, Siskin is not connected and Apple Push is used, the server just sends everything, as the XEP has no filtering support, and iOS displays it. There is nothing Siskin could do about it.
@kirschwipfel @ij @mattj You need to send a message with a text via Apple. E.g. “New message”. This is what Prosody does. A client can then have an app extension to fetch and decrypt the actual message and replace the text. An app extension cannot however just dismiss a message (at least as of iOS 13). Hence server side support for configuring for what to send a push is necessary. Matrix does this, but there is no such XEP. Which is why push does not work properly on all iOS XMPP clients.
It's not quite that simple.
Filtering already happens - both the user's XMPP server and the client's push gateway do already make decisions about whether/what to push. Client and server devs are working on the best practices here. It's not clear that protocol changes are needed for this.
No, there is no in-band way to configure a separate list of JIDs to what would normally be allowed to send you messages (if there is someone you don't want to receive messages from, block them!) I really don't see that as a primary problem.
@mattj @kirschwipfel @ij It is a real problem, because you want to configure push *per JID*: Being notified about every message in a MUC vs. every message from a person is an entirely different thing. For some MUCs, I might want every message, for others only when I'm mentioned.
XMPP lacks any way to configure this. This is what made push on iOS unusable for me in the end.
Matrix solves this by letting you configure that per room.
These two categories of MUC are generally easy to calculate: private groups can notify on every message, public channels only when mentioned. That gets the behaviour that most people expect without forcing them to configure anything.
@kirschwipfel @js @mattj There is a drawing of how Cisco Jabber does this and I think it's more or less valid for all implementations: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/push_notifications/cucm_b_push-notifications-deployment-guide/cucm_b_push-notifications-deployment-guide_chapter_01.html
So, there is the APNS and another server inbetween. For Monal it's ios13push.monal.im for Siskin/Beagle it's push.tigase.im. Usually you can see those connections in your server logs...
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!