Slashdot Mirror

Slashback tonight brings a few followups to recent Slashdot postings on the fate of model rocketry in the new, hypercautious America; a few Python gatherings for those who prefer that language to Perl; and a response from Los Alamos to recent claims of lax security. Enjoy!

Besides which, it's the hidden cameras that matter. An anonymous reader adds this followup to the story posted last month about Wired reporter Noah Shachtman's account of sneaking into classified areas at Los Alamos national Laboratory.

"In an email message to all Los Alamos National Laboratory employees, Pete Nanos, the current Director of LANL, responded with information suggesting that the Wired reporter who thought he had broken in to a 'top secret area' had in fact just crossed a cattle fence:

'The Wired reporter clearly did not enter a Laboratory security area. The Laboratory encompasses more than 40 square miles. The security force protects important assets within those boundaries but cannot -- and does not -- protect every square foot of property. Based on the article, it appears the reporter crossed a barbed-wire cattle fence, not a fence that protects a Los Alamos security area.
There is a small security area with several buildings (roughly 400 feet by 400 feet) near the driveway entrance to TA-33. That area is surrounded by a seven-foot-high chain-link fence topped with three strands of barbed wire. A security guard is stationed inside that area seven days a week and 24 hours a day. Clearly, the reporter did not climb that fence.
There are several other buildings outside the security area that are locked for property protection interests. They have no security interests. There are several gates and fenced areas on the TA-33 site, which are there for safety access control, not security.
It's unlikely the reporter would be prosecuted for trespassing; the Laboratory does not have law enforcement authority to prosecute, and none of the proper authorities witnessed the trespass.'"

Perhaps we can have a celebrity deathmatch. hfastedge writes "Ok, now that 2 perl conferences have been mentioned, I've been brought over the edge. Python is a language that is just as old, and arguably better from: most importantly a uniform standard of readability (enforced by using whitespace to delimit blocks (instead of {}), by avoiding overuse of cryptic symbols, and by a culture that strives to keep innovations as "pythonic"), and a rich development community. Anyway, normally, there are Python events in Europe, and a trail at O'Reilly's OSCON. But now, there is a far cheaper event taking place on March 24-28 in Washington DC: http://python.org/pycon/.

Examples of Python in action: 0, 1, 2, 3, 4, 5, 6, 7"

Fly up go phhhhhwwwtttpffffff .... MyNameIsFred writes "Slashdot recently discussed whether anti-terrorism laws would destroy model rocketry. The government has ruled, and the message is clear, "When it comes to the hobby of model rocketry, size does matter. And in this case, the magic number is 62.5 grams. That's the largest amount of propellant a single model rocket engine can have in it and still be exempt from a new set of federal rules that will go into effect May 24." What does this mean for the the big guys in model rocketry, who use engines larger than this?"

chromatic writes "It's easy to write code that works fine on single-processor systems but dies horribly on multi-processor boxes. Instead of spending thousands of dollars on a four- or eight-way system, you can use UML to emulate a multi-processor machine."

Richard Koman writes "My interview with EFF's Cory Doctorow just went up on O'Reilly. The interview is largely about his book, "Down and Out in the Magic Kingdom," but naturally veers towards discussing his view of Disney, programmers, and peer to peer. Then there's this: Doctorow: I think that Disney's art and technology kicks ass. But one thing you discover in the technology world, especially in free software, is that being a good programmer and being a good person are not necessarily correlated, or at least being a good programmer and being a person with whom other people want to spend a lot of time, who has good hygiene and good social skills, are not correlated."

cascadefx writes "There is a great article on writing a Vector Space Search Engine in Perl over at the Orielly Network's Perl.com site. Most search engines, such as Google, use a reverse keyword index algorithm. The article, complete with code, proves yet again that there is (definitely) more than one way to do it. Try your hand. Add improvements and you may have a handy search engine for your site or... the next Google-killer."

suzanne writes "The deadline cometh: if you have a hankering to participate in the 2003 O'Reilly Open Source Convention, get your proposal/s in by February 15. It's in Portland this year, and a little earlier than usual, July 7-11. (If you missed the fun last time, check out last year's coverage page, especially SuperSnail's photos of the event.)"

suzanne writes "The deadline cometh: if you have a hankering to participate in the 2003 O'Reilly Open Source Convention, get your proposal/s in by February 15. It's in Portland this year, and a little earlier than usual, July 7-11. (If you missed the fun last time, check out last year's coverage page, especially SuperSnail's photos of the event.)"

An anonymous reader writes "The PHP Extension and Application Repository (PEAR) is an online repository of high-quality, peer-reviewed PHP classes that conform to a rigorous coding standard. In this MacDevCenter article, Jason Perkins shows you how to install, configure and use the PEAR Package Manager on Mac OS X 10.2."

AShocka writes "The W3C has just released Scalable Vector Graphics (SVG) 1.1 and Mobile Scalable Vector Graphics (SVG) 1.1 as W3C Recommendations. W3C Fellow Dean Jackson has an article, on O'Reilly Network titled SVG On the Rise, in reply to Jacek Artymiak's article SWF Is Not Flash (and Other Vectored Thoughts). Also check out Dean's SVG answer to Powerpoint presentations at Visualising the Semantic Web in SVG."

AShocka writes "The W3C has just released Scalable Vector Graphics (SVG) 1.1 and Mobile Scalable Vector Graphics (SVG) 1.1 as W3C Recommendations. W3C Fellow Dean Jackson has an article, on O'Reilly Network titled SVG On the Rise, in reply to Jacek Artymiak's article SWF Is Not Flash (and Other Vectored Thoughts). Also check out Dean's SVG answer to Powerpoint presentations at Visualising the Semantic Web in SVG."

AShocka writes "The W3C has just released Scalable Vector Graphics (SVG) 1.1 and Mobile Scalable Vector Graphics (SVG) 1.1 as W3C Recommendations. W3C Fellow Dean Jackson has an article, on O'Reilly Network titled SVG On the Rise, in reply to Jacek Artymiak's article SWF Is Not Flash (and Other Vectored Thoughts). Also check out Dean's SVG answer to Powerpoint presentations at Visualising the Semantic Web in SVG."

chromatic writes "Howard Wen has written two pieces on Falcon's Eye (an alternate interface for Nethack). The first is a description of Falcon's Eye and its features. The second is an interview with Jaakko Peltonen, the project's creator."

chromatic writes "Jerry Cooperstein has written an excellent article summarizing the features removed from the upcoming 2.6 kernel. One controversial change may be tightening restrictions on binary-only modules." And Lovechild writes with some more 2.6 news: "I recently did an inteview with famous kernel hacker extraordinare and all round nice guy Robert M. Love for Tinyminds.org, about kernel 2.6 and what can be expected for desktop Linux users, when the new kernel series is released.

chromatic writes "Dustin Puryear has written a nice article summarizing the new and upcoming features of Samba. He's included a nice overview of what will be available when version 3.0 escapes. Let's hear it for interoperability!"

richard koman writes "Here's an interview I did with Karl Auerbach about ICANN in the aftermath of their eliminating public board members. 'October's distributed, denial-of-service attack against the domain name system--the most serious yet, in which seven of the thirteen DNS roots were cut off from the Internet--put a spotlight on ICANN, the nongovernmental corporation responsible for Internet addressing and DNS. The security of DNS is on ICANN's watch. Why is it so susceptible to attack, when the Internet as a whole is touted as being able to withstand nuclear Armageddon? It's religious dogma, says Karl Auerbach, a public representative to ICANN's board. There's no reason DNS shouldn't be decentralized, except that ICANN wants to maintain central control over this critical function. Worse, Auerbach said in a telephone interview with O'Reilly Network, ICANN uses its domain name dispute resolution process to expand the rights of trademark holders, routinely taking away domains from people with legitimate rights to them, only to reward them to multinational corporations with similar names.'" A Wired article suggests the five elected board members won't be stepping down on December 15 after all.

cpfeifer writes "Building browser-based java applications has involved a mixed bag of server side technologies (servlets, JSPs), client side technologies (HTML, Javascript) and frameworks (webmacro, Struts, Taglibs, Velocity). As these technologies appeared and matured, "The Right Way" (tm) to build web applications evolved to be an application of the classic model-view-controller pattern." Below is Craig's review of Struts in Action, a book which attempts to illustrate a successful path to making sure that web applications are designed the right way. Struts in Action author Husted, Dumoulin, Franciscus, Winterfeldt pages 630 publisher Manning rating (11/10) it goes to 11 reviewer Craig Pfeifer ISBN 1930110502 summary More than just a book about how to use the Struts framework, covers the best practices of web application design and development. If you are building a java web application of any appreciable size, YOU NEED THIS BOOK.

What's Needed So it is generally acknowledged that using the MVC pattern is the proper way to build web applications, but with the large number of technologies and frameworks it can be a long road to figure what is the best solution for your application. What we need is a book that covers the best practices of web application design and development from both a technology/architecture perspective, and is written by a few folks who have deep understanding of the underlying problems of building robust web applications.

That's what I love the most about this book, it doesn't just talk about how to configure and develop with Struts. It's a web application manifesto. Anyone can write a book about how to use Struts to build a web application. That's not the point. This book is ~8 people-years worth of first-hend developer knowledge (4 authors x ~2 years of working on the Struts project) condensed down into 630 pages. It doesn't just teach you how to use Struts (and Velocity and Taglibs and Tiles), but why you should use them. That's the most important thing this book has to offer. If your project is looking at using Struts & other Jakarta technologies, you need this book. If your project is currently using Struts & other Jakarta technologies, you need this book.

What's Bad?

The Velocity coverage is pretty light. If you are more comfortable building logic with a quasi-shell script language instead of using markup tags, then you should look to the project's documentation for further reference before embarking on a prototype. The Jakarta Lucene project, is touched on in the sample application they build, but are left as an exercise for the reader to investigate. While it's good to bring in related technologies to flesh out your sample apps, you have to be careful not to get sidetracked from the primary topic. You could easily write several books about the other components developed by the Jakarta project.

What's Good?

The best part is that the 4 authors are all Struts authorities (one Jakarta project manager, 2 Struts committers, one principal consultant), so they know Struts and the other Jakarta web frameworks inside and out. More than that, these guys have been solving the problems involved with web applications for several years now. They have deep experience in the patterns and best practices of building robust and flexible web applications, and this book passes on their experiences to the reader.

So What's In It For Me?

With this book and a little bit of effort on your part, you will be a competent Java web application developer. With a little bit more effort, you will become a Java web application architect. It's worth the extra effort. This is a tremendous book that will set the standard for web application references and will continue to be useful for years to come. It reminds me of the first Manning book I read, Neward's Server-Based Java Programming in terms of it's scope. approach and usefulness.

You can purchase Struts in Action from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

chromatic writes "Jerry Cooperstein has just written an excellent article explaining the competing threading implementations in the upcoming 2.6 kernel for the O'Reilly Network."

chromatic writes "Jerry Cooperstein has just written an excellent article explaining the competing threading implementations in the upcoming 2.6 kernel for the O'Reilly Network."

chromatic writes "I've published an essay about building online communities on the O'Reilly Network. It pulls together several thoughts gathered from observing sites like Slashdot, Everything2, and Perl Monks."

chromatic writes "I've published an essay about building online communities on the O'Reilly Network. It pulls together several thoughts gathered from observing sites like Slashdot, Everything2, and Perl Monks."

Patrick writes "The transcript of the oral arguments in Eldred v. Ashcroft is now online." Such exciting lines as: "CHIEF JUSTICE REHNQUIST: Well, but you want more than that. You want the right to copy verbatim other people's books, don't you?". See previous stories about the oral arguments and Lessig's thoughts on them. chromatic writes "The O'Reilly Network has just published Richard Koman's Lessons from the Internet Bookmobile about his travels with Brewster Kahle to Eldred v. Ashcroft. I particularly like how he describes the universal positive reception."

Patrick writes "The transcript of the oral arguments in Eldred v. Ashcroft is now online." Such exciting lines as: "CHIEF JUSTICE REHNQUIST: Well, but you want more than that. You want the right to copy verbatim other people's books, don't you?". See previous stories about the oral arguments and Lessig's thoughts on them. chromatic writes "The O'Reilly Network has just published Richard Koman's Lessons from the Internet Bookmobile about his travels with Brewster Kahle to Eldred v. Ashcroft. I particularly like how he describes the universal positive reception."

Peter Wayner writes "The book Creating Applications with Mozilla did not set out to capture the essence of modern open source software development in a few hundred pages, but it comes closer to that unreachable goal than almost any other book I can imagine. Everything is there: the proliferation of acronyms, the funky names, the endless layers, the earnest collaboration, the unstoppable yearning for customizability, and, of course, plenty of source code. The book is just supposed to be teaching us how to turn Mozilla into a front end for everything, but it's really a distilled exhibit of all that is hip and now in code creation." Peter's review continues below. Creating Applications with Mozilla author David Boswell, Brian King, Ian Oeschger, Pete Collins & Eric Murphy pages 454 publisher O'Reilly rating 9 reviewer Peter Wayner ISBN 0596000529 summary How to use the Mozilla APIs to do anything.

On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.

On another level, this book is also one of the first finished documents that explains what the Mozilla group has really been up to for the past five years. Some have abandoned the project, and others have attacked it as fundamentally misguided. This book shows why it took so long by demonstrating all of the cool features added during the long march to a new, thoroughly extensible architecture.

Are the results enough to justify the time and the effort? Some note that the features may be a bit overhyped, because building your own browser with the Mozilla API is like making a pizza with $15 and a telephone. While there's a large part of the book devoted to the work you can do to change the look and feel of the buttons on your browser, the book and the project offer much more. The Mozilla project is one of the biggest threats to simple tools like Visual Basic to come down the pike in some time. The various layers offer many ways to provide good, customizable interfaces to databases, the web, and much more. I can see how many corporate development shops may want to start making Mozilla the platform for a license-free front-end, simply because it's a straightforward tool without extra costs or restrictions.

At the most abstract level, the book is a great way to get a taste of modern software development. Computer scientists sometimes fix problems by adding more and more layers of indirection. This may not solve anything, but at least there are hooks for a real solution to use some time in the future if some one ever does figure out how to make the box do it. The Mozilla browser is one of the most extreme examples of this philosophy to ever emerge. Emacs was something special, but this is even more insane. Everything can be changed around by rewriting some XML and Javascript and most people don't need to juggle the pointers in grubby C to do amazing things. I realize it's not as beautiful as Lisp to some, but it's got a clarity and level of abstraction that's stunning to behold. Lisp was just procedural, while XML is more like logic programming.

This relentless customizability embodies one of the deepest reasons for the success of open source. Technology is inherently complicated and the only way we can use it is if we can look under the hood. You can say all you want about CVS trees and bazaars filled with competing code, but opening up the interface is one of the most powerful themes of open source. It's not about teaching people to build their own VCR or PVR from scratch, getting the VCRs for free or even debugging the VCR's source code -- it's just about making them easy enough to program.

The book illustrates how Mozilla opens up the API to create a relatively easy language for people to use. The real open source is not the C in the tar ball, but the XML interface spelled out in the book. Many people feel that the most important thing that the first browser designers did was make it easy for people to see the HTML tags marking up the document in front of them. The new Mozilla takes this transparency to a new high.

If you look at the book at all of these levels, you can see that this is one of the most important documents to emerge from the open source community in some time. At first glance, it's just another set of APIs for us to wiggle. I realize it's not fair to credit the Mozilla team or the book authors with creating the browser or XML ex nihilio -- they just jumped on some of the most popular bitwagons propagating across the Net. But the result is a stunning completion of a very important and cohesive vision. The book doesn't crackle with bleeding-edge novelty, but shines with the certainty of a job well-done.

Peter Wayner is the author of Translucent Databases , Disappearing Cryptography , and a number of other books. You can purchase Creating Applications with Mozilla from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

andyo writes "Why Human Rights Requires Free Software: Report on a practitioner's view of the critical role free software plays in the work of human rights activists around the globe."

nitro322 writes "Daniel Robbins, the leading developer for Gentoo Linux, has written an excellent O'Reilly Network article covering many of the various features of Gentoo, what's coming in version 1.4 (due out SOON), and why you should give it a try. If you haven't tried Gentoo yet, what are you waiting for?"

gnat writes "Tucked away on the O'Reilly Mac OS X Conference presentations page are links to Quicktime video and mp3 audio recordings of the Digital Rights Management panel featuring Dan Gillmor of the San Jose Mercury News, Cory Doctorow of the EFF, and others. (My apologies for the sometimes shaky video--three Cokes for breakfast is the anti-steadicam)"

gnat writes "Tucked away on the O'Reilly Mac OS X Conference presentations page are links to Quicktime video and mp3 audio recordings of the Digital Rights Management panel featuring Dan Gillmor of the San Jose Mercury News, Cory Doctorow of the EFF, and others. (My apologies for the sometimes shaky video--three Cokes for breakfast is the anti-steadicam)"

gnat writes "Tucked away on the O'Reilly Mac OS X Conference presentations page are links to Quicktime video and mp3 audio recordings of the Digital Rights Management panel featuring Dan Gillmor of the San Jose Mercury News, Cory Doctorow of the EFF, and others. (My apologies for the sometimes shaky video--three Cokes for breakfast is the anti-steadicam)"

gnat writes "Tucked away on the O'Reilly Mac OS X Conference presentations page are links to Quicktime video and mp3 audio recordings of the Digital Rights Management panel featuring Dan Gillmor of the San Jose Mercury News, Cory Doctorow of the EFF, and others. (My apologies for the sometimes shaky video--three Cokes for breakfast is the anti-steadicam)"

rhetland writes "An article on O'Reilly network discusses the new port of OpenOffice to Mac OS X. The public beta, due out next week, will be posted on the OpenOffice Mac site. I have been waiting for this for months, and can hardly wait."

davidwboswell writes "Oreillynet is running an article about how to create your own browser with Mozilla. This is a follow-up to a previous article that surveyed many of the alternate Mozilla browsers currently available including Chimera, Galeon, Phoenix and Aphrodite."

davidwboswell writes "Oreillynet is running an article about how to create your own browser with Mozilla. This is a follow-up to a previous article that surveyed many of the alternate Mozilla browsers currently available including Chimera, Galeon, Phoenix and Aphrodite."

davidwboswell writes "Oreillynet is running an article about how to create your own browser with Mozilla. This is a follow-up to a previous article that surveyed many of the alternate Mozilla browsers currently available including Chimera, Galeon, Phoenix and Aphrodite."

suzanne writes "A panel discussion was just added to the O'Reilly Mac OS X Conference, moderated by Dan Gillmor. He and Cory Doctorow, J.D. Lasica, Victor Nemechek, and Tim O'Reilly debate the expansive, pro-customer stance on DRM built in to Mac OS X. (Oh, and in case you don't have enough toys to play with yet, the complete conference schedule is available via iCal, Apple's latest groovy app.)"

suzanne writes "A panel discussion was just added to the O'Reilly Mac OS X Conference, moderated by Dan Gillmor. He and Cory Doctorow, J.D. Lasica, Victor Nemechek, and Tim O'Reilly debate the expansive, pro-customer stance on DRM built in to Mac OS X. (Oh, and in case you don't have enough toys to play with yet, the complete conference schedule is available via iCal, Apple's latest groovy app.)"

dooling writes "Continuing the tradition of well written O'Reilly 'Programming' books by those who know the language best, Programming PHP, co-written by the creator of PHP, Rasmus Lerdorf, provides a detailed overview of the popular PHP web-page scripting language. This book provides good programmers who have never used PHP enough information to do serious web development using PHP and serves as an excellent reference for web-page designers who dabble in PHP." Read on for the rest of his review. Programming PHP author Rasmus Lerdorf & Kevin Tatroe pages 507 publisher O'Reilly and Associates rating 7 reviewer dooling ISBN 1565926102 summary great PHP book for serious programmers, good reference While not as entertaining as Programming Perl, it isn't nearly as long either (and doesn't have to be). The book is written in a straightforward style and is very well organized. Appendices provide quick reference to all the PHP built-in functions and many PHP extensions. The most popular extensions, e.g., PEAR DB (database connectivity) and XML, have entire chapters devoted to them. Can't find a PHP extension for your favorite library? There's a chapter about writing your own PHP extensions, including writing C library wrappers.

This book begins as most O'Reilly "Programming" books do: with a brief introductory chapter. In Programming PHP, this chapter is very short, so don't look to this book for a gentle introduction. On the other hand, this is the perfect book for you if you are just looking to learn a new scripting language. The following chapters go over syntax, data types, built-in functions, etc. These chapters are a little dry, but move quickly and effectively demonstrate the unique features of PHP (as compared to other scripting languages).

Of particular interest to programmers who are interested in expanding their horizons to developing dynamic web pages are the chapters on PHP web techniques, security, and application techniques. The web techniques chapter gives a quick overview of HTML and the GET and POST methods (and why you would want to use one or the other). It then covers a lot of useful tips and tricks that may be foreign to someone who has done little or no web development. Topics such as getting server information, form processing, sticky forms, file uploads, document expiration, and authentication are covered. It ends with an excellent discussion of maintaining state from page to page and visit to visit, covering cookies and PHP's (very cool) session support.

The security chapter covers standard things you want to keep in mind when creating dynamic HTML. No surprises here, but it is always good to be reminded. The application techniques chapter starts with a collection of best-practices, tips, and tricks to make your development process easier and better. It concludes with sections about error handling and performance tuning. As with the security chapter, there is nothing here a good programmer doesn't already know, but you can never hear it too many times.

I think this is a great book for programmers who want to start developing dynamic web sites with PHP. It gives a detailed overview of PHP, lots of valuable tips, and a good sense of PHP's strengths.

As someone who has written a lot of code, but only a little CGI, I really liked the chapters that discussed application development techniques specific to the web. Along those lines, not much time is spent on standard coding techniques, so if you want to use PHP but have never written any serious code, you may want to look elsewhere for an introduction. For the rest of you, just think, you may never have to use CGI.pm again.

The index seems adequate, although I must admit I did not use it much on the first read-through. The book is so well organized that, when reading it, you do not have to flip around much. Perhaps someone who has used this book as a reference can comment further on the quality of the index.

Contents are available on O'Reilly's page Links

• PHP home page
• Rasmus Lerdorf's home page
• Kevin Tatroe's O'Reilly page
• O'Reilly page for book
  

See Rasmus's page for links to where you can buy the book (maybe he gets a kickback for the link). Of course, you could always go to a local bookstore and purchase it.

You can purchase Programming PHP from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

eggboard writes "The Linksys WET11 lets you bridge a wired network with up to 30 devices to any wireless access point that uses Wi-Fi. The utility is enormous: you could build a pseudo-mesh network by pairing cheap Wi-Fi APs with this cheap ($129) Wi-Fi bridge. Before this, the only generic Wi-Fi bridge was proprietary: you'd buy a bridge from Alvarion that paired with one of their hubs, and spend several hundred each. Even the dual-WAP11 bridge approach of last year was wonky and required extra gear (although it can handle more devices than 30 since it's a protocol bridge, not a MAC bridge). I review the WET at O'Reilly's wireless developer's site."

rgraham writes "James Duncan Davidson (the original author of Apache Tomcat and Apache Ant) has an article over at O'Reilly's MacDevCenter that walks you through the steps of not only getting Apache up and running on 10.2 (pretty simple, I know) but also DNS and Mail. The aricle goes along well with Alan Graham article on how to setup your own .Mac type service."

rgraham writes "James Duncan Davidson (the original author of Apache Tomcat and Apache Ant) has an article over at O'Reilly's MacDevCenter that walks you through the steps of not only getting Apache up and running on 10.2 (pretty simple, I know) but also DNS and Mail. The aricle goes along well with Alan Graham article on how to setup your own .Mac type service."

Slashback tonight with a few words on forcing Open software, NASA mind-reading tricks, a reminder of one nice way not to pay for an MP3 decoder, and more. Read on for the details. Update: 08/28 00:36 GMT by T : Oops -- No DoubleClick news tonight, as the original headline implied. Regrets.

They felt your unvoiced contempt. perl-guy writes "According to a recent NASA press release, reports such as those in this Slashdot story stating that NASA is planning to develop mind-reading equipment for airports in efforts against terrorism are exaggerated and ignore the facts and science behind current research. 'NASA does not have the capability to read minds, nor are we suggesting that would be done,' said Robert Pearce, Director, NASA's Strategy and Analysis Division in the Office of Aerospace Technology in Washington. 'Our scientists were asked to think outside the box with regards to ideas that could aid the nation in the war on terrorism and that's what they are doing. We have not approved any research in this area and because of the sensitivity of such research, we will seek independent review before we do.'"

Let's put that Schneier fellow on the "body-search" list. Quixotic1 writes "Four articles are highlighted over at The Atlantic Online arguing that to protect ourselves against terrorism we must rely on people, not simply on technology. The outline touches on the recent article about Bruce Schneier, the national ID card proposal, and the Clipper Chip."

Star systems, slip through fingers, etc. Since Thomson Multimedia / the Frauenhofer Institute has decided to press the $0.75-per-decoder charge for MP3 decoders mentioned earlier today, there are probably a lot of people suddenly more interested in other formats. I favor the Xiph Foundation's Ogg Vorbis; Xiph CEO Emmett Plant has written his thank-you note to Thomson Multimedia.

Depends what you consider "great." morhoj writes "ZDNet is running a great commentary that talks about the recent debate involving the Digital Software Security Act (the California law the would force governments to use open source software). ''Open source is supposed to be about freedom. Unfortunately, certain advocates have lost sight of that goal.'' I couldn't have summed it up better myself. Forcing anyone to use Open Source software is no better than ludicrous Microsoft licensing agreements." I think Carroll is dead-wrong when he focuses on cost-benefit analyses (and ignores the question of whose money is being spent by whom, for what), but YMMV.

I bet they'd have to edit Super Troopers, too. David_Bloom writes: "Following up on an earlier article, according to a page (link is a direct link to a frame - context sold separately) on the IMAX website, the first movie to use 35mm to 70mm IMAX DMR technology will be the hit 1995 flick Apollo 13. It is interesting to note that, according to a FilmRatings.com lookup, the film has been edited for content for its IMAX release (which is bad news for people hoping to see The Matrix or similar movies on IMAX)."

No, I said I'm meet you by the other telescope! Reader Dan Yocum points out that the skyward-gazing Yalies who captured asteroid 2002 NY40 digitally did so with a different telescope than the one reported. He writes: "They weren't even using WIYN. They were using the 0.9M that's next to it (about 50yd away)." Thanks for the correction!

eggboard writes "In the Seattle Times, published right across the lake from Microsoft headquarters, I argue that Microsoft's Macintosh Business Unit (MacBU) has produced some wonderfully engineered Mac OS X software, but they're generating most of the resentment they get because they miss the details: no Palm sync months after it should have come out; six-year-old broken features in Word; no common format for mail among Outlook, Entourage, and Outlook Express. If the MacBU could fix things as well as they write new features, their Mac customers would have a much better outlook." Tim O'Reilly recently had his own thoughts after meeting with people at MacBU, and meanwhile, MacBU also released Remote Desktop Connection Client for Mac OS X. What's the real future of Microsoft on Mac OS X? MacBU's marketing director told O'Reilly to reserve judgment: "Watch us for another six months."

mshiltonj writes "Tim O'Reilly wrote a little piece about his worries about the politicization of the Open Source community, specifically the Digital Software Security Act. He calls it a bad idea, saying, 'No one should be forced to choose open source, any more than they should be forced to choose proprietary software.'"

There's a tremendous difference between what government should be allowed to do and what individuals should be allowed to do. O'Reilly is attempting to blur the distinction, a common rhetorical tactic but one which does not advance his argument. As far as I can tell, his only argument besides this is that if the citizenry pushes for the government to use Free software, companies will push back to use proprietary crud. This argument doesn't hold water - every company selling proprietary software is lobbying the government all the time, have been for years, and they aren't going to stop just because we do. CNet carries news today that Microsoft has pressured the NSA to drop development of Security-Enhanced Linux. I can only imagine what sort of pressures might have been brought to bear behind the scenes, perhaps Microsoft threatened to cancel the NSA's site licenses of Windows and Microsoft Office. But in any case, there's no such thing as "mutual disarmament" - if we back down we'll just get smashed by the continuing efforts of companies pushing proprietary software.

But back to the government/individual distinction. Individuals, for instance, shouldn't be required to disclose their private papers to anyone who asks. But government should: that's the foundation of our freedom of information laws, and they exist for a good reason - keeping an eye on government is a necessary thing. Saying "People should be free to keep their papers private" as an argument against government FOI laws is just a stupid strawman, unworthy of further debate. And that's what O'Reilly's argument against California's proposed law is as well.

Governments play by different rules. They need to be fiscally responsible, transparent to the public, and promote the public commonwealth whenever possible. Using Open Source or Free Software in government promotes all three of these goals, and if Microsoft or any other corporation doesn't make quite as much money when the government alters its standards for software procurement... so what? Companies who make shoddy products do lose business when the government ups its standards, and they have the same choice as any business does: either produce better products, or lose the government's business. In this case the shoddiness comes in some of the most important areas as far as software goes: open access to the code, to ensure the software that we the citizenry pay for is doing what it is supposed to be doing, but the rationale would be the same if the government mandated a certain level of bug-free-ness or a certain level of performance for software - you can shape up and continue selling to the government or you can ship out. Your choice.

O'Reilly seems to be promoting the agenda of Microsoft's Software Choice campaign. He's a business man; perhaps there's a reason we don't know about. But whatever his motives, his lame arguments are no reason to stop pushing for governments to use Free or Open Source software wherever possible.

JeffBone writes: "I was the CTO of a company back in 1997-1999 (Activerse, mentioned in the comments on the original article) that made a bot development kit in many ways similar to ActiveBuddy's product. This is clear prior art, dating back well over two years before to the initial ActiveBuddy filing. I'd be happy to help out anybody seeking to overturn this patent. Some additional comments on this can be found at oreillynet.com." You might not agree with Bone about software patents in general, but he has an interesting perspective on this one.

prostoalex writes "Steve Anglin, author of such O'Reilly books as "C# in a Nutshell" and "VB.NET Core Classes in a Nutshell" from recent Java Virtual Machine Symposium. Among the questions discussed are intelligent garbage collection, faster implementations of Java bytecode, getting JVM's for even smaller and lighter devices and stopping thinking outside the box."

Big Dave Diode writes "A cool story about what happens when a bunch of bored nerds with a lot of wireless equipment takes a road trip. Intervehicle networking at 65 mph!"

Lisa writes "A new entry in Tim O'Reilly's blog, titled "Creativity, Flow, and Joy in Programming" talks about a survey of IS developers with projects hosted by Sourceforge. The results were presented at O'Reilly's Open Source Convention last week. 60% said, 'With one more hour in the day, I would program.' 70% of the respondents volunteered that lack of sleep was the most significant cost of participation. Almost 50% of the respondents agreed that 'When we prepare a program, it's just like composing poetry or music." OSDN has a page with the survey results in PDF or HTML. Slashdot is a part of OSDN.

Lisa writes "A new entry in Tim O'Reilly's blog, titled "Creativity, Flow, and Joy in Programming" talks about a survey of IS developers with projects hosted by Sourceforge. The results were presented at O'Reilly's Open Source Convention last week. 60% said, 'With one more hour in the day, I would program.' 70% of the respondents volunteered that lack of sleep was the most significant cost of participation. Almost 50% of the respondents agreed that 'When we prepare a program, it's just like composing poetry or music." OSDN has a page with the survey results in PDF or HTML. Slashdot is a part of OSDN.

x180 writes "Those goofy hackers over at the O'Reilly Open Source Convention in San Diego this week have, in a spate of fun, put together a series of Switch ad spoofs for the geeky ones. Writes Rael Dornfest in his blog, 'You've no doubt seen Apple's fabulous Switch campaign commercials. But what of the others? The geeky ones. The scripters. The sysadmins in their server cages. The command-line jockeys. Those through whom the source flows openly.' See the stories of hackers chucking Emacs in favor of Vi, leaving Perl to explore Python, and leaving the familiar home of Unix to play with XP." These, of course, aren't the only switch parodies. Their numbers are Legion.

x180 writes "Those goofy hackers over at the O'Reilly Open Source Convention in San Diego this week have, in a spate of fun, put together a series of Switch ad spoofs for the geeky ones. Writes Rael Dornfest in his blog, 'You've no doubt seen Apple's fabulous Switch campaign commercials. But what of the others? The geeky ones. The scripters. The sysadmins in their server cages. The command-line jockeys. Those through whom the source flows openly.' See the stories of hackers chucking Emacs in favor of Vi, leaving Perl to explore Python, and leaving the familiar home of Unix to play with XP." These, of course, aren't the only switch parodies. Their numbers are Legion.

x180 writes "Those goofy hackers over at the O'Reilly Open Source Convention in San Diego this week have, in a spate of fun, put together a series of Switch ad spoofs for the geeky ones. Writes Rael Dornfest in his blog, 'You've no doubt seen Apple's fabulous Switch campaign commercials. But what of the others? The geeky ones. The scripters. The sysadmins in their server cages. The command-line jockeys. Those through whom the source flows openly.' See the stories of hackers chucking Emacs in favor of Vi, leaving Perl to explore Python, and leaving the familiar home of Unix to play with XP." These, of course, aren't the only switch parodies. Their numbers are Legion.

Just a little reminder that Slashdot meetup is today! Sorry to the folks on the other side of the dateline for not posting this earlier. Check it out at slashdot.meetup.com we've had some 5000 people register all over the world so we thought a reminder ping was in order. The original story is available too. We won't be there this month as we're at OSCON today. But we'll be there next month perhaps. If you do go to a meetup put in a submission about it and we'll do a wrapup tonight or tomorrow sometime.