On Sun, 2009-11-08 at 02:40 -0700, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/25/09 6:08 AM, Tuomas Koski wrote: > > Cheers all, > > > > I may have a need for a new affiliation state: 'Moderator' > > > > User with affiliation state 'Moderator' would be like the 'Publisher', > > but could also modify the affiliation states of other node's > > subscribers (excluding 'Owner' and this possible new affiliation state > > 'Moderator'). > > > > > > Example use case could be for example: > > > > There is a popular Pubsub -node with high traffic and lots of > > subscription requests. Also there is one drunken 'basterd' with > > Publisher affiliation who starts to send unwanted items to the node. > > The Owner of the node is not online. > > > > Users with 'Moderator' affiliation would be able to Outcast the > > drunken one and accept/deny subscriptions to the channel. > > > > > > Of course to add this new affiliation state would have a need to > > change a bit the XEP-0060's "Owner Use Cases" and/or then allow this > > new affiliation state to use " > > http://jabber.org/protocol/pubsub#owner"; namespace. > > > > > > Does anyone come up with a better idea how to handle the above use case? > > What you are asking for is very similar to a room administrator in MUC, > I think. I'm not yet convinced that we need an affiliation for this (I > would prefer not to multiply affiliations beyond necessity). I see the > need in MUC because it's a real-time communication system.
I agree. Just have multiple entities with the owner affiliation. ralphm
