Slashdot Mirror

truthsearch writes "Lawrence Lessig's weblog points to 'a page by John Mark Ockerbloom at the University of Pennsylvania listing books that are in the public domain elsewhere but not, because of the Copyright Term Extension Act, in the United States. Check out the books you are not allowed to download.' Includes books like 'Animal Farm' and '1984'."

Adina Levin writes "An open letter to FCC chairman Michael Powell signed by internet and tech industry pioneers explains why the government shouldn't prop up the ailing telecom behemoths. Telecom companies bought expensive network technology with long bonds. That technology has been made obsolete by gear getting faster and cheaper all the time by Moore's law and Metcalfe's law. The telecom companies are asking for the equivalent of a bailout for their investments in sailing ships after the advent of steam. The way to speed the deployment of broadband to homes isn't to prop up businesses based on old technology, but to let uncompetitive businesses 'fail fast', and let new competitors play."

Denver is playing host to the Digital ID World conference, which is intended to discuss and examine the future of "digital identity" - how you'll be identified, tracked, and monitored online. Several people from the weblog community are in attendance and have reports available: Denise Howell, David Weinberger, Doc Searls.

Spencerian writes "I've become quite accustomed the depth of co-author Dave Taylor's writing on UNIX in previous books such as Teach Yourself UNIX in 24 Hours . As you can note from Dave's recent writing credits, his experience and knowledge of UNIX is vast and varied. That said, I was mildly disappointed with this latest offering that discusses the UNIX underpinnings of Mac OS X." Spencerian explains the logic underlying that conclusion in his complete review, below. Learning UNIX for Mac OS X author Dave Taylor & Jerry Peek pages 139 publisher O'Reilly and Associates, Inc. rating 7.5 reviewer Spencerian ISBN 0596003420 summary A good first-reference for new UNIX users, but steer clear if you're a UNIX vet.

For starters, I was annoyed to find that the book's title implied a larger format than the 139 pages it comprises. The book has an audience problem because of its size. UNIX guys like thick books. Is this book mostly for newbies to OS X, to UNIX, or to Mac OS X's implementation of UNIX? Despite this targeting problem, the book's contents are still useful, but I think its audience is more geared to new UNIX users. The book just doesn't have much depth for even a reference title, especially for a topic such as UNIX, and particularly for a new, little-documented UNIX family operating system such as OS X.

While Mac OS X is a BSD variant, it has a few idiosyncrasies that may throw off a veteran UNIX user, and this book manages to address most, if not all of these notable problems. For instance, Dave notes problems in sendmail that prevent it from working from the command line in Mac OS X's Terminal application, and presents a fix for the problem. If you use command lines in UNIX all the time, the book does present good instructions on getting Lynx, IRC, newsgroups, pine, and the like up and running in Terminal. The book shies away (quite appropriately) from any graphic interface items unless required, such as when changing Terminal's preferences.

This book was very recently published (May 2002) but already has fallen behind with the release of Mac OS X 10.2 (Jaguar). Some components of Jaguar, such as CUPS support for stronger printing options, are completely missing from this book. If you have Jaguar installed on your computer, don't dive headlong into the NetInfo Manager steps for LPR printer configuration. Books typically don't age this fast, but in the case of this book, small changes seem to mean a lot to this title's usefulness -- the introduction of CUPS may have made Chapter 5's contents almost irrelevant.

Another small nag involves the lack of information on useful commands for Mac OS X users that weren't available (or were difficult to find) with the old Mac OS 9. One such command, cron, makes my life easier for handling some tasks on my home computer. It's not even mentioned in this book, nor will you find much information on shell scripting or compiling UNIX code you might happen to find. I guess I'm most annoyed at the lack of compile information since the Apple Developer Connection marked this book as a Recommended Title.

Despite our fondness for (and tolerance of the slightly-higher prices of) Macintosh computers, Mac users aren't made of money and don't like to buy a bookstore's worth of tomes for basic information. It would have made a lot of sense to talk more about compiling software since Apple's software or other GUI products don't meet or can configure all UNIX needs. And I won't even talk about the lack of coverage about XDarwin, an application that starts XFree86 within a Mac OS X installation, allowing X Window applications to run atop or in tandem with the OS X interface. XDarwin has become popular enough for it to become part of the stable XFree86 distribution. Given that not every UNIX user is a command-line freak, this is a pretty critical omission in my mind.

So, who should buy this book?

If you are completely new to UNIX and have been a gooey-kiddie who's used almost nothing except Mac OS 9, this is a very good reference to get your toes moist with UNIX. However, as drug dealers say, "the first taste is free." This book will leave you wanting more detailed information. More experienced UNIX users can probably find out what they need about Mac OS X's command line from a few free locations such as Mac OS X Hints.

One last thing: A pox upon Tim O'Reilly for not using the platypus for the animal on the book's cover. Given that the open-source core operating system of Mac OS X is named Darwin and has a nicely-modified take-off on the BSD mascot that depicts both the name of the OS and its BSD origins, I would think that O'Reilly would have jumped on this obvious cover.

You can purchase Learning UNIX for Mac OS X from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

At Belle Haven Elementary School in Palo Alto, right about... *now*, the Internet Archive Bookmobile is starting its ten-day, cross-country trip to the Supreme Court. They're putting the hammer down (itinerary) (blog) to make it to Ohio for the Bookmobile Conference. Then they'll drive into Washington, D.C. on Oct. 8, the day before the nine Justices hear the copyright-extension case Eldred v. Ashcroft. The contraption is a Ford Aerostar with decals, satellite dish, wireless LAN, laptops... and a printer and binder to do on-demand printing of any of the thousands of public domain books on the internet. (The webpage says 20,000 but the decals claim 1,000,000... maybe they have 50 fonts :) Update: 10/01 01:33 GMT by T : Nick Arnett writes "The piece about Belle Haven School's bookmobile put the school in Palo Alto. It's not; it's across the freeway, in a far less wealthy and privileged neighborhood, where access to technology is much less common than in Palo Alto. (I'm on the board of Plugged In, a community technology center in the same area as Belle Haven.)"

David Mazzotta writes "Reading like an extended, Darin Morgan-penned episode of the X-files (Humbug, Bruckman, Coprophages, Chung), Christopher Buckley's Little Green Men uses alien abductions and UFO conspiracies as a backdrop for some of the surest and funniest satires in recent years." Read on for the rest of David's review; I tend to prefer books from William F. Buckley, but this one sounds fun. Little Green Men author Christopher Buckley pages 317 publisher Random House rating 8.0 reviewer David Mazzotta ISBN 0742963314 summary Political and social satire wrapped in a zany story of alien abduction.

John O. "Jack" Banion is a man of fearsome power. A combination of Larry King and Bill O'Reilly, he hosts a pompous Sunday morning "issues" talk show that is the hub of Washington media. Politicians hate him, but need him. The dowdy matrons of beltway society fall over themselves to get him to attend their dinner parties. He has the luxury of dismissing millions of dollars in endorsements as beneath his lofty station. In an early scene, the President appears on his show and gets treated with righteous disdain, about which he privately muses "Presidents come and go."

Banion's life is filled with stifling protocols that he has fully embraced. He has few passions -- his wife seems happily neglected, the arts bore him, he doesn't even truly care about the politics he is immersed in, except to the extent that he wields influence over it. Even his cynicism rings hollow.

Enter one Nathan Scrubbs, a frustrated, mid-level, black-ops bureaucrat and professional alien abductor for an unmentionable government program called MJ-12. For years, Scrubbs has located prime abductee candidates: those who are personally reliable and believable, yet have the social and educational standing that would cause the media to doubt their veracity -- that is to say, trustworthy rubes. He orders their abductions with bored detachment, then monitors the media reaction to ensure that there is just a subtle but consistent undercurrent of belief that can be used for various manipulative purposes (bolstering the defense budget, scaring the Russians, funding satellites, etc.).

But Scrubs is bitter. He dreams of being a CIA field op, but was rejected by the agency. His job is a dead end. He can't advance, can't transfer, can't even talk about it with anyone. So one Sunday morning, blind drunk on Bloody Marys, while watching Banion's talk show, he authorizes a rogue abduction of Banion.

Banion goes public about his abduction and finds himself outcast from his elite circles while Scrubbs flees for his life from his own agency. Not surprisingly, events spiral out of control and the fates of Scrubbs and Banion intertwine. No more hoaxing unsuspecting rednecks, or manipulating meaningless government policies; for the first time in their lives they find there are deadly serious consequences to their actions. The collision of the contemptuous gravitas of the political actors with the madcap world of UFO conspiracists provides ample opportunity to compare the two and leave us wondering which one is sillier.

As a former speechwriter for Bush the Elder, Buckley, the editor of Forbes FYI, is very assured in lampooning the Washington DC aristocracy he is undoubtedly familiar with. He perfectly captures the egos behind the noble facades in the degrade-or-be-degraded Capitol high society. After his on-air flaying of the President, Banion is greeted by other power players at an elite dinner party.

But here was Tony Flemm, host of the second-rated Washington show, trying not to look jealous. "Jack. Nice show."

"Do you think? I don't know."

That's right, torture the poor bastard, make him explain, make him elaborate in front of everyone on just why he though it was such a good show. But wait, here came Burt Galilee, beaming, shaking his head in mock horror at Banion's ruffling of presidential eagle feathers. And here, just behind him, came the Speaker of the House of Representatives, and behind him, the French ambassador. A triumph.

Buckley is equally sardonic with the abductee population, yet, perhaps because they are painfully sincere despite their silliness, they are treated with a bit less vitriol.

Another of [hypnotherapist Bart Hupkin's] regressees shared her breakthrough of wrapping herself in cellophane, which, like panty hose, made it more difficult for the aliens to drive home their vile phallic probes. She noted that this also helped with weight loss. Another abductee announced that she was depressed because she missed her alien children. The father had, contrary to their joint custody arrangement, taken them off to the Pleiades with a "slut" from Aldebran. Hupkin said she should not take this personally. Aliens were notoriously problematic when it came to commitment.

Banion left the workshop unable to shake the feeling that there was something lacking in these people's lives...Banion had to keep reminding himself that the early Christians must have been an odd bunch, too.

As with any satire of length, the droll commentary can only take you so far; then you need characters that can carry the story. Though both are essentially passionless cynics at heart, Banion and Scrubbs flesh out fairly well. A central irony: Banion finds zeal for the abductee movement that he never experienced in the "serious" world of politics, and Scrubbs finally gets a taste undercover agent life as he flees the wrath of MJ-12. The plot runs a bit low on steam towards the end, but by that time we are, if not sympathetic for, at least interested enough in Banion and Scrubbs to want to know how it all ends.

Buckley takes an unbiased approach to satire. He is non-partisan regarding politics or social standing; he punctures the pretentious and skewers the self-important wherever he finds them. If you would rather be amused than disgusted with the inanity you read in the news or see on TV, Little Green Men is for you.

You can purchase Little Green Men from bn.com; (Note the remaindered price of $3.99 for the hardcover). Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

David Mazzotta writes "It's not just Sci-Fi authors who have had influence on space technologies. Artist Chesley Bonestell produced beautiful space-art that inspiried people from Sagan to Heinlein."

Maple Syrup writes: "Fast Company has an interesting article written by John Ellis about the power shift on the Internet, as large corporate interests use political means to take over what had been a populist medium. The most interesting material comes at the end: 'There are no grass-roots efforts on the Web. The Internet army, which is enormous, hasn't been engaged or conscripted.'"

epeus writes: "The U.S. Commerce Department is holding a workshop on DRM today, and inviting 'stakeholders' to talk. The panel is loaded with the usual suspects -Jack Valenti, Mitch Glazier, Vivendi, Disney, Microsoft and Intel, with one 'customer' repesentative. Richard Stallman and the NY Fair Use group are going to protest and say that We are the stakeholders -- our computers are our stake, and DRM is theft. If you can't go, send in your comments or read mine"

David Mazzotta writes: "The jacket copy of these novels declares the writer, Haruki Murakami, to be 'a Japanese Philip K. Dick with a sense of humor.' That's pretty accurate. But while Murakami shares Dick's inventive imagination and plots that containing fantastic, near-mystical overtones, these novels are populated with deeper, more identifiable characters." If that's an intriguing idea for you, read on for the rest of David's review. A Wild Sheep Chase and Dance, Dance, Dance author Haruki Muarkami pages 304 / 393 publisher Vintage Books rating 8.5 reviewer David Mazzotta ISBN 037571894X / 0679753976 summary The real and surreal clash in post-modern Japan.

In A Wild Sheep Chase (1989) the main character and narrator lives a mediocre existence. He is passionless; seemingly unaffected by his wife's betrayal and subsequent divorce, and only attracted to his current girlfriend because he finds her ears to be "marvels of creation" that can incite irresistible desire in any man who sees them. This shallow view of life is further emphasized by the fact that, throughout the book, no characters are referred to by proper names.

When the "Rat," a nomadic friend of the narrator, sends him a photograph of some sheep from Hokkaido, a chain of events is set in motion. The sheep picture comes to the attention of a shadowy figure simply known as the "Boss" -- a mythically powerful underworld kingpin -- who has a dire need to get a hold of one of the sheep in the photo. The Boss sends a messenger to the narrator making it clear that unless he finds that sheep, he will face financial ruin, if not worse.

What follows is a surreal journey from Tokyo to Sapporo and points north, including a hotel that could be right out of a Kubrick film and creature known as the Sheep-Man, who is worthy of David Lynch. In the course of this journey, and in the face of extraordinary events, our narrator confronts his superficial world view and the affect it has had on his life.

Set six years later, Dance, Dance, Dance (1994) is murder mystery, but one in which the clues are revealed by chance rather than dogged investigation - often by a seemingly random psychic encounter. Our narrator has resumed a normal life as a freelance copywriter. He refers to this as "shoveling cultural snow" -- doing the thoughtless and thankless work that needs to be done to clear the path. He is fairly well disengaged from humanity, spending a lot of time alone doing absolutely nothing. Yet, in the midst of this anti-social life, he finds that his long missing girlfriend, the one with the amazing ears -- is calling to him as if in a dream, and she is weeping.

Once again, a chain of events is set in motion. He travels back to the strange hotel to find it modernized and corporate. He has another encounter with the Sheep-Man who tells him to "keep dancing." In the course of story he encounters, and finds sympathy for, a disaffected adolescent girl from a dysfunctional family, and an old high-school acquaintance who has become a famous movie star. Through his relationship with these characters he solves the mystery of his missing girlfriend, not through directed investigation but just by staying engaged with life and society -- by keeping up the "dance."

As a Westerner reading these novels, I was struck by how different the Japan portrayed here is from the hyper-efficient, sanitized, sexless and safe Japan of common impression. This is late twentieth-century post-modern Japan. References to Western pop culture are incessant. Call girls abound. Characters find themselves entangled in confusing, neurotic relationships worthy of HBO original programming. And nobody is practicing Kendo.

These books are hard-boiled -- that is to say, they are written in the hard-boiled style defined in the mid-twentieth century by U.S. mystery writers Raymond Chandler and Dashiell Hammet. There is a stark contrast between the blunt, gritty realism of hard-boiled style and the surreal, supernatural events that occur. This causes the stories to seem solidly planted in the real world, despite the occasional bizarre episodes.

There are certain shortcomings; the camera's eye perspective of the hard-boiled school lends itself to a bit too much dwelling on the details of setting. This is primarily in evidence at the beginning of A Wild Sheep Chase. And one suspects something is lost in the translation from the original Japanese. For example, this passage from Dance, Dance, Dance:

"... and if you consider the telephone as an object, it has this truly weird form. Ordinarily, you never notice it, but if you stare at it long enough, the sheer oddity of its form hits home. The phone either looks like it's dying to say something, or else it's resenting that it's trapped inside its form. Pure idea vested with a clunky body. That's the telephone."

There is a certain vagueness that may not be intentional. One is left with the feeling that "form" doesn't quite convey the same meaning it did in the original language.

Reading Murakami has been described feeling like you've just awakened from a deep sleep and you aren't sure if you're still dreaming. These are fascinating, engrossing books that will leave you full of ideas and impressions to dwell on for a long time to come.

You can purchase A Wild Sheep Chase and Dance,Dance,Dance from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

cpfeifer writes with the review below of O'Reilly's 802.11 Wireless Networks: The Definitive Guide; he warns that this is not a book for everyone setting up a casual home wireless network, but says it's excellent for its intended audience. Read on for his complete review. 802.11 Wireless Networks : The Definitive Guide author Matthew S. Gast pages 443 publisher O�Reilly & Associates rating 9/10 reviewer cpfeifer ISBN 0-596-00183-5 summary A thorough survey of the features, issues and potential solutions of deploying 802.11 based wireless networks.

The Scenario

For a lot of folks, implementing an 802.11 network involves selecting and purchasing an access point and adapter cards, and installing or compiling the proper drivers. From there, we are off and running, usually in under an hour. However for the few, the proud, the sysadmins of the world it's a whole different ballgame. Sysadmins need a deeper understanding of network technologies to be able effectively design, deploy and debug them.

What's Bad?

Most of the book is right on the mark when it comes to the sysadmin audience, however chapters 8 (the PCF, for contention free service), 10 (the ISM PHYs) and 11 (802.11a overview) are only of interest to folks who are implementing 802.11 hardware, IMHO. These chapters contain very low-level material about the 802.11 transmission protocol, and will not be generally useful since equipment manufacturers do not provide access to this layer. A dead giveaway that you can skip over chapter 8 is the phrase "The PCF has not been widely implemented." If it's not widely implemented, chances are you won't have the option of using it in a deployment.

After this bellycrawl through the weeds, chapters 12 and 14 give click-by-click instructions for installing two commercially available 802.11 access point/client adapter pairs on your Windows box. The selected products are Nokia's A032 Access Point along with their C110/C111 and Lucent's Orinoco (formerly WaveLan) Access Point and client adapter. It's worth noting that these are two of the most expensive 802.11 solutions available on the market and have enhanced features that are not present in other models. These chapters are simply rehashed vendor installation documentation for these products and provide very little added value. There's nothing that I hate more than paying $30-$50 for a book which repackages documentation that is freely available on the web. Skip these chapters; the rest of the book is excellent.

What's Good?

This book starts off with six strong chapters that cover the 802.11 protocol specification, why WEP is vulnerable, and some upcoming security specifications. The first six chapters are invaluable reading for any sysadmin that is planning (or already responsible) for an 802.11 deployment. This is your ammunition when users come and ask why the wireless network is slower than the wired network with fewer users (preventing contention adds more overhead in wireless) or why they really really should tunnel every wireless connection over SSH (because WEP is fundamentally flawed). The chapter that covers the current WEP implementation demystifies the "40 bit" vs. "64 bit" key-length sleight of hand that some vendors play. The standard WEP key length is 64 bits. However, 24 of those bits are used as WEP's initialization vector for the RC4 cipher. These bits aren't encrypted in an 802.11 packet, so by sniffing 802.11 traffic you can examine the IVs of the packets and see how many distinct keys are in use, and even retrieve the actual key once you have captured enough packets. AirSnort retrieves WEP keys by implementing the Fluhrer/Martin/Shamir attack (orig paper, Stubblefield paper). Chapter 16 covers using tools such as Airsnort and Ethereal to analyze the 802.11 traffic on your network. Remember to use your powers for good and not evil.

The final 3 chapters address deployment, analysis and tuning of 802.11 networks. These chapters, combined with the first six are the heart of this book and the whole motivation for buying the book. The analysis chapter has a particularly wonderful section about gathering user requirements with respect to 802.11 specific issues (security requirements, roaming ...) and a very practical section about physical installation that clearly illustrates the author's mastery of integrating 802.11 technologies into an existing infrastructure.

So What's In It For Me?

If you're an sysadmin and implementing 802.11 technologies is on the horizon, this book is a solid reference of the current state of 802.11 solutions, both good and bad. It pulls no punches in presenting issues and weaknesses with the current solutions and documents forthcoming standards that are being proposed or developed to address them. If you're considering a smaller deployment at home, the security aspects of the text are still applicable, but the design/deployment sections are more rigorous than you will need. There is a bit of starch (repackaged vendor installation documentation) and unnecessary details (knowing that 802.11 frequency hopping uses Gaussian frequency shift keying is good for impressing women at parties, but doesn't really impact the design/deployment of an 802.11 network) but the other chapters redeem themselves and make this a very valuable text.

Table of Contents

1. Preface
2. Introduction to Wireless Networks
3. Overview of 802.11 Networks
4. The 802.11 MAC
5. 802.11 Framing in Detail
6. Wired Equivalent Privacy (WEP)
7. Security, Take 2: 802.1x
8. Management Operations
9. Contention-Free Service with the PCF
10. Physical Layer Overview
11. The ISM PHYs: FH, DS, and HR/DS
12. 802.11a: 5-GHz OFDM PHY
13. Using 802.11 on Windows
14. Using 802.11 on Linux
15. Using 802.11 Access Points
16. 802.11 Network Deployment
17. 802.11 Network Analysis
18. 802.11 Performance Tuning
19. The Future, at Least for 802.11
20. 802.11 MIB
21. 802.11 on the Macintosh
22. Glossary
23. Index

You can purchase 802.11 Wireless Networks : The Definitive Guide from bn.com. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then visit the submission page.

cpfeifer asks: "I'm joining a small startup that needs a knowledge management solution. I know that 'knowledge management' is seen an empty buzzword, but after working at a company where the communication is very poor, I see the value of allowing folks to post their own news instead of having it filtered through some sort of corporate newsletter. I've seen the commercial portals (Plumtree & others), but after seeing a couple of OSS publication systems (phpNuke, Slash), I think these would fit the bill quite nicely." Aside from some of the basic features found in weblogs (posting, archival, sorting and searching), what else is necessary for the proper maintenance and use of such a system? How hard would it be to adapt existing weblog-ware to this task?

Michael Jennings writes: "Here is a review of the Game On exhibition that is on at the Barbican centre in London, and which will tour Japan and the US in 2003." Here are two previous mentions of the exhibit. Below are Michael's detailed impressions of the exhibit.

On Friday I attended the Game On exhibition about the history of computer games, at the Barbican Centre gallery. (Admission charge, 11 pounds ($16)). This is on in London from 16 May to 15 September, before moving to The Museum of Scotland in Edinburgh from October 2002 to February 2003 and touring to-be-announced venues in Europe, America and Japan in 2003.

The exhibition starts off well as you walk in. The first thing you see is a PDP-1, with a description of the development of SpaceWar in 1962. Sadly, the PDP-1 is not actually operating, but there is a later (1977) coin operated version of Space War that you can play. From there, we jump straight to the 1970s, where we have a couple of instances of "Computer Space," the very first coin-operated game, from 1971, which had a truly cool cabinet and was produced by Nolan Bushnell, who had then not yet founded Atari, but was otherwise unmemorable, (although this photo does seem to indicate that the sixties were not yet over). We then have working versions (of both cocktail and upright versions) of many coin-operated games from the 1970s.

Most of the classics are there, from a 1972 version of Pong (or Ping, as it was known in the UK due to the world "Pong" denoting a bad smell in British English). Space invaders, Mr and Ms Pacman, Asteroids, Tempest, Defender, Missile Command, Galaxian, Donkey Kong, Centipede etc. There is a very brief description of the Mame project, and a projection TV system running Mame with a choice of about 20 classic games. Unfortunately, the significance of the project from a preservation point of view is not adequately described, nor are the various issues that go with it. (I asked an attendant whether they legally owned copies of the 20 individual ROMs, and he had no idea what I was talking about). As we go on, a lack of explanation of the things on show turns out to be the major weakness of the exhibition. There are quite a few very significant things in the history of gaming in the exhibition, but in a lot of instances it isn't adequately explained just why they are significant, or even in some cases what they are.

From there, we go to a room containing "Ten playable consoles," showing a few of the things we might have had in our homes: working examples of both dedicated game consoles and early microcomputers: the Magnavox Odyssey, Atari 2600, Sinclair Spectrum, Nintendo Famicon, Spectravision, Commodore 64 (why not the Vic-20?) up to an early Amiga. This room also contains brief potted histories of the gaming activities of Atari, Commodore, Sega, Nintendo, Sony, with one or two pieces of classic hardware to look. Plus there is a little potted history of the IBM-PC (with an AT in a display case to look at). There is no mention of the Apple 2, somewhat curiously. No, it wasn't perhaps principally a gaming machine, but it was the first machine providing high resolution colour graphics that people could have in their homes. It was the first non-arcade machine I personally played games on, and I think this is true of a lot of people. (I cite the results of the "most nostalgic item" poll on Slashdot last week).

Up to this point, the exhibition has been largely chronological. From this point on, it drops the chronological aspects and becomes more theme based. This works with variable success. (Some themes work better than others). Some things that are historically quite closely related to each other are not close to one another in the exhibition due to the way they are categorised. A strictly chonological exhibition may have worked better.

Firstly we have a couple of rooms full of about 50 (mostly console) games that you can play. These are supposedly divided up into "Games of Action," "Games of Simulation," and "Games of Reflection and Thought," supposedly, but the distinctions are not very clear. Largely though it's just a room with lots of games in it. In one corner I found the Infocom game of "The Hitch-Hiker's Guide to the Galaxy," which was the only text-based game in the whole exhibition. (No Star Trek, no ADVENT, no ZORK). This was a shame, as the culture of text games would have amongst other things helped bridge the gap between Space War and the 1970s arcade games and would have fit in well in the early history of games section).

After this, we had a section devoted to the making and marketing of five famous games (or families of games): Grand Theft Auto, SimCity / Sims, Final Fantasy, Tomb Raider, and Pokemon. This section is good. We have original character concept drawings, storyboards and design diagrams from Yoshitaka Amano, James Kenny and other original designers of a number of these games, plus both artwork (both for marketing designs and simply for the sake of art) from many of the game designers. Most notably, we have a series of paintings from Ocean Quigley of Sims fame, showing his visions of various Sim Cities and Sim Worlds. This is really cool.

Upstairs, we find a display comparing games culture between "Europe and the USA" and "Japan." The "Europe and the USA" section is unimpressive, containing a few sports-based games and a few military-based games, without really explaining what these have to do with Europe and the USA. (A discussion of how military simulators and games have influenced each other is the best). The "Japan" half is much better, talking about the influence of manga and anime, the influence of the Pachinko culture, the Japanese love of simulations games ("Go by Train", and "Bass Fishing"), plus a really good demonstration of how the game "Renegade" was modified from its Japanese version (which was set in a violent schoolyard) to its US version (which dealt with violence in a perhaps politically less sensitive gang-dominated urban jungle).

The section devoted to "Character Design" gives us a brief overview of the development of Mario and Sonic, and we then get to a section on "Childrens Games." The most interesting part of this is a display of handheld games, in particular early single-game handheld versions of Donkey Kong, Scramble, and a few others like this. (These were quite important to me, as I remember playing many of these in the early 1980s), as well as the usual Game Boys and the like. (I am not sure what makes these "Childrens Games" any more than a lot of the other games in the exhibition, however).

We then have brief sections on game sound and movie-related games. Nothing too exciting here, although lots of movie posters for masterpieces like "Super Mario Brothers" plus a couple of non-working arcade machines with movie related themes. (Tron, most notably. A bit of a shame this one isn't working. Also a shame they didn't devote more time to the movie, given the movie was about game culture. At least the are showing the film as part of the film season associated with the exhibition).

A section on multi-player games is much too small, unfortunately. There are a small number of networked PCs playing a small number of games. (Red Ace Squadron and Worms Word Party when I was there), plus a sign saying that a changing program of games will be shown over the course of the exhibition. This was a little disappointing, as quite frankly this is a small part of a bigger story: the development and evolution of Doom and Quake into things like Counter-Strike is an interesting story, and one that is not covered in this exhibition. (Perhaps they thought that if they had lots of people playing death matches, this would make the exhibition less family friendly). One of the following sections of the exhibition is devoted to the use of gaming technologies for urban planning, and demonstrates the produce V/Spacelab, which is a planning tool used in real urban design, that was developed from the Quake 3 engine. This is really interesting, and one of the best things in the exhibition, but it the obvious connection with the multiplayer game section is missed.

Finally, we have a section on "Future Technology" which talks about where we are going from here. A little bit on games with evolving characters, and voice and body based user interfaces. I would have liked to have seen something on cell phone based games (Japanese i-mode perhaps) as I think this is going to be a big deal.

On the way out, there is a theatrette showing documentaries on the history of games. I sat an watched the documentary "Thumb Candy" from Britain's Channel 4 hosted by Iain Lee, which gave a much clearer history of games than did the exhibition, but this is at the very end of the exhibition when most people are tired, so I was the only person in the theatrette.

As well as all this, the exhibition includes a number of generally small, "contemporary commissions," mostly concept art on games-based subjects. None of this tells you very much about computer games, but I did have the opportunity to play a game of Space Invaders where I got to shoot down the words from quotations from Focault while listening to the sounds of short wave numbers stations. If nothing else, this reminds me that I am in Europe.

I was interrupted by a reporter for the Russian language programs of the BBC World Service, who saw me taking notes for this review in front of the PDP-1, and after I told him a little about the history of Space War and the like, he recorded an audio interview with about my impressions of the exhibition. Thus, the people of Moscow may be hearing my thoughts translated into Russian.

The exhibition bookshop has a book devoted to the exhibition for sale for 20 pounds, plus copies of virtually every book devoted to computer games that the organisers could lay their hands on, a bit of manga and books devoted to manga, one or two tangentially related board games (Harry Potter, anyone?) a little bit of cyberpunkish sf (The Difference Engine, Do Androids Dream of Electric Sheep), and, perplexingly, a large number of copies of Naomi Klein's "No Logo."

There is also a program of films and lectures/discussions taking place to go with the exhibition. The films are "Tron," "The Driver," "Crouching Tiger, Hidden Dragon" (huh?), "Final Fantasy: The Spirits Within," "Resident Evil," "Existenz," "Ghost in the Shell," and "The Matrix," some of which are clearly worth seeing.

What's good? There is some very cool stuff on display. They have a PDP-1. They have lots of old arcade machines. You can play most of the games. The paintings of SimCity are good. Most of the stories in the histories of gaming are here if you look carefully. The final section on the use of the Quake 3 engine in urban design was great. There haven't really been any major museum exhibits on computer games before, and this is a good effort.

What's bad? There is a lack of coverage of text based games, and anything PC-like prior to Windows 95. There is a lack of coverage of PC gaming. Many of the items on display aren't adequately explained. The organisation into categories doesn't really work.

Is it worth spending my money on? Yes.

Rating: 7.5 out of 10.

Slashdot welcomes reader-submitted features -- thanks, Michael!

shanksd1 writes "The IEE Review for May reports that BT is announcing the UK's first public access wireless LAN, with a little help from Motorola and Cisco. 400 wireless hotspots of range 100m should be implemented by June 2003, and 4000 by June 2005. These 500 kb/s access points will be located in hotels, railway stations, airports, bars and coffee shops."

Kilroy writes "According to a Seattle judge freedom of the press only applies to paid journalists. As a result, he has indefinantly imprisoned a 70 year old former journalism professor for posting mean things on the web. I wonder how much something has to earn in order to make it legal to publish?"

Bakajin asks: "The posting about the camera speedometer hack reminded me of my interest in portable time lapse photography. I wondered if the astute Slashdot crowd can make some suggestions for a very portable digital time-lapse system. I was initially thinking about a PDA connected to a small web-camera. I'll hack my own code if I have to, but I'd prefer to have something off the shelf or not involving too much work. Any suggestions on the PDA/camera/software combo or any different system?"

chaoticset writes "An experiment in minimally directed self-learning has been going fairly well, from the article: To test his ideas, Sugata Mitra launched something 13 months ago he calls "the hole in the wall experiment." He took a PC connected to a high-speed data connection and imbedded it in a concrete wall next to NIIT's headquarters in the south end of New Delhi. The wall separates the company's grounds from a garbage-strewn empty lot used by the poor as a public bathroom. Mitra simply left the computer on, connected to the Internet, and allowed any passerby to play with it...he discovered was that the most avid users of the machine were ghetto kids aged 6 to 12, most of whom have only the most rudimentary education and little knowledge of English. Yet within days, the kids had taught themselves to draw on the computer and to browse the Net." Update: 04/17 22:23 GMT by M : Mitra has a website about his experiments.

Reader cpfeifer contributes the review below of O'Reilly's Programming Jabber: if your job (or hobby) includes instant messaging in all its glory, Jabber is a free-beer, free-speech framework for setting up instant messaging systems not bound to a single server in the middle. As cpfeifer points out, instant messaging can mean a lot more than popping an on-screen note to your friend in Des Moines -- machines and programs can use a general purpose communication system like this, with no human middleman required. Programming Jabber author D.J. Adams pages 4555 publisher O'Reilly rating 9 reviewer http://cpfeifer.blogspot.com ISBN 0596002025 summary A detailed guide for developers to understanding and extending the Jabber messaging framework. Examples in Perl, Python and Java. The Scenario

Jabber was first conceived by Jeremie Miller (pic) in early 1998 in an effort to unify the disparate instant messaging networks. Instant Messaging networks rely on the network effect to gain and retain marketshare. The concept is the same when applied to any sort of participatory network whether it's a junk exchange, or content exchange, the value of the network increases with the square of the number of participants.

If this is true, then doesn't it follow that it is in the best interests of the IM networks to establish peering agreements with each other so that their users can directly contact users on other networks without having to install each client?

Hello, Jabber.

When I first picked up this book, I expected to understand the Jabber protocol in sufficient depth to implement my own IM client. Instead, the approach this book takes is that Jabber isn't just an XML-based protocol strictly for IM, rather it is a general purpose event notification protocol that has some very nice message routing and user management features built into it. While i was reading about the messages that Jabber has defined as part of the protocol, I could easily see other applications/devices generating Jabber messages to notify subscribers (either other systems, or people) of events.

Part 1 of the book focuses on getting you up to speed on the basics of Jabber technology: motivation, major features, XML protocol sample and compiling/configuring your own Jabber server. Chapter 2 presents the "10,000 foot view" of Jabber technology. In here you will find a sample client-query request/response flow with full HTTP headers, discussed step by step. The next two chapters are a very in-depth discussion of installing and configuring your own Jabber server. When you dive into a custom configuration of a fleet of Jabber servers (a "constellation" in Jabber terminology), it really starts to hit home that the real problem Jabber solves is far deeper than just IM.

From there, part 2 kicks off with a detailed discussion of the most basic building blocks of Jabber technology: resource identifiers, XML handling mechanism and the set of XML elements/attributes that make up the vocabulary of the Jabber protocol. Each element/attribute is presented with an annotated example and sample client/server interactions where appropriate. Examples can make or break a technical book, and these examples do a good job of illustrating how the element/attribute is used.

The following chapters take you through using standard Jabber features, user registration/authorization, messages, presence, groupchat, components and the event model to enable new applications. One very interesting application presented is enabling developers to receive CVS commit notifications via Jabber.

What's Bad?

I know the /. community is suspicious of glowing book reviews where everything is wonderful and nothing could be done to improve the book, so I'll nitpick. My major problem with this book is that the overwhelming majority of the sample applications are written in PERL/TK. This isn't a problem in and of itself, but I'm not a PERL/TK developer. If I build a Jabber solution, it will be in java, so PERL/TK samples don't do me a lot of good. I think equal time should be given to implementing Jabber using the two most-used languages, as defined by the number and activity of open source projects using Jabber technology.

What's Good?

This book covers everything relevant to Jabber technology, from lowest level inner workings and extensibility examples for developers to configuration and deployment for admins. Most of the book is spent looking directly at the Jabber XML protocol, instead of a specific API implementation. This way, the book covers the technology and doesn't get lost in how one particular API models the protocol.

So What's In It For Me?

If you want to implement an inside-the-firewall IM solution for your company/group/tribe or investigate integrating event notification into an application, this is a great starting point. If you're just curious about Jabber and want to know how it works, then this will give you enough information to get you hooked.

Table of Contents

PART 1: Getting Started with Jabber

• Chapter 1. Introducing Jabber
• Chapter 2. Inside Jabber
• Chapter 3. Installing the Jabber Server
• Chapter 4. Server Architecture and Configuration

PART 2: Putting Jabber's Concepts to Work

• Chapter 5. Jabber Technology Basics
• Chapter 6. Jabber Namespaces
• Chapter 7. User Registration and Authorization
• Chapter 8. Using Messages and Presence
• Chapter 9. Groupchat, Components, and Event Models
• Chapter 10. Pointers for Further Development

Appendix A. The Jabber.xml Contents

Appendix B. The IQRPC Classes for JabberRPCResponder

Index

O'Reilly has posted other reviews of the book on their site. You can purchase Programming Jabber from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

box2321 writes: "There's a time and a place for large and feature-filled software. And there's a place for tiny apps - in fact, there's tinyapps.org. This is a mighty-fine resource for free and shared Win/DOS programs that weigh in under 1.44 MB. I learned of TinyApps from a pleasant source."

NortonDC writes: "Now we know why Sun's Scott McNealy tells people to 'Get over it,' namely that his company is in the forefront of an effort to assault any hope of buying and using anything with privacy. This article from an MIT publication documents the collaborative effort by Sun, Motorola and others to tag all consumer items with transmitting radio tags that uniquely identify each individual item with a 96-bit ID, for less than a penny each." In fairness, there are a lot of fine and legitimate uses that I would have no problem seeing these used for, but the possibilities for tracking you closer than you'd like are obvious.

sdelmont writes "The developers of Rubinius, an experimental Ruby interpreter inspired by SmallTalk, have been discussing the possibility of adding a Lisp dialect to their VM. Pat Eyler collected some ideas and opinions from the people involved and it makes for some interesting reading. For many, Ruby already is an acceptable Lisp, and the language itself started as a 'perlification' of Lisp (even Matz says so) so it is perhaps fitting and might help explain why the whole idea feels right. Now, if someone added support for VB and gave it the respect it deserves, the world would be a better place."