Comment by Tepix
11 years ago
The problem right now is persistent connections on iOS. You need to use push messages instead, which requires a plugin on the jabber server and a matching client.
Not something you can expect all your friends to set up.
11 years ago
The problem right now is persistent connections on iOS. You need to use push messages instead, which requires a plugin on the jabber server and a matching client.
Not something you can expect all your friends to set up.
You could also have clients and servers implement http://xmpp.org/extensions/xep-0357.html .
ejabberd doesn't support 0357 [0]. Presumably because their 'pro' version has mobile support.
MongooseIM doesn't support it either, although there is talk of it being implemented [1]
To be fair though, it was only accepted on the 18th March 2015.
[0] - https://www.ejabberd.im/protocols [1] - https://github.com/esl/MongooseIM/issues/405
Hehe, over a week of time and it's still not there!
FWIW, somebody is working on an ejabberd module [1], and there's some discussion [2] on the <standards@xmpp.org> mailing list.
(And ejabberd's community edition supports the XEPs that are relevant to mobile clients too, BTW.)
[1] - https://github.com/royneary/mod_push [2] - http://mail.jabber.org/pipermail/standards/2015-March/thread...
i thought push notifications worked with IM+ on iOS? i am not very familiar with either though, so i'm probably wrong.
There is a number of IM clients for iOS, that store your credential "in the cloud" (use their own infrastructure to terminate the XMPP connection and route push notifications to their clients). This is not ideal for your privacy, to put it into friendly words.
interesting! i think iMessage works like that. not sure that IM+ does, but it might well.