Re: First Defcon: The Observer's Perspective
I think a list, without description might be okay, but the list is really long and getting longer, especially with events at locations like the various villages. Providing a URL to a complete list would also be,"better," as those with interest can read more if they are interested, but people not interested don't have to wait through announcements about the details of things they do not care about.
I do not like rewarding failure, so I am reluctant to offer this, but it might be good to mention any contests, events, parties or social gatherings that were added after the program information was printed. I do not like this, because it rewards failure to plan, and organize, but it is also a good idea, because even with good planning, some events change or have misinformation due to miscommunication, or reference to obsolete documentation:
* BlooKode blood drive listed as Friday and Saturday, but was only Friday, and hours were different. Error was found before Defcon, but after info went to print.
* Hacker Jeopardy information was unknown before program went to print, but found out later.
* Contests at the Hardware Hacking Village were known after the information went to program.
* A change to the SkyTalks was made after information for the program went to print.
* Speaker relocation from one track to another, and/or one time to another.
* New speakers/presentation added since program info was submitted for printing.
* There were a few more changes/differences. The above list is meant to show that omissions and mistakes can happen with good planning, and last-minute or late planning.
A summary of changes would be good for people new to Defcon. This same summary of changes would also be useful if announced before the first talk in every track.
It would also be good to have a static URL with just text and no extra formatting that contains an addendum to the program. If it is a web-accessible text/plain file, then even ghetto early-1990's styled cell phones with G1 text-only web browsing could get a list of changes while at Defcon. This same document could be updated with more updates as they are known. (Twitter is less reliable for this, as changes are not retained long enough, or they are distributed across too many accounts, or they are a shrinking signal compared to the noise of unrelated Defcon changes/updates.) The sucky part of this idea is that someone would have compile these changes and keep this text file up-to-date. If Information Desk had access to such a text file on a server, then they would be the ideal location to collect and distribute such information. Since changes always happen after the program is printed, the URL could be included in the program.
I think a list, without description might be okay, but the list is really long and getting longer, especially with events at locations like the various villages. Providing a URL to a complete list would also be,"better," as those with interest can read more if they are interested, but people not interested don't have to wait through announcements about the details of things they do not care about.
I do not like rewarding failure, so I am reluctant to offer this, but it might be good to mention any contests, events, parties or social gatherings that were added after the program information was printed. I do not like this, because it rewards failure to plan, and organize, but it is also a good idea, because even with good planning, some events change or have misinformation due to miscommunication, or reference to obsolete documentation:
* BlooKode blood drive listed as Friday and Saturday, but was only Friday, and hours were different. Error was found before Defcon, but after info went to print.
* Hacker Jeopardy information was unknown before program went to print, but found out later.
* Contests at the Hardware Hacking Village were known after the information went to program.
* A change to the SkyTalks was made after information for the program went to print.
* Speaker relocation from one track to another, and/or one time to another.
* New speakers/presentation added since program info was submitted for printing.
* There were a few more changes/differences. The above list is meant to show that omissions and mistakes can happen with good planning, and last-minute or late planning.
A summary of changes would be good for people new to Defcon. This same summary of changes would also be useful if announced before the first talk in every track.
It would also be good to have a static URL with just text and no extra formatting that contains an addendum to the program. If it is a web-accessible text/plain file, then even ghetto early-1990's styled cell phones with G1 text-only web browsing could get a list of changes while at Defcon. This same document could be updated with more updates as they are known. (Twitter is less reliable for this, as changes are not retained long enough, or they are distributed across too many accounts, or they are a shrinking signal compared to the noise of unrelated Defcon changes/updates.) The sucky part of this idea is that someone would have compile these changes and keep this text file up-to-date. If Information Desk had access to such a text file on a server, then they would be the ideal location to collect and distribute such information. Since changes always happen after the program is printed, the URL could be included in the program.
Seven days perhaps, would be glorious!! to me at least, since it coincides with my vacation time, it'd not be a problem, but, that won't be true for most people. A lot can't even attend the closing ceremonies because they need to take a flight, some might need to be present at work next day, who knows.
There are even shorter cons like Thotcon that basically last 1 day and probably there are some very 1337 cons out there just not for everybody. 
is what I tell my students. Maybe "The Jargon File" may help you.
Comment