|
nenolod
2012-03-07 03:38
reporter
~0016946
|
Agreed. I will try to get a patch going for this in a day or two. |
|
|
nenolod
2012-03-25 21:18
reporter
~0016962
|
I am unable to reproduce this. Are you certain you are NetAdmin? |
|
|
|
I can be NetAdmin, or any other IRCop, I can use my test net. What part are you unable to reproduce? Being able to see /names output as a netadmin externally from the given channel? Or not seeing them as non netadmin? Or unable to view people in the channel externally using a /who #chan as any ircop? |
|
|
nenolod
2012-03-30 03:08
reporter
~0016966
|
I can see NAMES output as NetAdmin when off the channel. I can't see any obvious logic errors in the code, either. |
|
|
|
Yes that's not what I'm confused about. I'm saying that a NetAdmin can use both /names and /who to view people in a channel who are +i without being in it. Any other oper can only use /who to achieve this. I see no reason why all the opers other than NetAdmin can't see +i users in a channel when using /names but can see them when they do a /who #chan, what's the point? |
|
|
nenolod
2012-04-06 00:45
reporter
~0016970
|
I think instead, the appropriate way of handling this is to introduce a new permission, which netadmin would imply.
This would allow for more customization and control over information visibility anyway. Do you agree? |
|
|
|
I think this is fixed in 3.4.x. We use the same "can ircop see this / user see this" type of hooks/callbacks |
|
