It wasn't our intent to spam (or create blogspam, to be precise), we just wanted to provide some exposure for the great website which complements the book very well.
We link every projects official website up in our coverage to make sure the source gets properly mentioned.
A record of Hacker News as a snapshot in time. Also, as all the links have been tagged, it could lead to some interesting information visualisation, for example - how the distribution of links has changed as hacker news gets older.
Edit: It also offers a new metric of how popular a submission is.
Presumably this is for http://www.minuteglass.com/? If you are after any significantly large sample data to base some usability/design decisions on, I'd recommend Amazon Mechanical Turk.
I was heavily involved with a university project of designing and building an open wheel racecar. We tried to do the exact same thing, that is, reduce our paperwork while increase knowledge dissemination (as well as knowledge retention and accountability for work).
At first we implemented a wiki. The techie guys on the team saw the long-term value of it and filled it in dutifully, however, many people simply didn't "get" the idea. The wiki ended up stagnating, as only a handful of people used it. The non-techie guys would inevitably ask about what was currently happening, of which the answer was already posted on the wiki. People just never warmed to it. Knowledge management and communication should not be a struggle, or else it will fall by the way side.
The solution was to step away from a wiki system (MediaWiki) and towards something else (Basecamp). Basecamp fitted in with how everyone used the net. Message threads that were relevant to people were sent to their inbox, they could reply to from their own mail account. Milestones are clear - tasks are clear. It's just usable and seamless.
A wiki has a perceived barrier of entry. It's a lot to take on at once for a non-techie. Using the systems which are currently in place, (eg email, a homepage/dashboard setup) to disseminate info will go a long way, rather than fighting an uphill battle of getting people to understand #REDIRECT [[pagename]]
There is a thread on Reddit where Mark Pilgram states that the final manuscript is due in June. He also states that if you have any suggestions/feedback, you should speak up.
Indeed, my university (in Australia) uses email@uts.edu.au, which is invalid. Interesting idea though - I like the upfront note/forethought about the cache settings.
Ben Fry is one of the fathers of Processing.org, he's done a lot of great stuff with information visualisation. He's done a lot of stuff looking at the relationships inside DNA,genes, emails and code. All of which are combination between art and information.
http://www.interactivegraphics.org/Home.html is the actual site for the book.