social.uhoreg.ca

MattJ mastodon (AP)
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! 😎
#xmpp
Jonathan S. mastodon (AP)
Sounds interesting, but are the protocol problems solved? As long as push cannot be configured server side, there'll always be push spam. Matrix solved this pretty well, I would be really happy if XMPP could have as good push as Matrix one day. (iOS + Push + XMPP being as terrible as it is is what made me move to Matrix)
MattJ mastodon (AP)
What kind of configuration are you thinking? What's your definition of "push spam"?
Jonathan S. mastodon (AP)
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)
MattJ mastodon (AP)
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!
Jonathan S. mastodon (AP)
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.
MattJ mastodon (AP)
Modern clients don't ask for "the last N messages" but use MAM with IDs and/or time ranges instead.
Hmm, SiskinIM has an option for that...
Image/photo
Jonathan S. mastodon (AP)
Also, as long as the server does not assign a unique id to every <message> that does not have one, there'll always be the duplicate messages problem when joining a MUC, as the client has no way of knowing they're the same :(.
MattJ mastodon (AP)
Modern MUCs all add unique ids to non-ephemeral messages 👍
Jonathan S. mastodon (AP)
Most recent Prosody release with Biboumi and I got no id on anything :(
MattJ mastodon (AP)
Obviously Biboumi is not a "native" MUC, but gatewaying to a protocol that has no concept of permanent message IDs. If you enable the bouncer/persistent mode though you'll certainly get stable IDs added
Jonathan S. mastodon (AP)
I did enable bnc mode and didn't get stable ids :(.

Also, when joining MUCs on other rooms (as in, not on my server), I also regularly did not get ids.

This made using any iOS client with push entirely unusable :(
MattJ mastodon (AP)
Are you looking at the sender-controlled id attribute perhaps? That's optional, specified by the sender and not the MUC, and not used for sync. The ID assigned by the MUC is separate.
It's nice to see XMPP development going well, with new projects like Snikket, Dino, and Kaidan, and even development on Gajim picking up again.