The good, the bad, and the ugly…

Firstly, I would like to apologise for the interruptions the network has experienced in the last week (and continues to experience as we speak). I would also like to thank our incredible server sponsors for the time and dedication they have shown in helping us attempt to deal with the situation.

Sponsors — sponsors are the lifeblood of the network; without sponsors there would be no freenode. Unfortunately, the recent attacks have been significant enough for some of our sponsors to pull the plug as they were unable to continue providing the same level of assistance to the network as they had in the past. These kind of attacks can be costly for our sponsors; the disruptions soon have a financial impact for sponsors and their paying clients when service is disrupted. They are also costly in time and resources spent trying to alleviate the issues caused within their networks. To those of our sponsors who have had to discontinue sponsorship, in part or in full, I would like to thank you for the years of support. Not just for freenode but for the Free and Open Source Software Communities and we can only apologise for the difficulties your organisations have experienced as a result of these recent attacks.

Free and Open Source Software Communities — whilst sponsors may be the lifeblood of the network, the FOSS communities are our reason for being. Unfortunately they, along with our sponsors, are the ones suffering at the hands of the attacker(s) — it is their projects that are disrupted and affected and we can only apologise for the instability and disruption experienced by projects on the network in this last week.

freenode — ironically freenode is the puzzle piece that gets off lightly. We’re just a bunch of people passionate about FOSS — the network itself is devoid of feeling and whilst our volunteers do their best dealing with the aftermath of the attacks and try to keep the network up and running the reality is that in the grand scheme of things freenode is nothing. freenode is just a means to an end; the projects that have chosen to use freenode could easily go elsewhere, the volunteers who staff the network… well, they could easily go wherever their projects went — we volunteer for freenode because we’re passionate about FOSS, and the majority of us also contribute to one or several FOSS projects or have done in the past. For us it has never been about “freenode” — it has been about FOSS; and the projects we, as individuals, care about. We are all freenode users first, and staffers second.

If there was no freenode, there would be other alternatives — perhaps similar alternatives, perhaps very different alternatives. The FOSS communities are full of talented, passionate people and I have no doubt that we’d all find different ways to stay in touch and work on our projects even if there was no freenode.

That’s not to say we’re about to throw in the towel — we’ve all invested a lot of time and effort in the network and I am sure we will continue to do so for as long as there are projects wanting to use it and sponsors willing to help us.

I wish I could provide you with detailed information about the attacks and the cause of them — but these details are but a mystery to us and with nearly 90,000 users I’d be loathe to speculate as to who we might have annoyed… or how. For the time being, we intend to continue mitigating attacks where possible and continuing to endeavour to provide service as usual!

Once more, thank you for the support and the faith in the project — and thank you for the patience whilst our infrastructure team desperately tries to juggle our infrastructure around to bring back as much of our normal services as is possible at this point in time.

Insert witty title here

Like every year, we would like to invite our users to take part in the April 1st quiz and have the chance to win an April Fools’ cloak.

Good luck, lots of fun, and thanks for flying freenode trebutchet!

What does Dorothy wish she was on the other side of?
###>++++++++++ [>++++++++++>+++++++++++>+++++++++++>+++++++++++>++++++++++><<<<<<-] >+>++>++++>+>+++> <<<<<< >.>.>.>.>.
##bhggbyhapu

Group Registration Closure

Our group registration system has been around for some time, in various guises.  Over that time, our small but dedicated team of staff has attempted to keep up with demand for groups.  Unfortunately, in the early years of GRF, this generated a substantial backlog of processing, since the system was very manual, a lot of data was processed (restricting the staff who had access) and each group can take some time to properly investigate.  To address this issue, we’ve tried a number of alternatives, such as priority group emails, and, lately, a streamlined group registration system known as “grf-f”.

For various reasons, these replacements haven’t worked quite how we’d want or need them to in order to achieve our objective of registering groups in a timely fashion.  Meanwhile, development of GMS, our automated replacement GRF system, continues.

For these reasons, we have taken the decision to temporarily close the group registration system.

What this means is that -

  • No new group registrations will be accepted from this point onwards, until further notice.
  • Outstanding grf-f applications already in the queue will be processed in due course.
  • Outstanding “old style” GRF applications will *not* be processed (most of the applications in this set are very old now, and the people who submitted them should have seen at least one reminder to refile under grf-f)
  • All existing registered groups are unaffected and continue as normal.

Please bear with us whilst we work on where we want to go next with this system.  Meanwhile, if there are channels currently owned by freenode-staff that your project could make use of, please contact a staffer to see if (provisional) op rights can be granted to your account. (These would likely be done on a somewhat temporary basis, until such time as registration re-opens.)  Note also that this is *only* to gain ops on channels, *not* for obtaining group cloaks.

As always, thanks for flying freenode!

mrmist.

April 1st, the aftermath

It’s been two weeks since our April Fools quiz; thanks to everybody who participated. Several people managed to complete the quiz; the first eight are:

  1. dwfreed
  2. bikcmp
  3. divVerent
  4. sbp
  5. meridion
  6. heftig
  7. JoshuaA
  8. [bjoern]

Here are the riddles and their solutions, in the original order:

Stage 1, the picture linked on the blog:

ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=


This was base64 + rot13 encryption,
##start

Stage 2, topic in ##start

###### MLG UZHGVI GSZM


Encryption A-Z Z-A,
“NOT FASTER THAN”

With a bit of thinking, this led the users to ######neutrinos

Stage 3, topic in ######neutrinos

#### C0LEMAK 43WRXC 34PTCXRW XSF34GDVC BHJ6 CTP4GHKNL7 87JHKMEN


Solvable with a picture of the Colemak keyboard layout and a bit of tracing with your fingers. Following the path between the keys on the keyboard gave you C, O, D, I, N, G.

Stage 4, topic in ####coding

3. #### Find a five-digit number in which the last number is the sum of the first, second, and third; the third is four less than the last; the fourth is two less than the last; and the first and fourth added are one less than the last. The last number is also three times the second.


Plain math, 13579

Stage 5, topic in ####13579

#### This “huge” work, written over twen ty years, contains ten books. What colour is it?


The Great Book of Amber
####amber

Last Stage, topic in ####amber

i yam what i yam but i yam ####

which lead to ####popeye, the final channel.

We hope you enjoyed our little quiz and had a great time.

Help us test our services upgrade!

Very soon we will be upgrading your favourite network helpers… (no not erry…): NickServ, ChanServ, Alis etc. They’re currently connected to our testnet and we need your help with testing, looking for any issues which may affect the production network.

You can connect to our testnet at testnet.freenode.net port 9002 (or 9003 for SSL)

The full changelog is rather long and not all of the features offered by atheme are loaded on freenode. So to help you out, we’ve pulled out the highlights which we think deserve attention:

  • NickServ’s certfp module. (see /msg nickserv help cert and this link.)
  • NickServ will now notify you in real time of failed logins.
  • NickServ’s previous limit on password lengths has been increased.
  • ChanServ will still hand over single-# channels to freenode-staff on expiration of the channel founders, but the method has changed.
  • NickServ & ChanServ’s ‘set’ commands have had a general reorganisation behind the scenes. Nothing should be visibly different but it won’t hurt to check them!

Please note that the services database on the testnet is probably more than a few days old. Don’t be surprised if recent changes you have made on the production network aren’t replicated there.

We’re all in in #freenode on the testnet so please come find us there if you have any questions or bugs.

Finally, look out for a followup blogpost (hopefully quite soon) with some important information on the upgrade itself and our planned database cleanup!

Thanks for using freenode!

P.s. a full list of changes from atheme ~5.1 to ~6 can be found here

Network wide policy privacy change

ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=

ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=

 

UPDATE : Yes, this was an April Fools Joke.  Some of you fell for it, some didn’t.  There’s still time to complete the quiz and get an April Fool cloak, if you can figure out where to go…

At dawn, we ride for FOSDEM Castle

As usual, some of us will be around at FOSDEM.

A possibly incomplete list of us includes Fuchs*, kloeri, Md*, mquin, RichiH, and spaceinvader; asterisks indicating first timers. We may or may not update this list as attendance changes. As a first, we will have a somewhat stable base for people wanting to meat us. I (RichiH) will help man the beer token sale for the Beer Event this year, it’s not unlikely that other staff will stick around as well. The first one to tell me where the quote is from (in person) will get a beer token.

Also, staff pets ahf and sejo will lurk the shadows of FOSDEM, ready to fulfill our every wish and dream. If you see them, toss them food.

Defocus’s visit to the opticians: new guidelines

A couple of months ago, mrmist posted about the #defocus-focus channel, which was looking to improve the atmosphere in #defocus.

One of the areas that has been concentrated on is improving the ruleset for the channel.  A number of people including Fuchs, dax, Ttech and others have involved in this improvement process.

As a result of the efforts of all the fantastic people involved in that channel, we now have a new set of guidelines for #defocus. You can read them on our website.

Hopefully these changes bring the guidelines up to date with the general expectations and aims of the channel. As always, comments are welcome!

Martinp23