A very brief mention of upcoming changes..

As you are probably aware we are in the process of rehauling the IRCd and Services software running on freenode. While hyperion and theia have served us well for a significant amount of time they are also starting to struggle under the weight of our rapid growth (we recently hit 43,000 users, which is a number we hadn’t anticipated — that’s 15,000 more users than we had a year ago).

We are of course pleased that our numbers are growing and that more and more people and projects are finding a use for freenode; it’s a fantastic feeling to be able to give something back to the wider FOSS community.

Services wise, we’re currently testing new services on testnet and are close to letting you all loose over there for wider testing before we introduce the new services to the production network. Now, there will be a few changes, and while most of them won’t be noticeable, I felt it was a good idea to remind you of a couple of things.

If as many people as possible can follow the above advice I’d be grateful — it would make the migration a lot easier for us, as well as for our users.

Expirations and e-mails aside, we’ve had a lot of feedback from projects and users who would like to see some changes to the services package — among other things a web-based frontend to services has been mentioned over and over again, particulary for project management. Group contacts would like a way to manage their project namespace, set project related cloaks, and the like. We are looking into OpenID and how to help users and projects which want to more easily integrate, for example, bugzilla and similar with their IRC infrastructure. We’re also trialling a new procedure for verifying group contact forms that may help to reduce the backlog somewhat; over the next few weeks we’ll be trying it out with a portion of the current queue.

In addition to everything I’ve mentioned, we’ve heard some really great ideas and suggestions for further improvement originating from our users, so I thought I’d ask you all what you would put on your wishlist. What can freenode do to better serve the communities? How can we improve irc as a communication and development tool for your project? For your users? I’d love to hear any ideas you may have and would love it if you dropped me a line to ideasATfreenodeDOTnet

Before I wrap up, I’d like to apologise for the instability of the network over the past few days. We have been under a pretty heavy DDoS attack, though hopefully it has all settled down by now. I’d like to thank our fantastic sponsors for the swift manner in which they dealt with things their end, for their continued support and for pulling together to ensure that we have the data required to pass on to the relevant authorities.

It’s pretty rare for us to be on the recieving end of an attack like that, and I sincerely hope it will turn out to be an isolated incident.

5 thoughts on “A very brief mention of upcoming changes..

  1. Excellent ideas, just a couple of ideas to add to the list..firstly, regarding nick registration which should be done in “/msg nickserv register password e-mail” form rather than individually registering than have an option as to whether to provide an e-mail or not. The Expiration policy is perfect..60 days is more than enough and of course, GCF is so slowww..must fix that ..and how about having a database of all the Groups that Freenode host somewhere for Public viewing as well (maybe Freenode’s own wiki hehe..)..Thanks..

  2. Cometstyles> Yeah, we are hoping that a new, more automated system will enable us to process the GCF queue a lot faster.

    We do list Groups on our website (under Primary Groups), however, only those who opt-in, I’d like to make it part of the GCF process: basically ask on the form whether they would like their project listed under the Groups listing with a URL and a small blurb about the project.

    There’s a few exciting changes coming up which we are all looking forward to a lot! :)

  3. hi :) you are saying: “…but individual drops are also done by request when a user wishes to use a nick which has expired.”

    but how am i going to do that? is there a mail address to send my request?

Comments are closed.