[Foundation-l] Status of cloak requests

[Dan Rosenthal]

I use colloquy on a mac. To op and de op, etc. I have to remember and  
type out the exact /msg chanserv op #channel (or whatever it is),  
because none of the mac IRC clients have good compatibility with  
freenode's services. Other networks have simple commands like !up and ! 
down. They also allow tools like /onotice, which works like the normal  
notice command, except it only goes to people who have the op flag  
turned on, allowing them to discuss op things within a channel, and  
non-ops won't see.

It's a continual source of frustration for me to have to fight against  
IRC to get it to work the way it should, when other networks are so  
easy. If we had a Wikimedia IRC network (that was using normal style  
IRC commands, not freenode's strange ones), it'd make being an op so  
much easier, and that would have a net effect on the enjoyment of the  
channel users too.

John if you know of a way that I can simplify the op/ban/deop process,  
that will work in colloquoy on a Mac, I'm open to suggestion.

-dan


On Feb 26, 2008, at 4:58 PM, John Reaves wrote:

> Well most of our bans are just zombie proxies, or whatever they're  
> called,
> so there's no real need for a long ban.  Persistent trouble makers  
> have
> longer expiries or are added to the autorem.  It takes what, maybe .5
> seconds to type your /cs op shortcut?  I for one can just click a  
> nick and
> op/remove/ban/deop in one fell swoop.  Discussing operator issues in  
> channel
> just invites drama.  I don't know what /onnotice is but it sounds  
> useful.
>
> --John Reaves
>
> On Tue, Feb 26, 2008 at 4:48 PM, Dan Rosenthal  
> <swatjester at gmail.com> wrote:
>
>> Actually, freenode is the only network I know that does that. For the
>> same reasons you view a network setup with perma-ops and long bans as
>> stupid, I view Freenode's setup that invites drama, and attacks and
>> hinders ops, as stupid. Every other IRC network I've been on, from  
>> big
>> ones of the EFnet/Undernet type, to smaller ones, the ops are always
>> opped so they are a) easily identifiable and we don't need a special
>> channel just to present issues to them; b) able to receive the  
>> benefit
>> of commands like /onotice, c) much faster to react to !kb a user (all
>> an opped user needs to do is type !kb name, or right click , kickban,
>> rather than /msg chanserv for ops, kick the user, deop self), d) It
>> shows to flooder types that there are ops in that channel,
>> discouraging attacks. For much the same reason, bans last for periods
>> of a few weeks unless specifically overturned, rather than banning
>> people and then allowing them back in a few days later to cause more
>> trouble.
>>
>>
>>
>>
>> On Feb 26, 2008, at 3:37 PM, John Reaves wrote:
>>
>>> Catalyzing is bit lame some times, I'll give you that.  But being
>>> opped all
>>> of the time and keeping bans for longer than a few days for people
>>> without a
>>> history of abuse is just plain stupid and I would assume any IRC
>>> network set
>>> up by WMF wouldn't allow it either.
>>
>>
>> _______________________________________________
>> foundation-l mailing list
>> foundation-l at lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/ 
>> foundation-l
>>
> _______________________________________________
> foundation-l mailing list
> foundation-l at lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l