Forums > Announcements
WormNET Service Updates
CyberShadow:
Hi,
Yesterday during testing WormNET flood detection we discovered a serious limitation. The WormNET IRC server has an upper limit for the number of simultaneous connections (a little lower than 180). When this limit is reached, users who try to join will see this:
Unfortunately this limit is hard-coded deep in the software, and we can't easily raise it.
I have observed this limit to be reached (and the above error message generated) during the past few weekends, which is unfortunate as it prevents players from connecting to WormNET. For this reason, I added a new module to SheriffBot which attempts to ensure that our very limited number of connection slots is used fairly. During times of very high activity (more than 120 simultaneous users), SheriffBot will kick out users who are idle (just sitting in a channel with no activity), starting with the users who have been idle the longest.
I understand that getting forcibly kicked off WormNET can be unpleasant, especially if you are used to being online all or a lot of the time. However, I count on your understanding that by staying online, you are occupying a slot which can't be used by someone who just wants to connect, join or host a game, and free up the slot for the next person, within the span of usually under a minute.
* Who is affected by this change? - Mostly, snooper / IRC users, or third-party bots. Users who have been online for less than two minutes, or made any public activity less than two minutes ago, are never affected.
* When will this occur? - The change is already live, but this behavior activates only when there are over 120 users in channels simultaneously. This is pretty rare. For comparison, at the time of writing there are 67 users in total.
* What exactly happens when an idle user is detected during high activity? - The user is kicked from WormNET. However, if the user rejoins WormNET and continues being idle, they will be banned for a short duration (1 minute). If this keeps happening, the duration increases (2 minutes, then 3 minutes, then 4 minutes etc.). This is so that AFK users whose clients are set to automatically reconnect do not wastefully take up a connection slot.
* What should I do if I want to stay online and chat in channels, or keep an eye on WormNET? - I invite you to use the Web Snooper, which uses only one WormNET connection slot no matter how many users are using Web Snooper at the moment.
* What should I do if I want to stay online and chat with people by PM? - I invite you to join #worms on GameSurge, which does not have the drastic user limitations that WormNET has.
* Why is SheriffBot's limit (120) much lower than the WormNET limit (180)? - A typical WormNET IRC connection needs to go through these stages: 1) TCP handshake 2) Authentication 3) Identification 4) Initialization (MOTD, server capabilities, channel list) 5) Joining a channel. SheriffBot can only count users which have reached stage 5, but the WormNET limit takes effect all the way at stage 1. Additionally, the WormNET server reserves some connection slots internally, which is why in /users you will see a maximum of 174, not 180. This is why we reserve a buffer to ensure that there are enough slots for connecting users, users who are currently switching channels, as well as to account for connections which never join a channel (such as some bots).I have also reduced the number of HostingBuddy PM sender proxies from 8 to 3 connections, which frees up connection slots while hopefully still being enough to avoid WormNET PM limits.
CyberShadow:
Other updates since March 22:
* Lower the width threshold to activate the narrow layout in WebSnooper
* Fix the WormNAT2 server running out of ports
* Fix bots not rejoining WormNET channels when they are temporarily locked by ChanServ
* Make WebSnooper use the same restart mechanism as HostingBuddy, so that hosted games continue in the background
* Fix WebSnooper's hosting feature generating bad wa:// URLs in some cases
* Disable some confusing syntax in the Help bot
* Fix a very rare crash in games hosted by HostingBuddy and friends
h3oCharles:
--- Quote from: CyberShadow on April 16, 2020, 05:01 PM ---
--- End quote ---
are you saying that you just found the slot limit of the server?
TheKomodo:
Personally I have always found it frustrating to log on, message someone, and realize they aren't even at their computer, possibly not even in their house!
I've always personally thought it would be nicer if people weren't allowed to remain idle on the server for more than 10 minutes, I mean, it's not exactly a lot of effort to re-connect when you are finally ready to be active again.
I know there are people who will disagree, but I for one welcome our new auto-idle-kick overlords!
Anubis:
--- Quote from: TheKomodo on April 17, 2020, 01:09 PM ---Personally I have always found it frustrating to log on, message someone, and realize they aren't even at their computer, possibly not even in their house!
I've always personally thought it would be nicer if people weren't allowed to remain idle on the server for more than 10 minutes, I mean, it's not exactly a lot of effort to re-connect when you are finally ready to be active again.
I know there are people who will disagree, but I for one welcome our new auto-idle-kick overlords!
--- End quote ---
Yup, I have also always avoided using a snooper in the past and prefer if every user in the channel was actually there and not just in idle mode. In times of high activity I wouldn't mind a broad kick to any and every snooper if that makes room for active players.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version