Slashdot Mirror

Michael J. Ross writes "Like all major programming languages, JavaScript can be extended in functionality through the use of libraries, such as jQuery, which is currently seeing tremendous popularity and enhancement in the Web development community. Designers and developers who want to learn how to use jQuery for creating rich user interfaces through client-side JavaScript are advised to begin their journey to jQuery proficiency by reading one of the many books dedicated to this powerful JavaScript resource — such as jQuery Cookbook: Solutions & Examples for jQuery Developers." Read below for the rest of Michael's review. jQuery Cookbook author Various authors pages 480 pages publisher O'Reilly Media rating 9/10 reviewer Michael J. Ross ISBN 978-0596159771 summary An extensive collection of solutions to jQuery problems. This book was published by O'Reilly Media on 19 November 2009, under the ISBN 978-0596159771, and is authored by no fewer than 19 contributors — all quite knowledgeable of JavaScript and jQuery — and edited by one of those contributors, Cody Lindley. On the publisher's page for the book, visitors can read the book's description, table of contents, and errata, of which there are 22 as of this writing, although none have been confirmed by the authors or publisher. Visitors can also download all of the sample code used in the book, in addition to the eight code demos for Chapter 13. Lastly, prospective buyers can purchase the print version of the book, the electronic one (in PDF, ePub, and Mobi format), or the two combined at a considerable discount — or read the book as part of Safari Books Online.

jQuery Cookbook's 480 pages are organized into 18 chapters, covering a wide range of topics: the basics, element selection, utilities, dimensions, effects, events, forms, plug-ins, user interfaces, theming, Ajax, data formats, and testing. Lindley starts off the first chapter, titled "jQuery Basics," by presenting the advantages, philosophy, and organization of jQuery. Readers will likely chuckle at his suggestion that they memorize the jQuery API outline, which comprises two pages. The many code snippets are quite helpful, but they are needlessly long, partly because most of them contain far more HTML elements than are needed to illustrate the point, and also because each snippet contains the DOCTYPE and head tags, among others — often taking up more lines on the page than does the code pertinent to the topic at hand. This pointless and space-wasting redundancy is seen also in a few of the chapters that follow. As well, some of the passages in the first chapter's narrative are oddly phrased, frequently requiring a rereading of the material, while others could be made more concise. Additionally, some of the sample code contains bugs, which fortunately are detailed on the errata page mentioned earlier. The second chapter, "Selecting Elements with jQuery," presents numerous techniques for specifying elements within the DOM. The only obvious blemish in the material is in section 2.4, where the author refers to animated elements, but with absolutely no explanation as to what that means; countless new readers may assume he is referring to animated GIFs. Nonetheless, these two chapters form a helpful foundation for the rest of the manuscript.

The third chapter, "Beyond the Basics," gets off to a questionable start with the assertion that "jQuery can [] extend jQuery to infinite possibilities," which sounds like a line wisely rejected for the movie Toy Story. Yet the discussion continues on a solid footing, as it covers more advanced techniques for working with selected elements. Some of the discussion overlaps material presented in the previous two chapters, but it is always worthwhile to hear critical concepts explained from a different perspective. However, section 3.8, which briefly introduces jQuery plug-ins, is out of place; that material should be folded into Chapter 12, which focuses on that topic. The fourth chapter may be brief, but it explains several jQuery utility methods. Most of the code snippets use a format of "(function($) (jQuery);" — whose usage and advantages are not explained in this chapter, nor any earlier ones. This points up one of the key downsides of having almost every chapter of a programming book written by separate authors: readers can be confused or misled by disparities in coding practices, especially when the reasoning behind them is not given. The title of the fifth chapter, "Faster, Simpler, More Fun," is a bit misleading, because the authors don't explain how to make one's jQuery programming simpler or more fun, but they do provide a great deal of information on troubleshooting, performance optimization, and jQuery coding practices, including those pertaining to progressive enhancement, accessibility, and unobtrusiveness. Section 5.19 lacks a figure showing the menu being discussed, but that's the only obvious flaw.

The remaining chapters are dedicated to more specific aspects of jQuery programming, including the important topics of page layout as well as element positioning and sizing, discussed in Chapter 6. The subsequent chapter delves into effects, which is one of the more exciting topics in the jQuery realm. Even though a portion of the readers may be put off by the trickiness of the code, the material does demonstrate some of the powerful capabilities of jQuery effects — which in conjunction with HTML5 may easily encroach on areas of client-side programming formerly dominated by Adobe Flash. Throughout Chapter 7, most if not all places where the author refers to the "mouse," he apparently means the "mouse pointer." Events play a critical role in JavaScript software, and even more so for code that is mostly jQuery — thus the value of chapters 8 and 9, which examine basic and advanced event handling. The next pair of chapters discuss a variety of techniques for enhancing HTML forms, from scratch and through the use of jQuery plug-ins. The sample source code is better commented than what is seen elsewhere in the book, and the explanations are quite good. The subsequent chapter focuses on jQuery plug-ins, beyond their usage within HTML forms, and briefly explains how to create your own plug-ins and how to perform unit testing on them.

Because JavaScript is primarily a client-side technology, it should come as no surprise that jQuery can prove an outstanding tool in crafting user interfaces for Web sites and Web-based applications. Chapters 13 through 15 explore such topics as drop-down menus, sliding panels, rotating images, modal windows, tooltips, the jQuery UI, and how to style jQuery UI widgets, a.k.a., theming. No Web interface is an island, and over the years there have emerged a number of data formats and protocols for utilizing those formats for transmitting information between browsers and servers — such as Ajax, XML, JSON, and JSONP — covered in Chapter 16. Finally, the last two chapters of the book are geared more to testing and deployment, and less so to interface design and development. The topics covered include techniques for persisting data in the browser, managing large amounts of code and data for major software projects, automating the unit testing of jQuery code, testing callbacks and user actions, grouping and selecting tests, and more.

Overall, jQuery Cookbook starts off with some basics, and only then moves on to higher-level concepts and related use cases. However, the book is ostensibly aimed at beginners and intermediate JavaScript programmers, but the former group may find the ideas difficult to grasp fully, despite the introductory chapters — because some of the techniques are fairly advanced, they involve terminology unfamiliar to anyone new to jQuery, and some of that terminology is not explained. On the other hand, the recipes are generally well written and clear, supplemented with properly tested and working code. Consequently, anyone who takes the time to work through the examples patiently, should be well rewarded.

Because of its coverage of a wide range of topics, jQuery Cookbook can be used not only as a learning aid, but in some respects also as a reference — and in this regard the book's index will be quite useful. In light of the considerable length of the manuscript, reading it from stem to stern would involve an investment of time — especially if one were to work through all of the examples and try them out in one's own development environment — quite easily, in fact, since all of it can be downloaded from the publisher's site. Most of it, however, is organized as plain text files, and not HTML files; and no reason is provided for this annoying choice.

In terms of the layout and appearance of the text and figures, one flaw is that in countless lines throughout the book, the words are jammed together, making it difficult to read the text rapidly. In fact, some of these lines almost look like single words. This is also seen in the subheads, an excellent example of which can be found on page 149: "Solution2:ChangingthehrefAttributeoftheStylesheetThat'sResponsible." Unfortunately, the same is true for much of the source code, but in a different sense: Operators and variables are jammed together, clearly illustrating the need for whitespace in making code more readable. Some of the code is excessively long (noted earlier), and the authors are inconsistent as to whether their JavaScript is placed at the end of the body element or in the header element. Nonetheless, the sample code is generally of good quality.

There is another aspect related to not only this book but all other computer programming books for which individual chapters are written by different authors: jQuery Cookbook does not seem to be a single book, but instead a collection of books that were bundled together because of a common thread, namely, jQuery. This leads to some of the problems mentioned earlier, such as discrepancies in coding techniques and formatting — from which the beginning reader is supposedly learning best practices. On the other hand, the multi-author approach makes it possible for each major subject area to be handled by one or more writers who are expert in that particular area — which in turn results in a better product overall, even if one or two of the chapters are noticeably weaker than the others.

The book contains a number of copyediting flaws not listed on the aforementioned errata page: "elevated" should instead read "alleviated" (page 12); "or [its] alias" (13); "could change" should read "could be changed" (26); "jQuery('a')removeAttr('title')" is missing a "." (30); "'blue')" is missing a terminating ";" (50); "season in" should read "season" (56); "was contained" should read "is contained" (144); "position: absolute" in the narrative should not be broken between two lines (156); "great[er] than" (157); "equal[-]sized panels" (160); "only running" should read "only runs" (165); "still support[s]" (168), "#source5txt" should read "#source4txt" (217); and at this point I stopped recording errata. Also, in countless places in most of the chapters, semicolons are used where dashes are called for, and vice versa. O'Reilly's copyeditors should have detected and fixed those errors prior to publication.

Yet most of these blemishes are of little significance. What really counts is the overall value provided to the reader: Usable for both learning and reference, jQuery Cookbook delivers a tasty buffet of programming essentials, best practices, illustrative examples, optimization tips, and other information of value to JavaScript developers who wish to spice up their Web creations with jQuery.

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

You can purchase jQuery Cookbook: Solutions & Examples for jQuery Developers from amazon.com. 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 "Like all major programming languages, JavaScript can be extended in functionality through the use of libraries, such as jQuery, which is currently seeing tremendous popularity and enhancement in the Web development community. Designers and developers who want to learn how to use jQuery for creating rich user interfaces through client-side JavaScript are advised to begin their journey to jQuery proficiency by reading one of the many books dedicated to this powerful JavaScript resource — such as jQuery Cookbook: Solutions & Examples for jQuery Developers." Read below for the rest of Michael's review. jQuery Cookbook author Various authors pages 480 pages publisher O'Reilly Media rating 9/10 reviewer Michael J. Ross ISBN 978-0596159771 summary An extensive collection of solutions to jQuery problems. This book was published by O'Reilly Media on 19 November 2009, under the ISBN 978-0596159771, and is authored by no fewer than 19 contributors — all quite knowledgeable of JavaScript and jQuery — and edited by one of those contributors, Cody Lindley. On the publisher's page for the book, visitors can read the book's description, table of contents, and errata, of which there are 22 as of this writing, although none have been confirmed by the authors or publisher. Visitors can also download all of the sample code used in the book, in addition to the eight code demos for Chapter 13. Lastly, prospective buyers can purchase the print version of the book, the electronic one (in PDF, ePub, and Mobi format), or the two combined at a considerable discount — or read the book as part of Safari Books Online.

jQuery Cookbook's 480 pages are organized into 18 chapters, covering a wide range of topics: the basics, element selection, utilities, dimensions, effects, events, forms, plug-ins, user interfaces, theming, Ajax, data formats, and testing. Lindley starts off the first chapter, titled "jQuery Basics," by presenting the advantages, philosophy, and organization of jQuery. Readers will likely chuckle at his suggestion that they memorize the jQuery API outline, which comprises two pages. The many code snippets are quite helpful, but they are needlessly long, partly because most of them contain far more HTML elements than are needed to illustrate the point, and also because each snippet contains the DOCTYPE and head tags, among others — often taking up more lines on the page than does the code pertinent to the topic at hand. This pointless and space-wasting redundancy is seen also in a few of the chapters that follow. As well, some of the passages in the first chapter's narrative are oddly phrased, frequently requiring a rereading of the material, while others could be made more concise. Additionally, some of the sample code contains bugs, which fortunately are detailed on the errata page mentioned earlier. The second chapter, "Selecting Elements with jQuery," presents numerous techniques for specifying elements within the DOM. The only obvious blemish in the material is in section 2.4, where the author refers to animated elements, but with absolutely no explanation as to what that means; countless new readers may assume he is referring to animated GIFs. Nonetheless, these two chapters form a helpful foundation for the rest of the manuscript.

The third chapter, "Beyond the Basics," gets off to a questionable start with the assertion that "jQuery can [] extend jQuery to infinite possibilities," which sounds like a line wisely rejected for the movie Toy Story. Yet the discussion continues on a solid footing, as it covers more advanced techniques for working with selected elements. Some of the discussion overlaps material presented in the previous two chapters, but it is always worthwhile to hear critical concepts explained from a different perspective. However, section 3.8, which briefly introduces jQuery plug-ins, is out of place; that material should be folded into Chapter 12, which focuses on that topic. The fourth chapter may be brief, but it explains several jQuery utility methods. Most of the code snippets use a format of "(function($) (jQuery);" — whose usage and advantages are not explained in this chapter, nor any earlier ones. This points up one of the key downsides of having almost every chapter of a programming book written by separate authors: readers can be confused or misled by disparities in coding practices, especially when the reasoning behind them is not given. The title of the fifth chapter, "Faster, Simpler, More Fun," is a bit misleading, because the authors don't explain how to make one's jQuery programming simpler or more fun, but they do provide a great deal of information on troubleshooting, performance optimization, and jQuery coding practices, including those pertaining to progressive enhancement, accessibility, and unobtrusiveness. Section 5.19 lacks a figure showing the menu being discussed, but that's the only obvious flaw.

The remaining chapters are dedicated to more specific aspects of jQuery programming, including the important topics of page layout as well as element positioning and sizing, discussed in Chapter 6. The subsequent chapter delves into effects, which is one of the more exciting topics in the jQuery realm. Even though a portion of the readers may be put off by the trickiness of the code, the material does demonstrate some of the powerful capabilities of jQuery effects — which in conjunction with HTML5 may easily encroach on areas of client-side programming formerly dominated by Adobe Flash. Throughout Chapter 7, most if not all places where the author refers to the "mouse," he apparently means the "mouse pointer." Events play a critical role in JavaScript software, and even more so for code that is mostly jQuery — thus the value of chapters 8 and 9, which examine basic and advanced event handling. The next pair of chapters discuss a variety of techniques for enhancing HTML forms, from scratch and through the use of jQuery plug-ins. The sample source code is better commented than what is seen elsewhere in the book, and the explanations are quite good. The subsequent chapter focuses on jQuery plug-ins, beyond their usage within HTML forms, and briefly explains how to create your own plug-ins and how to perform unit testing on them.

Because JavaScript is primarily a client-side technology, it should come as no surprise that jQuery can prove an outstanding tool in crafting user interfaces for Web sites and Web-based applications. Chapters 13 through 15 explore such topics as drop-down menus, sliding panels, rotating images, modal windows, tooltips, the jQuery UI, and how to style jQuery UI widgets, a.k.a., theming. No Web interface is an island, and over the years there have emerged a number of data formats and protocols for utilizing those formats for transmitting information between browsers and servers — such as Ajax, XML, JSON, and JSONP — covered in Chapter 16. Finally, the last two chapters of the book are geared more to testing and deployment, and less so to interface design and development. The topics covered include techniques for persisting data in the browser, managing large amounts of code and data for major software projects, automating the unit testing of jQuery code, testing callbacks and user actions, grouping and selecting tests, and more.

Overall, jQuery Cookbook starts off with some basics, and only then moves on to higher-level concepts and related use cases. However, the book is ostensibly aimed at beginners and intermediate JavaScript programmers, but the former group may find the ideas difficult to grasp fully, despite the introductory chapters — because some of the techniques are fairly advanced, they involve terminology unfamiliar to anyone new to jQuery, and some of that terminology is not explained. On the other hand, the recipes are generally well written and clear, supplemented with properly tested and working code. Consequently, anyone who takes the time to work through the examples patiently, should be well rewarded.

Because of its coverage of a wide range of topics, jQuery Cookbook can be used not only as a learning aid, but in some respects also as a reference — and in this regard the book's index will be quite useful. In light of the considerable length of the manuscript, reading it from stem to stern would involve an investment of time — especially if one were to work through all of the examples and try them out in one's own development environment — quite easily, in fact, since all of it can be downloaded from the publisher's site. Most of it, however, is organized as plain text files, and not HTML files; and no reason is provided for this annoying choice.

In terms of the layout and appearance of the text and figures, one flaw is that in countless lines throughout the book, the words are jammed together, making it difficult to read the text rapidly. In fact, some of these lines almost look like single words. This is also seen in the subheads, an excellent example of which can be found on page 149: "Solution2:ChangingthehrefAttributeoftheStylesheetThat'sResponsible." Unfortunately, the same is true for much of the source code, but in a different sense: Operators and variables are jammed together, clearly illustrating the need for whitespace in making code more readable. Some of the code is excessively long (noted earlier), and the authors are inconsistent as to whether their JavaScript is placed at the end of the body element or in the header element. Nonetheless, the sample code is generally of good quality.

There is another aspect related to not only this book but all other computer programming books for which individual chapters are written by different authors: jQuery Cookbook does not seem to be a single book, but instead a collection of books that were bundled together because of a common thread, namely, jQuery. This leads to some of the problems mentioned earlier, such as discrepancies in coding techniques and formatting — from which the beginning reader is supposedly learning best practices. On the other hand, the multi-author approach makes it possible for each major subject area to be handled by one or more writers who are expert in that particular area — which in turn results in a better product overall, even if one or two of the chapters are noticeably weaker than the others.

The book contains a number of copyediting flaws not listed on the aforementioned errata page: "elevated" should instead read "alleviated" (page 12); "or [its] alias" (13); "could change" should read "could be changed" (26); "jQuery('a')removeAttr('title')" is missing a "." (30); "'blue')" is missing a terminating ";" (50); "season in" should read "season" (56); "was contained" should read "is contained" (144); "position: absolute" in the narrative should not be broken between two lines (156); "great[er] than" (157); "equal[-]sized panels" (160); "only running" should read "only runs" (165); "still support[s]" (168), "#source5txt" should read "#source4txt" (217); and at this point I stopped recording errata. Also, in countless places in most of the chapters, semicolons are used where dashes are called for, and vice versa. O'Reilly's copyeditors should have detected and fixed those errors prior to publication.

Yet most of these blemishes are of little significance. What really counts is the overall value provided to the reader: Usable for both learning and reference, jQuery Cookbook delivers a tasty buffet of programming essentials, best practices, illustrative examples, optimization tips, and other information of value to JavaScript developers who wish to spice up their Web creations with jQuery.

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

You can purchase jQuery Cookbook: Solutions & Examples for jQuery Developers from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

osullish writes "People have been proclaiming the death of the floppy for years, yet millions are bought around the world. Who is buying them?"

Raul654 writes "In March, the jury in the Novell/SCO case found that Novell owns the copyright to Unix. Now, SCO's lawyers have asked judge Ted Stewart to order Novell to turn over the Unix copyright to them. 'SCO contends the jury did not answer the specific issue before Stewart that involves a legal principle called "specific performance," under which a party can ask a court to order another party to fulfill an aspect of an agreement.'" Over at Groklaw, PJ is deep into a community project to annotate SCO's filing. It's for the benefit of future historians, but it makes amusing reading now.

SergeyKurdakov sends in a followup to our discussion a couple of months ago on purported shortcomings to the Ogg format. The inventor of the format, Monty "xiphmont" Montgomery of the Xiph Foundation, now refutes those objections in detail, with the introduction: "Earnest falsehoods left unchallenged risk being accepted as fact." The refutation has another advantage besides authoritativeness: it's far better written than the attack.

eldavojohn writes "Disillusioned by PowerPoint at work? Some members of the US Military view it as 'an internal threat.' Marine Corps General James N. Mattis says, 'PowerPoint makes us stupid,' reaching the same conclusion NASA came to back in 2003. But nothing speaks to this more than the spaghetti-bowl PowerPoint slide of the US Military's strategy in the ongoing war in Afghanistan. The slide causes anyone's eyes to glaze over with confusion so much that General McChrystal jokingly stated when he saw it, 'When we understand that slide, we'll have won the war.' At my job, I know that feeling all too well."

goG sends in a piece from IBTimes on the latest study to confirm what is becoming pretty obvious. The article mentions the Internet addiction rehab center we discussed last year. "American college students are hooked on cellphones, social media and the Internet and showing symptoms similar to drug and alcohol addictions, according to a new study. Researchers at the University of Maryland who asked 200 students to give up all media for one full day found that after 24 hours many showed signs of withdrawal, craving and anxiety along with an inability to function well without their media and social links. ... 'Texting and IM-ing my friends gives me a constant feeling of comfort,' wrote one of the students, who blogged about their reactions. 'When I did not have those two luxuries, I felt quite alone and secluded from my life.'"

secretcurse writes "California police have served a search warrant and seized computers from Jason Chen, the Gizmodo editor who unveiled the 4th-generation iPhone to the world. Gawker Media's COO has replied claiming that the warrant was served illegally due to Mr. Chen's status as a journalist. The plot thickens..."

DJRumpy sends in this quote from an AP report:"The Supreme Court will decide whether free speech rights are more important than helping parents keep violent material away from children. The justices agreed Monday to consider reinstating California's ban on the sale or rental of violent video games to minors, a law the 9th US Circuit Court of Appeals in San Francisco threw out last year on grounds that it violated minors' constitutional rights. California Gov. Arnold Schwarzenegger, who signed the law in 2005, said he was pleased the high court would review the appeals court decision. He said, 'We have a responsibility to our kids and our communities to protect against the effects of games that depict ultra-violent actions, just as we already do with movies.'" SCOTUSblog has a more thorough legal description of the case.

eldavojohn writes "Passed in 2006, the Unlawful Internet Gambling Enforcement Act is set to go into effect June 1. New efforts by Democrats in the House of Representatives aim not only to stop that but to legalize and tax Internet gambling. Jim McDermott (D-WA), said, 'This is a huge boon to the state governments. If you look across the country you're seeing programs cut. In Arizona, they just cut out a program for children's health for 40,000 kids. Here's a source of money.' Basically, the bill proposes that for each state, a 6% cut would be taken from all wagers and go to the state in which the bet was made online, while federal would get 2%. They estimate in the next decade this would amount to $30 billion for state and tribal governments and $42 billion for the federal government in new taxes. Banks and casinos appear to be very much on board, while the usual crowd (Republicans, Focus on the Family, Think of the Children) gathered in opposition to the move."

krou writes "Buried within the New Start treaty, which saw the decommissioning of nuclear warheads, was an interesting provision as a result of Russian demands: the US must 'decommission one nuclear missile for every one' of a new type of weapon called Prompt Global Strike 'fielded by the Pentagon.' The warhead, which is 'mounted on a long-range missile to start its journey,' would be 'capable of reaching any corner of the earth from the United States in under an hour. ... It would travel through the atmosphere at several times the speed of sound, generating so much heat that it would have to be shielded with special materials to avoid melting. ... But since the vehicle would remain within the atmosphere rather than going into space, it would be far more maneuverable than a ballistic missile, capable of avoiding the airspace of neutral countries, for example, or steering clear of hostile territory. Its designers note that it could fly straight up the middle of the Persian Gulf before making a sharp turn toward a target.' The new weapon is in line with Obama's plans 'to move towards less emphasis on nuclear weapons,' and rather focus on conventional ones. The idea is not new, having been first floated under the Bush administration, but was abandoned, mainly because 'Russian leaders complained that the technology could increase the risk of a nuclear war, because Russia would not know if the missiles carried nuclear warheads or conventional ones.'"

krou writes "Buried within the New Start treaty, which saw the decommissioning of nuclear warheads, was an interesting provision as a result of Russian demands: the US must 'decommission one nuclear missile for every one' of a new type of weapon called Prompt Global Strike 'fielded by the Pentagon.' The warhead, which is 'mounted on a long-range missile to start its journey,' would be 'capable of reaching any corner of the earth from the United States in under an hour. ... It would travel through the atmosphere at several times the speed of sound, generating so much heat that it would have to be shielded with special materials to avoid melting. ... But since the vehicle would remain within the atmosphere rather than going into space, it would be far more maneuverable than a ballistic missile, capable of avoiding the airspace of neutral countries, for example, or steering clear of hostile territory. Its designers note that it could fly straight up the middle of the Persian Gulf before making a sharp turn toward a target.' The new weapon is in line with Obama's plans 'to move towards less emphasis on nuclear weapons,' and rather focus on conventional ones. The idea is not new, having been first floated under the Bush administration, but was abandoned, mainly because 'Russian leaders complained that the technology could increase the risk of a nuclear war, because Russia would not know if the missiles carried nuclear warheads or conventional ones.'"

SillySilly writes "The ban has been lifted: The Communications Ministry announced Saturday evening that starting Sunday it will allow Apple's iPad tablet computer into the country, following two weeks of confiscations and confusion."

therufus writes "A few days after the release of Assassin's Creed 2, naughty piracy sites were announcing they had cracked Ubisoft's Online Services Platform. Turns out, that wasn't entirely true. While it was possible to load into the game, players were unable to advance past a certain memory block. But now, it seems Ubisoft will need to draft a new response. A new crack has begun circulating that removes the DRM entirely."

bgweber writes "Last year, the IEEE conference on Computational Intelligence and Games hosted a competition to determine who could write the best AI for playing Mario levels (YouTube video). This year, the conference has expanded the competition to include a track on level generation as well, where the goal is to generate new levels online procedurally. Submitting an entry is as easy as implementing a Java interface that performs procedural content generation. The implications of this competition are techniques for greatly increasing the replayability of games, since each gameplay session could present new levels to the player."

jeremyz writes "With the inclusion of 802.11n in more and more Wi-Fi devices, the WRT54GL is losing its usefulness, even though it's still the de-facto standard for open source, Linux-running wireless routers. I've been looking around for a 802.11n router to replace the WRT54GL, but haven't really found anything besides the Netgear's WNR3500L. At first look, the WNR3500L looked great, but after some further investigation, I found that Netgear hasn't released all of the source, as they should have to comply with the GPL. Are there any good 802.11n routers to replace my aging WRT54GL?"

snydeq writes "Fatal Exception's Neil McAllister sees Twitter's latest move — to develop 'analytical products' based on Twitter data and to encourage third-party developers to do the same — as part of a growing trend toward a new kind of software platform. 'In the past, tool vendors have offered developers languages and code libraries that gave them access to computing functions in simple, standardized ways. In this new paradigm, however, a platform consists of more than just frameworks and APIs. It also comes prepackaged with a complete, rich data set, and often that data is the platform's most valuable aspect. These new "data platforms" are creating exciting new opportunities for developers, though they are not without their challenges.' Chief among these issues are privacy and security, as evidenced by a recent letter to Google from government regulators and activist tools such as PleaseRobMe. But for developers, the challenges also include livelihood. 'Even more than mobile platforms such as Apple's iPhone, a data platform like Twitter's is a walled garden. If Twitter cuts off a developer's access to its data sources for any reason, that developer's business is sunk.' Even those who develop 'cloud middleware' around such data platforms stand to gain little from their efforts, as doing so pits them in competition with their data platform vendors, which are in a far better position to reach potential customers."

snydeq writes "Fatal Exception's Neil McAllister sees Twitter's latest move — to develop 'analytical products' based on Twitter data and to encourage third-party developers to do the same — as part of a growing trend toward a new kind of software platform. 'In the past, tool vendors have offered developers languages and code libraries that gave them access to computing functions in simple, standardized ways. In this new paradigm, however, a platform consists of more than just frameworks and APIs. It also comes prepackaged with a complete, rich data set, and often that data is the platform's most valuable aspect. These new "data platforms" are creating exciting new opportunities for developers, though they are not without their challenges.' Chief among these issues are privacy and security, as evidenced by a recent letter to Google from government regulators and activist tools such as PleaseRobMe. But for developers, the challenges also include livelihood. 'Even more than mobile platforms such as Apple's iPhone, a data platform like Twitter's is a walled garden. If Twitter cuts off a developer's access to its data sources for any reason, that developer's business is sunk.' Even those who develop 'cloud middleware' around such data platforms stand to gain little from their efforts, as doing so pits them in competition with their data platform vendors, which are in a far better position to reach potential customers."

MojoKid writes "Earlier in the month, it was reported that Palm was being shopped around. At that time, two of the main potential suitors were HTC and Lenovo. HTC obviously felt like the best fit. Lately, HTC has shown that it has a penchant for creating fantastic hardware, but it has to rely on Google and Microsoft for software. It seemed as if buying Palm would give HTC the power they needed to move ahead as a standalone unit, pairing HTC hardware with the WebOS mobile operating system. Apparently, that's not going to happen. Based on a new report out of Asia, HTC has declined to place an official bid on Palm, leaving Lenovo as the only other potential buyer at the moment."

tomduck writes "The Guardian reports that climate researcher Andrew Weaver is suing the National Post newspaper in Canada in a libel action for publishing 'grossly irresponsible falsehoods.' The Post claimed he cherrypicked data to support his climate research, and tried to blame the 'evil fossil fuel' industry for break-ins at his office in 2008 to divert attention from mistakes in the 2007 IPCC report. This comes fast on the heels of another Guardian article describing lessons learned from the exoneration of UEA scientists involved in the so-called Climategate affair. Are climate scientists finally fighting back against their critics, who they were previously more inclined to ignore?"

Dj writes to let us know that Microsoft has regained its FAT patent in Germany. (We discussed it three years ago when the German Federal Patent Tribunal ruled that Microsoft's patent on the FAT file system, with short and long names, was not enforceable.) "The [German] appeal court's decision brings it into line with the US patent office's assessment of the FAT patent. In early 2006, after lengthy deliberations, the latter confirmed the rights to protection conferred by [US] patent number 5,579,517, claiming that the development was new and inventive."

Hugh Pickens writes "The NY Times writes about Henry S. Heine, a former Army microbiologist who worked for years with Bruce E. Ivins, whom the FBI has blamed for the anthrax letter attacks that killed five people in 2001. Heine told a 16-member National Academy of Sciences panel reviewing the FBI's scientific work on the investigation that he believes it is impossible that the deadly spores could have been produced undetected in Ivins's laboratory, as the FBI asserts. Heine told the panel that producing the quantity of spores in the letters would have taken at least a year of intensive work using the equipment at the army lab, an effort that would not have escaped colleagues' notice. Lab technicians who worked closely with Ivins have told Heine they saw no such work. Heine adds that, in addition, the biological containment measures where Ivins worked were inadequate to prevent the spores from floating out of the laboratory into animal cages and offices. 'You'd have had dead animals or dead people.' Asked why he is speaking out now, almost two years after Ivins's suicide, Heine says that Army officials had prohibited comment on the case, silencing him until he left the government laboratory. Although Heine does not dispute that there was a genetic link between the spores in the letters and the anthrax in Ivins's flask, Heine says samples from the flask were widely shared. 'Whoever did this is still running around out there. I truly believe that.'"

mdsolar writes "A new report from a nuclear watchdog group finds that the Nuclear Regulatory Commission 'is ignoring its oversight and enforcement responsibilities at the nation's increasingly leaky, uninspected and unmaintained nuclear power plants.' Because of this lack of oversight, 'at least 102 reactor units are now documented to have had recurring radioactive leaks into groundwater from 1963 through February 2009.' So, the leak at Vermont Yankee that Slashdot has been following is not just a fluke, but is systemic."

brothke writes "As computing and technology has evolved, so too have the security threats correspondingly evolved. The classic Yankee Doodle virus of 1989 did minimal damage, all while playing a patriotic, albeit monotone song. In 2010, aggressive malware now executes in stealth mode, running in the background with an oblivious end-user, and antivirus software that can’t detect it." Read on for the rest of Ben's review. Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet author Joseph Menn pages 304 publisher PublicAffairs rating 8/10 reviewer Ben Rothke ISBN 978-1586487485 summary Non-fiction cyber-thriller with super analytical advice Cybercrimes have evolved using increasingly sophisticated techniques, and the resulting financial losses are staggering. Many criminal cyber gangs are well organized and resourceful and their ability to recover after new defenses have been deployed make it a challenge for those on the right side of the law.

Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet is an excellent book billed as a non-fiction cyber-thriller, and describes the cyber gangs who operate on the Internet. Author Joseph Menn, a cyber security reporter for the Financial Times, takes the reader into the inner operations of today's cyber-criminal, who use the Internet as their personal mint.

While Willie Sutton never really said that the reason he robbed banks is because that's where the money is; the truth is that today's cyber criminal does know where the money is, and its address is the Internet. They use the net as a means to steal and extort money from businesses and individuals.

The book's protagonist is Barrett Lyon, a highly skilled technical engineer and entrepreneur, who founded companies such as Prolexic, BitGravity and 3Crowd. It was at Prolexic where Lyon developed the software used to fend off the DoS attacks that were bringing some of his client's networks to a standstill.

Lyon, along with the other major character in the book, Andy Crocker, a British policeman, were the 1-2 punch that resulted in the prosecution of a Russian cyber criminal. The fact that the prosecution took place via the Russian judicial system was a surprise to everyone. What was unusual about the prosecution is that criminals in Russia and Eastern Europe often operate with the assistance of corrupt political and police forces. Even though the evidence against the defendant was significant, the ability to secure a guilty verdict was far from a sure thing.

Much of the book deals with Lyon and his working relationship with BetCRIS, a company offering online gambling services, including sports betting, online casino games, online bingo and mobile gambling.

BetCRIS is an off-shore company, operating in the safe havens of the Republic of Costa Rica. In 2003, at the height of the DoS attacks, the BetCRIS website was down for nearly a month. With tens of millions of dollars of gambling revenue at stake, BetCRIS management were desperate for a solution, and they reached out to Lyon.

While Lyon created a first-generation solution to stop the early DoS attacks, the book details how the attackers were able to get around those countermeasures, and how it turned into a cat and mouse game of futility, where Lyon would create a fix, only to be beguiled by a new attack.

In the book, Menn writes about many of the major players in the Internet criminal world. He spends a good amount of time writing about the infamous Russian Business Network (RBN). He notes that little true business was carried out via the RBN; rather it was a front for Internet-based criminal activities in Russia.

Menn does get into some technical details, but not so much so to confuse a non-technical reader. He covers topics such as botnets, DoS and DDoS attacks, cyberwarfare, cyber espionage, and the difficulty in prosecuting the perpetrators.

Menn notes that there are many reasons why Russia and in Eastern Europe are ground zero for cybercriminals. The educational institutions there provide a good source of technical training; combined that with the fact that legitimate job opportunities are often quite limited. Add to the fact that political and law enforcement officials often ignore the cyber attacks again the rich capitalists of the US, the difficulty and challenges with jurisdiction, and you have a perfect storm for the creation of a sophisticated cyber criminal element. Finally, there is a long and established culture of corruption in Russia and in Eastern Europe that adds to the problem.

There are two directions that Fatal System Error takes. The main part of the book is Menn's narrative, which takes up 11 of the book's 12 chapters. These 11 chapters take the reader on an enthralling ride into the inner workings of the cyber-criminal world. Fatal System Error is an enjoyable read on par books such as The Cuckoo's Egg: Tracking a Spy Through the Maze of Computer Espionage and Takedown: The Pursuit and Capture of Kevin Mitnick.

Where the book truly stands out is in the final chapter Fixing What's Fixable, and is worth purchasing for that chapter alone. Menn displays his incredibly deep understanding of the underlying issues around computer security and why we are vulnerable. He suggests numerous pragmatic solutions to the crisis, and how to better secure the Internet and networks.

Some of the ideas include significantly greater budgets for information security, more liability against software developers who write insecure code, greater information sharing between the cybercrime agencies in the US and their counterparts in Russia, and more. His on-target analysis of what the US Government can and should do to increase the security of the Internet infrastructure is quite impressive.

Reading the narrative part of the book, many readers will likely be scared to death to connect their computers to the Internet, and to a limited degree, rightfully so. Even with Menn's balanced and compelling account of what transpired, the threat of identity theft and ease of how financial accounts are breached may be too much for some readers many to bear.

If corporate America and the US Government would take Menn's suggestions to heart on how to create a secure Internet infrastructure, many of those security concerns he wrote about could be obviated, and the cyber criminals of Eastern Europe would have to look for different work.

Additional pragmatic ideas that Menn suggests are to legalize and regulate online gambling, more funding to teach safer computing in schools, and for a complete re-engineering of the Internet, in order to build in the necessary security functionality which should have been in there in the first place. As part of the process to re-engineer the Internet, Menn suggests designs that create accountability into the Internet fabric.

Finally, Menn notes that many end-users are not blameless. By not educating themselves on how to securely use the Internet, they are setting themselves up to becoming victims. He writes that anyone that connects a computer to the Internet needs to have significant security vigilance to ensure that they don't make themselves a victim. It is 2010 and far too many people are still oblivious to the security threats. Many still naively believe that someone from Nigeria really does want to make them richer with tens of millions of dollars worth of gold from their deceased uncle.

Menn shows how the underlying infrastructure of the Internet is significantly more vulnerable than most people realize. Finally, what exacerbates the problem is that those doing the attacks are working much quicker than those who are trying to secure it.

One of Menn's criticisms is that the US Government spends a fraction of what it should on securing its critical technology infrastructure. Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet is the wake-up call that those in Washington, and those charged with IT need to wake up to. Unfortunately, it is likely those that truly need to read this book, will press the information security snooze button yet again.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

brothke writes "As computing and technology has evolved, so too have the security threats correspondingly evolved. The classic Yankee Doodle virus of 1989 did minimal damage, all while playing a patriotic, albeit monotone song. In 2010, aggressive malware now executes in stealth mode, running in the background with an oblivious end-user, and antivirus software that can’t detect it." Read on for the rest of Ben's review. Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet author Joseph Menn pages 304 publisher PublicAffairs rating 8/10 reviewer Ben Rothke ISBN 978-1586487485 summary Non-fiction cyber-thriller with super analytical advice Cybercrimes have evolved using increasingly sophisticated techniques, and the resulting financial losses are staggering. Many criminal cyber gangs are well organized and resourceful and their ability to recover after new defenses have been deployed make it a challenge for those on the right side of the law.

Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet is an excellent book billed as a non-fiction cyber-thriller, and describes the cyber gangs who operate on the Internet. Author Joseph Menn, a cyber security reporter for the Financial Times, takes the reader into the inner operations of today's cyber-criminal, who use the Internet as their personal mint.

While Willie Sutton never really said that the reason he robbed banks is because that's where the money is; the truth is that today's cyber criminal does know where the money is, and its address is the Internet. They use the net as a means to steal and extort money from businesses and individuals.

The book's protagonist is Barrett Lyon, a highly skilled technical engineer and entrepreneur, who founded companies such as Prolexic, BitGravity and 3Crowd. It was at Prolexic where Lyon developed the software used to fend off the DoS attacks that were bringing some of his client's networks to a standstill.

Lyon, along with the other major character in the book, Andy Crocker, a British policeman, were the 1-2 punch that resulted in the prosecution of a Russian cyber criminal. The fact that the prosecution took place via the Russian judicial system was a surprise to everyone. What was unusual about the prosecution is that criminals in Russia and Eastern Europe often operate with the assistance of corrupt political and police forces. Even though the evidence against the defendant was significant, the ability to secure a guilty verdict was far from a sure thing.

Much of the book deals with Lyon and his working relationship with BetCRIS, a company offering online gambling services, including sports betting, online casino games, online bingo and mobile gambling.

BetCRIS is an off-shore company, operating in the safe havens of the Republic of Costa Rica. In 2003, at the height of the DoS attacks, the BetCRIS website was down for nearly a month. With tens of millions of dollars of gambling revenue at stake, BetCRIS management were desperate for a solution, and they reached out to Lyon.

While Lyon created a first-generation solution to stop the early DoS attacks, the book details how the attackers were able to get around those countermeasures, and how it turned into a cat and mouse game of futility, where Lyon would create a fix, only to be beguiled by a new attack.

In the book, Menn writes about many of the major players in the Internet criminal world. He spends a good amount of time writing about the infamous Russian Business Network (RBN). He notes that little true business was carried out via the RBN; rather it was a front for Internet-based criminal activities in Russia.

Menn does get into some technical details, but not so much so to confuse a non-technical reader. He covers topics such as botnets, DoS and DDoS attacks, cyberwarfare, cyber espionage, and the difficulty in prosecuting the perpetrators.

Menn notes that there are many reasons why Russia and in Eastern Europe are ground zero for cybercriminals. The educational institutions there provide a good source of technical training; combined that with the fact that legitimate job opportunities are often quite limited. Add to the fact that political and law enforcement officials often ignore the cyber attacks again the rich capitalists of the US, the difficulty and challenges with jurisdiction, and you have a perfect storm for the creation of a sophisticated cyber criminal element. Finally, there is a long and established culture of corruption in Russia and in Eastern Europe that adds to the problem.

There are two directions that Fatal System Error takes. The main part of the book is Menn's narrative, which takes up 11 of the book's 12 chapters. These 11 chapters take the reader on an enthralling ride into the inner workings of the cyber-criminal world. Fatal System Error is an enjoyable read on par books such as The Cuckoo's Egg: Tracking a Spy Through the Maze of Computer Espionage and Takedown: The Pursuit and Capture of Kevin Mitnick.

Where the book truly stands out is in the final chapter Fixing What's Fixable, and is worth purchasing for that chapter alone. Menn displays his incredibly deep understanding of the underlying issues around computer security and why we are vulnerable. He suggests numerous pragmatic solutions to the crisis, and how to better secure the Internet and networks.

Some of the ideas include significantly greater budgets for information security, more liability against software developers who write insecure code, greater information sharing between the cybercrime agencies in the US and their counterparts in Russia, and more. His on-target analysis of what the US Government can and should do to increase the security of the Internet infrastructure is quite impressive.

Reading the narrative part of the book, many readers will likely be scared to death to connect their computers to the Internet, and to a limited degree, rightfully so. Even with Menn's balanced and compelling account of what transpired, the threat of identity theft and ease of how financial accounts are breached may be too much for some readers many to bear.

If corporate America and the US Government would take Menn's suggestions to heart on how to create a secure Internet infrastructure, many of those security concerns he wrote about could be obviated, and the cyber criminals of Eastern Europe would have to look for different work.

Additional pragmatic ideas that Menn suggests are to legalize and regulate online gambling, more funding to teach safer computing in schools, and for a complete re-engineering of the Internet, in order to build in the necessary security functionality which should have been in there in the first place. As part of the process to re-engineer the Internet, Menn suggests designs that create accountability into the Internet fabric.

Finally, Menn notes that many end-users are not blameless. By not educating themselves on how to securely use the Internet, they are setting themselves up to becoming victims. He writes that anyone that connects a computer to the Internet needs to have significant security vigilance to ensure that they don't make themselves a victim. It is 2010 and far too many people are still oblivious to the security threats. Many still naively believe that someone from Nigeria really does want to make them richer with tens of millions of dollars worth of gold from their deceased uncle.

Menn shows how the underlying infrastructure of the Internet is significantly more vulnerable than most people realize. Finally, what exacerbates the problem is that those doing the attacks are working much quicker than those who are trying to secure it.

One of Menn's criticisms is that the US Government spends a fraction of what it should on securing its critical technology infrastructure. Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet is the wake-up call that those in Washington, and those charged with IT need to wake up to. Unfortunately, it is likely those that truly need to read this book, will press the information security snooze button yet again.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Fatal System Error: The Hunt for the New Crime Lords Who are Bringing Down the Internet from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

eldavojohn writes "You may recall the hapless engineer who left a fairly sensitive iPhone at a bar recently. Well, in a PR stunt, Lufthansa has invited him to visit Germany on their dime after citing his latest Facebook status, 'I underestimated how good German beer is' as well as his obvious passion for German beer and culture. It's not clear if Gray Powell has decided to 'pick up where he last left off' (as the letter puts it). I know what my decision would be."

bennyboy64 writes "McAfee has changed its official response [warning: interstitial] on how many enterprise customers were affected by a bug that caused havoc on computers globally. It originally stated the bug affected 'less than half of 1 per cent' of enterprise customers. Now McAfee's blog states it was a 'small percentage' of enterprise customers. ZDNet is running a poll and opinion piece on whether McAfee should compensate customers. ZDNet notes a supermarket giant in Australia that had to close down its stores as they were affected by the bug, causing a loss of thousands of dollars."

Yesterday we mentioned the controversy facing Matt Stone and Trey Parker after last week's South Park (episode 200) depicted Muhammad, founder of Islam, concealed in a bear suit. Today, penguinman1337 writes "Apparently, all is not well over at Comedy Central. The heavily censored version of episode 201 that aired last night has a lot of people angry, including the show's creators." From their note: "In the 14 years we've been doing South Park we have never done a show that we couldn't stand behind. We delivered our version of the show to Comedy Central and they made a determination to alter the episode. It wasn't some meta-joke on our part. Comedy Central added the bleeps."

Annirak writes "With the bottom dropping out of the magnetic disk market and SSD prices still over $3/GB, I want to know if there is a way to to get the best of both worlds. Ideally, a caching algorithm would store frequently used sectors, or sectors used during boot or application launches (hot sectors), to the SSD. Adaptec has a firmware implementation of this concept, called MaxIQ, but this is only for use on their RAID controllers and only works with their special, even more expensive, SSD. Silverstone recently released a device which does this for a single disk, but it is limited: it caches the first part of the magnetic disk, up to the size of the SSD, rather than caching frequently used sectors. The FS-Cache implementation in recent Linux kernels seems to be primarily intended for use in NFS and AFS, without much provision for speeding up local filesystems. Is there a way to use an SSD to act as a hot sector cache for a magnetic disk under Linux?"

SheeEttin writes "Back in November 2008, Phoronix reported that Linux libraries appeared in the Left 4 Dead demo, and then in March, Valve announced that Steam and the Source engine were coming to Mac OS X. Now, Phoronix reports that launcher scripts included with the (closed beta) Mac version of Steam include explicit support for launching a Linux version."

Vamman writes "If you've been following the drama surrounding the free release of MechWarrior4, then you're probably aware that the initial announcement, made last summer, was a bit premature. Now, nearly a year since that announcement was made, MekTek Studios has announced that Microsoft Legal has given clearance for the free release of Mechwarrior4. This move by Microsoft Games couldn't come at a better time for the community, as the owners of MechWarrior are attempting a reboot of the franchise."

Sparky Anduril writes "In this book author Allan Walker writes to inform Joomla! website administrators and developers how to enrich their websites with the inclusion of multimedia. And be in no doubt, this book is not for novices. A decent understanding of Joomla! will be required for you to benefit from this book. But all-in-all, whether you are an experienced Joomla! administrator but fear to go where multimedia gremlins tread, or someone with knowledge of video and audio but having little idea how to integrate that into your Joomla! website, this book will give you a solid understanding and ability to enable you to embed multimedia in your website using a range of techniques and Joomla! extensions." Read on for the rest of Sparky's review. Joomla! 1.5 Multimedia author Allan Walker pages 376 publisher Packt Publishing rating 8 reviewer Sparky Anduril ISBN 1847197701 summary Build media-rich Joomla! websites by learning to embed and display multimedia content I do have one major gripe about this book, however: the author over-utilizes the word utilize, when English has a perfectly utilizable word which actually means what he wants to say, vis. "use." I wish technical writers would keep it simple and utilize the simple word rather than the fancy word which they mistakenly think makes them sound more intelligent! So, moan over, let's plunge into the contents of the book.

Chapter 1 provides an overview of multimedia (what is it?) and Joomla! (why that's needed when the book is aimed at Joomla! admins I don't know!) and then talks about where multimedia may be included in your site. The chapter is a bit repetitive and hence could have been shorter, but provides a useful foundation for what comes next. It also includes a timely reminder about web site accessibility...

Chapter 2 talks about how to manage media on the site — using the Joomla! Media Manager, an ftp program or a Joomla! extension. A bit basic, but in case you're a site admin with little experience in this area it's fairly essential stuff.

Chapter 3 was the biggest surprise of the book, but nonetheless a useful addition. It talks about text. "Text?" I hear you say. "What place does 'text' have in a book about multimedia (apart from as the medium by which information is transmitted to my brain)?" And in fact the first part of the chapter does seem like the author is riding his hobby horse to let us know what he thinks about fonts and CSS and so forth which, while relevant to any web site, are not really relevant to multimedia. But the chapter does include information about available text and typography extensions for Joomla! which will be news to many and may just solve your typographical problem.

And if you buy this book and read up to chapter 3 and complain it's a bit basic and tedious, well, keep on reading. In Chapter 4 we start the real stuff. In fact chapters 4 to 7 are where this book comes into its own. Chapters 4 to 6 cover (in turn) image content, audio and video. Chapter 7 covers collaborating with external sources.

Chapters 4 to 6 have similar structures, each of them dealing with a different class of media. A very useful section of each chapter deals with formats (image, audio and video respectively). Then the author deals with how to include the media in the web site, using in-built features (for images), custom HTML modules and third-party extensions. The section on third party extensions in each chapter quickly presents a number of options, without giving a great deal of detail about how to use each one. And that may be frustrating but is fair enough when in fact there are a whole load of extensions the user can choose from. What this approach leads to is an appreciation of the possibilities, a list of extensions to try out for starters, and hopefully an increasing confidence in the reader that they can try things out for themselves and find something suitable for their needs. The Image chapter covers for example image galleries and slideshows; the Audio chapter includes audio players and audio streaming, podcasts and RSS feeds; the Video chapter includes Video podcasting, players and streaming.

Chapter 7 is all about the "social web": so mostly it's about including media from external sites such as YouTube, Internet radio, social bookmarking and so on. This chapter is primarily a catalog of useful Joomla! extensions you can use to provide a variety of media from a variety of sources.

Chapter 8 is about Joomla! templates and multimedia. The chapter partly seems to serve as an advocate for commercial templates, but does have some interesting content about templates and extensions to provide mobile device access to your web site.

In Chapter 9 the author pulls all this together as he develops a multimedia website using some of the techniques in the book. At the start of the chapter, he describes how to set up a local development server so you can develop and/or enhance a site without breaking the live site. For admins who have been given a fully working site, this is essential information. For many of us, that is how we started and hence we already know how to do local development. The part missing from this section is how to install Joomla! on the local server (he starts to tell it but it really needs a couple more steps to be described — although that information is readily available at www.joomla.org of course). Also, this of all sections suffers from the fact that the author is a Mac-user — I am not trying to start a Mac-Windows war, but the fact of the matter is that the vast majority of users will be Windows users, so he should have provided more information on setting up a WAMP server or XAMPP on Windows.

The code used in the book is also available as a zip file download, in case you're too lazy to type it out again and want to use it exactly as-is from the book, or perhaps more reasonably you want to try out the code or CSS he has suggested and then tweak it to your own need! Would I recommend this book? It depends on whether you want a fast start to solve your media problems. If you have little awareness of how to start, this will help you out. Or if you don't want to spend hours trying out extension after extension this will probably save you a lot of time. If, however, you are really familiar with multimedia and Joomla! and are happy to play with extensions until you find the one you need, then you could save yourself some money and go play.

I have personally found the book to be informative and in some areas opened my eyes to what can already be achieved quite easily using Joomla! 1.5.

You can purchase Joomla! 1.5 Multimedia from amazon.com. Slashdot welcomes readers' book reviews; to see your own review here, read the book review guidelines, then visit the submission page.

Sparky Anduril writes "In this book author Allan Walker writes to inform Joomla! website administrators and developers how to enrich their websites with the inclusion of multimedia. And be in no doubt, this book is not for novices. A decent understanding of Joomla! will be required for you to benefit from this book. But all-in-all, whether you are an experienced Joomla! administrator but fear to go where multimedia gremlins tread, or someone with knowledge of video and audio but having little idea how to integrate that into your Joomla! website, this book will give you a solid understanding and ability to enable you to embed multimedia in your website using a range of techniques and Joomla! extensions." Read on for the rest of Sparky's review. Joomla! 1.5 Multimedia author Allan Walker pages 376 publisher Packt Publishing rating 8 reviewer Sparky Anduril ISBN 1847197701 summary Build media-rich Joomla! websites by learning to embed and display multimedia content I do have one major gripe about this book, however: the author over-utilizes the word utilize, when English has a perfectly utilizable word which actually means what he wants to say, vis. "use." I wish technical writers would keep it simple and utilize the simple word rather than the fancy word which they mistakenly think makes them sound more intelligent! So, moan over, let's plunge into the contents of the book.

Chapter 1 provides an overview of multimedia (what is it?) and Joomla! (why that's needed when the book is aimed at Joomla! admins I don't know!) and then talks about where multimedia may be included in your site. The chapter is a bit repetitive and hence could have been shorter, but provides a useful foundation for what comes next. It also includes a timely reminder about web site accessibility...

Chapter 2 talks about how to manage media on the site — using the Joomla! Media Manager, an ftp program or a Joomla! extension. A bit basic, but in case you're a site admin with little experience in this area it's fairly essential stuff.

Chapter 3 was the biggest surprise of the book, but nonetheless a useful addition. It talks about text. "Text?" I hear you say. "What place does 'text' have in a book about multimedia (apart from as the medium by which information is transmitted to my brain)?" And in fact the first part of the chapter does seem like the author is riding his hobby horse to let us know what he thinks about fonts and CSS and so forth which, while relevant to any web site, are not really relevant to multimedia. But the chapter does include information about available text and typography extensions for Joomla! which will be news to many and may just solve your typographical problem.

And if you buy this book and read up to chapter 3 and complain it's a bit basic and tedious, well, keep on reading. In Chapter 4 we start the real stuff. In fact chapters 4 to 7 are where this book comes into its own. Chapters 4 to 6 cover (in turn) image content, audio and video. Chapter 7 covers collaborating with external sources.

Chapters 4 to 6 have similar structures, each of them dealing with a different class of media. A very useful section of each chapter deals with formats (image, audio and video respectively). Then the author deals with how to include the media in the web site, using in-built features (for images), custom HTML modules and third-party extensions. The section on third party extensions in each chapter quickly presents a number of options, without giving a great deal of detail about how to use each one. And that may be frustrating but is fair enough when in fact there are a whole load of extensions the user can choose from. What this approach leads to is an appreciation of the possibilities, a list of extensions to try out for starters, and hopefully an increasing confidence in the reader that they can try things out for themselves and find something suitable for their needs. The Image chapter covers for example image galleries and slideshows; the Audio chapter includes audio players and audio streaming, podcasts and RSS feeds; the Video chapter includes Video podcasting, players and streaming.

Chapter 7 is all about the "social web": so mostly it's about including media from external sites such as YouTube, Internet radio, social bookmarking and so on. This chapter is primarily a catalog of useful Joomla! extensions you can use to provide a variety of media from a variety of sources.

Chapter 8 is about Joomla! templates and multimedia. The chapter partly seems to serve as an advocate for commercial templates, but does have some interesting content about templates and extensions to provide mobile device access to your web site.

In Chapter 9 the author pulls all this together as he develops a multimedia website using some of the techniques in the book. At the start of the chapter, he describes how to set up a local development server so you can develop and/or enhance a site without breaking the live site. For admins who have been given a fully working site, this is essential information. For many of us, that is how we started and hence we already know how to do local development. The part missing from this section is how to install Joomla! on the local server (he starts to tell it but it really needs a couple more steps to be described — although that information is readily available at www.joomla.org of course). Also, this of all sections suffers from the fact that the author is a Mac-user — I am not trying to start a Mac-Windows war, but the fact of the matter is that the vast majority of users will be Windows users, so he should have provided more information on setting up a WAMP server or XAMPP on Windows.

The code used in the book is also available as a zip file download, in case you're too lazy to type it out again and want to use it exactly as-is from the book, or perhaps more reasonably you want to try out the code or CSS he has suggested and then tweak it to your own need! Would I recommend this book? It depends on whether you want a fast start to solve your media problems. If you have little awareness of how to start, this will help you out. Or if you don't want to spend hours trying out extension after extension this will probably save you a lot of time. If, however, you are really familiar with multimedia and Joomla! and are happy to play with extensions until you find the one you need, then you could save yourself some money and go play.

I have personally found the book to be informative and in some areas opened my eyes to what can already be achieved quite easily using Joomla! 1.5.

You can purchase Joomla! 1.5 Multimedia from amazon.com. Slashdot welcomes readers' book reviews; to see your own review here, read the book review guidelines, then visit the submission page.

MongooseCN has a follow-up to last week's Chinese Sweatshop story. He says "The image Microsoft doesn't want you to see: Too tired to stay awake. These Chinese workers earn just 34p an hour (about 52 cents in US dollars), work 15-hour shifts, and deal with other abuses to package US-made products."

Ars covers the settlement of the RCN P2P throttling class-action lawsuit, which lets the company walk away without admitting guilt, without paying affected users, and without any meaningful restraint on their network management practices. "[The] settlement is due to be finalized on June 4. ... The case has largely flown under the radar. Yesterday, a notice ... was issued that alerted RCN customers to the settlement, and one Ars reader was aghast at the terms. Those terms provide nothing for users affected by RCN's practices. Instead, they require the cable company to change its network management practices. These changes are in two parts. ... These cessation periods would be retroactive. ... A moment's math will tell you that, when the settlement is finally approved, one cessation period will already have ended and the other will be ending soon. Once both cessation periods are over, RCN is allowed to implement whatever throttling regime it wants. Given that a federal court has just removed the FCC's authority to regulate network management, RCN appears to have carte blanche to single out BitTorrent and other P2P traffic for special throttling attention after November 1, 2010."

snydeq writes "Closing arguments concluded Monday in the city of San Francisco's case against Terry Childs, the network administrator charged with violating California hacking laws by refusing to hand over network passwords for the city's FiberWAN during a 12-day period in 2008. Childs was charged in July 2008 and has been held on $5 million bail ever since. The highly technical trial, which featured testimony from San Francisco Mayor Gavin Newsom and Cisco Chief Security Officer John Stewart, has dragged on for nearly six months. By Monday, five of the 18 jurors and alternates selected for the trial had dropped out, and the remaining jurors seemed relieved to see the arguments wrap up as they left the courtroom Monday afternoon. They will return Tuesday to start their deliberations. Childs faces five years in prison if he is convicted for disrupting service to the city's computer system by withholding administrative passwords — a verdict that, if rendered, puts all IT admins in danger."

snydeq writes "Closing arguments concluded Monday in the city of San Francisco's case against Terry Childs, the network administrator charged with violating California hacking laws by refusing to hand over network passwords for the city's FiberWAN during a 12-day period in 2008. Childs was charged in July 2008 and has been held on $5 million bail ever since. The highly technical trial, which featured testimony from San Francisco Mayor Gavin Newsom and Cisco Chief Security Officer John Stewart, has dragged on for nearly six months. By Monday, five of the 18 jurors and alternates selected for the trial had dropped out, and the remaining jurors seemed relieved to see the arguments wrap up as they left the courtroom Monday afternoon. They will return Tuesday to start their deliberations. Childs faces five years in prison if he is convicted for disrupting service to the city's computer system by withholding administrative passwords — a verdict that, if rendered, puts all IT admins in danger."

Blue Taxes writes "The cross-site scripting filter that ships with Microsoft's Internet Explorer 8 browser can be abused by attackers to launch cross-site scripting attacks on websites and web pages that would otherwise be immune to this threat. The IE8 filter works by scanning outbound requests for strings that may be malicious. When such a string is detected, IE8 will dynamically generate a regular expression matching the outbound string. The browser then looks for the same pattern in responses from the server. If a match is made anywhere in the server's response, the browser assumes that a reflected XSS attack is being conducted and the browser will automatically alter the response so that the XSS attack cannot succeed. The researchers figured out a way to use IE8's altered response to conduct simple abuses and universal cross-site scripting attacks, which worked against sites that would not otherwise have been vulnerable to XSS." Here is the researchers' backgrounder (PDF) on the attack. Microsoft says that they have issued two patches that address the issue, but the researchers insist that holes remain.
Update: 04/20 14:06 GMT by KD : Microsoft's Security Response Center has issued a statement on the vulnerability.

Last week we discussed news that a US government report questioned the reliability of piracy statistics from the media industry. Reader superapecommando sends in a follow-up written by Glyn Moody that examines a similar problem in Europe. Quoting: "As far as I know, no similar analysis has been carried out for European reports. So I thought it might be interesting to look at one particular European report on the subject — not least because I've heard that its findings influenced some of the MPs voting on the Digital Economy Act. ... the net result of this 68-page report, with all of its tables and detailed methodology, is that four out of the top five markets used for calculating the overall piracy loss in Europe draw on figures supplied by the recording industry itself. Those apparently terrifying new figures detailing the supposed loss of money and jobs due to piracy in Europe turn out to be little more than a re-statement of the industry's previous claims in a slightly different form. As a result, as little credence can be placed in the report as in those criticised by the US GAO."

An anonymous reader writes "There has been some speculation about it. Not anymore: 'This is Apple's next iPhone. It was found lost in a bar in Redwood City, camouflaged to look like an iPhone 3GS. We got it. We disassembled it. It's the real thing, and here are all the details.' Judging by Gizmodo's reaction, it looks like a winner."

Hugh Pickens writes "AP reports that plagiarizing or faking results is so rampant in Chinese academia that some experts worry it could hinder China's efforts to become a leader in science. China's state-run media recently rejoiced over reports that China publishes more papers in international journals than any other country except the US; but not all the research stands up to scrutiny. In December, a British journal retracted 70 papers from a Chinese university, all by the same two lead scientists, saying the work had been fabricated, and expressing amazement that a fake crystal structure would be submitted for publication. 'Academic fraud, misconduct and ethical violations are very common in China,' said professor Rao Yi, dean of the life sciences school at Peking University. 'It is a big problem.' Last month the Education Ministry released guidelines for forming a 35-member watchdog committee and has asked universities to get tough but Rao remains skeptical. Government ministries are happy to fund research but not to police it, Rao says. 'The authorities don't want to be the bad guy.'"

ocean_soul writes "More than three weeks after the release of The Settlers 7, with the controversial 'always on-line' DRM, a lot of people still can't connect to Ubisoft's DRM servers. The forum threads where people can post if they are unable to connect keep growing daily. One reason for the lack of fixes or responses from support seems to be that the people responsible were on vacation during the Easter holiday, despite the promise of 24/7 monitoring of the servers. The moral of this story seems to be that it is a bad idea to buy a game just before a major holiday." Or perhaps that it's wise to avoid games with such DRM altogether. So far, Ubisoft hasn't shown any sign that they're reconsidering the requirement of a constant connection. They've recently said it's "vital" to the success of their games and promised that their DRM would "evolve and improve" over time.

Pickens writes "Corporate Counsel recounts the profound legacy of Supreme Court Justice John Paul Stevens, author of the majority opinion in what some consider the most important copyright ruling of all time — the 1984 Betamax decision (Sony v. Universal City Studios) that established that consumers have a personal 'fair use' right to make copies of copyrighted material for non-commercial use. Justice Stevens's contribution to the ultimate decision in Betamax extended well beyond writing the opinion. The justices' initial debates in the case make it clear that Stevens was the only one of the nine (PDF) who believed that the 'fair use' doctrine gave consumers a right to make personal copies of copyrighted content for home use. It was his negotiating skill that pulled together the five-vote majority allowing home video recorders to be sold and used without interference from copyright holders. An IP litigator is quoted: 'The ruling that making a single copy for yourself of a broadcast movie was fair use ... that was truly huge, and was a point on which the court was deeply divided.' So the next time you're TiVo-ing an episode of your favorite show, remember to give a quick thanks to Justice Stevens; and let's hope that whoever President Obama appoints to replace him will follow in Stevens's footsteps and defend Fair Use, not corporate copyright interests." The review also touches on Stevens's "patent skepticism," which may be on display when the court delivers its eagerly awaited Bilski ruling.

theodp writes "Microsoft's Kin mobile phone project came under fire as Consumer Reports and others pointed out that a promotional video looked like an inappropriate endorsement of 'sexting,' prompting a quick edit and an apologetic tweet. 'The video,' observed Consumer Reports, 'includes a downright creepy sequence [beginning around 0:33] in which a young man is shown putting a Kin under his shirt and apparently snapping a picture of one of his naked breasts. The breast is then shown on the phone's screen, just before the guy apparently sends it to someone. Next we see the face of a young woman, seemingly the recipient, with an amused expression...'"

NewYorkCountryLawyer writes "Micah Kellner, the New York State assemblyman who last year submitted a bill to provide a tax credit to open source developers, has now proposed the 'Open New York Act,' a law that would make it mandatory for state agencies to put almost all of their public records on the Internet. According to Kellner's office, the law would 'revolutionize the relationship between New Yorkers and their state government, requiring all state agencies to make their records available through a central website — where the data can be used by activists, entrepreneurs, and others to create a host of applications useful in everyday life.' The Open Government Foundation, Citizens Union, and New York Public Interest Research Group all support the bill."

alphadogg writes "Michael Abbott, the head of Palm's software and services team, will leave the company at the end of next week, according to a regulatory filing Palm made on Friday to the US Securities and Exchange Commission. He submitted his resignation on Monday and will leave the company on April 23, Palm said. The resignation came as reports surface that the struggling handset maker is seeking a buyer. Last month Palm reported disappointing results for the quarter that ended Feb. 26. Its Pre and Pixi smartphone lines, which run the WebOS operating system, are up against a growing number of smartphones using Google's Android platform as well as Apple's popular iPhone."

funchords writes "As a settlement to the class-action lawsuits over Comcast's blocking of users' Internet traffic, Comcast stands to pay 'up to' $16.00 to every subscriber who makes a claim at their settlement website and declares, under penalty of perjury, that their online activity was for a lawful purpose consistent with applicable copyright and other laws. Robb Topolski, the veteran networking engineer who kicked off the case when he discovered the blocking back in 2007, says that the proposed settlement doesn't make sense, especially after the US Court of Appeals for the District of Columbia Circuit ruled this month that the US Federal Communications Commission didn't have the authority to enforce its Net neutrality principles on Comcast. 'You paid about $50 a month for the service, and the amount that Comcast stands to return is up to about 50c per month for each month that it blocked traffic,' he wrote. 'If that tiny amount of money is compensation, then there is no penalty to Comcast for interfering with its customers, for failing to disclose it, for repeatedly lying about it, and for taking so long to stop it.' The Associated Press and the Electronic Frontier Foundation, in late 2007, each independently confirmed Topolski's reports that Comcast was blocking BitTorrent and some other traffic without telling its customers. Comcast first denied interfering with traffic, then finally said it throttled some applications only during times of peak congestion. However, studies from the Max Planck Institute for Software Systems in Germany eventually proved that Comcast slowed BitTorrent traffic around the clock."

funchords writes "As a settlement to the class-action lawsuits over Comcast's blocking of users' Internet traffic, Comcast stands to pay 'up to' $16.00 to every subscriber who makes a claim at their settlement website and declares, under penalty of perjury, that their online activity was for a lawful purpose consistent with applicable copyright and other laws. Robb Topolski, the veteran networking engineer who kicked off the case when he discovered the blocking back in 2007, says that the proposed settlement doesn't make sense, especially after the US Court of Appeals for the District of Columbia Circuit ruled this month that the US Federal Communications Commission didn't have the authority to enforce its Net neutrality principles on Comcast. 'You paid about $50 a month for the service, and the amount that Comcast stands to return is up to about 50c per month for each month that it blocked traffic,' he wrote. 'If that tiny amount of money is compensation, then there is no penalty to Comcast for interfering with its customers, for failing to disclose it, for repeatedly lying about it, and for taking so long to stop it.' The Associated Press and the Electronic Frontier Foundation, in late 2007, each independently confirmed Topolski's reports that Comcast was blocking BitTorrent and some other traffic without telling its customers. Comcast first denied interfering with traffic, then finally said it throttled some applications only during times of peak congestion. However, studies from the Max Planck Institute for Software Systems in Germany eventually proved that Comcast slowed BitTorrent traffic around the clock."

funchords writes "As a settlement to the class-action lawsuits over Comcast's blocking of users' Internet traffic, Comcast stands to pay 'up to' $16.00 to every subscriber who makes a claim at their settlement website and declares, under penalty of perjury, that their online activity was for a lawful purpose consistent with applicable copyright and other laws. Robb Topolski, the veteran networking engineer who kicked off the case when he discovered the blocking back in 2007, says that the proposed settlement doesn't make sense, especially after the US Court of Appeals for the District of Columbia Circuit ruled this month that the US Federal Communications Commission didn't have the authority to enforce its Net neutrality principles on Comcast. 'You paid about $50 a month for the service, and the amount that Comcast stands to return is up to about 50c per month for each month that it blocked traffic,' he wrote. 'If that tiny amount of money is compensation, then there is no penalty to Comcast for interfering with its customers, for failing to disclose it, for repeatedly lying about it, and for taking so long to stop it.' The Associated Press and the Electronic Frontier Foundation, in late 2007, each independently confirmed Topolski's reports that Comcast was blocking BitTorrent and some other traffic without telling its customers. Comcast first denied interfering with traffic, then finally said it throttled some applications only during times of peak congestion. However, studies from the Max Planck Institute for Software Systems in Germany eventually proved that Comcast slowed BitTorrent traffic around the clock."

An anonymous reader writes "The joint comment filed by the Motion Picture Association of America (MPAA) and the Recording Industry Association of America (RIAA) requests anti-infringement software on all home computers, pervasive copyright filtering, border searches, forced US intellectual property policies on foreign nations and a joint departmental agency to combat infringement during major releases." The MPAA would also like to have its rent paid a bit by Congress, with a ban on what seems to me like a useful tool (for those in as well as outside the film industry), the recently-discussed futures market for box-office receipts.