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