Holger Weiß

> Wouldn't it be better to separate the whole push notifications from the XEP-0198 sessions? There is no association with it in the Push Notifications XEP-0357. It seems it is...

> Do you have a _better_ solution? I think it's better to fix client issues on the client side. > there aren't really any better desktop/Qt clients AFAIK? I'd try...

> there's no reason to think it's a client issue. In that case it will be easy to reproduce with other clients, right? Could you do that to double-check?

Another thing: > I have the Psi+ OMEMO plugin on the sender, but I don't know if it was enabled or not. Please always double-check such issues can be reproduced...

I'll close this issue for the moment then. If you run into it again and manage to reproduce the problem with OMEMO disabled, feel free to open a new one...

> @weiss: Have you seen comments from @iPPLE? Yes. As I've submitted this PR, I'm notified on comments. Actually, I've enabled all notifications for the ejabberd repository, so there's no...

@iPPLE > keep me posted when the patch will be done for WebSocket Actually, I didn't plan to support WebSocket (as it's not super-trivial and I don't need it myself)....

@badlop, everything you say is correct, and your ideas make sense. However, the solution I have in mind would be to get rid of the URLprocess mapping altogether by having...

As far as I can see, the only real change is checking whether the MIME type specified with the XMPP slot request matches the MIME type specified with the HTTP...

@mdosch, messaging.one now has [the commit in question][1], just in case you'd like to test it. If things look fine, this issue could be closed I guess. [1]: https://github.com/processone/xmpp/commit/1b1418ab2f79b26c31a6cd6c91d32fb477b56850