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