View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001636 | unreal | ircd | public | 2004-03-09 00:50 | 2015-07-19 19:58 |
Reporter | Stealth | Assigned To | syzop | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | duplicate | ||
Summary | 0001636: whowas suggestions | ||||
Description | 1. Optional expiry time, set in set::whowas-expire This would be a nice feature for people who dont want the whowas entries left in there until the IRCd resets, or the maximum entries is reached. [REJECTED] 2. Default return number, set in set::whowas-return This can be useful for the people who do not specify a number of entries they want. Any number specified in the /whowas will override the setting. If they want all the results, they can use /whowas nick 0. [PERHAPS] 3. Allow wildcards. Just for the fun of it. [YES, but oper only] 4. /whowas options like '/whowas +h <host>' and '/whowas +g <gecos>' would be useful. Suggested by White_Magic. [YES, but oper only] | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
1. Why not just set NICKNAMEHISTORYLENGTH correctly? I always set it to 500 instead of 2000 (the default) on a small net. Adding expire time would mean more CPU usage (would have to periodically [or on every add] check all the entries for expire time etc...) and not gain much IMO since you have already chosen a memory limit. 2. Uhh 3. Uhhhhhh *run* |
|
Perhaps a limit isn't a bad idea. I'll think about that. And wildcards, not sure. I can see the usefulness. You use Bugz, Bugz-Away, Bugz-Busy, etc. so /whowas Bugz* would make it easier for people to find you, but this also can cause problems when people decide to see what happens when they do /whowas *. |
|
about wildcard, if implemented then it should be oper only of course.. and even then we probably should still have a (default) output limit or else you accidently flood yourself to death. |
|
whowas * would only work if set::whowas-return is set. then that way, if an oper wanted to whowas *, he (or she) would only get the default number of results, if no number is specified. |
|
wheeeeee... /whowas * would be akin to running /list on a large network: suicidal. Maybe only let it happen for say, w00t* rather than *... that is, any part of a nick (*w00t*, *w00t, w00t*...) |
|
w00t: /whowas *a* or /whowas *_* would still return huge data, but that was not my reason of posting. I can, and cannot see the use of this. I can understand why someone wants it even though I personally don't think I will use it. But if it is to be added I suggest making it oper only and a config limit, meaning you can set the max return value to ~20. This way even if you do a /whowas * you will only get 20 resaults, even if you'r oper. |
|
devil, I bring your attention to the post before w00t's last post, and ALL the posts before that. =P |
|
Yeah I'm sorry about that.. |
|
Hmmm... Maybe even restricting to /whowas w00t* ?? I mean, most people I see do things like /nick w00t|toilet w00t|work ... etc. so it would be _used_ and have that restricted to a certain limit (~20?) and then have /whowas *w00t* etc only available to opers..? |
|
[w00t] >wheeeeee... /whowas * would be akin to running /list on a large network: suicidal. On one network (not an unreal network), I did /whois *. I still hate myself. |
|
aquanight: I ran /list on dalnet or something when I didnt know how to use IRC properly. I still have nightmares about that. Down to business: What about my previous post? |
|
erm, this is a little off topic but still covers into " whowas ", since /who can be used to retrieve, cant /whowas be used in a simliar kinda thing for users who was " using " the mask? |
|
Eh? Don't quite get you. |
|
Well w00t, you know with /who you specify masks Eg: /who +h *ipt.aol.com If /whowas could do the same, listing all the people that *WAS* connected on AOL Of course not all the flags would apply, just maybe have +h +n +u +g as the ones you may use, an example would be /whowas +h *ipt.aol.com then it would list all the people that was on aol. |
|
Erm. Wouldnt that end up with _huge_ memory usage on a large network? And besides, is it really necessary? The only thing I can think it would be used is for bans and suchlike... |
|
not really coz the info is stored anyway... when u do a whowas <nickname> you get all there information, thus ur not gaining any extra memory as its already saved, its just another way of retriving the information. |
|
Sorry, my bad. Man im tired. What I meant was, isnt it going to be, like, way to inefficient to search through the address of every user currently connected, and previously connected, and then display that... hm. |
|
/whowas +h <bla> etc seems a good idea. 'description' updated and feature acknowledged. Merged 0001743. |
|
Although this one is actually older, let's use 0002143 for this. |
Date Modified | Username | Field | Change |
---|---|---|---|
2004-03-09 00:50 | Stealth | New Issue | |
2004-03-09 10:17 | syzop | Note Added: 0005379 | |
2004-03-09 12:41 |
|
Note Added: 0005380 | |
2004-03-09 14:07 | syzop | Note Added: 0005382 | |
2004-03-09 21:34 | Stealth | Note Added: 0005390 | |
2004-03-10 21:01 | w00t | Note Added: 0005407 | |
2004-03-11 11:26 | devil | Note Added: 0005415 | |
2004-03-11 15:42 | Stealth | Note Added: 0005420 | |
2004-03-11 16:25 | devil | Note Added: 0005423 | |
2004-03-11 17:18 | w00t | Note Added: 0005424 | |
2004-03-11 18:42 | aquanight | Note Added: 0005437 | |
2004-03-11 19:15 | w00t | Note Added: 0005440 | |
2004-03-22 10:30 | White_Magic | Note Added: 0005572 | |
2004-03-22 17:30 | w00t | Note Added: 0005576 | |
2004-03-25 10:53 | White_Magic | Note Added: 0005585 | |
2004-03-27 10:07 | w00t | Note Added: 0005604 | |
2004-03-27 10:10 | White_Magic | Note Added: 0005605 | |
2004-03-27 10:51 | w00t | Note Added: 0005607 | |
2004-04-18 11:37 | syzop | Status | new => acknowledged |
2004-04-18 11:37 | syzop | Description Updated | |
2004-04-18 11:38 | syzop | Note Added: 0005881 | |
2004-10-29 15:07 |
|
Relationship added | related to 0002143 |
2015-07-19 19:58 | syzop | Note Added: 0018532 | |
2015-07-19 19:58 | syzop | Status | acknowledged => closed |
2015-07-19 19:58 | syzop | Assigned To | => syzop |
2015-07-19 19:58 | syzop | Resolution | open => duplicate |