View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004055 | unreal | ircd | public | 2011-11-20 22:03 | 2023-07-23 21:30 |
Reporter | katsklaw | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0004055: [feature] Move shun permissions to a shun block or set::shun | ||||
Description | This will allow admins to define permissions for users that are shunned to match their network policies. Example: shun { options { join "no"; join-help-chan "yes"; part "yes"; msg-opers "yes"; msg-users "no"; msg-chans "no"; keep-chanops "no"; }; Shun should always allow ADMIN, QUIT and PONG. For backward compat, all options as well as the block it's self should be optional. Values not included should be an implied "no". | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
This sounds like a good idea. It would make the SHUN feature a lot more useful. |
|
Perhaps there should also be a separate oper block flag for shun as well just to compliment this feature. |
|
This is still a good idea, the general idea that is, bumppppp... not for this release though, that one already has way too much :D |
Date Modified | Username | Field | Change |
---|---|---|---|
2011-11-20 22:03 | katsklaw | New Issue | |
2012-01-22 17:35 | syzop | Note Added: 0016895 | |
2012-01-22 17:35 | syzop | Status | new => acknowledged |
2012-05-10 19:28 | Jobe | Note Added: 0016998 | |
2023-07-23 19:17 | syzop | Relationship added | has duplicate 0006316 |
2023-07-23 21:30 | syzop | Note Added: 0022978 |