[IRCServices] Adding features to services

[Chris]

What do you gain by this? From how I read it, only IRCops can drop
channels. That can be a major pain. Users
should be able to drop stuff by themselves without having to go ask
somebody to do it for them, and getting put on a waiting list for the Opers
to get around to dropping their channel. I'm sorry, but if I read this
correctly, this isn't a good idea IMHO. I know if I were a user it'd really
piss me off.
Just my $.02

-Chris

P.S. I would like to see the aop/sop/av/etc. commands implemented into
services in replace of the "dreaded" ACCESS =)

----------
> From: Rafael Ritter <rafael at kapa.procergs.com.br>
> To: ircservices at ender.shadowfire.org
> Subject: Re: [IRCServices] Adding features to services
> Date: Thursday, November 18, 1999 6:18 AM
> 
> Just a suggestion:
> in my server, I had disabled the DROP and SET FOUNDER commands. To use
this
> command you need to be an IRCop.
> This simple change dont let users to stole channels from another users.
> They can even stole de password, but the channel's INFO allways will show
> the nickname of real founder. If someone, ask for a password or something
> relative, you only need to look at channel INFO.
> 
> Rafael Ritter
> Equipe VIA RS
> 
> At 11:10 18/11/99 +0200, you wrote:
> >
> >This is just a quickie based on what I read earlier.
> >
> >If you're going to add features to ircservices, especially if you intend
> >(or atleast, would like) your features to be incorporated into newer
> >releases, you MUST make sure ALL your code changes will accomodate ALL
> >supported IRCds.
> >
> >The way Andy originally coded services makes this quite easier... you
have
> >a number of compile-time directives which compile in the appropriate
code
> >based on the ircd selected at configuration.
> >
> >For example:
> >
> >	#ifdef IRC_DAL4_4_15
> >		... code ...
> >	#endif
> >
> >The expressions available are:
> >
> >	IRC_DALNET, IRC_DAL4_4_15, IRC_CLASSIC,
> >	IRC_UNDERNET_NEW, IRC_TS8, IRC_UNDERNET, 
> >
> >Don't suppose anyone is bored and would like to outline the differences
> >between these IRCds?  Maybe add it to a programming FAQ for services
which
> >another bored person could make?
> >
> >Lastly, I agree with the need for an additional list for the CODING of
> >ircservices.  Feature suggestions and things help requests are fine for
a
> >normal list, but I think a place where people could discuss
implementation
> >of certain things and what they break, how to fix these things, etc,
would
> >be constructive.
> >
> >- Gav
> >
> >---
> >Gaven Cohen aka Kinslayer <dragon at wastelands.net> www.wastelands.net
> >freelance sysadmin/programmer HABONIM DROR linux, fantasy enthusiast
> >RSA/1024 0xFC82B78F 4B 43 3C 20 47 58 AF AC  DB 1E 7F 6E 64 08 15 7E
> >
> >---------------------------------------------------------------
> >To unsubscribe, send email to majordomo at ender.shadowfire.org
> >with "unsubscribe ircservices" in the body, without the quotes.
> >
> >
> 
> ---------------------------------------------------------------
> To unsubscribe, send email to majordomo at ender.shadowfire.org
> with "unsubscribe ircservices" in the body, without the quotes.
---------------------------------------------------------------
To unsubscribe, send email to majordomo at ender.shadowfire.org
with "unsubscribe ircservices" in the body, without the quotes.