[Standards] Proposed XMPP Extension: Bookmarks 2 (This Time it's Serious)

Matthew Wild mwild1 at gmail.com
Wed Mar 21 17:05:44 UTC 2018


On 21 March 2018 at 17:01, Kevin Smith <kevin.smith at isode.com> wrote:
>
>
>> On 20 Mar 2018, at 18:21, Jonas Wielicki <jonas at wielicki.name> wrote:
>>
>> On Dienstag, 20. März 2018 19:12:57 CET Georg Lukas wrote:
>>>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>>> Title: Bookmarks 2 (This Time it's Serious)
>>>
>>> A number of issues I have with the current Bookmarks XEPs, and that I'd
>>> like to see addressed in the mid-term future (ideally by adding them to
>>> Bookmarks2):
>>>
>>> 1) Auto-Join
>>>
>>> The 'autojoin' flag name is a bit misleading in the time of always-on
>>> clients.  Maybe we should change the text to indicate that a client is
>>> supposed to join and stay joined(!) if this flag is set, and maybe also
>>> to automatically leave when the flag is unset.
>>
>> I’d argue that clients should always stay joined in MUCs the user hasn’t
>> explicitly left. So autojoin is just saying "join the MUC on startup" (and
>> thus, by extension, stay joined).
>
> I’d argue (and did at the Summit) that the opposite is true and that if we want (especially impromptu) MUC to start working nicely across multiple accounts we need clients to react to the user leaving rooms manually by disabling the autojoin and then having other clients leave as well. They only joined because the autoflag was set, so isn’t it logical for them to leave when it’s no longer set?

I agree with this. For an example UI, leaving a room could prompt to
leave the room on the current client, or all clients (i.e. unset
autojoin).

The whole point of the autojoin logic was to keep clients
synchronised. Either we want clients in sync or we don't. And I think
we do.

Regards,
Matthew


More information about the Standards mailing list