Slashdot Mirror

medea and several other readers noted that the LHC came back online early this morning. Here is the tweet from CERN announcing the milestone. As we discussed a few weeks ago, CERN plans to run the LHC at half power or less through 2011.

Google has launched a competitor or counterpart to Microsoft's Photosynth, which employs user-contributed photos of much-photographed sites to supplement the street-level view in an immersive way. Google's offering is called simply Navigate through User Photos, and unlike Photosynth — which requires Sliverlight and therefore is not available on Linux — is implemented in Flash. This YouTube video (also embedded at the link above) offers a quick tour of the new feature, which can use photos uploaded to Panoramico, Flickr, and Picasa.

Rob Weir got wind that a Slovakian tech site had been discussing the non-randomness of Microsoft's intended-to-be-random browser choice screen, which went into effect on European Windows 7 systems last week. He did some testing and found that indeed the order in which the five browser choices appear on the selection screen is far from random — though probably not intentionally slanted. He then proceeds to give Microsoft a lesson in random-shuffle algorithms. "This computational problem has been known since the earliest days of computing. There are 5 well-known approaches: 3 good solutions, 1 acceptable solution that is slower than necessary and 1 bad approach that doesn’t really work. Microsoft appears to have picked the bad approach. But I do not believe there is some nefarious intent to this bug. It is more in the nature of a 'naive algorithm,' like the bubble sort, that inexperienced programmers inevitably will fall upon when solving a given problem. I bet if we gave this same problem to 100 freshmen computer science majors, at least 1 of them would make the same mistake. But with education and experience, one learns about these things. And one of the things one learns early on is to reach for Knuth. ... The lesson here is that getting randomness on a computer cannot be left to chance. You cannot just throw Math.random() at a problem and stir the pot and expect good results."

Rob Weir got wind that a Slovakian tech site had been discussing the non-randomness of Microsoft's intended-to-be-random browser choice screen, which went into effect on European Windows 7 systems last week. He did some testing and found that indeed the order in which the five browser choices appear on the selection screen is far from random — though probably not intentionally slanted. He then proceeds to give Microsoft a lesson in random-shuffle algorithms. "This computational problem has been known since the earliest days of computing. There are 5 well-known approaches: 3 good solutions, 1 acceptable solution that is slower than necessary and 1 bad approach that doesn’t really work. Microsoft appears to have picked the bad approach. But I do not believe there is some nefarious intent to this bug. It is more in the nature of a 'naive algorithm,' like the bubble sort, that inexperienced programmers inevitably will fall upon when solving a given problem. I bet if we gave this same problem to 100 freshmen computer science majors, at least 1 of them would make the same mistake. But with education and experience, one learns about these things. And one of the things one learns early on is to reach for Knuth. ... The lesson here is that getting randomness on a computer cannot be left to chance. You cannot just throw Math.random() at a problem and stir the pot and expect good results."

Rob Weir got wind that a Slovakian tech site had been discussing the non-randomness of Microsoft's intended-to-be-random browser choice screen, which went into effect on European Windows 7 systems last week. He did some testing and found that indeed the order in which the five browser choices appear on the selection screen is far from random — though probably not intentionally slanted. He then proceeds to give Microsoft a lesson in random-shuffle algorithms. "This computational problem has been known since the earliest days of computing. There are 5 well-known approaches: 3 good solutions, 1 acceptable solution that is slower than necessary and 1 bad approach that doesn’t really work. Microsoft appears to have picked the bad approach. But I do not believe there is some nefarious intent to this bug. It is more in the nature of a 'naive algorithm,' like the bubble sort, that inexperienced programmers inevitably will fall upon when solving a given problem. I bet if we gave this same problem to 100 freshmen computer science majors, at least 1 of them would make the same mistake. But with education and experience, one learns about these things. And one of the things one learns early on is to reach for Knuth. ... The lesson here is that getting randomness on a computer cannot be left to chance. You cannot just throw Math.random() at a problem and stir the pot and expect good results."

Rob Weir got wind that a Slovakian tech site had been discussing the non-randomness of Microsoft's intended-to-be-random browser choice screen, which went into effect on European Windows 7 systems last week. He did some testing and found that indeed the order in which the five browser choices appear on the selection screen is far from random — though probably not intentionally slanted. He then proceeds to give Microsoft a lesson in random-shuffle algorithms. "This computational problem has been known since the earliest days of computing. There are 5 well-known approaches: 3 good solutions, 1 acceptable solution that is slower than necessary and 1 bad approach that doesn’t really work. Microsoft appears to have picked the bad approach. But I do not believe there is some nefarious intent to this bug. It is more in the nature of a 'naive algorithm,' like the bubble sort, that inexperienced programmers inevitably will fall upon when solving a given problem. I bet if we gave this same problem to 100 freshmen computer science majors, at least 1 of them would make the same mistake. But with education and experience, one learns about these things. And one of the things one learns early on is to reach for Knuth. ... The lesson here is that getting randomness on a computer cannot be left to chance. You cannot just throw Math.random() at a problem and stir the pot and expect good results."

jonverve writes "In May of 2009, the White House launched an Ideascale site to gather ideas from citizens to identify ways to 'strengthen our democracy and promote efficiency and effectiveness by making government more transparent, participatory, and collaborative.' The digital letdown was when many of the top ideas generated by the process were to legalize marijuana, solve tax issues and to reinvestigate Obama's birth origins. Fast forward to February 6 and the same process has been repeated with individual federal agencies as the subject. This time the idea generation has been much more productive, with ideas such as establishing clear benchmarks on humanitarian progress in Sudan to the State Department, funding for open source text books and materials to the Department of Education, making it easier to access previously FOIAed documents to the Department of Justice, and creating a Wiki for NASA to share its data and to engage the public. Hackers from NASA's Nebula cloud computing platform have created a site that aggregates 23 of these idea sites to give a quick peek into the best rated contributions in each category. Programmed in Python and using the MongoDB and Tornado web server, the Open Gov Tracker was highlighted by the open government blog Govfresh this past week as well. Jessy Cowan-Sharp, one of the creators, explained their motivation: 'We thought that a single access point would give a sense of the participation on all the different sites, a window into the discussions happening, build some excitement, and inspire people to participate.' The process closes on March 19th, so go and visit the site to contribute your ideas and vote!"

kamapuaa writes "The NY Times has an article about how real-time license plate scanning is changing the car repo business. MVTRAC is one of several companies providing technology to track car license plates automatically, in order to populate private databases. This new tech is used by car repo companies to help banks or other lenders repossess cars; by police to find stolen cars or to locate ticket scofflaws; or really for whatever application MVTRAC and its competitors feel like pursuing, as the new-found industry lacks any kind of government oversight."

Last month, we discussed news that President Obama's 2011 budget proposal did not include plans to continue NASA's Constellation program, choosing instead to focus on establishing a stronger foundation for low earth orbit operations. Unfortunately, as government officials prepare to shut down Constellation, they're warning that it won't be a quick or simple process due to the contracts involved. From the Orlando Sentinel: "Obama's 2011 budget proposal provides $2.5 billion to pay contractors whatever NASA owes them so the agency can stop work on Constellation's Ares rockets, Orion capsule and Altair lunar lander. But administration officials acknowledge that this number is, at best, an educated guess. ... Many inside and outside of the space agency, however, think the number is too low. The agency has signed more than $10 billion worth of contracts to design, test and build the Ares I rocket and Orion capsule that were the heart of Constellation. But government auditors said last year that the costs of some of those contracts had swelled by $3 billion since 2007 because of design changes, technical problems and schedule slips. How much NASA will owe on all those contracts if the plug gets pulled is unclear. Many of the deals are called 'undefinitized contracts,' meaning that the terms, conditions — and price — had not been set before NASA ordered the work to start. That means the agency will need to negotiate a buyout with the contractor — and that can be a long and painful process, according to government officials familiar with the cancellation process."

spidweb writes "Much virtual ink has been spilled over Ubisoft's new, harsh DRM system for Assassin's Creed 2. You must have a constant internet connection, and, if your connection breaks, the game exits. While this has angered many (and justifiably so), most writers on the topic have made an error. They think that this system, like all DRM systems in the past, will be easily broken. This article explains why, as dreadful as the system is, it does have a chance of holding hackers off long enough for the game to make its money. As such it is, if nothing else, a fascinating experiment. From the article: 'Assassin's Creed 2 is different in a key way. Remember, all of its code for saving and loading games (a significant feature, I'm sure you would agree) is tied into logging into a distant server and sending data back and forth. This vital and complex bit of code has been written from the ground up to require having the saved games live on a machine far away, with said machine being programmed to accept, save, and return the game data. This is a far more difficult problem for a hacker to circumvent.'"

Hugh Pickens writes "The NY Times reports that an independent board of scientists will be appointed to review the workings of the world's top climate science panel, which has faced recriminations over inaccuracies in a 2007 report that included a prediction that Himalayan glaciers would vanish by 2035, although there is no scientific consensus to that effect. That brief citation — drawn from a magazine interview with a glaciologist who says he was misquoted — and sporadic criticism of the panel's leader have fueled skepticism in some quarters about the science underlying climate change. Nick Nuttall, a spokesman for the United Nations Environment Program, said the review body would be made up of 'senior scientific figures' who could perhaps produce a report by late summer for consideration at a meeting of the climate panel in October in South Korea. 'I think we are bringing some level of closure to this issue,' says Nuttall. One area to be examined is whether the panel should incorporate so-called gray literature, a term to describe nonpeer-reviewed science, in its reports. Many scientists say that such material, ranging from reports by government agencies to respected research not published in scientific journals, is crucial to seeking a complete picture of the state of climate science."

shewfig writes "The California legislature, which previously tried to ban incandescent light bulbs, just added to the list of banned things ... swear words! Fortunately, the measure only applies for the first week of March, and compliance is voluntary — although, apparently, there will be a 'swear jar' in the Assembly and the Governor's mansion. No word yet on whether the Governator intends to comply."

shewfig writes "The California legislature, which previously tried to ban incandescent light bulbs, just added to the list of banned things ... swear words! Fortunately, the measure only applies for the first week of March, and compliance is voluntary — although, apparently, there will be a 'swear jar' in the Assembly and the Governor's mansion. No word yet on whether the Governator intends to comply."

kiehlster writes "I'm a software developer, and I know that most software has bugs, but how much trust can we put in the many lines of code found in our automobiles? I have a 2009 Camry that is involved in both of the recent Toyota recalls. As part of the floor-mat issue, they're offering to install a software update that would cause 'the brake pedal to take precedence over the gas pedal if both were pressed,' or, as their latest notice states, 'would cut power to the engine if both pedals were pressed.' In the computer world, we're all taught to install firmware updates only if there is a real problem because a large percentage of firmware updates actually brick the hardware or cause other unforeseen consequences. On a base of 100 million lines of code, can I really trust a software update to work safely when it is delivered in a three-month development cycle? My driving habits don't cause the floor mat to slide much, so I see the update as overkill. What do you think? If it doesn't void the warranty, should I tell them to skip the update?"

darthcamaro writes "Remember Mozilla Ubiquity? It was an effort to bring natural language commands to the Firefox browser. Now after almost two years of development and a half million downloads, the project is no longer being actively developed. Project founder Aza Raskin is now working on other projects, including Mozilla Jetpack, so Ubiquity is on the back burner. '"There is huge demand for being able to connect the Web with language — to not have to move from one site to another to complete your daily tasks," Raskin said. "And there is huge demand for anyone to be able to write small snippets of code that lets them command the Web the way they want. Ubiquity gave everyday developers a voice with how the browser and the Web works."'"

snydeq writes "Fatal Exception's Neil McAllister writes about the no-win scenario facing today's independent programmers: 'In a knowledge economy, programmers rank among our most valuable workers, yet the current legal and regulatory climate makes a career as an independent software developer virtually a dead-end prospect.' Section 1706 of the 1986 Tax Reform Act, the hurdles and costs of obtaining health care for one's own family, a hostile legal climate in search of accountability for any defects in code — these harsh realities make it 'easy to see why software developers would give up on entrepreneurship. For many, the risks simply don't match the potential rewards. Better to keep their heads down, not rock the boat, and hope they can hang onto their jobs until retirement.' Great news for big software vendors, which will be 'ensured an endless supply of programmers desperate for the safe haven of a steady paycheck, predictable taxation, health benefits, and a shield from civil prosecution when their code turns up buggy. But where will the next Microsoft come from? A field that discourages self-reliance sends the message that the status quo is the highest goal.'"

schliz writes "The Australian Federation Against Copyright Theft (AFACT) has appealed a Federal Court judgement that this month exonerated ISP iiNet for its subscribers' copyright-infringing activities. In the widely publicised case, AFACT sought to penalize iiNet for its users having made 100k illegal downloads. A judge ruled that 'mere provision of access to internet is not the means to infringement,' but AFACT now claims the judgement 'left an unworkable online environment for content creators and content providers' and 'represents a serious threat to Australia's digital economy.'"

diegocg writes "Version 2.6.33 of the Linux kernel has been released. This version includes the Nouveau driver, Nintendo Wii and Gamecube support, DRDB, TCP 'cookie transactions,' a syscall for batching recvmsg() calls, several new perf subcommands (perf probe, perf bench, perf kmem, perf diff), experimental support for cache compression through swap, Xen PV-on-HVM support, drivers for virtual network and graphic cards from VMWare and other improvements. See the full changelog here."

diegocg writes "Version 2.6.33 of the Linux kernel has been released. This version includes the Nouveau driver, Nintendo Wii and Gamecube support, DRDB, TCP 'cookie transactions,' a syscall for batching recvmsg() calls, several new perf subcommands (perf probe, perf bench, perf kmem, perf diff), experimental support for cache compression through swap, Xen PV-on-HVM support, drivers for virtual network and graphic cards from VMWare and other improvements. See the full changelog here."

Michael J. Ross writes "Of all the online resources devoted to assisting Web designers and developers, Smashing Magazine is one of the most highly regarded, primarily because of the depth and consistent quality of the articles that appear on its website. This apparently motivated many of its readers to encourage the magazine's editors to develop and release a book on Web design, which the company did in 2009, appropriately titled The Smashing Book." Read below for Michael's review. The Smashing Book author Various authors pages 311 publisher Smashing Media GmbH rating 6/10 reviewer Michael J. Ross ISBN None summary A visually rich compilation of advice from Web design experts The publication company, Smashing Media GmbH, chose to exclusively handle all aspects of the book's production, including its distribution — a unique approach that distinguishes The Smashing Book from the other technical books that most Web professionals are accustomed to reading. Because of the widely disparate results by the publisher in each aspect of this book's production — content, presentation, and distribution — it would be best to evaluate each aspect individually.

The bulk of the book's content is organized into ten chapters, each written by a different author or group of authors, and each covering some of the key areas of website design, especially for commercial sites: user interfaces, CSS-based layouts, typography, usability, color usage, performance optimization, sales conversions, and site branding. In addition, there are two chapters featuring interviews with design experts, and a summary of the company's history. The two main editors at Smashing Magazine — Sven Lennartz and Vitaly Friedman — provide a brief preface. At the other end of the book, one finds a page devoted to the thirteen authors — a page that cleverly and concisely conveys some personal information about each person, from a statistical perspective. This is followed by an index that does not even fill a single page, possibly because it is set in a font size that is just small enough to make the entries somewhat difficult to read. Even more annoying is that every entry is presented in all lowercase, making it more difficult to locate proper names.

The book's first chapter is titled "User Interface Design in Modern Web Applications," and it discusses the basic characteristics and building blocks of an effective user interface. Its pithy advice on optimizing forms is particularly valuable. The only portion of the material that is unclear is the reference to "Ballpark" in the caption of the second figure on page 15. The second chapter, "The Art and Science of CSS-Layouts," first compares the advantages and disadvantages of fixed versus flexible layouts, and then explains how to create fluid grid layouts and adaptive fluid layouts — two topics rarely discussed in Web design books. Lastly, elastic and hybrid layouts are considered. Chapter 3 is titled "Web Typography: Rules, Guidelines and Common Mistakes" (but the Table of Contents has it wrong). Its authors present the basics of Web typography, its historical context, basic terminology, font size units, white space, typographic grids, size hierarchy, scales, paragraph styling, CSS fonts, text replacement techniques, and more. It is a particularly wide-ranging and information-packed chapter, marred only by the authors equating the Golden Ratio with the Fibonacci Sequence (page 80); they are related, but not synonymous. The next chapter, "Usability Principles for Modern Websites" explains the basics of how to optimize sites for the behavior of the typical Internet user. Despite its ridiculously hyperbolic title, "The Ultimate Guide to Fantastic Color Usage in Web Design, Usability and Experience" does present some examples of effective color use.

Roughly halfway through the book, it shifts focus from design considerations to the performance of a site — both technical and commercial. In "Performance Optimization for Websites," many of the techniques advised are unusable for most websites, since their Web hosting services do not allow SSH access and modification of the Apache, PHP, or MySQL settings. Also, the reader does not need to be told repeatedly that faster page loading leads to a better user experience — especially at least eight times. The next chapter, titled "Design to Sell — Increasing Conversion Rates" explains key concepts of online selling, as well as the applicability of sales knowledge gleaned long before there was an Internet. Aside from misstating how to calculate a conversion rate, the selling methods presented are excellent, and illustrated with real-world examples. A key component of online marketing is one's brand, the topic of the eighth chapter, "How to Turn a Site into a Remarkable Brand," which also makes heavy use of illustrative examples. The last two chapters are rather unique. The first one, "Learning from Experts — Interviews and Insights," consists of Q&A with half a dozen Web designers, and encompasses some terrific insights from industry veterans. The final chapter, "Behind the Curtains: The Smashing Magazine Story," presents a (sometimes tedious) history of the publication and its defining principles.

The content of the book is generally good, with some chapters offering far more value than others — which naturally varies according to what type of information the reader is most interested in. The formatting of the text could be improved in future editions. The CSS, JavaScript, and PHP code is double-spaced, which is unnecessary and actually makes it less readable, not more. Each chapter contains at least a few pullouts, which are of no value, because the text is already broken up visually with color images, headings and subheadings (of a different color than the regular text), and the occasional code snippet.

Many of the references in the book can be found at A Smashing List of Links, which could be made less frustrating by ordering the chapters' sections to match the order of the chapters in the book. At the bottom of the homepage, one will find a list of the authors, linked to their websites, as well as a list of errata. Strangely, the first erratum refers to errors in the book's introduction, even though the book does not have an introduction. Those errors are in the Table of Contents. That's not the only erratum in the errata: The erratum for page 38 is stated twice. The erratum for page 40 claims that the Clearleft slogan takes one line at a width of 1280 pixels, when actually it is split into two lines, as stated in the text and demonstrated in the screenshot in the book. At the bottom of the links page, it reads "an 404-page." Also, the errata would be much more helpful to the reader if they were sorted by page number. (All of these mistakes exist at the time of the writing of this review, and may have been corrected by the time you read this.)

There are additional errata not listed on that links page: "a #content-block" should read "a content block" (pages 38 and 39); "a JavaScript that" should read "JavaScript code that" (page 49); the three quotation marks (there should be four) near the end of the first paragraph on page 60, should be removed or fixed; the last sentence in the second paragraph on page 64, needs a verb; "users['] ability" (page 73); "using [it] when" (page 80); "see [the] screenshot" (page 86); "cave at" (page 89); page 91 has two footnote 11 superscripts, and the first one's URL is missing; "grab [the] user's" (page 115); "track on" should read "track of" (page 116); "
" should read "…" (pages 117 and 118); "[do] not always" (page 137, section 11); "of interest[s]" (page 143); "an disorganized" (page 145); "shopping basket" is missing a closing quotation mark (page 146); "based [on] words" (page 147); "pound sign sign" (page 157); "CoLd" (page 171); "a indicator" (page 195); "in [the] future" (pages 203, 307, and 309); "might [be] a" (page 212); "one give[s]" (page 222); the phrase "at a website promotes" on page 239, is completely extraneous; "flash" (page 258); and "planing" (page 276).

As for the production of the book, there are certainly some positive and negative qualities. The entire book is glossy, full-color, and quite attractive. But there are disadvantages to such glossy pages, including the glare on the pages from one's light source; plus, the book is rather heavy relative to its diminutive size, because the pages are quite thick. Even though the book consists of over 300 pages, they are small in size (14 by 21 cm), and thus contain less material than that found in the average computer book. Also, the short length of each line has induced the typesetters to jam the words closer together, making it nearly impossible to read each line at a fast pace. Incidentally, the copy that I received had an outside spine that at first appeared to be damaged by razor cuts, which instead turned out to be thin threads of glue (which were not difficult to remove).

The book is packaged so as to provide a lot more protection than one finds from the well-known online booksellers. The book is encased in shrink wrap plastic, and housed inside a tight-fitting cardboard box (which turned out to be rather difficult to open without tearing it apart). Yet my primary complaint is a combination of several problems: The small and heavy pages are obvious candidates for metal ring binding, which would allow the reader to open the book completely with ease. But instead, the publisher chose to use a glue binding that is very tight, which makes it difficult to open the book beyond 90 degrees, and impossible to get it to lay flat (which would be quite handy when trying to implement the book's ideas in one's own code, and thus needing to use the keyboard and pointing device). Even worse, the gutter is even narrower than the outer margin, for every page, and thus much of the text disappears into the gap. This compels the reader to pull the book open further, which quickly damages the spine, and eventually causes the pages to become detached, as evidenced in descriptions and even pictures posted by unhappy buyers. As for myself, in reading the book from cover to cover, it is now the only book in my library held together with a rubber band.

Smashing Media GmbH sells the book directly from its website, for $29.90 or €23.90 per copy. The company elected to self-publish the book, and without an ISBN number. Consequently, none of the major online booksellers in the United States make the book available. Prospective buyers anywhere in the world must order the book from the publisher, and wait for it to be shipped from Freiburg, Germany. This poses a serious problem, aside from the delay. Notably, an untold number of orders are never received by the buyers — reflected in the endless complaints on a page announcing the book's release. The shipping problems would have been avoided for US and UK buyers had the publisher listed the book with Amazon.com and/or Barnes & Noble. Offering the book in electronic format would have completely avoided all of these shipping problems, but that is not an option now nor one planned for the future.

If my experience is anything to go on, then your purchase order could turn into a fiasco. One full month after I was told that the book would be shipped to me, it still had not arrived. So the editor-in-chief kindly asked the customer support department to contact me, but they didn't. They told him that the book had been shipped, but when I asked repeatedly for the tracking number, it was not provided. I later figured out why: Typically no tracking number is used, so neither you nor the publisher will likely know where the book is in the shipping process! It should have been obvious as to the problems that this would have caused, especially for overseas shipments. All of this is independent of the initial multi-month delay that plagued the release of the book, apparently due to production problems. Initially slated for a September 2009 release, the company began taking pre-orders, but the book did not begin shipping until December.

European residents should have no difficulties receiving the book from the publisher, and will receive their copies sent by Deutsche Post — assuming the copies are not lost in the mail. However, buyers in the United States, the UK, or anywhere else, will probably get much better results by asking local booksellers whether they can special-order a copy, or by checking online auction websites.

In terms of its content, The Smashing Book is an elegant and valuable compilation of select best practices in Web design and site optimization. In terms of production and delivery, the many problems experienced by buyers and readers can provide lessons that would benefit future efforts by the publisher.

Michael J. Ross is a freelance website developer and writer.

Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael J. Ross writes "Of all the online resources devoted to assisting Web designers and developers, Smashing Magazine is one of the most highly regarded, primarily because of the depth and consistent quality of the articles that appear on its website. This apparently motivated many of its readers to encourage the magazine's editors to develop and release a book on Web design, which the company did in 2009, appropriately titled The Smashing Book." Read below for Michael's review. The Smashing Book author Various authors pages 311 publisher Smashing Media GmbH rating 6/10 reviewer Michael J. Ross ISBN None summary A visually rich compilation of advice from Web design experts The publication company, Smashing Media GmbH, chose to exclusively handle all aspects of the book's production, including its distribution — a unique approach that distinguishes The Smashing Book from the other technical books that most Web professionals are accustomed to reading. Because of the widely disparate results by the publisher in each aspect of this book's production — content, presentation, and distribution — it would be best to evaluate each aspect individually.

The bulk of the book's content is organized into ten chapters, each written by a different author or group of authors, and each covering some of the key areas of website design, especially for commercial sites: user interfaces, CSS-based layouts, typography, usability, color usage, performance optimization, sales conversions, and site branding. In addition, there are two chapters featuring interviews with design experts, and a summary of the company's history. The two main editors at Smashing Magazine — Sven Lennartz and Vitaly Friedman — provide a brief preface. At the other end of the book, one finds a page devoted to the thirteen authors — a page that cleverly and concisely conveys some personal information about each person, from a statistical perspective. This is followed by an index that does not even fill a single page, possibly because it is set in a font size that is just small enough to make the entries somewhat difficult to read. Even more annoying is that every entry is presented in all lowercase, making it more difficult to locate proper names.

The book's first chapter is titled "User Interface Design in Modern Web Applications," and it discusses the basic characteristics and building blocks of an effective user interface. Its pithy advice on optimizing forms is particularly valuable. The only portion of the material that is unclear is the reference to "Ballpark" in the caption of the second figure on page 15. The second chapter, "The Art and Science of CSS-Layouts," first compares the advantages and disadvantages of fixed versus flexible layouts, and then explains how to create fluid grid layouts and adaptive fluid layouts — two topics rarely discussed in Web design books. Lastly, elastic and hybrid layouts are considered. Chapter 3 is titled "Web Typography: Rules, Guidelines and Common Mistakes" (but the Table of Contents has it wrong). Its authors present the basics of Web typography, its historical context, basic terminology, font size units, white space, typographic grids, size hierarchy, scales, paragraph styling, CSS fonts, text replacement techniques, and more. It is a particularly wide-ranging and information-packed chapter, marred only by the authors equating the Golden Ratio with the Fibonacci Sequence (page 80); they are related, but not synonymous. The next chapter, "Usability Principles for Modern Websites" explains the basics of how to optimize sites for the behavior of the typical Internet user. Despite its ridiculously hyperbolic title, "The Ultimate Guide to Fantastic Color Usage in Web Design, Usability and Experience" does present some examples of effective color use.

Roughly halfway through the book, it shifts focus from design considerations to the performance of a site — both technical and commercial. In "Performance Optimization for Websites," many of the techniques advised are unusable for most websites, since their Web hosting services do not allow SSH access and modification of the Apache, PHP, or MySQL settings. Also, the reader does not need to be told repeatedly that faster page loading leads to a better user experience — especially at least eight times. The next chapter, titled "Design to Sell — Increasing Conversion Rates" explains key concepts of online selling, as well as the applicability of sales knowledge gleaned long before there was an Internet. Aside from misstating how to calculate a conversion rate, the selling methods presented are excellent, and illustrated with real-world examples. A key component of online marketing is one's brand, the topic of the eighth chapter, "How to Turn a Site into a Remarkable Brand," which also makes heavy use of illustrative examples. The last two chapters are rather unique. The first one, "Learning from Experts — Interviews and Insights," consists of Q&A with half a dozen Web designers, and encompasses some terrific insights from industry veterans. The final chapter, "Behind the Curtains: The Smashing Magazine Story," presents a (sometimes tedious) history of the publication and its defining principles.

The content of the book is generally good, with some chapters offering far more value than others — which naturally varies according to what type of information the reader is most interested in. The formatting of the text could be improved in future editions. The CSS, JavaScript, and PHP code is double-spaced, which is unnecessary and actually makes it less readable, not more. Each chapter contains at least a few pullouts, which are of no value, because the text is already broken up visually with color images, headings and subheadings (of a different color than the regular text), and the occasional code snippet.

Many of the references in the book can be found at A Smashing List of Links, which could be made less frustrating by ordering the chapters' sections to match the order of the chapters in the book. At the bottom of the homepage, one will find a list of the authors, linked to their websites, as well as a list of errata. Strangely, the first erratum refers to errors in the book's introduction, even though the book does not have an introduction. Those errors are in the Table of Contents. That's not the only erratum in the errata: The erratum for page 38 is stated twice. The erratum for page 40 claims that the Clearleft slogan takes one line at a width of 1280 pixels, when actually it is split into two lines, as stated in the text and demonstrated in the screenshot in the book. At the bottom of the links page, it reads "an 404-page." Also, the errata would be much more helpful to the reader if they were sorted by page number. (All of these mistakes exist at the time of the writing of this review, and may have been corrected by the time you read this.)

There are additional errata not listed on that links page: "a #content-block" should read "a content block" (pages 38 and 39); "a JavaScript that" should read "JavaScript code that" (page 49); the three quotation marks (there should be four) near the end of the first paragraph on page 60, should be removed or fixed; the last sentence in the second paragraph on page 64, needs a verb; "users['] ability" (page 73); "using [it] when" (page 80); "see [the] screenshot" (page 86); "cave at" (page 89); page 91 has two footnote 11 superscripts, and the first one's URL is missing; "grab [the] user's" (page 115); "track on" should read "track of" (page 116); "
" should read "…" (pages 117 and 118); "[do] not always" (page 137, section 11); "of interest[s]" (page 143); "an disorganized" (page 145); "shopping basket" is missing a closing quotation mark (page 146); "based [on] words" (page 147); "pound sign sign" (page 157); "CoLd" (page 171); "a indicator" (page 195); "in [the] future" (pages 203, 307, and 309); "might [be] a" (page 212); "one give[s]" (page 222); the phrase "at a website promotes" on page 239, is completely extraneous; "flash" (page 258); and "planing" (page 276).

As for the production of the book, there are certainly some positive and negative qualities. The entire book is glossy, full-color, and quite attractive. But there are disadvantages to such glossy pages, including the glare on the pages from one's light source; plus, the book is rather heavy relative to its diminutive size, because the pages are quite thick. Even though the book consists of over 300 pages, they are small in size (14 by 21 cm), and thus contain less material than that found in the average computer book. Also, the short length of each line has induced the typesetters to jam the words closer together, making it nearly impossible to read each line at a fast pace. Incidentally, the copy that I received had an outside spine that at first appeared to be damaged by razor cuts, which instead turned out to be thin threads of glue (which were not difficult to remove).

The book is packaged so as to provide a lot more protection than one finds from the well-known online booksellers. The book is encased in shrink wrap plastic, and housed inside a tight-fitting cardboard box (which turned out to be rather difficult to open without tearing it apart). Yet my primary complaint is a combination of several problems: The small and heavy pages are obvious candidates for metal ring binding, which would allow the reader to open the book completely with ease. But instead, the publisher chose to use a glue binding that is very tight, which makes it difficult to open the book beyond 90 degrees, and impossible to get it to lay flat (which would be quite handy when trying to implement the book's ideas in one's own code, and thus needing to use the keyboard and pointing device). Even worse, the gutter is even narrower than the outer margin, for every page, and thus much of the text disappears into the gap. This compels the reader to pull the book open further, which quickly damages the spine, and eventually causes the pages to become detached, as evidenced in descriptions and even pictures posted by unhappy buyers. As for myself, in reading the book from cover to cover, it is now the only book in my library held together with a rubber band.

Smashing Media GmbH sells the book directly from its website, for $29.90 or €23.90 per copy. The company elected to self-publish the book, and without an ISBN number. Consequently, none of the major online booksellers in the United States make the book available. Prospective buyers anywhere in the world must order the book from the publisher, and wait for it to be shipped from Freiburg, Germany. This poses a serious problem, aside from the delay. Notably, an untold number of orders are never received by the buyers — reflected in the endless complaints on a page announcing the book's release. The shipping problems would have been avoided for US and UK buyers had the publisher listed the book with Amazon.com and/or Barnes & Noble. Offering the book in electronic format would have completely avoided all of these shipping problems, but that is not an option now nor one planned for the future.

If my experience is anything to go on, then your purchase order could turn into a fiasco. One full month after I was told that the book would be shipped to me, it still had not arrived. So the editor-in-chief kindly asked the customer support department to contact me, but they didn't. They told him that the book had been shipped, but when I asked repeatedly for the tracking number, it was not provided. I later figured out why: Typically no tracking number is used, so neither you nor the publisher will likely know where the book is in the shipping process! It should have been obvious as to the problems that this would have caused, especially for overseas shipments. All of this is independent of the initial multi-month delay that plagued the release of the book, apparently due to production problems. Initially slated for a September 2009 release, the company began taking pre-orders, but the book did not begin shipping until December.

European residents should have no difficulties receiving the book from the publisher, and will receive their copies sent by Deutsche Post — assuming the copies are not lost in the mail. However, buyers in the United States, the UK, or anywhere else, will probably get much better results by asking local booksellers whether they can special-order a copy, or by checking online auction websites.

In terms of its content, The Smashing Book is an elegant and valuable compilation of select best practices in Web design and site optimization. In terms of production and delivery, the many problems experienced by buyers and readers can provide lessons that would benefit future efforts by the publisher.

Michael J. Ross is a freelance website developer and writer.

Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Joel writes "Over six months ago, Google announced it would start phasing out support for Internet Explorer 6 on Orkut and YouTube, and started pushing its users to modern browsers. The search giant has now given a specific kill date for old browser support on the video website: 'Support stops on March 13th. Stopped support essentially means that some future features on YouTube will be rolled out that won't work in older browsers.'"

An anonymous reader followed up on the Windows memory-leak fraud scandal, which is worth reading before you read the perpetrator's justification. "Randall C. Kennedy comes clean about his past, his relationship to Craig Barth and how it all came tumbling down. Includes an inside look at the politics of IDG and why you can never trust an IT publication that's as obsessed with page views as InfoWorld."

eldavojohn writes "Kotaku is running an investigative piece examining what internet censorship means for games in Australia. Australia has some of the most draconian video game attitudes in the world, and the phrase 'refused classification' should strike fear in game developers and publishers looking to market games there. Internet censorship may expand this phrase to mean that anybody hosting anything about the game may suffer censorship in AU. Kotaku notes, 'This means that if a game is refused classification (RC) in Australia — like, say, NFL Blitz, or Getting Up — content related to these games would be added to the ISP filter. [This would bring up] a range of questions, foremost of those being: what happens when an otherwise harmless website ... hosts material from those games (screenshots, trailers, etc) that is totally fine in the US or Japan or Europe, but that has been refused classification in Australia?' Kotaku received a comment from the Australian Department of Broadband Communication promising that the whole website won't be blocked, just the material related to the game (videos, images, etc). Imagine maintaining that blacklist!"

CWmike writes "A federal judge on Monday ordered the Pennsylvania school district accused of spying on its students to stop activating the cameras in school-issued MacBook laptops. According to the original complaint, Blake Robbins was accused by a Harriton High School assistant principal of 'improper behavior in his home' and shown a photograph taken by his laptop as evidence. In an appearance on network television last Saturday, Robbins said he was accused by the assistant principal of selling drugs and taking pills — but he claimed the pictures taken by his computer's camera showed him eating candy. Also on Monday, the company selling the software used by the school district to allegedly spy on its students blasted what it called laptop theft-recovery 'vigilantism.'" jamie found two posts from stryde.hax pointing out suggestive information about one school district network administrator, and coaching students how to determine if their school-issued laptops were infected with the LANRev software used to operate the cameras remotely and in secret.

CWmike writes "A federal judge on Monday ordered the Pennsylvania school district accused of spying on its students to stop activating the cameras in school-issued MacBook laptops. According to the original complaint, Blake Robbins was accused by a Harriton High School assistant principal of 'improper behavior in his home' and shown a photograph taken by his laptop as evidence. In an appearance on network television last Saturday, Robbins said he was accused by the assistant principal of selling drugs and taking pills — but he claimed the pictures taken by his computer's camera showed him eating candy. Also on Monday, the company selling the software used by the school district to allegedly spy on its students blasted what it called laptop theft-recovery 'vigilantism.'" jamie found two posts from stryde.hax pointing out suggestive information about one school district network administrator, and coaching students how to determine if their school-issued laptops were infected with the LANRev software used to operate the cameras remotely and in secret.

TACD writes "Simon Singh, author, television presenter and known critic of pseudoscience, is in court today appealing the decision made against him last May over his use of the term 'bogus' to describe the methods used by the British Chiropractic Association. Today's decision could have far-reaching implications for the movement to reform Britain's horrifically outdated libel laws (that even America is making moves to protect its citizens against), and to begin taking steps to elevate Britain above the likes of China when it comes to open debate and freedom of speech."

mdsolar writes "The leaking Vermont Yankee nuclear power plant was hit last week by a whistleblower allegation that a previous tritium leak had occurred. Now the parent company, Entergy, has admitted the occurrence of at least one prior leak to the Nuclear Regulatory Commission. This is particularly significant for three reasons: because the leak occurred in pipes that company officials later testified under oath did not exist, because the Vermont Senate will likely soon vote to deny Entergy a needed approval to extend the power plant's license for another 20 years, and because President Obama just put taxpayers on the hook for new nuclear power plants in Georgia."

mdsolar writes "The leaking Vermont Yankee nuclear power plant was hit last week by a whistleblower allegation that a previous tritium leak had occurred. Now the parent company, Entergy, has admitted the occurrence of at least one prior leak to the Nuclear Regulatory Commission. This is particularly significant for three reasons: because the leak occurred in pipes that company officials later testified under oath did not exist, because the Vermont Senate will likely soon vote to deny Entergy a needed approval to extend the power plant's license for another 20 years, and because President Obama just put taxpayers on the hook for new nuclear power plants in Georgia."

thatpythonguy writes "Learning Python is a well-written book by an experienced Python trainer that has served the Python community well since the first edition was published in 1999. Now, at its fourth edition, this book by Mark Lutz arguably continues to be Python's bible." Read on for the rest of Ahmed's review. Learning Python, 4th Edition author Mark Lutz pages 1216 publisher O'Reilly Media rating 9/10 reviewer Ahmed Al-Saadi ISBN 0596158068 summary A hands-on book that will help you be productive with Python 3.0 quickly This book is addressed as an introductory text to programmers new to Python. Although people with no programming experience are not discouraged from reading it, they are warned that time is mostly spent teaching Python, not programming fundamentals. I agree with this picture, though from my own experience and those of others, the book is equally valuable to more experienced Python programmers both as a pseudo-reference and as an introduction to more advanced topics. The critical point here is that the book does not make assumptions about educational or vocational experiences and provides many examples; this renders the book approachable by a large audience.

Both Python 2.6 and 3.x are covered in this edition. However, the latest 3.x line is considered the reference from which variations in 2.6 are discussed when appropriate. This approach is logical; the new Python 3.x presents a major change to the language, but is not sufficiently dominant to warrant exclusive treatment.

This book discusses the Python language and excludes the Python standard and non-standard libraries. The latter are discussed in other places including Lutz's own Programming Python which stands at its third edition at the time of writing of this article. I find this division necessary because of size considerations and, in fact, this division did not exist in the first edition of the book! However, there is one topic that does not seem to fit the language/libraries divide, and that topic is packaging and deployment.

I will argue that there are not many (if any) books that discuss packaging and deployment of Python programs well. I will also argue that this topic should be included in the book being reviewed here since it is so essential to real Python programming. Since Lutz discusses the Python runtime environment, I do not think it detracts from the book's coherence to include a chapter on packaging.It is possible that the proliferation of various packaging and deployment options such as distutils, setuptools, pip, buildout, virtualenv, paver, fabric and others, is the reason for this exclusion. Or it could be that these tools are in a state of major flux that any text will become quickly outdated. If size is the reason for this exclusion, maybe Lutz or someone else can publish 'Packaing and Deploying Python' as a separate volume.

The book starts by building a case for the use of Python. Both the features of the language and its prominent users are discussed to build credibility. Then, the runtime environment is discussed: how to run programs in various ways on various operating systems and language interpreters.

Types and statements, which are at the core of any language, are discussed next. Notably, there is an excellent discussion of the topic of iterators and generators (also discussed in a later chapter). Functions, modules and classes are then introduced. The text also includes a discussion of general object-oriented programming (OOP) principles which I find to be invaluable as it brings the topic of classes to life.

Exceptions are introduced and discussed in detail. The placement here is appropriate since exceptions are now objects in Python so classes had to be discussed first. This chapter should prove to be especially useful for people migrating from other languages that do not have simple, yet effective, exception-handling constructs.

Finally, four advanced topics are covered: decorators, Unicode, managed attributes, meta-classes. I find the first two to be absolutely necessary for almost any system nowadays, even small ones! The atter two are not as ubiquitous, but should be useful to more experienced programmers.

I should mention here that the discussion of the topics discussed above does not stop at the basics but provides comprehensive coverage. This is evident in the discussion of concepts such as dynamic typing, inheritance order, iterators, generators, comprehensions, and functional programming, among many others. There is even an interlude on documentation and the pydoc library.

Like many programming texts, the book uses small programming examples (appropriately executed in the Python interactive shell). The small examples hope to capture the essence of the topic at hand, and that, it does well within the limitations of a small-scale context. But this fourth edition adds a new chapter on classes (Chapter 27) that contains a more realistic code example presented in a tutorial format.

In addition to examples, each chapter ends with a summary of the chapter's content as well as a quiz on that content. The quiz is immediately followed by its answers for easy reference. I have to admit that I do not use any of these two features, so I will not be able to comment on their efficacy.

Like many O'Reilly books, this is a well-written, coherent, and beautifully type-set book. I highly recommend it to anyone who wants to, or already does, program using python. It should help the novice in the transition to an excellent programming language or, otherwise, make an already familiar environment more powerful in the hands of veterans.

Ahmed Al-Saadi is a Software Analyst who works for a Montreal Python house. He wrote his first lines of code on a Sinclair ZX Spectrum+, though unfortunately not in Python at the time.

You can purchase Learning Python, 4th Edition from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

thatpythonguy writes "Learning Python is a well-written book by an experienced Python trainer that has served the Python community well since the first edition was published in 1999. Now, at its fourth edition, this book by Mark Lutz arguably continues to be Python's bible." Read on for the rest of Ahmed's review. Learning Python, 4th Edition author Mark Lutz pages 1216 publisher O'Reilly Media rating 9/10 reviewer Ahmed Al-Saadi ISBN 0596158068 summary A hands-on book that will help you be productive with Python 3.0 quickly This book is addressed as an introductory text to programmers new to Python. Although people with no programming experience are not discouraged from reading it, they are warned that time is mostly spent teaching Python, not programming fundamentals. I agree with this picture, though from my own experience and those of others, the book is equally valuable to more experienced Python programmers both as a pseudo-reference and as an introduction to more advanced topics. The critical point here is that the book does not make assumptions about educational or vocational experiences and provides many examples; this renders the book approachable by a large audience.

Both Python 2.6 and 3.x are covered in this edition. However, the latest 3.x line is considered the reference from which variations in 2.6 are discussed when appropriate. This approach is logical; the new Python 3.x presents a major change to the language, but is not sufficiently dominant to warrant exclusive treatment.

This book discusses the Python language and excludes the Python standard and non-standard libraries. The latter are discussed in other places including Lutz's own Programming Python which stands at its third edition at the time of writing of this article. I find this division necessary because of size considerations and, in fact, this division did not exist in the first edition of the book! However, there is one topic that does not seem to fit the language/libraries divide, and that topic is packaging and deployment.

I will argue that there are not many (if any) books that discuss packaging and deployment of Python programs well. I will also argue that this topic should be included in the book being reviewed here since it is so essential to real Python programming. Since Lutz discusses the Python runtime environment, I do not think it detracts from the book's coherence to include a chapter on packaging.It is possible that the proliferation of various packaging and deployment options such as distutils, setuptools, pip, buildout, virtualenv, paver, fabric and others, is the reason for this exclusion. Or it could be that these tools are in a state of major flux that any text will become quickly outdated. If size is the reason for this exclusion, maybe Lutz or someone else can publish 'Packaing and Deploying Python' as a separate volume.

The book starts by building a case for the use of Python. Both the features of the language and its prominent users are discussed to build credibility. Then, the runtime environment is discussed: how to run programs in various ways on various operating systems and language interpreters.

Types and statements, which are at the core of any language, are discussed next. Notably, there is an excellent discussion of the topic of iterators and generators (also discussed in a later chapter). Functions, modules and classes are then introduced. The text also includes a discussion of general object-oriented programming (OOP) principles which I find to be invaluable as it brings the topic of classes to life.

Exceptions are introduced and discussed in detail. The placement here is appropriate since exceptions are now objects in Python so classes had to be discussed first. This chapter should prove to be especially useful for people migrating from other languages that do not have simple, yet effective, exception-handling constructs.

Finally, four advanced topics are covered: decorators, Unicode, managed attributes, meta-classes. I find the first two to be absolutely necessary for almost any system nowadays, even small ones! The atter two are not as ubiquitous, but should be useful to more experienced programmers.

I should mention here that the discussion of the topics discussed above does not stop at the basics but provides comprehensive coverage. This is evident in the discussion of concepts such as dynamic typing, inheritance order, iterators, generators, comprehensions, and functional programming, among many others. There is even an interlude on documentation and the pydoc library.

Like many programming texts, the book uses small programming examples (appropriately executed in the Python interactive shell). The small examples hope to capture the essence of the topic at hand, and that, it does well within the limitations of a small-scale context. But this fourth edition adds a new chapter on classes (Chapter 27) that contains a more realistic code example presented in a tutorial format.

In addition to examples, each chapter ends with a summary of the chapter's content as well as a quiz on that content. The quiz is immediately followed by its answers for easy reference. I have to admit that I do not use any of these two features, so I will not be able to comment on their efficacy.

Like many O'Reilly books, this is a well-written, coherent, and beautifully type-set book. I highly recommend it to anyone who wants to, or already does, program using python. It should help the novice in the transition to an excellent programming language or, otherwise, make an already familiar environment more powerful in the hands of veterans.

Ahmed Al-Saadi is a Software Analyst who works for a Montreal Python house. He wrote his first lines of code on a Sinclair ZX Spectrum+, though unfortunately not in Python at the time.

You can purchase Learning Python, 4th Edition from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Frequent Slashdot Contributor Bennett Haselton writes in "A federal judge rules that a student can seek attorney's fees against a high school principal who suspended her for a Facebook page she made at home. Good news, but how could the school have thought they had the right to punish her for that in the first place? Posing the question not rhetorically but seriously. What is the source of society's attitudes toward the free-speech rights of 17-year-olds?"

Well, you knew this post was coming when you read the news. A federal judge has ruled that Katie Evans, who had been suspended from high school for creating a Facebook group calling one of her teachers "the worst teacher I've ever met," can proceed with her suit seeking attorney's fees from her principal for violating her First Amendment rights. Evans, now a journalism student at the University of Florida, is represented in her suit by the ACLU of Florida.

If any of the recent student online free-speech cases should have been adjudicated in the student's favor, this would most clearly be the one. As Judge Barry Garber wrote in his ruling, Evans's page did not contain threats of violence (if it had, it would have been a matter for the police, not for a school punishment), and the principal didn't even find out about the page until two months after she took it down. It's hard to believe that the principal's lawyers, if he consulted with them, would have gone along with a recommendation to suspend the student. And once the Florida ACLU contacted the principal, wouldn't he have realized that the longer he fought the case, the more legal bills the ACLU would amass, along with the possibility that the principal could be ordered to pay them? Even if he had estimated that there would only be a 5% chance that he could end up being ordered to pay legal fees, was it worth the risk, if the fees could come to thousands or tens of thousands of dollars? Well, now he knows.

When a different judge ruled that a student had no right to challenge his suspension for making a vulgar Myspace page about his principal, I said that there was no more objective basis for saying that the ruling was legally "right" than it was "wrong," because if you put 10 judges in separate rooms and ask them how they would rule on the case, you could get 10 different, mutually contradictory answers. Well, fair is fair — even though I support Judge Garber's ruling 100%, I have to concede that it did not necessarily follow inevitably from the facts and the law, and there's no objective basis for calling it "the" right ruling. Judges are not like doctors who look at a mammogram, and draw on experience that the general public does not have, in order to see something that would be hidden from the rest of us. In cases like these, judges simply have multiple plausible interpretations in front of them, and they pick one. As such they're acting more like referees (who make a decision so that the game — or, in this case, society — can move on) than true "experts."

There is a temptation to think that there is some consistent reasoning behind the different courts' rulings — say, that the student who created a vulgar page mocking his principal (the student was identified in papers only as "J.S.") went too far and crossed a line, while Katie Evans's page complaining about her teacher was clean enough to stay on the safe side of the line, and make her eligible for damages in a First Amendment suit. This, I think, is nonsense, an attempt to put a consistent theory on top of a legal system that does not follow consistent rules from one court ruling to the next. If different judges had been randomly assigned to J.S.'s case and Evans's case, then it might have been J.S. who won and Evans who lost. After all, it was a federal judge who once ruled that a Utah high school had the right to suspend a student for wearing sweatshirts emblazoned with "Vegan" and "Vegans Have First Amendment Rights." (The judge and the principal had apparently confused veganism with eco-terrorism.) How do you reconcile that with any of the recent rulings? (No prizes for guessing how that judge would have ruled if the shirts had said "Christian.")

But even if it's still a roll of the dice how a court would rule in a particular student free-speech case, what matters from the point of view of a principal in a future case, are the potential payoffs. What if you're thinking about suspending a student for a non-threatening, non-libelous Facebook page? If the case ends up in court and you win, then you get the satisfaction of being "vindicated." But if you lose, you could be ordered to pay tens of thousands of dollars to the student's attorneys. So even a small number of victories for students in free-speech cases, even if mixed in with an equal or greater number of victories for the schools, still create an enormous incentive for a principal not to risk the case at all, when the potential gain is so small and the potential loss so huge. Even if you think there's only a 5% chance of being ordered to pay the student's $10,000 legal bill, that means you'd still have to decide if it's worth (on average) about $500 to get the satisfaction of suspending them.

(On the other hand, if a student created a page that was so threatening or libelous towards a staff member, that the school would run the risk of being sued if the principal didn't suspend the student, then the school and the principal are taking some legal risk either way, but the risk involved in suspending the student is much smaller. Fine — there's nothing wrong with suspending a student for threats of violence.)

So the ruling is a much more significant victory for student speech than many of the parties involved probably realize. Even though Judge Garber didn't actually award Evans her attorney's fees (yet?) — he only said that she could proceed to seek them against the principal — just the fact that it's coming dangerously close to that, means that principals in future cases now know what the risks are.

But why was all this necessary? How did the legal and societal climate of attitudes toward people under 18, lead to a principal thinking that he could punish a 17-year-old for comments that she made about a teacher, on her own time, to a third-party audience? If the students in the school had been comprised, not of minors, but of adults from some other minority group — African Americans, immigrant women, native Spanish speakers — there's no question that the principal never would have thought he could get away with suspending the student for criticizing a teacher.

Similarly, students at Harriton High School in Rosemont, Pennsylvania just discovered that school officials had given laptops to students to take home with remotely-activated webcams, that could be used to take photos in student's homes and transmit them back to school officials. Incredibly, this was discovered not by students or their parents examining the laptops, but because school officials used the feature to take a photo of a student in his bedroom, and then confronted him about "inappropriate" behavior, not considering that the students and their parents might consider it "inappropriate" that the school snuck spy cams into their bedrooms. (The school has issued a denial claiming, "At no time did any high school administrator have the ability or actually access the security-tracking software" — which doesn't seem to make sense, since the lawsuit was filed in the first place because the student was told by the assistant principal that the webcam had caught him engaging in "inappropriate behavior.") What was the school thinking? Probably, they were thinking, "These are minors, we can do what we want." If their student clientele had been comprised of adults, they never would have dreamed that they could confront a student about behavior in their room that they captured with a hidden camera. (Ironically, the school may end up in more trouble for spying on minors, as this editorial argues, since the school officials may now be guilty of recording and possessing child porn, depending on what the cameras "captured" in the students' rooms!)

So no matter how much ink is spilled analyzing the legal technicalities of suspending a 17-year-old student for off-campus speech, that's not what the case is really about. The case is really about attitudes. Change society's attitudes to think of 17-year-olds the way we currently think of 25-year-olds, and no judge is going to deny them their right to criticize their school on their own time, any more than a judge in today's society would deny that right to a 25-year-old.

And where does this attitude towards minors come from? I suspect that most people who believe that we have to draw the line somewhere around age 18, believe it for no better reason than because they were raised in a society where most other people believe it too. If you think that setting the cutoff age at 18 is just "common sense," then I would bet my house that if you had been raised in a society where the cutoff age was set at 13, that would seem like "just common sense" to you as well, and similarly if you had been raised in a society where the cutoff had been set at 22. This may seem like an unremarkable observation, but my belief in minors' rights has always been motivated by a more fundamental belief that you should not believe things merely because most people in your society believe them. If that sounds like a trite platitude, consider how few people in the US seem to question the rule that you can show a man's chest on television but not a woman's chest. In more liberal Denmark, supermarkets can stock tabloids at toddler-eye-level with photos of topless women on the cover, while in Saudi Arabia, adult women can't leave the house without covering their faces, and in all three societies, the majority thinks these regulations are just plain "common sense." Is the age of majority just another arbitrary illusion caused by the power of consensus?

When I said this on The David Lawrence Show, the host made the thoughtful observation that most countries all over the world set the age of majority for most purposes at 18. Close, I said, but it doesn't quite prove what it seems to prove, because those globally diverse societies did not reach that conclusion independently — they move in similar directions because of cross-cultural influences. (The voting age was set at 21 in many democracies before many of them lowered it to 18 in the 1970's within a few years of each other.) To get a better sense of whether there is any merit to the idea, we'd have to do something like the "putting the 10 judges in 10 separate rooms" test — put 10 different societies in mutual isolation from each other, let them develop and debate things on their own, and see if all or most of them reach the conclusion that 18 us a good cutoff age for adulthood.

The idea that actual children — under the age of, say, 11 — are qualitatively different from adults, has in fact been re-discovered by civilizations that developed independently at different points in history, all over the world. So there's probably something to it. The idea that teenagers are qualitatively different from adults, is something particular to recent history, and a wise person transported forward in time from the 1500's to the present day might scratch their heads and wonder why we think that 18-year-olds should be allowed to criticize their teachers but 17-year-olds cannot. I suspect the artificial extension of childhood grew out of the fact that because modern jobs are more complicated than they used to be, we need more years of schooling before we can go out and compete in the workforce. The fallacy there, though, is that just because we need more years of schooling, doesn't mean that the natural age of "human maturity" has gone up. So we end up with 17-year-olds having to go to court to establish their right to criticize their teachers on their own time.

Judge Garber wouldn't have been in a position to make this argument in his ruling even if he agreed with it. But even if his ruling was based on logic that has nothing to do with the underlying case for minors' rights, it was still a step in the right direction.

Frequent Slashdot Contributor Bennett Haselton writes in "A federal judge rules that a student can seek attorney's fees against a high school principal who suspended her for a Facebook page she made at home. Good news, but how could the school have thought they had the right to punish her for that in the first place? Posing the question not rhetorically but seriously. What is the source of society's attitudes toward the free-speech rights of 17-year-olds?"

Well, you knew this post was coming when you read the news. A federal judge has ruled that Katie Evans, who had been suspended from high school for creating a Facebook group calling one of her teachers "the worst teacher I've ever met," can proceed with her suit seeking attorney's fees from her principal for violating her First Amendment rights. Evans, now a journalism student at the University of Florida, is represented in her suit by the ACLU of Florida.

If any of the recent student online free-speech cases should have been adjudicated in the student's favor, this would most clearly be the one. As Judge Barry Garber wrote in his ruling, Evans's page did not contain threats of violence (if it had, it would have been a matter for the police, not for a school punishment), and the principal didn't even find out about the page until two months after she took it down. It's hard to believe that the principal's lawyers, if he consulted with them, would have gone along with a recommendation to suspend the student. And once the Florida ACLU contacted the principal, wouldn't he have realized that the longer he fought the case, the more legal bills the ACLU would amass, along with the possibility that the principal could be ordered to pay them? Even if he had estimated that there would only be a 5% chance that he could end up being ordered to pay legal fees, was it worth the risk, if the fees could come to thousands or tens of thousands of dollars? Well, now he knows.

When a different judge ruled that a student had no right to challenge his suspension for making a vulgar Myspace page about his principal, I said that there was no more objective basis for saying that the ruling was legally "right" than it was "wrong," because if you put 10 judges in separate rooms and ask them how they would rule on the case, you could get 10 different, mutually contradictory answers. Well, fair is fair — even though I support Judge Garber's ruling 100%, I have to concede that it did not necessarily follow inevitably from the facts and the law, and there's no objective basis for calling it "the" right ruling. Judges are not like doctors who look at a mammogram, and draw on experience that the general public does not have, in order to see something that would be hidden from the rest of us. In cases like these, judges simply have multiple plausible interpretations in front of them, and they pick one. As such they're acting more like referees (who make a decision so that the game — or, in this case, society — can move on) than true "experts."

There is a temptation to think that there is some consistent reasoning behind the different courts' rulings — say, that the student who created a vulgar page mocking his principal (the student was identified in papers only as "J.S.") went too far and crossed a line, while Katie Evans's page complaining about her teacher was clean enough to stay on the safe side of the line, and make her eligible for damages in a First Amendment suit. This, I think, is nonsense, an attempt to put a consistent theory on top of a legal system that does not follow consistent rules from one court ruling to the next. If different judges had been randomly assigned to J.S.'s case and Evans's case, then it might have been J.S. who won and Evans who lost. After all, it was a federal judge who once ruled that a Utah high school had the right to suspend a student for wearing sweatshirts emblazoned with "Vegan" and "Vegans Have First Amendment Rights." (The judge and the principal had apparently confused veganism with eco-terrorism.) How do you reconcile that with any of the recent rulings? (No prizes for guessing how that judge would have ruled if the shirts had said "Christian.")

But even if it's still a roll of the dice how a court would rule in a particular student free-speech case, what matters from the point of view of a principal in a future case, are the potential payoffs. What if you're thinking about suspending a student for a non-threatening, non-libelous Facebook page? If the case ends up in court and you win, then you get the satisfaction of being "vindicated." But if you lose, you could be ordered to pay tens of thousands of dollars to the student's attorneys. So even a small number of victories for students in free-speech cases, even if mixed in with an equal or greater number of victories for the schools, still create an enormous incentive for a principal not to risk the case at all, when the potential gain is so small and the potential loss so huge. Even if you think there's only a 5% chance of being ordered to pay the student's $10,000 legal bill, that means you'd still have to decide if it's worth (on average) about $500 to get the satisfaction of suspending them.

(On the other hand, if a student created a page that was so threatening or libelous towards a staff member, that the school would run the risk of being sued if the principal didn't suspend the student, then the school and the principal are taking some legal risk either way, but the risk involved in suspending the student is much smaller. Fine — there's nothing wrong with suspending a student for threats of violence.)

So the ruling is a much more significant victory for student speech than many of the parties involved probably realize. Even though Judge Garber didn't actually award Evans her attorney's fees (yet?) — he only said that she could proceed to seek them against the principal — just the fact that it's coming dangerously close to that, means that principals in future cases now know what the risks are.

But why was all this necessary? How did the legal and societal climate of attitudes toward people under 18, lead to a principal thinking that he could punish a 17-year-old for comments that she made about a teacher, on her own time, to a third-party audience? If the students in the school had been comprised, not of minors, but of adults from some other minority group — African Americans, immigrant women, native Spanish speakers — there's no question that the principal never would have thought he could get away with suspending the student for criticizing a teacher.

Similarly, students at Harriton High School in Rosemont, Pennsylvania just discovered that school officials had given laptops to students to take home with remotely-activated webcams, that could be used to take photos in student's homes and transmit them back to school officials. Incredibly, this was discovered not by students or their parents examining the laptops, but because school officials used the feature to take a photo of a student in his bedroom, and then confronted him about "inappropriate" behavior, not considering that the students and their parents might consider it "inappropriate" that the school snuck spy cams into their bedrooms. (The school has issued a denial claiming, "At no time did any high school administrator have the ability or actually access the security-tracking software" — which doesn't seem to make sense, since the lawsuit was filed in the first place because the student was told by the assistant principal that the webcam had caught him engaging in "inappropriate behavior.") What was the school thinking? Probably, they were thinking, "These are minors, we can do what we want." If their student clientele had been comprised of adults, they never would have dreamed that they could confront a student about behavior in their room that they captured with a hidden camera. (Ironically, the school may end up in more trouble for spying on minors, as this editorial argues, since the school officials may now be guilty of recording and possessing child porn, depending on what the cameras "captured" in the students' rooms!)

So no matter how much ink is spilled analyzing the legal technicalities of suspending a 17-year-old student for off-campus speech, that's not what the case is really about. The case is really about attitudes. Change society's attitudes to think of 17-year-olds the way we currently think of 25-year-olds, and no judge is going to deny them their right to criticize their school on their own time, any more than a judge in today's society would deny that right to a 25-year-old.

And where does this attitude towards minors come from? I suspect that most people who believe that we have to draw the line somewhere around age 18, believe it for no better reason than because they were raised in a society where most other people believe it too. If you think that setting the cutoff age at 18 is just "common sense," then I would bet my house that if you had been raised in a society where the cutoff age was set at 13, that would seem like "just common sense" to you as well, and similarly if you had been raised in a society where the cutoff had been set at 22. This may seem like an unremarkable observation, but my belief in minors' rights has always been motivated by a more fundamental belief that you should not believe things merely because most people in your society believe them. If that sounds like a trite platitude, consider how few people in the US seem to question the rule that you can show a man's chest on television but not a woman's chest. In more liberal Denmark, supermarkets can stock tabloids at toddler-eye-level with photos of topless women on the cover, while in Saudi Arabia, adult women can't leave the house without covering their faces, and in all three societies, the majority thinks these regulations are just plain "common sense." Is the age of majority just another arbitrary illusion caused by the power of consensus?

When I said this on The David Lawrence Show, the host made the thoughtful observation that most countries all over the world set the age of majority for most purposes at 18. Close, I said, but it doesn't quite prove what it seems to prove, because those globally diverse societies did not reach that conclusion independently — they move in similar directions because of cross-cultural influences. (The voting age was set at 21 in many democracies before many of them lowered it to 18 in the 1970's within a few years of each other.) To get a better sense of whether there is any merit to the idea, we'd have to do something like the "putting the 10 judges in 10 separate rooms" test — put 10 different societies in mutual isolation from each other, let them develop and debate things on their own, and see if all or most of them reach the conclusion that 18 us a good cutoff age for adulthood.

The idea that actual children — under the age of, say, 11 — are qualitatively different from adults, has in fact been re-discovered by civilizations that developed independently at different points in history, all over the world. So there's probably something to it. The idea that teenagers are qualitatively different from adults, is something particular to recent history, and a wise person transported forward in time from the 1500's to the present day might scratch their heads and wonder why we think that 18-year-olds should be allowed to criticize their teachers but 17-year-olds cannot. I suspect the artificial extension of childhood grew out of the fact that because modern jobs are more complicated than they used to be, we need more years of schooling before we can go out and compete in the workforce. The fallacy there, though, is that just because we need more years of schooling, doesn't mean that the natural age of "human maturity" has gone up. So we end up with 17-year-olds having to go to court to establish their right to criticize their teachers on their own time.

Judge Garber wouldn't have been in a position to make this argument in his ruling even if he agreed with it. But even if his ruling was based on logic that has nothing to do with the underlying case for minors' rights, it was still a step in the right direction.

Frequent Slashdot Contributor Bennett Haselton writes in "A federal judge rules that a student can seek attorney's fees against a high school principal who suspended her for a Facebook page she made at home. Good news, but how could the school have thought they had the right to punish her for that in the first place? Posing the question not rhetorically but seriously. What is the source of society's attitudes toward the free-speech rights of 17-year-olds?"

Well, you knew this post was coming when you read the news. A federal judge has ruled that Katie Evans, who had been suspended from high school for creating a Facebook group calling one of her teachers "the worst teacher I've ever met," can proceed with her suit seeking attorney's fees from her principal for violating her First Amendment rights. Evans, now a journalism student at the University of Florida, is represented in her suit by the ACLU of Florida.

If any of the recent student online free-speech cases should have been adjudicated in the student's favor, this would most clearly be the one. As Judge Barry Garber wrote in his ruling, Evans's page did not contain threats of violence (if it had, it would have been a matter for the police, not for a school punishment), and the principal didn't even find out about the page until two months after she took it down. It's hard to believe that the principal's lawyers, if he consulted with them, would have gone along with a recommendation to suspend the student. And once the Florida ACLU contacted the principal, wouldn't he have realized that the longer he fought the case, the more legal bills the ACLU would amass, along with the possibility that the principal could be ordered to pay them? Even if he had estimated that there would only be a 5% chance that he could end up being ordered to pay legal fees, was it worth the risk, if the fees could come to thousands or tens of thousands of dollars? Well, now he knows.

When a different judge ruled that a student had no right to challenge his suspension for making a vulgar Myspace page about his principal, I said that there was no more objective basis for saying that the ruling was legally "right" than it was "wrong," because if you put 10 judges in separate rooms and ask them how they would rule on the case, you could get 10 different, mutually contradictory answers. Well, fair is fair — even though I support Judge Garber's ruling 100%, I have to concede that it did not necessarily follow inevitably from the facts and the law, and there's no objective basis for calling it "the" right ruling. Judges are not like doctors who look at a mammogram, and draw on experience that the general public does not have, in order to see something that would be hidden from the rest of us. In cases like these, judges simply have multiple plausible interpretations in front of them, and they pick one. As such they're acting more like referees (who make a decision so that the game — or, in this case, society — can move on) than true "experts."

There is a temptation to think that there is some consistent reasoning behind the different courts' rulings — say, that the student who created a vulgar page mocking his principal (the student was identified in papers only as "J.S.") went too far and crossed a line, while Katie Evans's page complaining about her teacher was clean enough to stay on the safe side of the line, and make her eligible for damages in a First Amendment suit. This, I think, is nonsense, an attempt to put a consistent theory on top of a legal system that does not follow consistent rules from one court ruling to the next. If different judges had been randomly assigned to J.S.'s case and Evans's case, then it might have been J.S. who won and Evans who lost. After all, it was a federal judge who once ruled that a Utah high school had the right to suspend a student for wearing sweatshirts emblazoned with "Vegan" and "Vegans Have First Amendment Rights." (The judge and the principal had apparently confused veganism with eco-terrorism.) How do you reconcile that with any of the recent rulings? (No prizes for guessing how that judge would have ruled if the shirts had said "Christian.")

But even if it's still a roll of the dice how a court would rule in a particular student free-speech case, what matters from the point of view of a principal in a future case, are the potential payoffs. What if you're thinking about suspending a student for a non-threatening, non-libelous Facebook page? If the case ends up in court and you win, then you get the satisfaction of being "vindicated." But if you lose, you could be ordered to pay tens of thousands of dollars to the student's attorneys. So even a small number of victories for students in free-speech cases, even if mixed in with an equal or greater number of victories for the schools, still create an enormous incentive for a principal not to risk the case at all, when the potential gain is so small and the potential loss so huge. Even if you think there's only a 5% chance of being ordered to pay the student's $10,000 legal bill, that means you'd still have to decide if it's worth (on average) about $500 to get the satisfaction of suspending them.

(On the other hand, if a student created a page that was so threatening or libelous towards a staff member, that the school would run the risk of being sued if the principal didn't suspend the student, then the school and the principal are taking some legal risk either way, but the risk involved in suspending the student is much smaller. Fine — there's nothing wrong with suspending a student for threats of violence.)

So the ruling is a much more significant victory for student speech than many of the parties involved probably realize. Even though Judge Garber didn't actually award Evans her attorney's fees (yet?) — he only said that she could proceed to seek them against the principal — just the fact that it's coming dangerously close to that, means that principals in future cases now know what the risks are.

But why was all this necessary? How did the legal and societal climate of attitudes toward people under 18, lead to a principal thinking that he could punish a 17-year-old for comments that she made about a teacher, on her own time, to a third-party audience? If the students in the school had been comprised, not of minors, but of adults from some other minority group — African Americans, immigrant women, native Spanish speakers — there's no question that the principal never would have thought he could get away with suspending the student for criticizing a teacher.

Similarly, students at Harriton High School in Rosemont, Pennsylvania just discovered that school officials had given laptops to students to take home with remotely-activated webcams, that could be used to take photos in student's homes and transmit them back to school officials. Incredibly, this was discovered not by students or their parents examining the laptops, but because school officials used the feature to take a photo of a student in his bedroom, and then confronted him about "inappropriate" behavior, not considering that the students and their parents might consider it "inappropriate" that the school snuck spy cams into their bedrooms. (The school has issued a denial claiming, "At no time did any high school administrator have the ability or actually access the security-tracking software" — which doesn't seem to make sense, since the lawsuit was filed in the first place because the student was told by the assistant principal that the webcam had caught him engaging in "inappropriate behavior.") What was the school thinking? Probably, they were thinking, "These are minors, we can do what we want." If their student clientele had been comprised of adults, they never would have dreamed that they could confront a student about behavior in their room that they captured with a hidden camera. (Ironically, the school may end up in more trouble for spying on minors, as this editorial argues, since the school officials may now be guilty of recording and possessing child porn, depending on what the cameras "captured" in the students' rooms!)

So no matter how much ink is spilled analyzing the legal technicalities of suspending a 17-year-old student for off-campus speech, that's not what the case is really about. The case is really about attitudes. Change society's attitudes to think of 17-year-olds the way we currently think of 25-year-olds, and no judge is going to deny them their right to criticize their school on their own time, any more than a judge in today's society would deny that right to a 25-year-old.

And where does this attitude towards minors come from? I suspect that most people who believe that we have to draw the line somewhere around age 18, believe it for no better reason than because they were raised in a society where most other people believe it too. If you think that setting the cutoff age at 18 is just "common sense," then I would bet my house that if you had been raised in a society where the cutoff age was set at 13, that would seem like "just common sense" to you as well, and similarly if you had been raised in a society where the cutoff had been set at 22. This may seem like an unremarkable observation, but my belief in minors' rights has always been motivated by a more fundamental belief that you should not believe things merely because most people in your society believe them. If that sounds like a trite platitude, consider how few people in the US seem to question the rule that you can show a man's chest on television but not a woman's chest. In more liberal Denmark, supermarkets can stock tabloids at toddler-eye-level with photos of topless women on the cover, while in Saudi Arabia, adult women can't leave the house without covering their faces, and in all three societies, the majority thinks these regulations are just plain "common sense." Is the age of majority just another arbitrary illusion caused by the power of consensus?

When I said this on The David Lawrence Show, the host made the thoughtful observation that most countries all over the world set the age of majority for most purposes at 18. Close, I said, but it doesn't quite prove what it seems to prove, because those globally diverse societies did not reach that conclusion independently — they move in similar directions because of cross-cultural influences. (The voting age was set at 21 in many democracies before many of them lowered it to 18 in the 1970's within a few years of each other.) To get a better sense of whether there is any merit to the idea, we'd have to do something like the "putting the 10 judges in 10 separate rooms" test — put 10 different societies in mutual isolation from each other, let them develop and debate things on their own, and see if all or most of them reach the conclusion that 18 us a good cutoff age for adulthood.

The idea that actual children — under the age of, say, 11 — are qualitatively different from adults, has in fact been re-discovered by civilizations that developed independently at different points in history, all over the world. So there's probably something to it. The idea that teenagers are qualitatively different from adults, is something particular to recent history, and a wise person transported forward in time from the 1500's to the present day might scratch their heads and wonder why we think that 18-year-olds should be allowed to criticize their teachers but 17-year-olds cannot. I suspect the artificial extension of childhood grew out of the fact that because modern jobs are more complicated than they used to be, we need more years of schooling before we can go out and compete in the workforce. The fallacy there, though, is that just because we need more years of schooling, doesn't mean that the natural age of "human maturity" has gone up. So we end up with 17-year-olds having to go to court to establish their right to criticize their teachers on their own time.

Judge Garber wouldn't have been in a position to make this argument in his ruling even if he agreed with it. But even if his ruling was based on logic that has nothing to do with the underlying case for minors' rights, it was still a step in the right direction.

v1x writes "I have had an account with my current web hosting company for a few years, with 3 domains being hosted there (using Linux/PHP/MySQL). Recently, all three of these websites stopped functioning, and upon checking the site, all my directory structures were intact, whereas all of the files were gone. Upon contacting their technical support, I was given the run-around, and later informed by one of their administrators that none of the files could be restored. Needless to say that I am looking for a different web hosting company at this point, but I would like to make a more informed choice than I did with the current company. I have read a similar Slashdot article (from 2005) on the topic, but the questions posed there were slightly different." Reader mrstrano has a similar question: "I am developing a web application and, after registering the domain, I am now looking for a suitable web hosting provider. It should be cheap enough so I can start small, but should allow me to scale up if the web site is successful (as I hope). The idea is simple enough so I do not need other investors to implement it. This also means that I don't have a lot of money to put on it at the moment. Users of the website will post their pictures (no, it's not going to be a porn website), so scalability might be an issue even with a moderately high number of users. I would like to find a good web hosting provider from day one, so I don't have to go through the pain of a data migration. Which web host would you choose?"

A few days ago, we ran word of a report alleging that Windows 7 consumed more memory than it should, based on a report from Devil Mountain Software; a followup post linked to Ars Technica's robust deconstruction of that claim. Now the story gets weird: Fred Flowers writes The original story quoted the company's CTO, Craig Barth on the issue. Now, InfoWorld editor in chief Eric Knorr has still more to add. From Knorr's blog at InfoWorld.com: 'On Friday, Feb. 19, we discovered that one of our contributors, Randall C. Kennedy, had been misrepresenting himself to other media organizations as Craig Barth, CTO of Devil Mountain Software (aka exo.performance.network), in interviews for a number of stories regarding Windows and other Microsoft software topics. ... There is no Craig Barth.' Knorr's post goes on to say that Kennedy has been fired from his blogging gig at InfoWorld over this 'serious breach of trust,' and that his blog will be removed."

A few days ago, we ran word of a report alleging that Windows 7 consumed more memory than it should, based on a report from Devil Mountain Software; a followup post linked to Ars Technica's robust deconstruction of that claim. Now the story gets weird: Fred Flowers writes The original story quoted the company's CTO, Craig Barth on the issue. Now, InfoWorld editor in chief Eric Knorr has still more to add. From Knorr's blog at InfoWorld.com: 'On Friday, Feb. 19, we discovered that one of our contributors, Randall C. Kennedy, had been misrepresenting himself to other media organizations as Craig Barth, CTO of Devil Mountain Software (aka exo.performance.network), in interviews for a number of stories regarding Windows and other Microsoft software topics. ... There is no Craig Barth.' Knorr's post goes on to say that Kennedy has been fired from his blogging gig at InfoWorld over this 'serious breach of trust,' and that his blog will be removed."

tekgoblin writes "The Lower Merion School District of Pennsylvania was recently accused of privacy invasion. Now the school has released an official response to the allegations. According to the school, the security feature was installed in the laptops as an anti-theft device and was not intended to invade privacy. The software that was installed would take a photo of the person using the laptop after it was stolen to give to the authorities. Now this may be what it was intended for, but it seems that someone didn't get the memo." The district's claim that it "has not used the tracking feature or web cam for any other purpose or in any other manner whatsoever" doesn't square with the allegations which set off this whole storm. And if there was nothing wrong with it, why does the school say it won't start using the snooping feature again without "express written notification to all students and families"?

Via newsycombinator comes a reaction at Ars Technica to the recently reported claims of excessive memory use on machines running Windows 7. From the article: "I installed the XPnet performance monitoring tool and waited for it to upload my data to see what it might be complaining about. The cause of the problem was immediately apparent. It's no secret that Windows 7, just like Windows Vista before it, includes aggressive disk caching. The SuperFetch technology causes Windows to preload certain data if the OS detects that it is used regularly, even if there is no specific need for it at any given moment. Though SuperFetch is a little less aggressive in Windows 7, it will still use a substantial amount of memory—but with an important proviso. The OS will only use memory for cache when there is no other demand for that memory."

MikeChino sends along this awe-inspiring excerpt: "Think claims of electric vehicles that get over 200 MPG are impressive? Try this on for size: a group of mechanical engineering students at Cal Poly have developed a vehicle that can get up to 2752.3 MPG — and it doesn't even use batteries. The Cal Poly Supermileage Team's wondercar, dubbed the Black Widow, has been under construction since 2005. The 96 pound car has three wheels, a drag coefficient of 0.12, a top speed of 30 MPH, and a modified 3 horsepower Honda 50cc four-stroke engine. It originally clocked in at 861 MPG and has been continuously tweaked to achieve the mileage we see today." It's not quite as street-worthy, though, as Volkswagen's 235 MPG One-Liter concept. Updated 20:01 GMT: The Cal Poly car's earlier incarnation achieved 861 MPG, not MPH; corrected above.

rjch writes "After its recent win against mod chip piracy in the Australian Federal courts, Nintendo is now on the prowl for other companies to sue. 'Nintendo will pursue those who attempt to jeopardise the gaming industry by using all means available to it under the law. In particular, Nintendo is currently contemplating bringing further actions against other sellers of game copying devices in Australia.' The game company said since 2008 it had pursued over 800 actions in 16 countries to stop game piracy, confiscating 'well over' half a million game copiers for the Nintendo DS. The company said piracy affected sales, the price of video games, and employment in the video game industry." Reader daria42 sends in a related piece asking whether Nintendo is being too harsh over this and the recent $1.5 million settlement with a man who leaked New Super Mario Bros. Wii.

rjch writes "After its recent win against mod chip piracy in the Australian Federal courts, Nintendo is now on the prowl for other companies to sue. 'Nintendo will pursue those who attempt to jeopardise the gaming industry by using all means available to it under the law. In particular, Nintendo is currently contemplating bringing further actions against other sellers of game copying devices in Australia.' The game company said since 2008 it had pursued over 800 actions in 16 countries to stop game piracy, confiscating 'well over' half a million game copiers for the Nintendo DS. The company said piracy affected sales, the price of video games, and employment in the video game industry." Reader daria42 sends in a related piece asking whether Nintendo is being too harsh over this and the recent $1.5 million settlement with a man who leaked New Super Mario Bros. Wii.

On Thursday we discussed news that a Pennsylvania high school was spying on students through the webcams in laptops that were issued to the students. The FBI is now taking an interest in the case, investigating whether federal wiretap and computer-intrusion laws were violated in the process. "The FBI opened its investigation after news of the suit broke on Thursday, the law-enforcement official said. Montgomery County District Attorney Risa Vetri Ferman may also investigate, she said Friday." Ferman said her office is "looking to see whether there are potential violations of Pennsylvania criminal laws."

angry tapir writes "French lawmakers have voted to approve a draft law to filter Internet traffic that Slashdot previously discussed. The government says the measure is intended to catch child pornographers. The Senate, where the government has a majority, will soon give the bill a second reading. If the Senate makes no amendments to the text, that will also be its final reading, as the government has declared the bill 'urgent,' a procedural move that reduces the usual cycle of four readings to two."

schliz writes "The Federal Court has ordered an Australian distributor to pay Nintendo over half a million dollars for selling the R4 mod chip, which allows users to circumvent technology protection measures in Nintendo's DS consoles. The distributor, RSJ IT Solutions, has been ordered to cease selling the chip through its gadgetgear.com.au site and any other sites it controls, as well as paying Nintendo $520,000 in damages."

A few weeks ago we discussed news of Ubisoft's DRM plans for future games, which reportedly went so far as to require a constant net connection, terminating your game if you get disconnected for any reason. Well, it's here; upon playing review copies of the PC version of Assassin's Creed 2 and Settlers VII, PCGamer found the DRM just as annoying as you might expect. Quoting: "If you get disconnected while playing, you're booted out of the game. All your progress since the last checkpoint or savegame is lost, and your only options are to quit to Windows or wait until you're reconnected. The game first starts the Ubisoft Game Launcher, which checks for updates. If you try to launch the game when you're not online, you hit an error message right away. So I tried a different test: start the game while online, play a little, then unplug my net cable. This is the same as what happens if your net connection drops momentarily, your router is rebooted, or the game loses its connection to Ubisoft's 'Master servers.' The game stopped, and I was dumped back to a menu screen — all my progress since it last autosaved was lost."

At his Freedom to Tinker blog, Ed Felten has a thoughtful, accessible piece on the debate at Mozilla about whether Firefox, by default, should trust a Chinese certificate authority (as it has since October). Felten explains in clear language why this is significant, and therefore controversial. An excerpt: "To see why this is worrisome, let's suppose, just for the sake of argument, that CNNIC were a puppet of the Chinese government. Then CNNIC's status as a trusted CA would give it the technical power to let the Chinese government spy on its citizens' 'secure' web connections. If a Chinese citizen tried to make a secure connection to Gmail, their connection could be directed to an impostor Gmail site run by the Chinese government, and CNNIC could give the impostor a cert saying that the government impostor was the real Gmail site."

An anonymous reader writes with word that the outcome of the large-scale cyberattack simulation promised a few days ago isn't too rosy. From the Help Net Security article: "During the simulated cyber attack that took place yesterday in Washington and was recorded by CNN, one thing became clear: the US are still not ready to deflect or mitigate such an attack to an extent that would not affect considerably the everyday life of its citizens. The ballroom of the Washington's Mandarin Oriental Hotel was for this event transformed into the White House Situation Room, complete with three video screens displaying maps of the country, simulated updates and broadcasts by 'GNN,' an imaginary television network 'covering' the crisis."

terrywallwork writes "Things have been moving along lately on the Blender 3D book front; a friend of mine informed me that Allan Brito released a new book called Blender 3D 2.49 Incredible Machines. I had previously reviewed one of Allan Brito's other books Blender 3D — Architecture, Buildings and Scenery, which covered the Architectural Visualization side of using Blender 3D. This new book takes a very different approach to teaching the use of Blender 2.49. It does this by taking the reader through the modeling, texturing and lighting of 3 different objects, those objects being: a futuristic gun, a futuristic spaceship (steam-punk styled) and finally a robot. Read below for the rest of Terry's review. Blender 2.49 3D Incredible Machines author Allan Brito pages 316 publisher Packt Publishing rating 7 reviewer Terry Wallwork ISBN 1847197469 summary Blender 3D book on the processes of studio model creation and display with various external renders. The introduction in the book states that the reader requires no previous experience of Blender to make use of the book. However further on in the book it is said that the book is not a beginners book and that many things will not be described in detail as the reader is expected to know the basics of how to use Blender in terms of its interface and various buttons and keypresses. After having read the entire book I would say that a beginning Blender user would be able to understand most of the book as most of the time things such as key presses and the basics of how to use Blender are explained in a way a new user to Blender would be able to follow.

The book is organized so as to be read from cover to cover and slowly progress from easy tasks to harder tasks. If you have some intermediate experience with Blender then I think the progression is well graded and will help the reader to quickly progress through the book. If you are a complete beginner some sections of the text will get a little confusing at times but with a bit of re-reading they should be understandable.

One thing that I did notice right away was the awful grammar of the text. This is most likely because English is not Allan Brito native language. Sometimes the grammar issues get in the way of understanding what task he is trying to accomplish. This does not happen often but I did find myself re-reading paragraphs to get his meaning. Now it is important to point out that I am not blaming Mr Brito for the grammar issue, the editors of the book however should have a serious talking to.

I bought the ebook version and that is what I am using to base this review on, this caused me a slight problem because the ebook mentioned some resources and graphics that were available to download from the Packt site, however on going to site the resources are not available for download (yet). As luck would have it though the EBook PDF file had good screen shots and so I was able to copy the resources directly from my PDF reader. Hopefully the site will be updated to have the resources available from the book.
I am also pleased that packt publishing has removed password protection and you can copy and select parts out of the ebook. They do however plaster your address on every page border which is irksome and if i was a pirate I could remove it easily but still they are heading in the right direction.

The book tries to present the production of the various objects in a way that is similar to how it would be done in a real production studio. While this may help give a glimpse to Blender newbies about how things are done in a real studio, to be honest those that know more than the basics will know that a lot of steps are missing that would be in a real studio setup.

With a few glaring exceptions most of the vital areas of Blender are covered in just enough detail for the information to be useful to a beginner and a memory jogger for a Blender user with some experience. Notable things that were missing from the book were any kind of use of Blender Compositing features, while this is surprising given the aim of the book, there was really no choice given the page count.

Given what was just said above, what was surprising was some of the topics that were covered, specifically the use of external renders such as Yaf(a)Ray and LuxRender. The book goes into a fair bit of detail on setting up Blender so as to use the external renderers. You won't be a Yaf(a)Ray or LuxRender guru but it gives enough to get you going. I am a Linux Fedora user and had to compile my version of the Renders from source and the book does not cover this, so if you in this position you are out of luck. There is a nice description of progressive renders and how they are different from more traditional rendering systems.

So all in all this is a passable book, useful for the info on External Renders and as a memory jogger for an experienced Blender user.

You can purchase Blender 3D 2.49 Incredible Machines from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

terrywallwork writes "Things have been moving along lately on the Blender 3D book front; a friend of mine informed me that Allan Brito released a new book called Blender 3D 2.49 Incredible Machines. I had previously reviewed one of Allan Brito's other books Blender 3D — Architecture, Buildings and Scenery, which covered the Architectural Visualization side of using Blender 3D. This new book takes a very different approach to teaching the use of Blender 2.49. It does this by taking the reader through the modeling, texturing and lighting of 3 different objects, those objects being: a futuristic gun, a futuristic spaceship (steam-punk styled) and finally a robot. Read below for the rest of Terry's review. Blender 2.49 3D Incredible Machines author Allan Brito pages 316 publisher Packt Publishing rating 7 reviewer Terry Wallwork ISBN 1847197469 summary Blender 3D book on the processes of studio model creation and display with various external renders. The introduction in the book states that the reader requires no previous experience of Blender to make use of the book. However further on in the book it is said that the book is not a beginners book and that many things will not be described in detail as the reader is expected to know the basics of how to use Blender in terms of its interface and various buttons and keypresses. After having read the entire book I would say that a beginning Blender user would be able to understand most of the book as most of the time things such as key presses and the basics of how to use Blender are explained in a way a new user to Blender would be able to follow.

The book is organized so as to be read from cover to cover and slowly progress from easy tasks to harder tasks. If you have some intermediate experience with Blender then I think the progression is well graded and will help the reader to quickly progress through the book. If you are a complete beginner some sections of the text will get a little confusing at times but with a bit of re-reading they should be understandable.

One thing that I did notice right away was the awful grammar of the text. This is most likely because English is not Allan Brito native language. Sometimes the grammar issues get in the way of understanding what task he is trying to accomplish. This does not happen often but I did find myself re-reading paragraphs to get his meaning. Now it is important to point out that I am not blaming Mr Brito for the grammar issue, the editors of the book however should have a serious talking to.

I bought the ebook version and that is what I am using to base this review on, this caused me a slight problem because the ebook mentioned some resources and graphics that were available to download from the Packt site, however on going to site the resources are not available for download (yet). As luck would have it though the EBook PDF file had good screen shots and so I was able to copy the resources directly from my PDF reader. Hopefully the site will be updated to have the resources available from the book.
I am also pleased that packt publishing has removed password protection and you can copy and select parts out of the ebook. They do however plaster your address on every page border which is irksome and if i was a pirate I could remove it easily but still they are heading in the right direction.

The book tries to present the production of the various objects in a way that is similar to how it would be done in a real production studio. While this may help give a glimpse to Blender newbies about how things are done in a real studio, to be honest those that know more than the basics will know that a lot of steps are missing that would be in a real studio setup.

With a few glaring exceptions most of the vital areas of Blender are covered in just enough detail for the information to be useful to a beginner and a memory jogger for a Blender user with some experience. Notable things that were missing from the book were any kind of use of Blender Compositing features, while this is surprising given the aim of the book, there was really no choice given the page count.

Given what was just said above, what was surprising was some of the topics that were covered, specifically the use of external renders such as Yaf(a)Ray and LuxRender. The book goes into a fair bit of detail on setting up Blender so as to use the external renderers. You won't be a Yaf(a)Ray or LuxRender guru but it gives enough to get you going. I am a Linux Fedora user and had to compile my version of the Renders from source and the book does not cover this, so if you in this position you are out of luck. There is a nice description of progressive renders and how they are different from more traditional rendering systems.

So all in all this is a passable book, useful for the info on External Renders and as a memory jogger for an experienced Blender user.

You can purchase Blender 3D 2.49 Incredible Machines from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.