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 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 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.
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!