Excerpts from the NEWS file follow:
-<blockquote>
-
->
> Various bug fixes. Highlights include:
>
> Bans of the form *!*@!* are now corrected properly, rather
>
> Remove cmode +F. Forwarding finally appears safe for general
> use.
->
->
-</blockquote>
Thanks for your patience and understanding, and thank you for using freenode!
-
+
1. Make sure you're [ready to go](http://freenode.net/faq.shtml#nicksetup).
-
+
2. Identify to nickserv and stop by **#fundraiser** to **announce that you're willing to be a glutton for punishment.** :)
-
+
3. We'll announce you're available as a victim on WALLOPS!
-
+
1. Turn on WALLOPS. One of these commands should work:
-<blockquote> **/umode +w**
-**/mode <yournick> +w**</blockquote>
+> **/umode +w**
+
+> **/mode <yournick> +w**
+
-
2. Make sure your [nick is set up](http://freenode.net/faq.shtml#nicksetup).
-
+
3. Identify to nickserv and stop by **#fundraiser**.
-
+
4. Watch for a WALLOPS message announcing someone you'd like to hang that embarrassing label on. Don't get too nasty, please? We'll give you pretty broad latitude. ;)
-
+
5. Bid the donation you're willing to make on **#fundraiser**. It should be a standard [support level](http://freenode.net/pdpc.shtml#donorlevels) (base or student, active, sustaining, bronze, or silver). We'll wait five minutes, and the highest donation wins; if there's a tie, we'll get three staffers to vote on which one they saw first (since messages may arrive at different servers at different times).
-
+
6. If you won the cloak, message us the text you want to appear on it. You get to specify up to 52 characters, and it will end in **.fundraiser.pdpc**.
-
+
7. Just [donate](http://freenode.net/news-2004-07-05.shtml#donate) on the website via paypal or credit card, and when it comes in, we'll set up the cloak, and your poor victim will wear it whenever they're on the network, for the next 24 hours!
-
+
8. Be kind. Well, okay, you won't be kind. But at least be kind to *me*, darn it!! 8)
-We'll give out acknowledgement cloaks as usual to donors, and after the 24 hours is up, we'll return all users to their regularly-scheduled hostname or cloak. Happy **Silly Cloak Day**, and thank you for using freenode! :)
+We'll give out acknowledgement cloaks as usual to donors, and after the 24 hours is up, we'll return all users to their regularly-scheduled hostname or cloak. Happy **Silly Cloak Day**, and thank you for using freenode! :)
slug: announcement-pdpc-fundraiser
title: [Announcement] PDPC Fundraiser
---
-Good evening to everyone. Here's hoping you're having an excellent new year. In the next day or so, [Peer-Directed Projects Center](http://freenode.net/pdpc.shtml), the IRS 501(c)(03) parent organization of **freenode**, will begin its fundraising campaign for the fiscal year ending 30 June 2006. We're still working on budget estimates for FYE 2006, and we begin the campaign with about $2,440 in donations over and above those required for the current year.
-The board of directors of PDPC passed the following resolution today, pertaining to fundraising:
-
-
-<blockquote> _ Whereas Peer-Directed Projects Center is an IRS 501(c)(03) organization, with a responsibility to contribute to the public welfare, and whereas donors to PDPC represent a broad range of community participants, and whereas the recent tsunami has demonstrated a genuine need for public support for international relief and welfare organizations, and
-
-Whereas the welfare of children, nationally and internationally, is of significant importance to the future of Free and Open Source Software and Peer-Directed Projects, be it
-
-Resolved, that during the Fiscal Year ending June 30, 2005, one quarter of each donation to PDPC beginning in the near future will be forwarded to UNICEF, initially targetted toward tsunami relief efforts, provided that donors who so choose may opt out of this program and designate their donations specifically and solely for PDPC's own use, and
-
-Resolved, that the Executive Director is instructed to begin this program as soon as is feasible from a technical, financial and public relations standpoint. _</blockquote>
-
-
-If you're considering a donation to PDPC, we strongly urge you to participate. Thanks in advance for your help, and thank you for using freenode!
+Good evening to everyone. Here's hoping you're having an excellent new year.
+In the next day or so, [Peer-Directed Projects
+Center](http://freenode.net/pdpc.shtml), the IRS 501(c)(03) parent
+organization of **freenode**, will begin its fundraising campaign for the
+fiscal year ending 30 June 2006. We're still working on budget estimates for
+FYE 2006, and we begin the campaign with about $2,440 in donations over and
+above those required for the current year.
+
+The board of directors of PDPC passed the following resolution today,
+pertaining to fundraising:
+
+> Whereas Peer-Directed Projects Center is an IRS 501(c)(03) organization,
+> with a responsibility to contribute to the public welfare, and whereas
+> donors to PDPC represent a broad range of community participants, and
+> whereas the recent tsunami has demonstrated a genuine need for public
+> support for international relief and welfare organizations, and
+
+> Whereas the welfare of children, nationally and internationally, is of
+> significant importance to the future of Free and Open Source Software and
+> Peer-Directed Projects, be it
+
+> Resolved, that during the Fiscal Year ending June 30, 2005, one quarter of
+> each donation to PDPC beginning in the near future will be forwarded to
+> UNICEF, initially targetted toward tsunami relief efforts, provided that
+> donors who so choose may opt out of this program and designate their
+> donations specifically and solely for PDPC's own use, and
+
+> Resolved, that the Executive Director is instructed to begin this program as
+> soon as is feasible from a technical, financial and public relations
+> standpoint.
+
+If you're considering a donation to PDPC, we strongly urge you to participate.
+Thanks in advance for your help, and thank you for using freenode!
Hyperion represents the return to active maintenance of our source tree, and provides [a number of bug fixes and operational enhancements.](http://svn.freenode.net/hyperion/trunk/NEWS) There will be a few visible enhancements, such as the use of the
-<blockquote>** /stats p **</blockquote>
+> **/stats p**
command, which will allow the user to get a list of freenode staffers who have marked themselves as "available to handle problems" with a new user mode, +T. We'll make another new umode, +u, available to group members to allow them to bypass channel join limits. And one more major new feature, NOIDPREFIX support, may affect registered nickname formats. Nothing will be implemented for at least two months, but you're urged to read the [draft policy](http://freenode.net/policy_draft_1123442180.shtml#usernames) and comment to email address **policy at freenode dot net**.
In a few minutes, we'll be reconfiguring the network to prevent unregistered users from sending private messages. This is an experimental feature which can be turned on and off at will. In the short term, it should prevent private message flooding from spambots; in the long term, combined with changes to authentication, it could make such flooding very rare. Please email us at **_policy at freenode dot net_** and let us know what you think of the feature. You'll also be able to use
-<blockquote> **_/stats p_**</blockquote>
+> **_/stats p_**
to locate a staffer if you wish to comment, and staffers will be able to see your comments, whether or not you are registered and identified. Please take the opportunity to register your IRC nickname if you need the ability to send private messages. If you've already registered your nickname and have not set auto-identification on, please configure your client accordingly. Remember that the easiest way to auto-identify is to connect with your registered nick and specify your nickserv password as your server password.
slug: scheduled-maintenance-services-upgrade
title: [Scheduled Maintenance] Services Upgrade
---
- Yesterday around noon, we ran into such serious problems with hyperion-ircd 1.0.1 that it became necessary to back out the NOIDPRIVMSG feature, which blocks unregistered users from sending private messages. But users responding to requests for feedback on the feature, via global notice and news item, commented very positively, with about 60% favoring the permanent adoption of the feature, and 83% favoring its use in some temporary or permanent form.
+Yesterday around noon, we ran into such serious problems with hyperion-ircd 1.0.1 that it became necessary to back out the NOIDPRIVMSG feature, which blocks unregistered users from sending private messages. But users responding to requests for feedback on the feature, via global notice and news item, commented very positively, with about 60% favoring the permanent adoption of the feature, and 83% favoring its use in some temporary or permanent form.
-We've resolved the problems with the 1.0.1 code release and will be phasing the patched code in over the next 8 or 9 hours, with our main rotation servers restarted between 4am and 5am UTC. We'll be working on providing a non-default NickServ setting for registered users, allowing them to receive messages from unregistered users. This feature should be available very soon. We'll continue to test for the next few days, and you can help by telling us what you think of the feature; just email your comments to **_policy at freenode dot net_**. And registered or unregistered users can message an active staffer for help; just use
-
-
-<blockquote>**_ /stats p _**</blockquote>
+We've resolved the problems with the 1.0.1 code release and will be phasing the patched code in over the next 8 or 9 hours, with our main rotation servers restarted between 4am and 5am UTC. We'll be working on providing a non-default NickServ setting for registered users, allowing them to receive messages from unregistered users. This feature should be available very soon. We'll continue to test for the next few days, and you can help by telling us what you think of the feature; just email your comments to **_policy at freenode dot net_**. And registered or unregistered users can message an active staffer for help; just use
+> **_ /stats p _**
to get the list.
-We appreciate your patience and your support for the network. Thank you for using freenode!
+We appreciate your patience and your support for the network. Thank you for using freenode!
I will try and speak of some of the reasoning behind closing down #freenode-social, and replacing it with respectively #freenode for help and #defocus for social chatter. The below quotations may help you understand some of the reasoning behind changing the way we operate our social channel, these are just some and not all of the observations made.
-<blockquote>Over the last little while it has become apparent that running #freenode-social the way we currently do is not working for staff or users, and as such is not working for the network, the community or the visions and goals we possess.
-
-We (freenode staff) propose to close down #freenode-social and replace it with #freenode (focused on user/network support ala #tapthru) and #freenode-offtopic (for general natter), in this regard we would like to extend an invitation to the tapthru staff to come on board and co-manage #freenode with us.
-
-The list of items below should be considered a starting point for conversation rather than any definitive pronouncement of how the world should wag. It's not complete (no such list can ever be) but tries to hit most of the major issues we'll face as we embark on this project. Be blunt about your likes/dislikes of the various suggestions and about suggesting changes/additions/removals! Please note that there is no significance to the ordering of the items in the list below; that's just how they came out. They have numbers only to speed the referencing of them during discussion.
-
-1. What is wrong with #freenode-social? (This isn't the finger of blame! Just a way to get a handle on what we are trying to fix.)
-1. No defined topic (so no way to say: "that's offtopic")
-2. No defined rules
-3. Lack of regular chanops (we got scared and ran away)
-4. Chanop behaviour is sporadic and hard to predict
-5. Voicing/devoicing system has holes
-1. Voicing is random. This can cause various behaviors:
-1. People want to capture voice and hold it forever, against the time they might want to speak
-2. When someone has waited hours to be voiced, (s)he may already be quite frustrated
-3. By the time you're voiced, you forgot why you came
-2. We can't remember why a person was devoiced
-3. Access list too long to meaningfully evaluate
-4. No system for 'devoice for xx minutes', so devoices either get forgotten and remain forever, or someone is re-voiced sooner than the devoicing staffer wanted them to be.
-6. We used to say 'be a catalyst in #freenode-social and maybe we'll ask you to be staff someday' ... is that still true?
-2. Some scenarios for the new #freenode channel (things people will come to say). ?? Categorize as (O)OK, (N)Not OK, (P)Private ??
-1. Nick issues
-1. Help me register my nick
-2. Cloak me!
-3. Someone took my nick
-4. Lost my password
-5. Help me admin my nick options
-2. Client issues
-1. Help me with my client
-2. How does $somecommand work?
-3. Cannot connect to freenode
-3. Channel issues
-1. I need help with my channel registration, modes, etc
-2. They banned me in #foo!
-3. #foo is offtopic/offensive/criminal/other, whatcha gonna do about it?
-4. #foo has mean chanops
-5. We are having a disagreement in #foo, please come and mediate
-6. Explain primary/about channels for me again?
-7. Does #foochannel exist?
-8. Everybody come to #foo, it is the ubar-greatest!
-4. About individuals
-1. $somenick is PMing me and I don't like it
-2. $somenick is spamming/trolling/racist remarks/other on #foo
-3. $somenick is spamming/trolling/racist remarks/other on several channels
-4. $somenick is an asshole, kline him now
-5. $somenick's nick offends me
-6. My friend $somenick was klined, remove it already!
-5. Group issues
-1. GCF approvals
-2. Explain groups to me
-3. I'm a GC and I need something done
-4. Who is the GCF for $somegroup
-5. $somegroup has no right to exist, we are the rightful owners of that group name
-6. Freenode issues
-1. $somestaffer treated me unfairly
-2. I want to be a staffer
-3. Teach me to be a catalyst
-4. Announcements by staff
-5. Donation issues
-6. I want to host a freenode server
-7. This wierd thing just happened, is it a network issue, help!
-8. Help me understand the Freenode policy about $whatever.
-9. I disagree with Freenode policy
-10. Freenode should do this wonderful thing _______!
-11. Freenode should endorse my campaign to save the world
-12. I hate Freenode, rant-rant-rant.
-13. I love Freenode, love-love-love.
-7. Other
-1. I need help with something not in 1-6 above
-2. Let's talk about my life issues/problems/whatever.
-3. My political/religious/societal views
-4. spam
-5. random invective
-6. http://somelink is funny/offensive/interesting/whatever, let's all talk abut it
-7. well, all sorts of stuff not found in 1-6 above
-3. Escalating help. We all have different freenode-admin privs; some of us have none other than 'helpful person'.
-1. General SLA for the channel: "#Freenode tries but does not promise to solve your issue; if you are still unsolved here, talk to staffer via /stats p"
-2. Try to identify things that should happen privately (in PM) and move there as soon as possible.
-3. If you haven't the privs to resolve an issue, send them to /stats p or /who *freenode/staff* asap
-4. Suggestions?
-4. #freenode discipline
-1. What do we discipline for?
-1. Offtopic
-2. Tone/attitude
-1. Ontopic but rude
-2. Note- how to handle "I was not being rude, I was joking!"
-3. Personal attacks/characterizations/judgements. (Suggest: we simply avoid all observations of a personal matter)
-4. Giving out bad advice on the channel. Again, the issue of "I was joking" should be addressed.
-2. Possible discipline escalations:
-1. Catalyze in-channel, never ban or mute
-2. Catalyze in-channel, ban or mute after x lines or minutes if it doesn't work
-3. Mute immediately and catalyze in PM; unmute when they understand
-4. Ban/mute for x minutes on first offense, y minutes on second offense, z minutes on third offense
-5. Replace ban/mute with redirec to #freenode-offtopic; perform all catalyzation in there
-6. Some combination of the above
-3. How to handle leftover bans/mutes?
-1. leave forever since no one wants to override another chanop's actions
-2. periodically flush any ban/mute more than x days old
-5. #freenode-offtopic discipline
-1. none at all
-2. same as main channel
-3. relaxed rules
-4. different rules entirely</blockquote>
+> Over the last little while it has become apparent that running #freenode-social the way we currently do is not working for staff or users, and as such is not working for the network, the community or the visions and goals we possess.
+>
+> We (freenode staff) propose to close down #freenode-social and replace it with #freenode (focused on user/network support ala #tapthru) and #freenode-offtopic (for general natter), in this regard we would like to extend an invitation to the tapthru staff to come on board and co-manage #freenode with us.
+>
+> The list of items below should be considered a starting point for conversation rather than any definitive pronouncement of how the world should wag. It's not complete (no such list can ever be) but tries to hit most of the major issues we'll face as we embark on this project. Be blunt about your likes/dislikes of the various suggestions and about suggesting changes/additions/removals! Please note that there is no significance to the ordering of the items in the list below; that's just how they came out. They have numbers only to speed the referencing of them during discussion.
+>
+> 1. What is wrong with #freenode-social? (This isn't the finger of blame! Just a way to get a handle on what we are trying to fix.)
+> 1. No defined topic (so no way to say: "that's offtopic")
+> 2. No defined rules
+> 3. Lack of regular chanops (we got scared and ran away)
+> 4. Chanop behaviour is sporadic and hard to predict
+> 5. Voicing/devoicing system has holes
+> 1. Voicing is random. This can cause various behaviors:
+> 1. People want to capture voice and hold it forever, against the time they might want to speak
+> 2. When someone has waited hours to be voiced, (s)he may already be quite frustrated
+> 3. By the time you're voiced, you forgot why you came
+> 2. We can't remember why a person was devoiced
+> 3. Access list too long to meaningfully evaluate
+> 4. No system for 'devoice for xx minutes', so devoices either get forgotten and remain forever, or someone is re-voiced sooner than the devoicing staffer wanted them to be.
+> 6. We used to say 'be a catalyst in #freenode-social and maybe we'll ask you to be staff someday' ... is that still true?
+> 2. Some scenarios for the new #freenode channel (things people will come to say). ?? Categorize as (O)OK, (N)Not OK, (P)Private ??
+> 1. Nick issues
+> 1. Help me register my nick
+> 2. Cloak me!
+> 3. Someone took my nick
+> 4. Lost my password
+> 5. Help me admin my nick options
+> 2. Client issues
+> 1. Help me with my client
+> 2. How does $somecommand work?
+> 3. Cannot connect to freenode
+> 3. Channel issues
+> 1. I need help with my channel registration, modes, etc
+> 2. They banned me in #foo!
+> 3. \#foo is offtopic/offensive/criminal/other, whatcha gonna do about it?
+> 4. \#foo has mean chanops
+> 5. We are having a disagreement in #foo, please come and mediate
+> 6. Explain primary/about channels for me again?
+> 7. Does #foochannel exist?
+> 8. Everybody come to #foo, it is the ubar-greatest!
+> 4. About individuals
+> 1. $somenick is PMing me and I don't like it
+> 2. $somenick is spamming/trolling/racist remarks/other on #foo
+> 3. $somenick is spamming/trolling/racist remarks/other on several channels
+> 4. $somenick is an asshole, kline him now
+> 5. $somenick's nick offends me
+> 6. My friend $somenick was klined, remove it already!
+> 5. Group issues
+> 1. GCF approvals
+> 2. Explain groups to me
+> 3. I'm a GC and I need something done
+> 4. Who is the GCF for $somegroup
+> 5. $somegroup has no right to exist, we are the rightful owners of that group name
+> 6. Freenode issues
+> 1. $somestaffer treated me unfairly
+> 2. I want to be a staffer
+> 3. Teach me to be a catalyst
+> 4. Announcements by staff
+> 5. Donation issues
+> 6. I want to host a freenode server
+> 7. This wierd thing just happened, is it a network issue, help!
+> 8. Help me understand the Freenode policy about $whatever.
+> 9. I disagree with Freenode policy
+> 10. Freenode should do this wonderful thing _______!
+> 11. Freenode should endorse my campaign to save the world
+> 12. I hate Freenode, rant-rant-rant.
+> 13. I love Freenode, love-love-love.
+> 7. Other
+> 1. I need help with something not in 1-6 above
+> 2. Let's talk about my life issues/problems/whatever.
+> 3. My political/religious/societal views
+> 4. spam
+> 5. random invective
+> 6. http://somelink is funny/offensive/interesting/whatever, let's all talk abut it
+> 7. well, all sorts of stuff not found in 1-6 above
+> 3. Escalating help. We all have different freenode-admin privs; some of us have none other than 'helpful person'.
+> 1. General SLA for the channel: "#Freenode tries but does not promise to
+> solve your issue; if you are still unsolved here, talk to staffer via
+> /stats p"
+> 2. Try to identify things that should happen privately (in PM) and move
+> there as soon as possible.
+> 3. If you haven't the privs to resolve an issue, send them to /stats p or
+> /who *freenode/staff* asap
+> 4. Suggestions?
+> 4. \#freenode discipline
+> 1. What do we discipline for?
+> 1. Offtopic
+> 2. Tone/attitude
+> 1. Ontopic but rude
+> 2. Note- how to handle "I was not being rude, I was joking!"
+> 3. Personal attacks/characterizations/judgements. (Suggest: we simply avoid all observations of a personal matter)
+> 4. Giving out bad advice on the channel. Again, the issue of "I was joking" should be addressed.
+> 2. Possible discipline escalations:
+> 1. Catalyze in-channel, never ban or mute
+> 2. Catalyze in-channel, ban or mute after x lines or minutes if it doesn't work
+> 3. Mute immediately and catalyze in PM; unmute when they understand
+> 4. Ban/mute for x minutes on first offense, y minutes on second offense, z minutes on third offense
+> 5. Replace ban/mute with redirec to #freenode-offtopic; perform all catalyzation in there
+> 6. Some combination of the above
+> 3. How to handle leftover bans/mutes?
+> 1. leave forever since no one wants to override another chanop's actions
+> 2. periodically flush any ban/mute more than x days old
+> 5. \#freenode-offtopic discipline
+> 1. none at all
+> 2. same as main channel
+> 3. relaxed rules
+> 4. different rules entirely
Having spent some time discussing the situation and mulled over the above channel thoughts it was decided to move forward and start working out some clearer guidelines for the new channels. The name #freenode-offtopic was also replaced by #defocus, we considered keeping the #freenode-social name but decided that it was better to start afresh and sculpt something from the ground up and so we decided to re-name.
category: pdpc
category: social
---
-Today has been an interesting day in 'freenodia', a day of reflection, and a day where both myself and my incredible staff got a feel of what it means to be surrounded and embraced by so many large and vibrant communities as those who choose to use the freenode network. We are proud and happy to host the projects we host, and we are tremendously grateful that by using freenode you allow us to get a peek behind the curtains on how your project operates, which is always refreshing.
-We also appeared in the news today, when [NewsForge](http://newsforge.org) and [linux.com](http://linux.com) broke the [news](http://www.linux.com/article.pl?sid=07/05/16/2037231) (though, old news to our blog readers!) of [freenode](http://freenode.net) and [OFTC](http://oftc.net) exploring further collaboration.
+Today has been an interesting day in 'freenodia', a day of reflection, and a
+day where both myself and my incredible staff got a feel of what it means to be
+surrounded and embraced by so many large and vibrant communities as those who
+choose to use the freenode network. We are proud and happy to host the projects
+we host, and we are tremendously grateful that by using freenode you allow us
+to get a peek behind the curtains on how your project operates, which is always
+refreshing.
-And we saw some changes to the structure of the PDPC board.
-
-
-<blockquote>As of the board meeting on May 22nd 2007 a few changes have been made with immediate effect. David Levin has stepped down from his position as President. Christel Dahlskjaer (freenode Head of Staff) replaces him as President by unanimous vote, while David retains a position on the PDPC board.
-
-Phil Stracchino follows in Christel's footsteps, assuming her previous position as secretary pro tem.
-
-Joining the board we have Richard (RichiH) Hartmann in the position as treasurer pro tem, representing freenode staff, and David (cdlu) Graham as a community board member.
-
-All members of the board are excited to be working together to provide even better services to the communities we serve and look forward to a interesting future for PDPC and its sub projects.
-
-We would like to thank all the freenode staff volunteers, server sponsors and users who have helped build up the organization and the projects as they are today. We could not have done it without you and appreciate your continued support and enthusiasm in helping us in our efforts to lay the structures for building vibrant peer directed communities.
-
-Congratulations to the additional board members of the PDPC, both of whom were voted in unanimously.
+We also appeared in the news today, when [NewsForge](http://newsforge.org) and
+[linux.com](http://linux.com) broke the
+[news](http://www.linux.com/article.pl?sid=07/05/16/2037231) (though, old news
+to our blog readers!) of [freenode](http://freenode.net) and
+[OFTC](http://oftc.net) exploring further collaboration.
-The corporate officers of the PDPC are as follows:
-
-* Christel Dahlskjaer - President
-* Phil Stracchino - Secretary
-* Richard Hartmann - Treasurer
-
-The PDPC board of directors:
-
-* Christel Dahlskjaer - Member (Head of Staff, freenode)
-* Phil Stracchino - Member
-* David Levin - Member
-* Richard Hartmann - Member
-* David Graham - Community Board Member
-
-In unrelated news, it has come to the attention of freenode and the PDPC Board that certain users of the freenode network have been propagating unfounded rumors concerning the status of PDPC board members and freenode staff, claiming to represent or acting on behalf of the President of the PDPC Board. The Board wishes it to be clearly understood that these users do not speak for or represent either freenode or the Peer Directed projects Center in any capacity, official or otherwise. We politely request that you disregard any rumors about Freenode or PDPC obtained from sources other than official Freenode/PDPC communication channels.
-
-We thank you for your attention, and assure you that PDPC will continue to operate freenode to the best of its ability in the best interests of the network and the F/OSS community.
-
-On behalf of the PDPC board,
-
-Christel Dahlskjaer - President, Head of Staff - freenode
-Phil Stracchino - Secretary
-David Graham - Community Board Member</blockquote>
+And we saw some changes to the structure of the PDPC board.
-The above is copied from the news announcement made [here](http://freenode.net/news-2007-05-22.shtml).
+> As of the board meeting on May 22nd 2007 a few changes have been made with
+> immediate effect. David Levin has stepped down from his position as
+> President. Christel Dahlskjaer (freenode Head of Staff) replaces him as
+> President by unanimous vote, while David retains a position on the PDPC
+> board.
+>
+> Phil Stracchino follows in Christel's footsteps, assuming her previous
+> position as secretary pro tem.
+>
+> Joining the board we have Richard (RichiH) Hartmann in the position as
+> treasurer pro tem, representing freenode staff, and David (cdlu) Graham as a
+> community board member.
+>
+> All members of the board are excited to be working together to provide even
+> better services to the communities we serve and look forward to a interesting
+> future for PDPC and its sub projects.
+>
+> We would like to thank all the freenode staff volunteers, server sponsors and
+> users who have helped build up the organization and the projects as they are
+> today. We could not have done it without you and appreciate your continued
+> support and enthusiasm in helping us in our efforts to lay the structures for
+> building vibrant peer directed communities.
+>
+> Congratulations to the additional board members of the PDPC, both of whom
+> were voted in unanimously.
+>
+> The corporate officers of the PDPC are as follows:
+>
+> * Christel Dahlskjaer - President
+> * Phil Stracchino - Secretary
+> * Richard Hartmann - Treasurer
+>
+> The PDPC board of directors:
+>
+> * Christel Dahlskjaer - Member (Head of Staff, freenode)
+> * Phil Stracchino - Member
+> * David Levin - Member
+> * Richard Hartmann - Member
+> * David Graham - Community Board Member
+>
+> In unrelated news, it has come to the attention of freenode and the PDPC
+> Board that certain users of the freenode network have been propagating
+> unfounded rumors concerning the status of PDPC board members and freenode
+> staff, claiming to represent or acting on behalf of the President of the PDPC
+> Board. The Board wishes it to be clearly understood that these users do not
+> speak for or represent either freenode or the Peer Directed projects Center
+> in any capacity, official or otherwise. We politely request that you
+> disregard any rumors about Freenode or PDPC obtained from sources other than
+> official Freenode/PDPC communication channels.
+>
+> We thank you for your attention, and assure you that PDPC will continue to
+> operate freenode to the best of its ability in the best interests of the
+> network and the F/OSS community.
+>
+> On behalf of the PDPC board,
+>
+> Christel Dahlskjaer - President, Head of Staff - freenode<br/> Phil
+> Stracchino - Secretary<br/> David Graham - Community Board Member
+
+
+The above is copied from the news announcement made
+[here](http://freenode.net/news-2007-05-22.shtml).
I hope you are all having a wonderful day.
From _[The Pragmatic Programmer](http://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X)_:
-<blockquote>**Care and Cultivation of Gurus **With the global adoption of the internet, gurus suddenly are as close as your Enter key. So, how do you find one, and how do you get one to talk with you? We find there are some simple tricks.
-
->
->
-
+> **Care and Cultivation of Gurus** With the global adoption of the internet, gurus suddenly are as close as your Enter key. So, how do you find one, and how do you get one to talk with you? We find there are some simple tricks.
+>
+>
> * Know exactly what you want to ask, and be as specific as you can be.
->
-
+>
> * Frame your question carefully and politely. Remember that you're asking a favor; don't seem to be demanding an answer.
->
-
+>
> * Once you've framed your question, stop and look again for the answer. Pick out some keywords and search the Web. Look for appropriate FAQs (lists of frequently asked questions with answers).
->
-
+>
> * Sit back and be patient. People are busy, and it may take days to get a specific answer.
->
-
-Finally, please be sure to thank anyone who responds to you. And if you see people asking questions _you_ can answer, play your part and participate.</blockquote>
+>
+> Finally, please be sure to thank anyone who responds to you. And if you see people asking questions _you_ can answer, play your part and participate.
This strikes particularly close to home as a freenode denizen. Everyone has some sort of problem and needs help, and it truly is a pleasure to help people who have done their homework.This quote was only a panel in the book, but documenting the especially tricky problems and staying around to help others ameliorates channel load and increases overall quality. It's what makes freenode what it is.Thanks.
---
We've noticed a lot of people who are confused (and rightly so!) about the new nickname system - particularly the way that nickname grouping has changed. Hopefully this blog post will clear some of it up.
-**Nicknames and Accounts**
+# Nicknames and Accounts
freenode now uses a system of ownership that is different to the old nicknames system. Now, when you register a _nickname_ for the first time, that _nickname_ becomes the primary _nickname_ on your _account_ (which has the same name). An example:
-
-<blockquote>**User1** vists Freenode for the first time. She registers by using the command:
-
->
-> <blockquote>/msg NickServ REGISTER myshinypass my@shiny.email</blockquote>
->
->
-**User1 **now has an _account_. freenode services have automatically assigned the _nickname_ **User1** to the _account_ **User1**. **User1** is now happy.</blockquote>
+> **User1** vists Freenode for the first time. She registers by using the
+> command:
+>
+> > /msg NickServ REGISTER myshinypass my@shiny.email
+>
+> **User1 **now has an _account_. freenode services have automatically assigned
+> the _nickname_ **User1** to the _account_ **User1**. **User1** is now
+> happy.
So, _nicknames_ are now assigned to your _account_. But what does this actually mean, practically?
-**Identification**
+# Identification
When you identify:
-<blockquote> /msg NickServ IDENTIFY <password></blockquote>
+> /msg NickServ IDENTIFY <password>
freenode services will try and identify you to your _account_. It does this by taking your _nickname_, and looking it up in the database - to find the _account_ associated with it. Let's go back to User1 for a little demonstration:
-<blockquote>**User1** returns to freenode. She identifies using the command:
-
->
-> <blockquote> /msg NickServ IDENTIFY myshinypass</blockquote>
->
->
-freenode services finds an _account_ (**User1**) with the same _nickname_ as her (**User1**), and so identifies her succesfully.</blockquote>
+> **User1** returns to freenode. She identifies using the command:
+>
+> > /msg NickServ IDENTIFY myshinypass
+>
+>
+> freenode services finds an _account_ (**User1**) with the same _nickname_ as
+> her (**User1**), and so identifies her succesfully.
But what happens when you try and identify with a different nickname?
-<blockquote>**User1 **connects to freenode, but her client decides to connect with the _nickname_ **User12.** She tries to identify using the command:
-
->
-> <blockquote> /msg NickServ IDENTIFY myshinypass</blockquote>
->
->
-freenode services tries to look up an account called **User12** (as this is her current nickname). This nickname is unregistered, and so does not have an account associated with it. The identification fails, and she is not logged in.</blockquote>
+> **User1 **connects to freenode, but her client decides to connect with the
+> _nickname_ **User12.** She tries to identify using the command:
+>
+> > /msg NickServ IDENTIFY myshinypass
+>
+> freenode services tries to look up an account called **User12** (as this is
+> her current nickname). This nickname is unregistered, and so does not have an
+> account associated with it. The identification fails, and she is not logged
+> in.
With the new accounts system, there is a command that allows you to identify to your account from any nickname!
-<blockquote>**User1 **connects to freenode, but her client decides to connect with the _nickname_ **User12.** She can identify using the command:
-
->
-> <blockquote>/msg NickServ IDENTIFY User1 myshinypass</blockquote>
->
->
-freenode services will now look for an _account_ named **User1**, and log her into that. Since she already registered this, the identification succeeds.</blockquote>
+> **User1 **connects to freenode, but her client decides to connect with the
+> _nickname_ **User12.** She can identify using the command:
+>
+> > /msg NickServ IDENTIFY User1 myshinypass
+>
+> freenode services will now look for an _account_ named **User1**, and log her
+> into that. Since she already registered this, the identification succeeds.
However, this isn't ideal, as she is now logged in, but is using an unregistered _nickname_. She may want to consider GROUPing the _nickname_.
-**Grouping**
+
+# Grouping
With the new system, GROUP basically means to add another _nickname_ to your _account_. **User1** is fed up of being connected as **User12** and using an unregistered _nickname_, so she has decided to GROUP the _nickname_ to her existing _account_.
There are two ways to go about this:
-<blockquote>**User1 **connects to freenode, but her client decides to connect with the _nickname_ **User12.** She can identify using the command:
-
->
-> <blockquote>/msg NickServ IDENTIFY User1 myshinypass</blockquote>
->
->
-freenode services will now look for an _account_ named **User1**, and log her into that. Since she already registered this, the identification succeeds. She can now GROUP the _nickname_ (**User12**) to her _account_ (**User1**) by typing:
-
->
-> <blockquote>/msg NickServ GROUP</blockquote>
->
->
-The command takes the current _nickname_, and adds it to the currently logged in _account_. She can now, in the future, identify using the command:
-
->
-> <blockquote>/msg NickServ IDENTIFY myshinypass</blockquote>
->
->
-when connected as **User12**.</blockquote>
+> **User1 **connects to freenode, but her client decides to connect with the
+> _nickname_ **User12.** She can identify using the command:
+>
+> > /msg NickServ IDENTIFY User1 myshinypass
+>
+>
+> freenode services will now look for an _account_ named **User1**, and log her
+> into that. Since she already registered this, the identification succeeds.
+> She can now GROUP the _nickname_ (**User12**) to her _account_ (**User1**) by
+> typing:
+>
+> > /msg NickServ GROUP
+>
+>
+> The command takes the current _nickname_, and adds it to the currently logged
+> in _account_. She can now, in the future, identify using the command:
+>
+> > /msg NickServ IDENTIFY myshinypass
+>
+>
+> when connected as **User12**.
Or, she can do this:
-<blockquote>**User1** connects to freenode. She identifies using the command:
-
->
-> <blockquote> /msg NickServ IDENTIFY myshinypass</blockquote>
->
->
-freenode services finds an _account_ (**User1**) with the same _nickname_ as her (**User1**), and so identifies her succesfully. She can now change her _nickname_:
-
->
-> <blockquote>/nick User12</blockquote>
->
->
-And GROUP her new _nickname_, as freenode services does not log her out of her _account_ when she changes _nickname_.
-
->
-> <blockquote>/msg NickServ GROUP</blockquote>
->
->
-The command takes the current _nickname_, and adds it to the currently logged in _account_. She can now, in the future, identify using the command:
-
->
-> <blockquote>/msg NickServ IDENTIFY myshinypass</blockquote>
->
->
-when connected as **User12**.</blockquote>
-
-
-**Conclusion**
+> **User1** connects to freenode. She identifies using the command:
+>
+> > /msg NickServ IDENTIFY myshinypass
+>
+>
+> freenode services finds an _account_ (**User1**) with the same _nickname_ as her (**User1**), and so identifies her succesfully. She can now change her _nickname_:
+>
+> > /nick User12
+>
+>
+> And GROUP her new _nickname_, as freenode services does not log her out of her _account_ when she changes _nickname_.
+>
+> > /msg NickServ GROUP
+>
+>
+> The command takes the current _nickname_, and adds it to the currently logged in _account_. She can now, in the future, identify using the command:
+>
+> > /msg NickServ IDENTIFY myshinypass
+>
+>
+> when connected as **User12**.
+
+
+# Conclusion
So, to wrap up, freenode now allows you to register an account, to which you add nicknames as explained above. That's not an easy concept to grasp if you are used to the old system, and if you have any questions, feel free to drop into #freenode and ask away!
-
-
-<blockquote></blockquote>
title: Community Leadership Summit - July 18-19th 2009, San Jose, CA.
category: community
---
-[](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.
+[](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.
-<blockquote>The goal is simple: if those passionate about building great communities can get together to compare notes and discuss and debate these topics, we will all benefit from better communities.
-The summit gathers together community managers, leaders and organizers as well as the projects, organizations, commercial vendors, ISVs and others who have an interest in building a strong and enabled community. The purpose of the event is to get everyone together to talk about the many nuances of building strong and effective community, such as governance, creating collaborative environments, conflict resolution, transparency, open infrastructure, social networking, commercial investment in community, engineering vs. marketing approaches to community leadership and more.</blockquote>
+> The goal is simple: if those passionate about building great communities can
+> get together to compare notes and discuss and debate these topics, we will
+> all benefit from better communities.
+>
+> The summit gathers together community managers, leaders and organizers as
+> well as the projects, organizations, commercial vendors, ISVs and others who
+> have an interest in building a strong and enabled community. The purpose of
+> the event is to get everyone together to talk about the many nuances of
+> building strong and effective community, such as governance, creating
+> collaborative environments, conflict resolution, transparency, open
+> infrastructure, social networking, commercial investment in community,
+> engineering vs. marketing approaches to community leadership and more.
-You can read the rest of that over at [Jono's blog](http://www.jonobacon.org/2009/04/12/community-leadership-summit-2009/) and of course, head over to the [conference website](http://www.communityleadershipsummit.com/), check it out and sign up if you can make it and it sounds like a good fit for you!
+You can read the rest of that over at [Jono's
+blog](http://www.jonobacon.org/2009/04/12/community-leadership-summit-2009/)
+and of course, head over to the [conference
+website](http://www.communityleadershipsummit.com/), check it out and sign up
+if you can make it and it sounds like a good fit for you!
Jonathan mentioned in his [blog post](http://blog.freenode.net/2009/04/free-as-in-node-episode-3-released/) about the free-as-in-node podcast yesterday that this weeks guest on "Pimp My Project" was there to talk about **PHP TestFest**.
-<blockquote>The TestFest is an event that aims at improving the [code coverage](http://gcov.php.net/) of the [test suite](http://qa.php.net/running-tests.php) for the PHP language itself. As part of this event, local User Groups (UG) are invited to join the TestFest. These UGs can meet physically or come together virtually. The point however is that people network to learn together. Aside from being an opportunity for all of you to make friends with like minded people in your (virtual) community, it also will hopefully reduce the work load for the PHP.net mentors. All it takes is someone to organize a UG to spearhead the event and to get others involved in [writing phpt tests](http://qa.php.net/write-test.php). The submissions will then be reviewed by members of php.net before getting included in the official test suite.</blockquote>
+> The TestFest is an event that aims at improving the [code
+> coverage](http://gcov.php.net/) of the [test
+> suite](http://qa.php.net/running-tests.php) for the PHP language itself. As
+> part of this event, local User Groups (UG) are invited to join the TestFest.
+> These UGs can meet physically or come together virtually. The point however
+> is that people network to learn together. Aside from being an opportunity for
+> all of you to make friends with like minded people in your (virtual)
+> community, it also will hopefully reduce the work load for the PHP.net
+> mentors. All it takes is someone to organize a UG to spearhead the event and
+> to get others involved in [writing phpt
+> tests](http://qa.php.net/write-test.php). The submissions will then be
+> reviewed by members of php.net before getting included in the official test
+> suite.
As per [http://qa.php.net/testfest.php](http://qa.php.net/testfest.php) Head over there if you want some more information on how to get involved!
author: christel
date: 2009-04-14 09:52:41+00:00
slug: wikipedia-licensing-change
-title: Wikipedia licensing change?
+title: Wikipedia licensing change?
---
**Wikipedia to change license to Creative Commons BY-SA?** -- From [http://creativecommons.org/weblog/entry/13967](http://creativecommons.org/weblog/entry/13967)
-<blockquote>A community vote is now underway, hopefully one of the final steps in the process the migration of Wikipedia (actually Wikipedias, as each language is its own site, and also other Wikimedia Foundation sites) to using [Creative Commons Attribution-ShareAlike](http://creativecommons.org/licenses/by-sa/3.0/) as its primary content license.
-
-This migration would be a huge boost for the free culture movement, and for Wikipedia and Creative Commons — until the migration happens there is an unnecessary licensing barrier between the most important free culture project (Wikipedia of course, currently under the Free Documentation License, intended for software documentation) and most other free culture projects and individual creators, which use the aforementioned CC BY-SA license.
-
-To [qualify](http://meta.wikimedia.org/wiki/Licensing_update#Decision-making_process) to vote, one must have made 25 edits to a Wikimedia site prior to March 15. Make sure you’re logged in to the project on which you qualify, and you should see a site notice at the top of each page that looks like the image below (red outline added around notice).</blockquote>
-
+> A community vote is now underway, hopefully one of the final steps in the process the migration of Wikipedia (actually Wikipedias, as each language is its own site, and also other Wikimedia Foundation sites) to using [Creative Commons Attribution-ShareAlike](http://creativecommons.org/licenses/by-sa/3.0/) as its primary content license.
+>
+> This migration would be a huge boost for the free culture movement, and for Wikipedia and Creative Commons — until the migration happens there is an unnecessary licensing barrier between the most important free culture project (Wikipedia of course, currently under the Free Documentation License, intended for software documentation) and most other free culture projects and individual creators, which use the aforementioned CC BY-SA license.
+>
+> To [qualify](http://meta.wikimedia.org/wiki/Licensing_update#Decision-making_process) to vote, one must have made 25 edits to a Wikimedia site prior to March 15. Make sure you’re logged in to the project on which you qualify, and you should see a site notice at the top of each page that looks like the image below (red outline added around notice).
If you are eligible, please head over to [http://creativecommons.org/weblog/entry/13967](http://creativecommons.org/weblog/entry/13967) and find out how to cast your vote!
---
Every couple of years, freenode likes to get out the shears and prune the services database. Recently we broke the 80,000 usercount barrier, but the services stats are way ahead:
-
-
-
-
-<blockquote>Sat 13:35:46 -OperServ(OperServ@services.)- Registered accounts: 446777
-Sat 13:35:46 -OperServ(OperServ@services.)- Registered nicknames: 557497
-Sat 13:35:47 -OperServ(OperServ@services.)- Registered channels: 141373</blockquote>
-
-
-
-
-
-We've noticed that nearly half of the accounts shown there haven't been used in the past 6 months! More importantly, over the past few months many people have noticed significant waits when issuing certain services commands - and we'd like to fix that.
-
-Hopefully, the [services upgrade](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/) should help with this, but we're going to coincide this with a database prune.
-
-As of the services upgrade date, any nicks unused for > 150 days are at risk of being dropped. This includes grouped nicks. The easy way to avoid this happening is to use each of your grouped nicks (while identified to the appropriate account) within the next few weeks - and to drop those that you don't need anymore!
-
-The testnet (testnet.freenode.net, port 9002. 9003 for SSL) is running a database snapshot from mid-March and will be periodically updated from the production network. This database instance is being regularly pruned - so check there to see how your account will be affected (use /msg nickserv info on both the production and test networks to see the differences).
-
-Remember that testnet isn't running a real-time duplicate of the production network, so when you use nicks which would be expired on the production network, they will still appear expired on testnet until the next database snapshot is migrated. Don't worry though - the actual pruning will only occur on the current database at the time of upgrade.
-
-On which note.. an upgrade date hasn't been formally fixed but we're aiming for mid-May.
-
-Thanks, and don't forget to [test the testnet](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/)!
+> Sat 13:35:46 -OperServ(OperServ@services.)- Registered accounts: 446777<br/>
+> Sat 13:35:46 -OperServ(OperServ@services.)- Registered nicknames: 557497<br/>
+> Sat 13:35:47 -OperServ(OperServ@services.)- Registered channels: 141373<br/>
+
+We've noticed that nearly half of the accounts shown there haven't been used in
+the past 6 months! More importantly, over the past few months many people have
+noticed significant waits when issuing certain services commands - and we'd
+like to fix that.
+
+Hopefully, the [services
+upgrade](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/)
+should help with this, but we're going to coincide this with a database prune.
+
+As of the services upgrade date, any nicks unused for > 150 days are at risk of
+being dropped. This includes grouped nicks. The easy way to avoid this
+happening is to use each of your grouped nicks (while identified to the
+appropriate account) within the next few weeks - and to drop those that you
+don't need anymore!
+
+The testnet (testnet.freenode.net, port 9002. 9003 for SSL) is running a
+database snapshot from mid-March and will be periodically updated from the
+production network. This database instance is being regularly pruned - so check
+there to see how your account will be affected (use /msg nickserv info on both
+the production and test networks to see the differences).
+
+Remember that testnet isn't running a real-time duplicate of the production
+network, so when you use nicks which would be expired on the production
+network, they will still appear expired on testnet until the next database
+snapshot is migrated. Don't worry though - the actual pruning will only occur
+on the current database at the time of upgrade.
+
+On which note.. an upgrade date hasn't been formally fixed but we're aiming for
+mid-May.
+
+Thanks, and don't forget to [test the
+testnet](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/)!
-
+
* Though we are not aware of any evidence that we have been targeted, or our private key compromised, [this is inevitably a possibility](https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013). SSL sessions established prior to 2014/04/12 may be vulnerable. If your current connection was established prior to this date via ssl then you should** consider reconnecting to the network.
**
-
- * **We would advise that users reset their password** (after reconnecting) using instructions returned by the following command:
+ * **We would advise that users reset their password** (after reconnecting) using instructions returned by the following command:
-<blockquote>/msg nickserv help set password</blockquote>
+> /msg nickserv help set password
-
+
* In line with general best practice, we would always recommend using separate passwords on separate systems - if you shared your freenode services password with other systems, you should **change your password on all of these systems**; preferably into individual ones.
-
+
* If you use CertFP, you should **regenerate your client certificate** ([instructions](http://freenode.net/certfp/makecert.shtml)) ****and ensure that you update NickServ with the new certificate hash. You can find out how to do this using the following command:
-<blockquote>/msg nickserv help cert</blockquote>
+> /msg nickserv help cert
+
-
* Having changed passwords and/or certificate hashes, it cannot hurt to **verify your other authentication methods** (such as [email](http://blog.freenode.net/2013/08/check-your-nickserv-email/), ACCESS or CERT). It is possible you have additional access methods configured either from past use or (less likely) due to an account compromise.
-
+
* At the recommendation of the Tor Project, we have regenerated private keys for our hidden services. [The new list of addresses is now available on our website](http://freenode.net/irc_servers.shtml#tor). **Please update your tor configuration!**
-
+
* Finally, it is worth noting that although probably the least likely attack vector, [Heartbleed can also be used as client-side attack](https://www.eff.org/deeplinks/2014/04/wild-heart-were-intelligence-agencies-using-heartbleed-november-2013), i.e. if you are still running a vulnerable client a server could attack you. This could be a viable attack if, for instance, you connect to a malicious IRC server and freenode at the same time; hypothetically the malicious IRC server could then attack your client and steal your IRC password or other data. If affected, you should** ensure your OpenSSL install is updated and not vulnerable then restart your client**.
---
We have loaded a new module on the network which provides the $j extban type:
-
-<blockquote>$j:<chan> - matches users who are or are not banned from a specified channel</blockquote>
-
+> $j:<chan> - matches users who are or are not banned from a specified channel
As an example...
-
-<blockquote>/mode #here +b $j:#timbuktu</blockquote>
-
+> /mode #here +b $j:#timbuktu
...would ban users from #here that are banned (+b) in #timbuktu.
Please note that there are a couple of gotchas:
+ * Only matching +b list entries are checked. Quiets (+q) Exemptions (+e) & invexes (+I) are NOT then considered. As such, the following mode change would not alter the behaviour of the first example:
+ > /mode #timbuktu +e \*!\*@\*
-
- * Only matching +b list entries are checked. Quiets (+q) Exemptions (+e) & invexes (+I) are NOT then considered. As such, the following mode change would not alter the behaviour of the first example:
-
-
-
-
-<blockquote>/mode #timbuktu +e *!*@*</blockquote>
-
-
-
-
-
-
- * Quiets and the quieting effect of bans may not immediately take effect on #here when #timbuktu's ban list changes due to caching by the ircd.
-
-
- * $j isn't recursive. Any $j extbans set in #timbuktu are ignored when matching in #here.
+ * Quiets and the quieting effect of bans may not immediately take effect on #here when #timbuktu's ban list changes due to caching by the ircd.
+ * $j isn't recursive. Any $j extbans set in #timbuktu are ignored when matching in #here.
We imagine you'll have some more useful use cases than the above.
projects / irc / freenode / web-7.0.git / commitdiff
