Hi, Philipp already defended this better, so I don't have much to add. A few small points though:
but doesn't want to use the name the user explicitly chose
My wording must be off somewhere because that is precisely *not* the intent. :) Slidge used to write in the basic 'name' field for bookmarks (roster items too btw) but this is a bad approach. These fields are meant for user-set custom names, which should not be overridden by anything automated.
we can imagine that your homeserver does fill such a attribute for you also for XMPP MUCs.
Indeed, a 3rd use-case to add, thanks.
Now I'm wondering why a gateway would publish the name of all available groupchats as bookmarks.
Because that is what clients use for the "start chat"-like dialogs so that's the best integration. FTR, slidge also provides an adhoc command to list the groupchats you can join. This is fine but not as well integrated from the end-user side.
This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.
Oh damn, got my hand caught in the ctrl+c/ctrl+v jar! Thanks for your feedback. -- Nicolas