Latest update for threativore was pushed in order to be able to handle our anti-Xitter links rule.

What it adds is the scope keyword when setting up a new rule. Scope can either be:

• global: The same as the existing implementation; it will match regardless of instance.
• instance: Will only match from local communities (local to the instance threativore runs in)
• community::<community_name>: Will only match from within the local community named <community_name>.

This means that threativore can now also be used for specific local community management. However currently threativore doesn't accept commands from non-admins, so if any community mod needs to set up a threativore rule, they need to contact the instance admins. In the future hopefully I can allow direct filter specifications from comm-mods.