]>
Commit | Line | Data |
---|---|---|
1 | author: Pricey | |
2 | date: 2014-06-18 15:54:08+00:00 | |
3 | slug: new-extban-j | |
4 | title: New extban: $j | |
5 | category: freenode | |
6 | category: infrastructure | |
7 | category: technical | |
8 | imported: yes | |
9 | --- | |
10 | We have loaded a new module on the network which provides the $j extban type: | |
11 | ||
12 | > $j:<chan> - matches users who are or are not banned from a specified channel | |
13 | ||
14 | As an example... | |
15 | ||
16 | > /mode #here +b $j:#timbuktu | |
17 | ||
18 | ...would ban users from #here that are banned (+b) in #timbuktu. | |
19 | ||
20 | Please note that there are a couple of gotchas: | |
21 | ||
22 | * 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: | |
23 | ||
24 | > /mode #timbuktu +e \*!\*@\* | |
25 | ||
26 | * 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. | |
27 | ||
28 | * $j isn't recursive. Any $j extbans set in #timbuktu are ignored when matching in #here. | |
29 | ||
30 | We imagine you'll have some more useful use cases than the above. | |
31 | ||
32 | Thanks for flying freenode! |