Group registration with freenode

Hi all. I’d like to talk about a unique feature that freenode has that many are not aware of for my first post to this blog. Sitting quietly in a small corner of our website, the concept of group registration is one of the things that makes freenode unique amongst IRC networks and it is something that I think highlights our commitment to open projects. The process is simple: after submitting a group contact form, a representative of freenode will contact you, usually by telephone, to verify your identity and to help get things set up.

The concept of registering your project and the availability of this service has been around for some time. Rob Levin, the late founder of PDPC and freenode, placed particularly emphasis on the importance of real world-backed relationships between projects and the network, and there are many benefits to the projects for going through the process: they have rights over the channels they register, and to this end can request transfer of ownership of any channels that they lay claim to as part of their group – assuming, of course, they are able to prove that they are involved in the group to a sufficient level of authority to authorise this. Additionally, project cloaks can be requested. These replace the default unaffiliated cloaks given out; for example, I wear a Wikimedia cloak to show my involvement. Group registration is also possible for about, reference or topical groups, such as those found at ##cooking, ##philosophy and ##security on freenode, to name but a few. They too can request cloaks and gain an official relationship with the network and its staff.

Now, for a bit of honesty: we’re rather backlogged in processing requests for group registration. This is no secret; those of you who have already submitted forms will have probably noticed that you have not been contacted. Recently however, several staff have got involved in the verification process and we are starting to process forms more quickly. We operate on a squeaky wheel system: poke a staff member listed on /stats p to process your form if you have not heard back from us after a week or so, and they will try and find someone. We’re also making improvements to the systems and infrastructure we’re using to record the forms and verifications to make things smoother for everyone.

So, if you like freenode and are using it for your open project, why not register your group today?

[Scheduled Maintenance] IRCD upgrade.

In order to upgrade our ircd code to fix various bugs and security issues, it has become necessary to restart a large portion of freenode network.

This morning, between 6:00 and 7:00AM UTC, we will be restarting numerous servers, including our network hubs. Approximately 35% of the network will be disconnected and the rest will notice significant fragmentation. We have planned the upgrades well in advance and with hope, the affected servers will only be down for a few minutes, at which point the network will return to normal operation.

We have already sent notices to users on the affected servers (i.e., those that will shunt clients). A list is also below. You may find which server you’re on by a WHOIS command on yourself (i.e., /whois nick)


Additionally, servers used for tor connections will shunt users.

We apologize for the inconvenience, and thank you for using freenode. Further questions can be directed to [email protected]

[Downtime] Unexpected downtime.

We would like to apologise to those of our users affected by the network downtime earlier tooday, November 2nd 2006. The network went down unexpectedly after one of our staffers accidentally found a bug in the IRCD code.
I’d also like to take this opportunity to suggest that you keep your eyes on this webpage as we will shortly be announcing some exciting changes and bringing you some great news!
Thank you for using freenode and have a great day.

Questions can as always be directed to [email protected], or feel free to /msg christel or LoRez on IRC.

[Scheduled Maintenance] European Rehubbing

We’ll be rehubbing our European servers at about 6am UTC tomorrow, in about 9 hours (11pm US/Pacific, 8am Europe/Paris, 4pm Australia/Sydney). We’re returning our normal hubbing, which was modified several days ago due to backbone connectivity problems between our US and Europe hubs. This correction should reduce transatlantic latencies.

Thanks to everyone for your patience and understanding, and thank you for using freenode. Have a great night!