I don’t think it needs to be said but security is important to users of the DigitalIRC Network. In line with our continued mission to provide the best experience possible for users of the network we are introducing Security Group as a new extended ban type.
Introducing extended ban type ~G #
Security Groups are a new feature of the IRCd we use for the network which allows users to be put into groups based on various categories.
- Are they identified
- Have they been on the network for a while
- Are they from a webchat
Available Security Groups #
The Groups currently defined are
|Identified with services and has been connected for a reasonable length of time
|Users who are not connected to webchat, are not identified with services, and are new to the network.
|Users who are not identified to services.
|Users connected via an approved webchat (Our own, kiwiirc, etc) and are not identified with services.
|Users connected via an approved webchat (Our own, kiwiirc, etc) and are identified with services.
|Users connected via an approved webchat (Our own, kiwiirc, etc) and are not identified with services, but have been connected for a while (i.e. not new connections to the network).
|All users connected via an approved webchat.
|Users who are not connected to webchat and are not identified with services but have been connected for a reasonable length of time.
More info about how reputation works
We also use the Security Groups to reduce flooding by restricting the number of actions a user may take depending on which group they fall into.
Example Usage #
As you can see from the table above if you want to ban webchat users you can now easily do it. Just do
/mode +b ~G:webchat-all and that’s it, all webchat users will now be banned from the channel.
Users may fall into multiple groups, and you can even add a NOT operator to any ban. For example
/mode +b ~G:!webchat-all would match all users that do not fall into the webchat-all group.
As always if you have any feedback for groups you want feel free to ask in
#irc-help with your usecase