View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003165 | unreal | ircd | public | 2006-12-26 14:06 | 2015-05-27 18:33 |
| Reporter | Bricker | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | wont fix | ||
| OS | ALL | OS Version | 0 | ||
| Product Version | 3.2.7 | ||||
| Summary | 0003165: add "is channel visible?" hooks // only +z users can see specific information | ||||
| Description | Maybe this is a crazy idea, but what about on a network that has a lot of +z (SSL) users who don't want other people to see where they are if they are using a +z channel. Such as Whois On: BrickerII ([email protected]) Real Name: KEKEK Channels: @#Shit Total Channels: 1 Common Channels: 0 Server: maybe.tspre.org (the reason why socks disappear in the wash) Secure Connection End Of Whois who is on #Shit, and #Shit has +z. Maybe some sort of usermode like +z +g so that only other +z users can see the +z channels. (I know it may sound weird, but say theres a place you have to be +z to be there in the first place, and simply dont wanna use +s because users who are +z should be able to find it. | ||||
| Additional Information | eh...maybe its a stupid idea..i dunno. Comments? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
| has duplicate | 0003213 | resolved | SSL Queries Only |
|
|
i like this idea, but there is no need of any extra modes. i think that +z channels should not be visible in any way to any non-ssl user, weather it be /who /whois /list or some other command |
|
|
yeah, maybe thats a better idea. or maybe have that a an option in the config file or during compile |
|
|
conf file sounds best, easy to configure :) |
|
|
Something like this would be best in ./Config, so it can be compiled in statically rather than making Unreal check every time |
|
|
yeah |
|
|
Hm, not sure if I like this :P But.. something I've been thinking about (also useful for my commercial mods) is to add some "is this channel visible?" hooks for /who, /whois, /names, /list (well one system probably). That way this can be fully implemented in a module (then whether it adds a +Z or does with the current +z, is up to that module coder). Something for 3.3*. I'll rename the bugreport slightly |
|
|
sounds good |
|
|
For 3.3? Should we add the parent relationship? |
|
|
yeah, and yay |
|
|
I dunnow. Seems like quite a job... I'm dropping this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-12-26 14:06 | Bricker | New Issue | |
| 2006-12-27 07:16 | djGrrr | Note Added: 0012911 | |
| 2006-12-27 12:38 | Bricker | Note Added: 0012915 | |
| 2006-12-27 13:08 | djGrrr | Note Added: 0012917 | |
| 2006-12-27 16:38 | Stealth | Note Added: 0012921 | |
| 2006-12-27 17:45 | Bricker | Note Added: 0012922 | |
| 2006-12-28 09:56 | syzop | Note Added: 0012929 | |
| 2006-12-28 09:57 | syzop | Summary | only +z users can see specific information => add "is channel visible?" hooks // only +z users can see specific information |
| 2006-12-28 10:18 | Bricker | Note Added: 0012933 | |
| 2007-04-18 16:12 | WolfSage | Note Added: 0013530 | |
| 2007-04-18 20:34 | Bricker | Note Added: 0013565 | |
| 2007-04-19 02:15 |
|
Status | new => acknowledged |
| 2007-04-19 03:22 |
|
Relationship added | has duplicate 0003213 |
| 2015-05-27 18:33 | syzop | Note Added: 0018368 | |
| 2015-05-27 18:33 | syzop | Status | acknowledged => closed |
| 2015-05-27 18:33 | syzop | Assigned To | => syzop |
| 2015-05-27 18:33 | syzop | Resolution | open => wont fix |
