We’ve introduced a new server to the network last night thanks for the support from its owner. We’d like to introduce you to indolent.idlechat.net! With the server came a returned Server admin — Lexie. She’s a native of Texas, likes long walks off short piers. She’s normally active in the evening once she returns home from work.
Thanks to the Staff of IdleChat we’ve added another server to the network
procrastinate.idlechat.net located in (Fremont, California). Sadly we had to do some work on one of our older servers so hopefully its more stable now.
If you experience any issues with connecting to the network please keep trying to connect until you can then join #help and let us know.
Hello IdleChat users! Our eu.idlechat.net round-robin will be undergoing maintenance for the next couple of days. If you use eu.idlechat.net to connect to the network, please use irc.idlechat.net instead for an uninterrupted experience.
The IdleChat Network Team would like to welcome our newest staff members Amyashi & Coyote`.
Also, we’ve migrated all users of the long-inactive channel #iPocalypse to #IdleChat to find a more enjoyable experience in a fresh and active channel.
As always any questions can be answered in #help
We’ve currently made a couple changes to the LightIRC generator & applet.
1. A password field to the nick selection box has been added. This change will allow users identify with services at connection. (can be disabled with the generator by selecting the No option)
2. Going along with that change we’ve also added a button to register a nickname inside the applet.
We also added a new server (ineffective.idlechat.net) to the network (a few days ago) located in New York . Other Small changes has been applied to a couple servers to help them from netspliting like they had been.
One of our servers is currently offline at the moment, We’re looking into the issue and have recently removed the server from our DNS until it comes back online. Sadly it can remain in your DNS Cache for up to 48 hours if you experience issues trying to connect just keep trying, We will update this post as we find out more about why the server is offline.
If you enjoy playing Minecraft and have an account and would like to play with some of the network staff then join #minecraft and get added to the server’s whitelist.
We’re running Minecraft 1.8 Spigot Server that has Custom Portals & an IRC plugin so you can chat to people in the IRC channel while playing.
Recently you may have noticed that IdleChat has had a few server restarts in the last week or so, We’re sorry but there is nothing we can really do about them. Most XEN hosts are restarting their hardware for security updates, you can look at the email we’ve received from one of our hosts below.
Linode recently received several Xen Security Advisories (XSAs) that require us to perform updates to our host servers. In order to apply the updates, hosts and the Linodes running on them must be rebooted. The XSAs will be publicly released by the Xen project team on March 10th, therefore we must complete the updates before that date.
These updates are required to protect the security and safe operations of not only our infrastructure, but yours as well. We understand that a disruption with such limited notice is inconvenient, and we hope you understand that these measures are warranted due to the severity of the XSAs.
(Some information has been removed)
Before March 10th we might experience more restarts. If you have any questions or concerns you can always join #help
We’ve been noticing since updating to Anope-2.0.* that some channels have been incorrectly registered, We’ve talked to a few channel owners but we can’t catch every channel. So if you’ve registered a channel between now and Sept 15, 2014 please check your channel info and check the description field to make sure your not unknowingly displaying a password. The correct command to register a channel is now.
/msg chanserv register #yourchannelname [description]
To see if your channel is effected by the new registering command you can run the command
/msg chanserv info #yourchannelname
You’ll get something similar to the following depending on your client and how its scripted.
[12:10:10] [ChanServ]: Information for channel #damdevil:
[12:10:10] [ChanServ]: Founder: Radien
[12:10:10] [ChanServ]: Description: Something here
[12:10:10] [ChanServ]: Registered: Sep 02 15:15:48 2014 UTC (135 days, 2 hours, 54 minutes ago)
[12:10:10] [ChanServ]: Last used: Jan 15 18:10:10 2015 UTC (now)
[12:10:10] [ChanServ]: Ban type: 2
[12:10:10] [ChanServ]: Mode lock: +nt
[12:10:10] [ChanServ]: Options: Peace, Security, Secure founder, Signed kicks, Topic retention
[12:10:10] [ChanServ]: Last topic: Good Luck is hard to come by ° Our website: http://damdevil.org °
[12:10:10] [ChanServ]: Topic set by: iRadien
the line your looking for is the
Description: Something here line. If your channel password or any other thing shows up that shouldn’t be there chances are your channel is one of the effected channels. You don’t need to drop your channel or anything all you’ll have to do is run a command to change the Description of your channel.
/msg chanserv set description #yourchannel [your new description]
If by chance you’ve been effected by this change we suggest that you change your nick password and anything else that might be attached to the password that has been shown.
We’re Sorry for any inconveniences this may have caused you, and for taking so long for it to be noticed.