home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!manuel.anu.edu.au!coombs!phone
- From: phone@coombs.anu.edu.au (matthew green)
- Newsgroups: alt.irc
- Subject: Re: Protecting privacy of users against IRCops; making umode +i effective.
- Date: 19 Dec 92 16:31:00 GMT
- Organization: Australian National University
- Lines: 21
- Message-ID: <phone.724782660@coombs>
- References: <1fv607INN50n@grasp1.univ-lyon1.fr> <1992Dec09.212330.114790@zeus.calpoly.edu> <1992Dec10.161356.26601@murdoch.acc.Virginia.EDU>
- NNTP-Posting-Host: 150.203.76.2
- Keywords: invisibility privacy and IRCops
-
- gl8f@fermi.clas.Virginia.EDU (Greg Lindahl) writes:
-
- >In article <1992Dec09.212330.114790@zeus.calpoly.edu> asamonte@hertz.elee.calpoly.edu (Just some loser...) writes:
-
- >>Let's take Scott for example. Or rather take one of his floodbots.
- >>A nick changing robot that will endlessly harass user(s). Now if
- >>all the servers worked as per your code what would happen to one of
- >>scott's bots that was umode +i and changing nick all the time. How
- >>would we ever be rid of it? Since it would probably be on the santafe
- >>server, the only solution (which is bad) is to /squit.
-
- >How can you get rid of it even if you can see it? The only way to "get
- >rid" of it is user@host ignore, which works just fine whether or not
- >it's umode +i.
-
- I am loath to say this, but KILL follows nick changes, rather well at
- that...
-
- phone
-
- say NO to non-local operator KILLS..
-