On Sun, 25 Oct 2026 at 19:59, Philipp Hörist <philipp@hoerist.com> wrote:
Yes i think you miss the point, but there are some confusing things in the XEP.
Thanks, yes.
First i dont see where the XEP says, the client does not want to use a name the user sets. If the bookmark name attribute is filled, this should be used, and this XEP has no relevance in this case.
Right, this is the missing feature.
I think the idea is a gateway like for Matrix, fills your Bookmarks with matrix chatrooms. Now as a client you log in, and get 50 known matrix rooms synced. But these are just "known" rooms, not necessarily rooms you want to autojoin on that client.
If you dont join the room on sync, no client will disco a room which we dont intend to join. Hence we have nothing in the Bookmark but the JID.
So this would be a way, how a gateway can tell you upfront what the name of the groupchat is, so you dont just have the JID.
Got it. Now I'm wondering why a gateway would publish the name of all available groupchats as bookmarks. I do, however, run into some related problems from time to time. For example, joining a chatroom on my local server is easy - my client grabs disco and uses it for type-ahead search. But joining one on a remote server is hard because my client doesn't know which server I might want. Being able to have a bookmarked list of MUC services to disco would feel like it's solving this problem as well as mine. (Bearing in mind the name is in disco#items).
Now why does the XEP talk about the "name" attribute, because it tries to counter the argument that someone potentially raises, "Why dont you publish the name into the existing name attribute".
I think this would be unclean, because the name attribute is currently filled only by users, if they assign a name themself. If a server sets this, a client cannot differentiate anymore between a user chosen nick and one another identity assigned.
Hence the whole proposal for an additional attribute.
Right, this makes more sense now.
This has also relevence in non-gateway cases.
For example in Gajim we store all known MUCs in bookmarks, also ones we do not join anymore currently.
If i setup Gajim on a new client, it downloads all the MUCs, but for the chats we dont autojoin, we only have the JID. It would be nice if a server component which has all disco info, can simply update my bookmark so it always has the right server name, without me executing disco on all known mucs.
And with that, I'm now confused again. Easy to do. All known MUCs? Presumably this is all MUCs that Gajim has ever joined, or is it all MUCs it's ever discovered via disco, MUC search services, etc? Dave.