[Standards] MIX - an approach to JIDs that avoids the four into three problem

Florian Schmaus flo at geekplace.eu
Sat Jun 2 13:04:50 UTC 2018


On 02.06.2018 14:47, Kevin Smith wrote:
> On 2 Jun 2018, at 13:01, Florian Schmaus <flo at geekplace.eu> wrote:
>>
>> On 02.06.2018 13:46, Kevin Smith wrote:
>>>> On 2 Jun 2018, at 11:44, Florian Schmaus <flo at geekplace.eu> wrote:
>>>> I think I'm currently in the
>>>> - messages from channel at service/nick
>>>> - IQs to/from and presence from channel at service/nick/client-id
>>>> (where client-id is a random unique string not containing '/')
>>>> camp.
>>>
>>>
>>> That’s option 2, except that it has to be a stable ID, not nick (and that some IQs are just /user-id not /user-id/client-id, e.g. vcard)
>>
>> Why can't it be the nick?
> 
> The nick’s not stable and life is much better if you don’t conflate the identity and the current nick.

I'm sorry, I confused the many concepts. What is the official name for
participant ID string (the thingy before the # character in the
localpart of MIX addresses in the current spec)? Then replace the name
with 'nick' in my suggestion above.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180602/3fbd232f/attachment.sig>


More information about the Standards mailing list