[Standards] MIX: Roster entries -> private PEP node (or something)

Jonas Schäfer jonas at wielicki.name
Sat Sep 14 14:28:58 UTC 2019

On Montag, 17. Juni 2019 18:20:53 CEST Daniel Gultsch wrote:
> Hi,
> at the last summit we sort of came to the conclusion that we want to
> get rid of MIX roster entries and instead place 'joined channels' into
> a private PEP node or some other (non roster) place.
> The arguments in favor of roster were that it can be used to
> automatically send presence; However the same is true for any other
> storage place as the server can just decide to do that.
> Speaking against putting it in the roster is that it couples roster
> and MIX (some modern implementations might not want to use a roster
> but want to use MIX).
> For my own implementation i’m currently stuck at this point because
> loading the list of joined channels is the next logical step but
> without defining the syntax to retrieve that (and without having a
> server implementation) I can’t really move forward with that.
> So could we (as a community) reconfirm that we actually want to move
> mix entries out of the roster and then define where we want to store
> them again?

Yes, a private PEP node which is read-only to the clients (write access only 
via the MIX IQ flows) seems very sensible to me.

kind regards,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20190914/7e55ea99/attachment.sig>

More information about the Standards mailing list