On 02/04/13 11:48, Dave Cridland wrote:
But if you want to use roster groups as first-class items, then they need to have jids, and you go from there. If you're happy to move the complexity client-side, then that's fine.
I guess so. My concern is that this kind of approach would move complexity to *every* client, rather than just clients that wants to support blocking by group, to be able to accurately understand (and show the user) who is and is not blocked.
> If you get into blocking roster groups, you have to consider what happens if you unblock a JID which is inside a blocked group; how you represent to the user that moving a user out of a group they've blocked might (?) unblock them; etc. UI considerations. :-)
Sure :) (once you've defined what the actions mean at the protocol level). And then, once again, it's every UI's consideration. One of the nice things about 0191 (versus privacy lists) is that the simple conceptual model makes the UI author's life easier.
(Ahem. One of these days I'll finish bolting 0191 into Telepathy…) -- Will
