As irony would have it, the day we removed someone from staff, they reappear out of nowhere! We welcome back Kieran to the staff, and he has become the new owner of the Xi server. Xi was abruptly shut down yesterday, so there were some quick changes made to get it back online. We have decided to part way with BluntMaster. We wish him well with his IRC network.
The new report module system is working awesome so far, although a few users did tend to ‘test’ it at a level we weren’t expecting. :P That’s fine. We know people like to try new things! :D The new automation system for users to remove their own account has been started, and should be in place by the end of this week. I am also looking at the ability for a user to add additional IRC servers to their account, as long as they are for the same IRC network. Our service bot is already set up to automatically determine which network many IRC servers are for (especially: EFnet, IRCnet, Link-Net, and almost all with *.netname.* such as us.undernet.org), so if the bot recognizes the server request is for the same network the user is already on, it would accept the request for the addition. This latter system probably won’t be in place for a couple of weeks or so, as I will make absolutely sure it works before putting it into service.
IRCnet has again been temporarily suspended for 5 days. Our wonderful IRCnet hoarder was found to have 3 more accounts over the last 2 days we didn’t know about until we were alerted by our service bot. This now brings the total to 13 accounts removed, 12 of them to IRCnet. The user zubzub / zub_zub is now on permanent ban from our service for repeatedly violating our rules.
We were hoping the DDoS situation on our servers had subsided, but that didn’t hold true a few hours ago. For the first time since we opened, Zeta was hit by a massive attack and had to be restarted. It was hit with over 200GB of data in just 20 minutes, and then was hit by a second DDoS a few minutes after the first attack. A restart was the only option left. Apologies to those users. We are looking for a possible user that could have been behind the attack so we can remove them.
Once again, thanks to everyone for the continued support. We appreciate the users spreading the word (without spamming networks) about our service. We have grown bigger than I expected to be at this point, with our user count now surpassing the 400 mark in just 3 months. We wouldn’t be doing this without you.
Comments are closed.