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

On SOPA/PIPA

Today, January 18th 2012, a number of websites, organisations and institutions along with countless individuals have chosen to take a stance to protest the proposed SOPA and PIPA legislations.

We believe that these acts could have a significant impact on the way in which we currently use the internet, and we strongly encourage and support raising awareness about the legislative proposals in order for people to make an informed decision about their stance on the issue.

Whilst we will not be partaking in any blackout to mark the occasion, we very much welcome frank and open discussion about SOPA/PIPA in ##sopa on the freenode network. The channel is not run by freenode staff, but was created by some people with a passion about the topics covered by the proposed legislations. If you feel passionate about SOPA/PIPA or you want to find out what all this is about, why not come along and join in the discussion?

As the USA is a power house in so far that they directly or indirectly control most of the internet’s infrastructure, and the proposed legislation has been written in a manner in which they specifically take into account “foreign rogue sites”, the legislation will, should it pass, have an impact upon the world as a whole.

For more information about SOPA/PIPA, please see:

 

Focus on #defocus

We’ve been working on improving the environment in #defocus for a while now.  We think we’re on the right track with opening up channel moderation to more than @freenode/staff/ but we need your help to get to where we want to be.

So this is a call out to those who think that they might be able to work with us to improve #defocus further.  If you think you have what it takes to be a #defocus channel operator, or simply have some ideas that you want to share as to how the existing or new team can improve things, please /join #defocus-focus where you can state your desire to be considered for the team, or share your ideas, or both!

(Don’t worry if you’re the first one there, either, someone has to be!)

Hope to see you there.

mrmist.

Wednesday Server Updates

This Wednesday (September 14th, 2011) we will be continuing our server updates as mentioned here.

The following servers will be affected: leguin, gibson, wolfe, hitchcock, and pratchett.

During the update process these servers will be restarted and anyone connected to them will need to reconnect. You may wish to connect to an alternate server if you are currently connected to one of these.  You can check what server you are currently connected to using the command “/whois nickname” with your own nick as “nickname”.

We apologize for any inconvenience as we continue to improve the technology behind freenode.

Update: This is now done.

IRCD Upgrades

Over the next weeks we will be upgrading our servers to the next version of ircd-seven. This means restarting all our servers. Downtime should be minimal, and as we will not upgrade all servers at the same time this should not be as noisy as the upgrade from hyperion to ircd-seven was. When the server you are on is upgraded you will be disconnected, but should be able to reconnect immediately (most clients will do this automatically).

The following user-visible changes have been made since the versions in production:

– The channel quiet list is now sent using the new numerics RPL_QUIETLIST(728) and RPL_QUIETLISTEND(729) instead of overloading the same numerics as for ban lists. You may find that clients have to be updated before they will display this in a user-friendly format.
– Users who cannot send to a channel are now prevented from changing its topic, even when mode +t is not set.
– Sending a private message to another user while user mode +g is active will now automatically add an accept-list entry so that they can reply.
– Account names are now displayed in WHOWAS entries.
– Two new client capabilities are available: ACCOUNT-NOTIFY and EXTENDED-JOIN. These two together with the existing extended WHO syntax allow clients to track account names of other users who share a channel.
– Client flood control settings have been made configurable; you may notice them being stricter than before.

Once all ircds have upgraded we also plan to re-enable the +S channel mode, which only allows users connected using SSL to join.

Some more features will become available once we upgrade services, which will happen at some point after we have upgraded all irc servers:

– It will be possible to identify to services using SSL client certificates.
– ChanServ mode locks will be (mostly) enforced by the server. Instead of setting a mode and having ChanServ revert it immediately, you will not be able to change a locked mode.

Fixing #defocus

We want #defocus, the network social channel, to be a welcoming place for relaxed, easy conversation. Of late, we’re seeing that staff are acting in a policing role more than we are able to take an active part in the flow of the channel. This is something of a circle, as the more we are seen to be police, the harder it is for us to achieve what we want with the channel.

We’ve had some extensive discussions with #defocus regulars and ops on various channels around what we can do to improve the day-to-day atmosphere of the channel and bring it around to be what we want it to be, and one of the more immediate outcomes of these discussions was that we need to introduce more specific channel ops for #defocus, to work alongside staff in shaping the channel’s future.

To that end, the following users are now channel ops in #defocus, and are ready and able to asist when moderation might be required. _msh, jbroome , rww , Ttech, bburhans, frantk, gry, Fuchs , TheEvilPhoenix, Zuu.

Please help us in welcoming them to the #defocus team.