On Mon, 2026-10-26 at 09:36 +0000, Dave Cridland wrote:
(Again, I wonder if a full bushy tree is the right option, as opposed to, say, tagging/groups).
I was thinking the same and then read the actual specification only to find that - as far as I understand - it doesn't do a full tree, it really only has a list (not tree) of "directories" (I will call them groups throughout the rest of this message) and then each bookmark through bookmark extension is put into a group with an ordering weight. So what this specification currently brings in terms of features is: 1. ordering of groups (as they are in an ordered list) 2. assignment of bookmarks to a group id 3. ordering of bookmarks within a group 4. group id-to-title mapping Regarding 2 and 4: This makes me wonder how to do UX when two ids map to the same title. In Roster Groups we don't have IDs, we just group by the title of the group, thereby entirely eliminating this issue. Regarding 1 and 3: It struck me that there is two ordering mechanisms that are both independent and work differently (directories/groups ordered by an ordered list and bookmarks within a group ordered by assigned weights). It seems this can be collapsed to just one ordering, where you just order all bookmarks and then may decide to assign a group title to a subset of the bookmarks that is consecutive by weight to create a group. So I feel we could reach the same functionality essentially by assigning just weight and group title via a bookmark extension. If nesting of groups is really desired, it could be realized in a similar fashion as we do for roster: by using a delimiter in the group name. I assume the idea of id-to-title mapping was to make a group rename a relatively lightweight operation, but at least to me that seems like not a very common operation and not doing so IMO significantly reduces complexity. Marvin