View Issue Details

IDProjectCategoryView StatusLast Update
0003291unrealircdpublic2019-10-14 15:43
Reporterlocal8 Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionno change required 
PlatformN/AOSN/AOS VersionN/A
Product Version3.2 
Summary0003291: [Feature/request] View channels in /whowas
DescriptionApologies if it was already suggested. My small search didn't reveal anything. I'd like to suggest the ability to see what channels a client was in. So a /whowas local8 would return something like: local8 was ident@host gecos; local8 was on server at time; local8 was in #channel1, #channel2, #etc. One of our past network coders had added in that ability, and with later versions coming out, it might be nice to have it professionally coded in from the beginning. Other thoughts?
Steps To ReproduceN/A
Additional InformationIt appears the code was added in client exitings, and nickname changes. Any place the add_history() function was called.
TagsNo tags attached.
3rd party modulesN/A

Activities

Bricker

2007-04-22 20:35

reporter   ~0013635

i dont like this much, as the output would just be ugly, and it would take up that much more RAM, and to keep up with that information i believe would increase cpu usage as well. Maybe im wrong, anyone else?

Bricker

2007-04-22 20:36

reporter   ~0013636

should also note, that if the channel was in, say 20 channels, well OMG

Stealth

2007-04-23 00:27

reporter   ~0013637

Oh yes, let's break a standard message...

<- :server 314 you nick ident host * :real name
<- :server 312 you nick server :signoff time

There is nowhere in those numerics to add a multi-parameter list. You'd need to create a new numeric for this purpose.

local8

2007-04-23 05:17

reporter   ~0013638

The numeric would be the channel whois numeric, just as the server, 312, is the server whois numeric:

314 local8 dave id host * :If I ever develope Thanatophobia, kill me.
312 local8 dave unreal.server :Mon Apr 23 03:11:13 2007
319 local8 dave :#channel20 #channel19 #channel18 #channel17 #channel16 #channel15 #channel14 #channel13 #channel12 #channel11 #channel10 #channel9 #channel8 #channel7 #channel6 #channel5 #channel4 #channel3 #channel2 #channel1

The only concern would be memory and usage. If most people limit channel to 20, what drawbacks would that be memory wise, 20 channels, for...200 users? The nickname history would just fill up quicker, and a nick that was online 2 hours ago might not return anything.

stskeeps

2007-04-24 05:59

reporter   ~0013660

I honestly think this would be better for a service, as it can handle the data load a lot more, perhaps connect to a DB.

stskeeps

2007-04-26 06:12

reporter   ~0013727

Acknowledged, but I think it should be in a 3rd party service/module.

Stealth

2007-04-26 13:50

reporter   ~0013744

Perhaps to make it possible to write a module that does not require people releasing their own version of WHOWAS, we should add a hook for before RPL_ENDOFWHOWAS is sent. This would make it possible for people to add their own replies to WHOWAS, such as a channels list

syzop

2019-10-14 15:43

administrator   ~0020980

I think we can drop this idea, since nobody expressed interest in the past 12 years.

Issue History

Date Modified Username Field Change
2007-04-22 13:23 local8 New Issue
2007-04-22 13:23 local8 3rd party modules => N/A
2007-04-22 20:35 Bricker Note Added: 0013635
2007-04-22 20:36 Bricker Note Added: 0013636
2007-04-23 00:27 Stealth Note Added: 0013637
2007-04-23 05:17 local8 Note Added: 0013638
2007-04-24 05:59 stskeeps Note Added: 0013660
2007-04-26 06:11 stskeeps Relationship added child of 0003284
2007-04-26 06:12 stskeeps Note Added: 0013727
2007-04-26 06:12 stskeeps Status new => acknowledged
2007-04-26 13:50 Stealth Note Added: 0013744
2010-07-14 17:49 syzop QA => Not touched yet by developer
2010-07-14 17:49 syzop U4: Need for upstream patch => No need for upstream InspIRCd patch
2010-07-14 17:49 syzop U4: Upstream notification of bug => Not decided
2010-07-14 17:49 syzop U4: Contributor working on this => None
2010-07-14 17:49 syzop Severity minor => feature
2019-10-14 15:41 syzop Relationship deleted child of 0003284
2019-10-14 15:43 syzop Assigned To => syzop
2019-10-14 15:43 syzop Status acknowledged => closed
2019-10-14 15:43 syzop Resolution open => no change required
2019-10-14 15:43 syzop Note Added: 0020980