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