So without further ado -- Happy Birthday [GNU](http://www.gnu.org)!
-[![Freedom Fry](../static/img/fry720.jpg)](http://www.gnu.org/fry/happy-birthday-to-gnu.html)
+[![Freedom Fry](static/img/fry720.jpg)](http://www.gnu.org/fry/happy-birthday-to-gnu.html)
title: Community Leadership Summit - July 18-19th 2009, San Jose, CA.
category: community
---
-[![](../static/img/3432437765_914490f5e9.jpg)](http://www.communityleadershipsummit.com/)
+[![](static/img/3432437765_914490f5e9.jpg)](http://www.communityleadershipsummit.com/)
[Jono Bacon](http://jonobacon.org), one of my friends and a FOSS contributor for which I have a lot of respect, known to many for his work as [Ubuntu](http://www.ubuntu.com)'s Community Manager is one of the people behind arranging the Community Leadership Summit -- a conference aimed at bringing people from various projects together to look at cross project collaboration and such things. The conference complements freenode and the PDPC's Group Advisory Board very well and I for one shall be attending.
As users please be aware that during the migration all clients will be temporarily disconnected and will need to reconnect in order to move over to the new servers. For most of you this will happen as the old servers are shut down.
-**Please Note:** While we will copy over channel modes and topics for registered channels (there will be no changes to the services database, all nick and channel settings with services will stay the same) we are unable to do so for channels NOT registered with ChanServ. If your project utilises non-registered channels for whatever reason, please make note of the topics and modes so you can make a manual transfer of these yourselves. For more information on registering a channel, see this [post](../2008/04/registering-a-channel-on-freenode/).
+**Please Note:** While we will copy over channel modes and topics for registered channels (there will be no changes to the services database, all nick and channel settings with services will stay the same) we are unable to do so for channels NOT registered with ChanServ. If your project utilises non-registered channels for whatever reason, please make note of the topics and modes so you can make a manual transfer of these yourselves. For more information on registering a channel, see this [post](news/2008-04-22-registering-a-channel-on-freenode).
-If you operate a channel on freenode and have any concerns, feel free to stop by #freenode to discuss any issues you might have. If you run any channel utility bots, you may want to test them on the current testnet. More information can be found [here](http://blog.freenode.net/2009/11/testing-the-nets/).
+If you operate a channel on freenode and have any concerns, feel free to stop by #freenode to discuss any issues you might have. If you run any channel utility bots, you may want to test them on the current testnet. More information can be found [here](news/2009-11-09-testing-the-nets).
**Important Changes**
-
+
* The CAP LS command will list all client capabilities that are available to the client.
-
+
* The CAP REQ :<cap1> <cap2> <...> command can be used to request one or more capabilities. The response to this will be either CAP ACK :<cap> <...>, or CAP NAK :<cap> <...>, depending on whether the request was successful.
-
+
* A CAP name token can be prefixed by - to disable that capability. This was not available with hyperion's CAPAB command.
-
+
* CAP negotiation can take place either during connection and registration (as is required for SASL), or afterwards, to enable identify-msg.
category: different
category: open source
---
-![going-to-fosdem-2011](../static/img/going-to-fosdem-2011.png)
+![going-to-fosdem-2011](static/img/going-to-fosdem-2011.png)
As every year, some of freenode staff will attend FOSDEM. If you have any concerns, praise, criticism or free beer you want to share with us, you are more than welcome to meat us. The best way to coordinate meatings is to simply join #freenode-fosdem and poke us.
---
Hello everyone and Happy St Valentine's Day!
-![Love PDPC! 2011 Fundraiser](../static/img/pdpc-heart.png)
+![Love PDPC! 2011 Fundraiser](static/img/pdpc-heart.png)
We here at freenode and PDPC love Free and Open Source Software (FOSS), and we know that at least 70,000 of you do too.
slug: important-service-announcement-regarding-defocus
title: 'Important service announcement regarding #defocus'
---
-As many of you are aware, [back in 2008](../2008/09/change-in-defocus-policy-and-what-do-you-think/) we changed our policy in #defocus and the method in which the channel works to require users have voice to speak. For the past few years we've been using a combination of manual action, scripts and bots to voice users as needed to control when and how and when they are voiced.
+As many of you are aware, [back in 2008](news/2008-09-14-change-in-defocus-policy-and-what-do-you-think) we changed our policy in #defocus and the method in which the channel works to require users have voice to speak. For the past few years we've been using a combination of manual action, scripts and bots to voice users as needed to control when and how and when they are voiced.
Starting today, we are changing the policy to one we believe is fairly balanced and which gives users much more control over gaining and keeping voice in the channel.
GURER VF N CEVMR. VG'F JBEGU VG. UVAG: ZBGQ.
-![enigma_cat_says_PQOWIELA](../static/img/enigma-cat.jpg)
+![enigma_cat_says_PQOWIELA](static/img/enigma-cat.jpg)
slug: network-wide-policy-privacy-change
title: Network wide policy privacy change
---
-![ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=](../static/img/ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD.jpg)
+![ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=](static/img/ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD.jpg)
ITucplOwnTShozIfVT1cM2u0VTWyVPZwp3EupaD=
---
UPDATE: This was of course an April Fool... you can "/msg nickserv set property GOOGLE+" to remove the property from your account. There might still be other secrets within the message though...
-![freenode4](../static/img/freenode41.png)
+![freenode4](static/img/freenode41.png)
Edit: Previous versions of the post contained an incorrect NickServ command. We have corrected this and apologise for the inconvenience.