For the updates on the server side we have now provided UMode +D which will turn off all PMs towards users if they are registered or not. There is also /ircops which will return all the active opers on the network so you know who to connect.

For the services update we have had many updates. On the ChanServ side we have added Autovoice. To use this feature you can use /cs help AutoVoice.

These updates among many others will help us streamline activity on the network for you.

CONNECT AND PLAY TRIVIA NOW

/mode #channel +f [{#}{,...}]:

The amount specifies the number of times the specified flood must occur before action is taken. Below are the available types:

The difference between type m and t is that m is tallied for the entire channel whereas t is tallied per user.

If you choose to specify an action for a mode, you may also specify a time (in minutes) after which the specific action will be reversed.

An example of the use of this command is:

/mode #TheLounge +f [2c#C5,6j#R3,3k#K10,15m#m5,5n#N3,5t#b60]:5

This means…

• If there are 2 channel CTCP messages (2c) in 5 seconds(:5) set mode +C for 5 mins (#C5)
• If there are 6 joins (6j) in 5 seconds (:5) set mode +R for 3 mins (#R3)
• If there are 3 /KNOCK commands on the channel (3k) in 5 seconds (:5) set mode +K for 10 mins (#K10)
• If there are 15 messages in total from all users (15m) in 5 seconds (:5) set mode +m for 5 mins (#m5)
• If there are 5 nickname changes (n5) in 5 seconds (:5) set mode +N for 3 mins (#N3)
• If there are 5 messages from any single user (5t) in 5 seconds (:5) ban the user for 60 mins (#b60)

It has been observed lately that bot nets are joining channels and rapidly joining and parting. In order to prevent this, you can use channel mode j. This mode will allow only x joins to your channel in y seconds for each client. The recommended setting for this is 1 join in 1 second as this will entirely eradicate join/part flooding from botnets. An example of the use of this is:

/mode #TheLounge +j 1:1

You can use extended bans to set up an alternative kind of ban that will give you more options, like silencing users.

When you silence a user, you allow the person to stay in the channel, but block the person’s ability to participate in the discussion or change nicks. It’s an online equivalent of a short timeout, where the person has to sit quickly for several minutes before rejoining discussion.

To silence a user manually, you’d type:

/mode #YourChannel +bb ~q:nick!ident@user.host ~n:nick!ident@user.host

That command sets two bans, which is why the host information is listed twice. The first one (~q:nick!ident@user.host) prevents the user from participating in the discussion (unless the user is +v or higher). The ~q stands for quiet. The second one (~n: nick!ident user.host) prevents the user from changing nicks. The ~n stands for nick.

In #YourChannel, bans are normally set by the user’s host, so an example ban would look like this:

/mode #YourChannel +bb ~n:*!*@protectedhost-1234578.hsd1.wa.comcast.net
~q:*!*@protectedhost-1234578.hsd1.wa.comcast.net

That example bans anyone (with any nick or ident) with the hostmask protectedhost-12345678.hsd1.wa.comcast.net.

Removing a Silence Extended Ban

If you silence a user manually, you have to remove the ban manually as well. Since you set the ban with +b, you will remove it by using the same command, but with -b. So to remove the ban, you would type:

/mode #YourChannel -bb ~q:nick!ident@user.host ~n:nick!ident@user.host

Everything is the same. You’re just removing the ban. Here’s the way to remove the example ban from above:

/mode #YourChannel -bb ~n:*!*@protectedhost-1234578.hsd1.wa.comcast.net
~q:*!*@protectedhost-1234578.hsd1.wa.comcast.net

Setting a Channel Extended Ban

There are two other kinds of extended bans:

• ~c sets an extended ban based on a channel users are in
• ~r sets an extended ban based on a user’s real name

You are unlikely to need either of these bans, but for the sake of thoroughness here is how they work.

To set an extended channel ban, you’d type:

/mode #YourChannel +b ~c:#channel

That ban would prevent anyone in #channel from joining #YourChannel.

Let’s pretend there’s a channel called #YourChannelHaters. We might decide that we do not want anyone from #YourChannelHaters to join #YourChannel. We could use this extended ban to prevent them from joining #YourChannel:

/mode #YourChannel +b ~c:#YourChannelHaters

You remove this kind of ban by switching to -b, so I could remove the ban on folks from #YourChannelHaters like this:

/mode #YourChannel -b ~c:#YourChannelHaters

Setting a Real Name Extended Ban

To set an extended ban based on a user’s real name, you’d type:

/mode #YourChannel +b ~r:*real_name*

The * character works as a wildcard, just as it does in other bans. Use the underscore character ( _ ) to represent spaces in the user’s real name. The underscore is also interpreted as an actual underscore character. In other words, the ban above would block someone using either “real name” (with a space) or “real_name” (with an underscore).

Here’s an example:

/mode #YourChannel +b ~r:*Jane_Doe*

That ban would prevent anyone who was using the real name “Jane Doe” or “Jane_Doe” from joining #YourChannel. Because of the * wildcard, someone with a real name like “Jane Doe rules” or “Jane_Doe_rules” would also be banned.

You remove this kind of ban by switching to -b, so I could remove the ban on “Jane Doe ” like this:

/mode #YourChannel -b ~r:*Jane_Doe*

On the evening of May 5 at around 06:00 GM

T. LogicLounge IRC was attacked by a large scale DDoS attack, for those of you who are unfamiliar to DDoS please refer to this article.

At the moment we currently have no leads on who the user or users were who attacked the network. And from the staff at LogicLounge, we want to assure you that we are working with our datacenters to resolve and prevent this issue. We would also like to set the record straight for some users, that at no time was your encrypted user data open to the attackers.

The cause of this attack is still unknown and much time is being put into securing the servers so that this type of attack never happens. It sickens us here at LogicLounge IRC that someone would would do such a thing to attack server like this. We are working on getting two server up at the moment to spread the load of the server to ease the attack.

Thank you so much and if you have any more questions drop by #help.