]>
Commit | Line | Data |
---|---|---|
271fb63d SB |
1 | author: Pricey |
2 | date: 2014-06-18 15:54:08+00:00 | |
3 | slug: new-extban-j | |
4 | title: 'New extban: $j' | |
d7dd9d5b SB |
5 | --- |
6 | ||
271fb63d SB |
7 | We have loaded a new module on the network which provides the $j extban type: |
8 | ||
9 | ||
10 | <blockquote>$j:<chan> - matches users who are or are not banned from a specified channel</blockquote> | |
11 | ||
12 | ||
13 | As an example... | |
14 | ||
15 | ||
16 | <blockquote>/mode #here +b $j:#timbuktu</blockquote> | |
17 | ||
18 | ||
19 | ...would ban users from #here that are banned (+b) in #timbuktu. | |
20 | ||
21 | Please note that there are a couple of gotchas: | |
22 | ||
23 | ||
24 | ||
25 | ||
26 | * Only matching +b list entries are checked. Quiets (+q) Exemptions (+e) & invexes (+I) are NOT then considered. As such, the following mode change would not alter the behaviour of the first example: | |
27 | ||
28 | ||
29 | ||
30 | ||
31 | <blockquote>/mode #timbuktu +e *!*@*</blockquote> | |
32 | ||
33 | ||
34 | ||
35 | ||
36 | ||
37 | ||
38 | * Quiets and the quieting effect of bans may not immediately take effect on #here when #timbuktu's ban list changes due to caching by the ircd. | |
39 | ||
40 | ||
41 | * $j isn't recursive. Any $j extbans set in #timbuktu are ignored when matching in #here. | |
42 | ||
43 | ||
44 | We imagine you'll have some more useful use cases than the above. | |
45 | ||
46 | Thanks for flying freenode! |