After testing Siskin and Monal for a few days, my impression is that XMPP is now way more usable on iOS than it was back in the days. Many thanks to @tigase for their great work on Siskin IM.
@tigase gave it a try and muc pushes as well a omemo work fine. But is it normal / intended to receive a "new message" push each time oneself is typing? Server is prosody 0.11.5
@held No, it's not normal. Do you have any other client connected? Do you have any additional prosody configuration? Have you checked in prosody logs whether it forwards typing notification to push server?
@tigase I had chatsecure and monal on that device as well, but now both are uninstalled. However, prosody shows a push registration for this client for all three push servers in its log file. I know, you're no prosody support, but do you know when these push registrations will be deleted from the server?
Self-pushing while typing still occurs... I have no additional push config added to prosody except the enabling of mod_cloud_notify. Should I provide the whole config?
@held I don't know about retention of those push-registrations. In case of siskin it's not possible to remove account without disabling push.
As for self-typing notification this is definitely weird - does it happen always or only on selected chats / groupchats? Could you check prosody logs whether prosody forwards those stanzas? In general Chat States (https://xmpp.org/extensions/xep-0085.html) should not be forwarded to push.tigase.im
@tigase the prosody - guys call the self-pushing a "a really interesting issue indeed" 😂 and also have no fast solution to it. It happens in all chats, except mucs (not surprising, since pushes do not work there at all currently).
Edit : even if the push activation slider in muc still can not be enabled, muc pushes work currently (no idea what changed in the mean time). Self pushing still occurs in chat, but not in muc
@held btw. MUC push in siskin will only work with Tigase XMPP Server (for now) - the area of MUC for mobile devices is quite "wild west" but we are working on making it more workable :-)
@tigase just to clarify that: muc pushes work perfectly for most mobile devices. Only the bizarre 🍏 causes problems. But thanks so far! I'll have a look on the logs once again, but the prosody guys mention that it looks more like a client / app push server problem, while I think, the biggest client problem is the 🍏😜
@holger @held just to clarify - in Siskin we expect that the muc room will send messages to user's server and it will forward them (if needed) to push server without the need to not-closing the stream (which has it's own problems). In Tigase we achieve that by users registering to the room (using method defined in MUC specification: https://xmpp.org/extensions/xep-0045.html#register), so MUC can send messages even if the user disconnects. This is somewhat similar to MIX and MucSub from ejabberd (which also resembles MIX)
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!