Jump to: navigation, search

How To Plan A Code4LibCon

1,919 bytes added, 16:55, 22 February 2010
Freenode IRC connection
=== Freenode IRC connection ===
* mbklein: Chatted with some super helpful people in Historically, conference attendees have had trouble maintaining persistent connections to the #freenodecode4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and sent they're happy to work with organizers to raise the connection limit. Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are "private" IP ranges used for connection sharing.) Once you have the IP address or range, send an official request email to [ once I found out] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. ResultFor example: "  To: Hello, I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. Since our backchannel runs through #code4lib on Freenode has raised , we're trying to plan ahead to avoid running up against the IRC connection limit on . Would it be possible to raise the cap for us during the conference? Details follow. Conference: code4lib 2010 < > Dates: February 22-26, 2010 Attendees: 250 Location: Renaissance Asheville Hotel, Asheville, NC IP range served by Ranges: and the attwifi_meeting connectionentire block We encourage in-channel participation, so we expect a high percentage of attendees to be connected at once. We'll also have two or three channel bots connected from the conference for the lobby monitors. Please let me know if you need any further information, and thanks very much for your help! Michael I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. Additional support is available from the helpful volunteer Freenode staff in the #freenode channel."
== At the Conference ==

Navigation menu