View Issue Details

IDProjectCategoryView StatusLast Update
0003235unrealircdpublic2010-04-03 19:57
ReporterBricker Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version3.2.6 
Summary0003235: more decriptive extended bans
Descriptionheres the thing

you have +b ~c:#channel1 and +e ~c:+#channel2, I take it?

would be nice to add in some "inverse logic" ;P as someone put it, to check for voice, which would mean said user is a "regular" there by most cases

so you would do

+b ~c:#channel1 and +e ~c:<+#channel2 to check if that user is a voice user, instead of someone who knows that said channel is exempted thus his ban wont stick...more info just ask

3rd party modules

Activities

Shining Phoenix

2007-04-26 00:47

reporter   ~0013708

~c:+#channel2 should match users with voice or higher in #channel2 ...does that not work? I've got a feeling stuff involving extbans, extexceptions, invites and status modes isn't quite perfect. Someday when I'm bored I might do another test of this stuff.

stskeeps

2007-04-26 06:31

reporter   ~0013732

Ack. Discuss?

Bricker

2007-04-26 15:43

reporter   ~0013745

sts i think we discussed this between aquanight and wolfsage, i dont think this is a problem anymore as + makes it so users with voice or higher may join. feel free to close

Bricker

2010-04-03 19:57

reporter   ~0016062

Closed. Trying to do my part in cleaning the tracker.

Issue History

Date Modified Username Field Change
2007-02-13 18:15 Bricker New Issue
2007-04-26 00:47 Shining Phoenix Note Added: 0013708
2007-04-26 06:31 stskeeps Note Added: 0013732
2007-04-26 06:31 stskeeps Status new => acknowledged
2007-04-26 15:43 Bricker Note Added: 0013745
2010-04-03 19:57 Bricker QA => No need for QA
2010-04-03 19:57 Bricker U4: Need for upstream patch => No need for upstream InspIRCd patch
2010-04-03 19:57 Bricker Note Added: 0016062
2010-04-03 19:57 Bricker Status acknowledged => closed
2010-04-03 19:57 Bricker Resolution open => fixed