[standards-jig] UPDATED AGAIN: Multi-User Chat, v. 0.4

Richard Dobson richard at dobson-i.net
Thu Sep 19 17:19:46 UTC 2002


Yea I know it was just stating a fact about how the /irc style commands were
good, and then went on to suggest improvements to the new namespace
protocol.

Richard

----- Original Message -----
>From: "David Sutton" <jabber at dsutton.legend.uk.com>
To: <standards-jig at jabber.org>
Sent: Thursday, September 19, 2002 6:12 PM
Subject: Re: [standards-jig] UPDATED AGAIN: Multi-User Chat, v. 0.4

Hi there,

 This isn't really an issue, you just have to look at the problem from a
 different angle.

 If you prefer irc-style commands, then why not have a plugin for
 chatbot which you send commands, it translates and sends the server
 your request in the new protocol? That way the server implementation
 stays clean, with admin functions seperate from message functions.

Regards,

 David

On Thu, Sep 19, 2002 at 10:01:55AM +0100, Richard Dobson wrote:
> Hi,
>
> Changing it to use a special namespace is good but....
>
> Clients now HAVE to be updated to support this, the previous method was
easy
> and would work now without modification increasing the initial user base.
>
> <iq type='get' to='room at service' id='ban2'/>
>   <x xmlns='jabber:gc:admin'>
>     <banned/>
>   </x>
> </iq>
>
> Why under the iq is it in an x element?
>
> for the grants and revokes instead of:
>
> <iq type='set' to='room at service' id='voice1'/>
>   <x xmlns='jabber:gc:admin'>
>     <grantvoice>somecooldude</grantvoice>
>   </x>
> </iq>
>
> wouldnt it be nicer to do:
>
> <iq type='set' to='room at service' id='voice1'/>
>   <voice xmlns='jabber:gc:admin'>
>     <grant>somecooldude</grant>
>   </voice>
> </iq>
>
> <iq type='set' to='room at service' id='voice1'/>
>   <voice xmlns='jabber:gc:admin'>
>     <revoke>somecooldude</revoke>
>   </voice>
> </iq>
>
> This allows easy extension of the different types allowed having to parse
> for grantvoice and revokevoice is more complicated as is adding support
for
> new privileges, a bit of a hack, when xml is capable of so much more.
>
> its also then easier to get the lists of people on each list:
>
> <iq type='get' to='room at service' id='voice1'/>
>   <voice xmlns='jabber:gc:admin'/>
> </iq>
>
> with response of
>
> <iq type='get' to='room at service' id='voice1'/>
>   <voice xmlns='jabber:gc:admin'>
>     <jid>user7 at domain.com</jid>
>     <jid>user1 at domain.com</jid>
>     <jid>user4 at domain.com</jid>
>   </voice>
> </iq>
>
> this could be applied to all the types like banned and invite.
>
> also the others can be simplified as:
>
> <iq type='set' to='room at service' id='ban1'/>
>   <ban xmlns='jabber:gc:admin'>
>     <jid>totaljerk</jid>
>     <jid>otherjerk</jid>
>   </ban>
> </iq>
>
> <iq type='set' to='room at service' id='ban1'/>
>   <kick xmlns='jabber:gc:admin'>
>     <jid>totaljerk</jid>
>   </kick>
> </iq>
>
> or the banning could be done as:
>
> <iq type='set' to='room at service' id='ban1'/>
>   <banned xmlns='jabber:gc:admin'>
>     <add>totaljerk</add>
>   </ban>
> </iq>
>
> and un banning as
>
> <iq type='set' to='room at service' id='ban1'/>
>   <banned xmlns='jabber:gc:admin'>
>     <remove>totaljerk</remove>
>   </ban>
> </iq>
>
> or maybe done as (more inline with previous work like the Server based
> privacy rules):
>
> <iq type='set' to='room at service' id='ban1'/>
>   <banned xmlns='jabber:gc:admin'>
>     <item jid="totaljerk" type="add"/>
>   </ban>
> </iq>
>
> <iq type='set' to='room at service' id='ban1'/>
>   <banned xmlns='jabber:gc:admin'>
>     <item jid="totaljerk" type="remove"/>
>   </ban>
> </iq>
>
> Overall I think the new namespace for admin is good, but does need a bit
of
> tweaking.
>
> Richard
>
> ----- Original Message -----
> From: "Peter Saint-Andre" <stpeter at jabber.org>
> To: <standards-jig at jabber.org>
> Sent: Thursday, September 19, 2002 5:29 AM
> Subject: [standards-jig] UPDATED AGAIN: Multi-User Chat, v. 0.4
>
>
> > I have just released version 0.4 of the multi-user chat JEP. This
contains
> > some major changes, including:
> >
> > 1. Removed that /kick and /ban junk, what a hack!
> >
> > 2. Added protocol for including participant privileges (admin and voice)
> > in presence updates.
> >
> > 3. Added use cases for granting/revoking voice and approving/denying
> > messages held for approval in moderated rooms.
> >
> > 4. A few other niceties.
> >
> > I think this is now getting to be fairly complete and even (*gasp*)
worth
> > considering in a serious manner. I will probably release a 0.4.1 version
> > by about 18:00 UTC tomorrow in order to address a few minor points, so
> > keep those cards and letters coming! :)
> >
> > http://www.jabber.org/jeps/jep-0045.html
> >
> > Peter
> >
> > --
> > Peter Saint-Andre
> > Jabber Software Foundation
> > http://www.jabber.org/people/stpeter.html
> >
> > _______________________________________________
> > Standards-JIG mailing list
> > Standards-JIG at jabber.org
> > http://mailman.jabber.org/listinfo/standards-jig
> >
>
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig

--
David Sutton
Email: dsutton at legend.co.uk
Jabber: peregrine at legend.net.uk





More information about the Standards mailing list