View Issue Details

IDProjectCategoryView StatusLast Update
0004055unrealircdpublic2012-10-06 12:52
ReporterkatsklawAssigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status acknowledgedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0004055: [feature] Move shun permissions to a shun block or set::shun
DescriptionThis 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".
TagsNo tags attached.
3rd party modules

Activities

syzop

2012-01-22 17:35

administrator   ~0016895

This sounds like a good idea. It would make the SHUN feature a lot more useful.

Jobe1986

2012-05-10 19:28

reporter   ~0016998

Perhaps there should also be a separate oper block flag for shun as well just to compliment this feature.

Issue History

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 Jobe1986 Note Added: 0016998