On Mon, 26 Oct 2026 at 04:16, Nicolas Cedilnik <nicoco@nicoco.fr> wrote:
2) I'm a bit $thing about putting a hierarchy as a different item in the same pubsub node. What we've done previously is used a distinct node where the node id is derived from the node that "uses" it. So in the case of bookmarks, we might use urn:xmpp:bookmarks:1:hierarchy for example.
I was definitely expecting this feedback. With my gateway dev hat on, this does not change much for me. edhelas will likely chime in to defend this better than me, but I think it makes it more annoying for clients to make sure bookmarks and their categories stay consistent with a different node, and more IQs and pubsub#events to handle in general.
Edhelas sent me one or two messages last night, indeed. Anyway, this is true, but I don't think existing clients expect to have heterogenous nodes - that is, a node where the items have different syntaxes. They'll likely treat it as an error, and it feels possible they'd simply remove the erroneous item. It's all, of course, a trade-off. You could also inject the hierarchy directly into the bookmark extension data, giving its path, and letting clients figure out the hierarchy from there. (Again, I wonder if a full bushy tree is the right option, as opposed to, say, tagging/groups). Dave.