Slashdot Mirror
Why PyCon 2010's Conference Wi-Fi Didn't Melt Down
jafo writes "There's been a lot of teeth gnashing going on recently about broken wireless at conferences. We just wrapped up PyCon 2010, with around 600 (out of 1,000) attendees simultaneously accessing the volunteer-run network, and response has been fairly positive. 2.4GHz (802.11b/g) continues to be problematic, but most users were on 5.2GHz (using 802.11n) and associating at 130mbps, with a 100mbps link to the net (though after the fact we found that 35mbps would have sufficed). My PyCon 2010 wrap-up reveals all the secrets of how we did it, including pretty bandwidth and user graphs."
They redirected all requests to goatse.
(Also, how do I write non-ASCII characters here?)
What makes you think you can, huh? Just because url's can contain them and the civilized portion of the net is already fine with them?
Hmmm.... that's odd.... the Cylons must have managed to just miss all of Picon's wireless access points with their barrage of nukes. Or maybe it was just part of their "plan" all along?
awwww man, it "worked" on preview. Way to go, Taco. Ruined my fsck'n joke.
▲<br>
▲ ▲
Verilan and Swisscom are the IETF's providers at the present, for when the sponsor doesn't want to do it themselves.
When sponsors do do it themselves (generally because they sell wireless gear) I would advise them to be afraid. I still remember a poor sales-engineer from a previous meeting (that did not go well in a wireless sense) being told they had implemented some piece of the standard wrong, by engineers who had helped to write the standard. After a few rounds of that, he started visibly flinching whenever someone else came up to complain.
My Alma Mater was incorporated in 1410; anything founded after that is a Community College. :P
If you were blocking sigs, you wouldn't have to read this.
Triforce fail
Life is rarely fair. Cherish the moments when there is a right answer.