A workflow for private messaging #1
Description
After reading the code and trying out this plugin, I better understand the standard for being able to subscribe and authorize to a specific user. However, I can only ever seem to do it one way.
I'm working with a resource (user@server.com/resource) which I'm not sure this plugin supports but I couldn't get a clear picture from the data being sent back and forth to ejabberd whether this was an issue or not. In any case, this was always false for me, even after checking the roster manually to ensure the to jid existed.
So my workflow was simply to add a jid: roster.add(jid, username, ['friends'])
Then subscribe: roster.subscribe(jid)
On the other client, it would receive the subscribe presence, check if they existed in the friends list and then roster.authorize(jid). Both clients would do this because the friends list exists outside of ejabberd and syncs with the roster. However, the problem is I could never ever get them to say subscribed="both". It would say "from" and "to" and there was nothing I could do about it.
What am I missing?