Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[therock247uk]

What does everyone think about the recent changes? ie opers being able to be kicked from channels cause they don't ID first (the restricted option is on) and how services opers can't do a simple /os global anymore only admins can... I know theres a mod that allows you to say who can do what commands but it does seem silly to me.

[Freekie]

I agree.  
It seems that they have been making Services Opers more and more "useless".  It basically seems that services opers are "trusted" that they can use akill and other commands, but, dear god,  if they want to send out a global to alert users of a netsplit or important issue, and they are rejected.  
Seems a bit silly.  

Its not that we want Services Opers to equal an Admin, but you are taking more and more of their clearance away all the time.

[Jan Milants]

being ircop should come with no extra privileges in channels they wouldn't have access to without their oper status. being oper is a network/server related privilege...

as for global, it s a command used to administrate the network and therefore falls in the domain of SAs. SOs only get access to commands needed on a daily basis to maintain the networks operation.

edit: SO have access to
    * MODE
    * KICK
    * CLEARMODES
    * AKILL
    * SGLINE
    * SQLINE
    * SZLINE
    * CHANLIST
    * USERLIST
    * SESSION
    * EXCEPTION
... wouldn't call that useless.
that s what needed to take care of daily operation.
as for informing users about a netsplit... they can see it for themselves.

actually being admin add less extra commands then being oper..

also opers were given access to the SASET command which was previously restricted...

[Edited on 29-4-2008 by Viper]

[Jobe]

Also in most IRCd's /oper's are perfectly capable if doing "/notice $*.<tld> <message>" to send a message to all users on servers with names that match the glob mask "*.<tld>" in that example.

A recent change in UnrealIRCd, means opers can use "/notice $* <message>" without the requirement for at least 1 "." and at least 1 character after the "."

[Edited on 29-4-2008 by Jobe1986]

[Jan Milants]

For those interested: link to bugtrackter on entry on this subject.

[therock247uk]

Its nice that we have ns saset but we can't /ns nickname info all to see there email addy to send the password to.

[Jan Milants]

for obvious reasons SASET PASSWORD is further restricted to SAs anyways
and info all may contain a users' private details which he would probably not want to be accessible except to a most limited group.

there is sendpass and with encryption there s a 3rd party module that allows SO a reset i think..

[Edited on 29-4-2008 by Viper]

[therock247uk]

I can use saset password on a network im a services oper on...

[Jan Milants]

oh nvm.. i just took a quick look at the code and saw an admin check so thought admin, but apparently it was only the check to make sure the target isn't an admin

[Freekie]

It does seem silly to me that we can change a users password for them, but can't see the email address they used to register with to make sure that it really them.  Don't you think?

[katsklaw]

Originally posted by therock247uk
I can use saset password on a network im a services oper on...

Anope does not add/delete features simply because some other services on XYZNet does it. Sorry.

Additionally, Anope is Open Source software licensed under GPL. This means you are more than welcome to make all the changes you like and get rid of the silliness.

[Pieter Bootsma]

The improvements made related to bug 729 actually allowed services opers to do more. Services Opers can now do nearly every daily maintenance required, while Services Admins get to do more network-maniging stuff.

I do agree that opers should have the right to show all NickServ info; actually, i just fixed that in SVN (r1393).

[therock247uk]

Thanks much appricated.