View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001745 | unreal | ircd | public | 2004-04-18 14:07 | 2007-04-27 06:03 |
| Reporter | Technomage | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | All | ||||
| Summary | 0001745: Adding oper viewable-only field(s) to whois | ||||
| Description | Feature request: Implement a line that displays in the WHOIS response - it is only visible to ircOps, and is also settable/appendable by ircOps via a priviledged irc command. It would be bound by nick (if registered) or user@host mask (if not registered). I believe this would be similar to the currently implemented SWHOIS line, but only visible to ircOps, and changable in real time as opposed to in the config file. (We could call this the 'Clueless Wonder' field, cause there's a heap of those running around) An expansion of the idea would be to have multiple fields that could be set/unset/edited/deleted on a per-nick/per-user@hostmask basis. As an example, this could be very useful for identifying and/or tracking of problem users, and users who skirt the lines of the server rules. Or for tagging various bots that don't look like bots! :) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
That sounds like a cool idea, I would have to agree with Technomage on that idea :) |
|
|
Well there definately would not be multiple fields, I can guarantee that. I'm not going to add a super complex system like that for such a basic task. And it also definately would not be bound by user/host like you suggest, and even more definately not by registered nickname. Those are services features, not IRCd features. Furthermore, I don't quite see the point. Tagging bots? Isn't that what umode +B is for? Breaking the rules? Well there are dozens of commands to deal with that, I don't see why you need to mark someone as a rule breaker... |
|
|
Well not not users breaking rules but what about people who are bending them. Ie not breaking rules but need to keep a eye on or have been previously warned? Some times users don't want to take a hitler style approach and just kline for the first small offence, like a argument between two users? |
|
|
Well, the list was not designed as an exhaustive list of reasons :) How about: suspected (but not yet proven) spambots, potential (but not yet proven) DDoS hosts/nicks, possible ban-evader nicks/uhosts, possible channel/user harassers, VIP users (although what a VIP on irc would be, I dunno). As far as complexity, it's basically the gline/qline logic applied to a whois field, isn't it? Just another class of line which doesn't kill the offender, but just tags the whois data with the comment. |
|
|
I agree with codemastr, if this was implemented it would be just a simple command (from opers/services) to 'tag' a user, not something with *lines, config directives, exceptions, and what not. However that shouldn't be a problem for you, services (or a module) would just tag them whenever they connect or do anything suspicious. So, if implemented and you would want to do it on user@host or registered nick it would be services maintaining a 'list'. Still, I'm not totally sure if this is useful. Like I can think of: - a user connects - services tag the user as 'suspected spambot' because he matches a list of X000 suspicious usernames or other criteria that have quite some false positives - oper can then look into this But then... why wouldn't services/whatever just send a message/notice to (eg) #opers about this.. why would they have to be "tagged". Tagging would mean you only see it when you do a /whois, that's only "after you wonder who it is".. Other stuff like 'CHGSHsd Friendz0r :This is a friend of Syzop!!! plz not to kill' also seems a bit.. *ahem*. And then you have 'CHGfdsdh Idiot :This is an idiot, keep an eye on him'.. hmmm ehhhh. I can see some use for it for the larger nets (>1000) because then it might get a bit hard to remember every trouble maker, but.. I don't know... As you can see I'm still unsure. |
|
|
Better suited for services/module |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-04-18 14:07 | Technomage | New Issue | |
| 2004-04-18 14:16 | mitchellj | Note Added: 0005883 | |
| 2004-04-18 14:25 |
|
Note Added: 0005884 | |
| 2004-04-18 14:37 | mitchellj | Note Added: 0005885 | |
| 2004-04-18 14:42 | Technomage | Note Added: 0005886 | |
| 2004-04-19 12:00 | syzop | Note Added: 0005889 | |
| 2007-04-27 06:03 |
|
Relationship added | child of 0003284 |
| 2007-04-27 06:03 |
|
Status | new => closed |
| 2007-04-27 06:03 |
|
Note Added: 0013852 | |
| 2007-04-27 06:03 |
|
Resolution | open => fixed |
