Hi, Thanks for your contribution Nicolas and Timothée. Le lundi 26 octobre 2026, 05:16:08 heure normale d’Europe centrale Nicolas Cedilnik a écrit :
Hi,
1) I hate hierarchies. Amen, brother. I hope this doesn't reach the ears of some of your clients famously known for being pretty serious about hierarchy, though? :oP 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.
That's what XEP-0496 (Pubsub Node Relationships) is for, you have a clean way to do nodes hierarchy and maintain them, and for non supporting pubsub service it stays a flat list. if you are going the directory ID ways as in your proposal, the directories structure should not be in an item. We should have something like pubsub attachments, but for the node itself. I'm wondering if node metadata could be good fit here. Another option is to uses "tags" in a similar way as for roster, with a separator for hierarchies. The main issue is renaming in this case. Regarding the feature itself, with my council hat on, I'm in favor of it, it's a nice addition. Best, Goffi