DALnet XFLAGs FAQ

Introduction

A common question on DALnet is: "How can I stop floodbots from attacking my channel?". This document attempts to help stop or at least minimize the flooding. It explains the new eXtended flags command and how it exactly works, and why it might be needed in the channel.

1 · What is XFLAG?

The XFLAG is a command that prevents floodbots or annoying users from abusing your channel with unwanted messages or notices. The extended channel flags can be set by the managers or the founder only.

NOTE: This feature can help you to avoid attackers from abusing your channel, and it can make your channel more secured. For more information please read the article https://www.dal.net/kb/view.php?kb=414

2 · Do I need XFLAG?

In most cases, the answer is "no". DALnet's Channel modes are designed to prevent floodbots from joining your channel and stop them from their misbehavior. In fact, you can still set your channel to +RM. Read more about channel modes in http://docs.dal.net/docs/modes.html.

There are many options and values for extended flags in your channel, and they are all going to be explained one by one in this FAQ. We will also show you how to set your channel XFLAG to the recommended options which will protect your channel from being abused, or reset it to default option. Please check our special eXtended Flags at section 5

3 · How to check a channel eXtended flags

To check a channel XFLAG, you will need to be at least an AOp to issue the command.

XFLAG Command: /msg ChanServ@services.dal.net XFLAG #channel-name

Below is an example of what the XFLAG INFO request may return as an information for the channel #docsteam:

-ChanServ- XFLAGs for the channel #docsteam:
-ChanServ- JOIN_CONNECT_TIME: 30
-ChanServ- TALK_CONNECT_TIME: 0
-ChanServ- TALK_JOIN_TIME: 60
-ChanServ- NO_NOTICE: On
-ChanServ- NO_CTCP: On
-ChanServ- NO_PART_MSG: On
-ChanServ- NO_QUIT_MSG: On
-ChanServ- NO_NICK_CHANGE: Off
-ChanServ- NO_UTF8: On
-ChanServ- NO_VPNS: Off
-ChanServ- NO_SHELLS: On
-ChanServ- HIDE_MODE_LISTS: On
-ChanServ- EXEMPT_OPPED: On
-ChanServ- EXEMPT_VOICED: On
-ChanServ- EXEMPT_IDENTD: On
-ChanServ- EXEMPT_REGISTERED: On
-ChanServ- EXEMPT_INVITES: On
-ChanServ- EXEMPT_WEBIRC: On
-ChanServ- AUTOMSG: On
-ChanServ- USER_VERBOSE: Off
-ChanServ- End of list.

NOTE:In this example, users will only be able to join the channel after being online for 30 seconds and will only be able to talk on the channel after 60 seconds (+r'ed users and users with identd will be exempted from both, while voiced+opped users will be exempted from the 30 seconds delay). In fact, you can use a recommended eXtended flags, for more information please check section 5.

4 · What is the XFLAG Command?

Syntax: /msg ChanServ@services.dal.net XFLAG #channel option:value [...] option:value

You can set an option and value to extend the security for your channel, and here is an example of JOIN_CONNECT_TIME and NO_NOTICE all in a row:

Example: /msg ChanServ@services.dal.net XFLAG #docsteam JOIN_CONNECT_TIME:10 NO_NOTICE:ON

For more information about how to add in a row /msg ChanServ@services.dal.net XFLAG HELP.

5 · Special XFLAG

DALnet has designed special flags for the channels that are being flooded. In fact, you can also set your own desired options with the special eXtended flags.

6 · Frequently Asked Questions

In Sunday, the 25th of November 2018, DALnet planned for services training session about the new DALnet Services features!. The session was about XFLAG and others features that were not released yet. At the end of the session, DALnet did a Frequently Asked Questions session, and in this section you will read some of users questions

Q: What works best for JOIN_CONNECT_TIME and is the value in seconds?

A: /ChanServ XFLAG #channel JOIN_CONNECT_TIME:30 and Yes its in seconds.

Q: Can we change GREETMSG?

A: No, you can only use a default premade greeting with the following command. /ChanServ XFLAG #channel AUTOMSG:ON

Q: Is there a maximum integer value for any of the time settings?

A: Any number between 0 to 2592000 should be fine

Q: Does blocking CTCP also block CTCP ACTION (aka a /me command)?

A: Yes, NO_CTCP also blocks actions (/me something)

Q: What about the channels that the founders and managers are away. How can the ops set these commands to prevent flooders?

A: A channel must have a founder set, you should be able to send a memo to the founder. If you can't reach the founder at all, join #OperHelp and we will try to help you.

Q: Could add a help to show what RECOMMENDED does, assuming it will change

A: The recommended feature currently enables the following xflags:

NO_NOTICE:ON, NO_CTCP:ON, NO_PART_MSG:ON, NO_QUIT_MSG:ON, EXEMPT_OPPED:ON, EXEMPT_VOICED:ON, EXEMPT_REGISTERED:ON, EXEMPT_INVITES:ON, HIDE_MODE_LISTS:ON, AUTOMSG:ON, TALK_JOIN_TIME:30

Q: What could XFLAG do, that my bot can't?

A: It adds more tools to help you prevent thousands of drones from thousands of IP addresses from joining your channel, instead of just being limited to things like setting mode +R (registered nicks only).

Q: Can I use the RECOMMENDED option for XFLAG and turn off EXEMPT_IDENTD ?

A: Yes. You can do /ChanServ XFLAG #channel RECOMMENDED and then tweak the options.

Q: With the no_ctcp, it blocks someone from user info, is that valid only for as long as that person is in the channel?

A: No, it doesn't block private ctcps. It only prevents /ctcp request to the channel, i.e. /ctcp #channel ping

NOTE: Here is the link of the session https://www.dal.net/kb/view.php?kb=430.

7 · Conclusion

During a huge flood, this feature will minimize the flood effect on channels. These flags will be controlled by DALnet services, and will be available to all channels and IRC Operator will be able to check the channel flags.