Hi, Yes i think you miss the point, but there are some confusing things in the XEP. 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. 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. 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. 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. Regards Philipp On Sun, Oct 25, 2026, at 20:38, Dave Cridland wrote:
On Sun, 25 Oct 2026 at 05:44, Daniel Gultsch <daniel@gultsch.de> wrote:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Bookmark last known name Abstract: This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.
URL: https://xmpp.org/extensions/inbox/bookmark-last-known-name.html
The Council will decide in the next two weeks whether to accept this proposal as an official XEP.
I don't object to this - it's harmless, and well designed as far as it goes - but I'm struggling to understand the rationale.
So a client, which has no information cached, wants to show a list of bookmarks, but doesn't want to use the name the user explicitly chose, and presents the "official" name of the chatroom instead? Did I get that right? But only the official name when some other client that supports this protocol last checked?
Obviously, clients can do whatever they want, but ... why? Why ignore what the user explicitly directed?
If what we want to do is shortcut the disco#info for bookmarked rooms, BTW, we can absolutely do that. Imagine a bot-like client that preiodically republishes the disco#info to the item. And that could reasonably be built into the server.
Anyway, all this might be just me missing the point, or not being hip with the yoof, or something.
Dave. _______________________________________________ Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org