Slashdot Mirror

ewsnow writes "The Focus Fusion Society reports that the scientists and engineers at Lawrenceville Plasma Physics have finally built an operational Dense Plasma Focus device. While still at less than half power, they were able to achieve a pinch on their device. The small company that Eric Lerner started recently gathered enough funding to start a two-year study on the validity of his theory regarding fusion-inducing plasmoids. If the theory holds, the device will produce more electricity than it consumes. In contrast to the billions of dollars spent on Tokamak fusion (think ITER), LPP is conducting their research on a budget around a million dollars. Yet, if it works, it will provide nuclear fusion with much simpler equipment and much less cost. Eric Lerner and Focus Fusion have been discussed on Slashdot before."

The Installer writes "Wizards of the Coast is in the process of settling its claim against several individuals for illegal distribution of its newest copyrighted handbook. 'In one of three lawsuits brought by Wizards of the Coast LLC, a subsidiary of Hasbro Inc., US District Judge Thomas S. Zilly on Friday accepted a settlement in which Thomas Patrick Nolan of Milton, Fla., agreed to a judgment against him of $125,000.' These were the lawsuits that went along with WotC's decision to stop selling the handbook in .PDF format. 'According to court filings, more than 2,600 copies of the handbook were downloaded from Scribd.com, and more than 4,200 copies were viewed online before the material was pulled from the document-sharing site at Wizards' request.'"

ZosX writes "Around 11:45 PM Friday night, I was prompted by Firefox that it had disabled the addons that Microsoft has been including with .NET — specifically, the .NET Framework Assistant and the Windows Presentation Foundation. The popup announcing this said that the 'following addons have been known to cause stability or security issues with Firefox.' Thanks, Mozilla team, for hitting the kill switch and hopefully this will get Microsoft to release a patch sooner." Here's the Mozilla security blog entry announcing the block, which Mozilla implemented via its blocklisting mechanism.

ZosX writes "Around 11:45 PM Friday night, I was prompted by Firefox that it had disabled the addons that Microsoft has been including with .NET — specifically, the .NET Framework Assistant and the Windows Presentation Foundation. The popup announcing this said that the 'following addons have been known to cause stability or security issues with Firefox.' Thanks, Mozilla team, for hitting the kill switch and hopefully this will get Microsoft to release a patch sooner." Here's the Mozilla security blog entry announcing the block, which Mozilla implemented via its blocklisting mechanism.

Hugh Pickens writes "The president of the Maldives and 11 ministers, decked out in scuba gear, held a cabinet meeting 4m underwater to highlight the threat of global warming to the low-lying Indian Ocean nation. While officials said the event itself was light-hearted, the idea is to focus on the plight of the Maldives, where rising sea levels threaten to make the nation uninhabitable by the end of the century. President Mohamed Nasheed and his cabinet spent half an hour on the sea bed, communicating with white boards and hand signals and signed a document calling for global cuts in carbon emissions. The Maldives has already begun to divert a portion of the country's billion-dollar annual tourist revenue to buy a new homeland as an insurance policy against climate change that threatens to turn the 300,000 islanders into environmental refugees. Emerging out of the water, a dripping President Nasheed removed his mask to answer questions from reporters and photographers crowded around on the shore. 'We are trying to send a message to the world about what is happening and what would happen to the Maldives if climate change isn't checked,' he said, bobbing around in the water with his team of ministers. 'If the Maldives is not saved, today we do not feel there is much chance for the rest of the world.'"

holy_calamity writes "Remember Microsoft's camera to be slung around the necks of people with Alzheimer's to help them recall where they'd been? A version of this device will now be mass-produced by a UK firm, Vicon, which obtained a license from Microsoft to manufacture the camera. It is worn around the neck and takes an image every thirty seconds, or in response to its light sensor, accelerometer, or body-heat sensor indicating that something of interest may be happening. Until now only a few hundred had been made for research, which showed they can genuinely help people with memory problems. The new version will be marketed to Alzheimer's researchers this winter, and to consumers for 'lifelogging' beginning in 2010."

theodp writes "Among those charged in the largest hedge-fund insider trading case in US history was IBM Sr. VP Robert W. Moffat, the heir apparent to IBM CEO Sam Palmisano and the guy behind Big Blue's 'workforce rebalancing' and the sale of IBM's PC unit to Lenovo. IBM's not talking about the incident, but it's interesting that Moffat's bio is MIA at IBM.com ('Biography you tried to access does not exist.'), and his Smarter Planet video can no longer be found ('This video has been removed by the user.') at IBM's YouTube Channel. Do you need approval from the Feds before tidying up after someone who's under investigation? BTW, if stories and comments appearing in the Times Herald-Record and Poughkeepsie Journal are any indication, Moffat may want to avoid a local jury trial. 'I have talked to a few IBMers today, and there seems to be a lot of cheering in the halls of IBM over his arrest,' said Lee Conrad of Alliance@IBM."

uuddlrlrab writes "A group of 72 Democratic lawmakers is the latest to question the US Federal Communications Commission's move to create new net neutrality regulations. Democrats, including US President Barack Obama, have generally supported new rules that would prohibit broadband providers from selectively blocking or slowing Web content, but the group of 72 members of the House of Representatives sent a letter Thursday to FCC Chairman Julius Genachowski, saying they're concerned that new regulations would slow down investment in broadband networks. A coalition of minority groups made their objections known as well, saying, 'We are concerned that some of the proposed regulations on the Internet could, as applied, inhibit the goal of universal access and leave disenfranchised communities further behind.' This follows news from earlier in the week that similar letters were sent by a group of 44 tech companies and a group of 18 Republican senators." It's worth noting that the FCC is receiving letters in support of the net neutrality regulations as well. One such is from a group of internet pioneers, which includes Vint Cerf and Stephen Crocker.

Hugh Pickens writes "The Los Angeles Times reports that California regulators are poised to pass the nation's first ban on energy-hungry big-screen televisions just as they did with refrigerators, air conditioners and dozens of other products since the 1970s. 'We would not propose TV efficiency standards if we thought there was any evidence in the record that they will hurt the economy,' said Commissioner Julia Levin, who has been in charge of the two-year rule-making procedure. 'This will actually save consumers money and help the California economy grow and create new clean, sustainable jobs.' California's estimated 35 million TVs and related electronic devices account for about 10% of all household electricity consumption, but manufacturers quickly are coming up with new technologies that are making even 50-inch-screen models much more economical to operate. Sets with screens of up to 58 inches would have until the start of 2011 to comply with a minimum efficiency standard, with more stringent rules being introduced two years later. If all TVs met state standards, California could avoid the $600-million cost of building a natural-gas-fired power plant, says Ken Rider, a commission staff engineer. Switching to more-efficient TVs could have an estimated net benefit to the state of $8.1 billion, the commission staff reported."

Smelly Jeffrey writes "The BBC is reporting that the LHC has had all eight of its sectors cooled to 1.9 Kelvin. Their tagline is that it is now 'colder than deep space,' referring to the CMB. LHC engineers have spent nearly $40,000,000 USD on a new system to prevent the 'quench' condition that caused the LHC to be down for warming, repairs, and re-cooling over the last year. The LHC is now cold enough to begin colliding particles in search of the Higgs Boson. High power collisions won't be started until late December, or perhaps early January. However, a low-power beam through parts of the collider could be tested as early as next week!"

SpaceGhost sends in a story from San Antonio, TX: "Police have arrested a 16-year-old girl on charges of harassment under a new Texas law that took effect September 1, 2009. H.B. 2003 says a person commits a third degree felony if the person posts one or more messages on a social networking site with the intent to harm, defraud, intimidate or threaten another person. Police say the harassment went on for a few months and involved a dispute over a boy. ... Some people expect legal challenges to the constitutionality of the new Internet law.' The law is evidently a response to the Lori Drew case.

nandemoari writes "T-Mobile is taking a huge financial hit in the fallout over the Sidekick data loss. But Microsoft, which bears at least part of the responsibility for the mistake, is paying the price with its reputation. As reported earlier this week, the phone network had to admit that some users' data had been permanently lost due to a problem with a server run by Microsoft-owned company Danger. The handset works by storing data such as contacts and appointments on a remote computer rather than on the phone itself. BBC news reports today that Microsoft has in fact recovered all data, but a minority are still affected (out of 1 million subscribers). Amidst this, Microsoft appears not to have suffered any financial damage. However, it seems certain that its relationship with T-Mobile will have taken a major knock. The software giant is also the target of some very bad publicity as critics question how on earth it failed to put in place adequate back-ups of the data. That could seriously damage the potential success of the firm's other 'cloud computing' plans, such as web-only editions of Office."

babboo65 writes "Dungeons and Dragons Online is enjoying a second life in terms of player count and buzz, all thanks to its new business strategy: giving the game away. Turbine is making their MMO as accessible as possible, and that includes making players who don't pay anything as happy as possible. Subscriptions are up 40 percent. Ars explores how free can be very profitable."

bennyboy64 writes "iTnews reports the patent battle between Australia's CSIRO and 14 of the world's largest technology companies has gained the research organization $200 million from out of court settlements. CSIRO executive director of commercial, Nigel Poole, said the CSIRO were wanting to license their technology further, stating that he 'urged' companies using it to come forward and seek a license. 'We believe that there are many more companies that are using CSIRO's technology and it's our desire to license the technology further,' Poole said.'We would urge companies that are currently selling devices that have 802.11 a,g or n to contact CSIRO and to seek a license because we believe they are using our technology.'"

Vigile writes "When you sell over 100 million handheld gaming systems, everyone wants to be involved in your success; just ask Nintendo. As a company with many different obstacles in its path, NVIDIA could definitely use the boost in revenues that would come from partnering with a company like Nintendo on a handheld system, and it looks like the Tegra processor will make that happen. The NVIDIA Tegra processor is an SoC that runs a set of ARM cores, a GeForce-based graphics core and an HD video processor capable of 1080p output that would definitely give the current Nintendo DS/DSi systems a performance boost in line with the Sony PSP. The 'Nintendo TS,' as it has been dubbed, will apparently be ready for a late winter 2010 release and should put a spark in the mobile gaming market and give Nintendo's developers the power to bring higher quality games to the platform."

Ponca City, We love you writes "The EFF has warned Texas Instruments not to pursue legal threats against calculator hobbyists who perform modifications to the company's programmable graphing calculators. TI's calculators perform a 'signature check' that allows only approved operating systems to be loaded, but researchers have reverse-engineered signing keys, allowing tinkerers to install custom operating systems and unlock new functionality in the calculators' hardware. In response, TI has unleashed a torrent of demand letters claiming that the anti-circumvention provisions of the Digital Millennium Copyright Act require the hobbyists to take down commentary about and links to the keys. 'This is not about copyright infringement. This is about running your own software on your own device — a calculator you legally bought,' says EFF Civil Liberties Director Jennifer Granick. 'Yet TI still issued empty legal threats in an attempt to shut down discussion of this legitimate tinkering. Hobbyists are taking their own tools and making them better, in the best tradition of American innovation.'"

plover writes "Kim Zetter of Wired documents an extensive hack of Wal-Mart that took place in 2005-2006. She goes into great detail about the investigation and what the investigators found, including that the hackers made copies of their point-of-sale source code, and that they ran l0phtCrack on a Wal-Mart server. 'Wal-Mart uncovered the breach in November 2006, after a fortuitous server crash led administrators to a password-cracking tool that had been surreptitiously installed on one of its servers. Wal-Mart's initial probe traced the intrusion to a compromised VPN account, and from there to a computer in Minsk, Belarus.' Wal-mart has long since fixed the flaws that allowed the compromise, and confirmed that no customer data was lost in the hack — which is why they did not need to report the breach publicly earlier." This intrusion happened around the same time that Albert Gonzalez's gang was breaking into Marshall's and its parent company, TJX. The MO was quite similar: researching and closely targeting the point-of-sale systems in use. But the article notes that "There's no evidence Wired.com has seen linking Gonzalez to the Wal-Mart breach."

xander_zone_xxx writes with news that Ray Beckerman, known around here as NewYorkCountryLawyer, was not a "vexatious" litigant, as the RIAA claimed. In the same ruling the judge dismissed Beckerman's counter-claims against the RIAA. (We discussed the claims and counters a year back.) "An attorney defending against a music-piracy lawsuit didn't cross ethical bounds by filing motions broadly attacking the recording industry and posting them on his blog, a magistrate judge has ruled, rejecting demands from the RIAA for monetary sanctions. Attorney Ray Beckerman was 'less than forthcoming at times' in defending a client against an RIAA lawsuit, but the music industry's concerns were 'largely overstated,' New York Magistrate Judge Robert M. Levy wrote Friday."

xander_zone_xxx writes with news that Ray Beckerman, known around here as NewYorkCountryLawyer, was not a "vexatious" litigant, as the RIAA claimed. In the same ruling the judge dismissed Beckerman's counter-claims against the RIAA. (We discussed the claims and counters a year back.) "An attorney defending against a music-piracy lawsuit didn't cross ethical bounds by filing motions broadly attacking the recording industry and posting them on his blog, a magistrate judge has ruled, rejecting demands from the RIAA for monetary sanctions. Attorney Ray Beckerman was 'less than forthcoming at times' in defending a client against an RIAA lawsuit, but the music industry's concerns were 'largely overstated,' New York Magistrate Judge Robert M. Levy wrote Friday."

An anonymous reader tips news that Blizzard will be requiring all World of Warcraft players to use Battle.net accounts to log into the game starting on November 11th. After that time, players who don't switch will be unable to play the game. Some time after the transition is complete, players will be able to "participate in cross-realm chat in World of Warcraft, create real-life friends lists, and communicate across different games." More details on the new Battle.net and what it will do are available in our Blizzcon wrap-up and interviews from August. Naturally, the idea that the new Battle.net is getting closer to deployment has sparked speculation that the StarCraft II beta might come along soon.

An anonymous reader tips news that Blizzard will be requiring all World of Warcraft players to use Battle.net accounts to log into the game starting on November 11th. After that time, players who don't switch will be unable to play the game. Some time after the transition is complete, players will be able to "participate in cross-realm chat in World of Warcraft, create real-life friends lists, and communicate across different games." More details on the new Battle.net and what it will do are available in our Blizzcon wrap-up and interviews from August. Naturally, the idea that the new Battle.net is getting closer to deployment has sparked speculation that the StarCraft II beta might come along soon.

stoolpigeon writes "Google's mobile OS Android has received plenty of press. As with a lot of Google products, there was much anticipation before any devices were even available. Now a number of phones are available, with many more coming out world-wide in the near future. Part of the lure of Android is the openness of the platform and the freely available tools for development. The SDK and accompanying Eclipse plug-in give the would be creator of the next great Android application everything they need to make their idea reality. The bar to entry in the official Google Android Marketplace is very low and it doesn't seem to be much of a stretch to predict that the number of developers working on Android is only going to grow. As with any hot technology the number of books will grow as well and O'Reilly's Android Application Development has jumped into the fray, promising to help budding Android developers what they need to get started." Read on for the rest of JR's review. Android Application Development: Programming with the Google SDK author Rick Rogers, John Lombardo, Zigurd Mednieks, Blake Meike pages 332 publisher O'Reilly Media Inc. rating 7/10 reviewer JR Peck ISBN 978-0-596-52147-9 summary Programming with the Google SDK. The book begins with a brief introduction to Android followed by detailed instructions on procuring and installing the Android SDK. Space is given to Windows, Linux and Mac. The install is relatively simple on all three platforms, extra information is provided for Ubuntu users but no others distributions. Extra care is taken to help Windows users with items they may not use regularly, such as environmental variables. This is all pretty basic and gives the book very much of a 'for beginners' feel. Before I had the book I had already installed the SDK and Eclipse plug-in on Windows, Ubuntu and Fedora without any issues beyond getting a current version of Eclipse for the Ubuntu machine. The version I already had from the Ubuntu repositories was not able to run the plug-in. It's a short chapter and if someone really struggles with it, they probably should shift their focus from learning to code to learning how to use their platform of choice. This does set the tone though, that this is a book for those who are very new to development.

Chapter two steps the reader through the ever present "Hello World" and gives an overview of the structure of Android applications. Chapter three introduces the example application that will be used for the rest of the book. There is a lot of repetition here on just what directories and files make up the guts of an Android program. I was quickly worried ( the first four chapters are only fifty-six pages in ) that maybe four authors had been too many. The repetition made it feel as if separate work had been combined without enough editing to remove what was redundant. Fortunately this got better, though there was still a strange proclivity to list files while referring to earlier chapters that explained their purpose. This would be helpful to anyone jumping right into the middle of the book, but the index also serves the same purpose and saves space for more valuable content, as opposed to explaining the purpose of AndroidManifest.xml repeatedly.

Once I moved into the fifth chapter, Debugging Android Applications and the following chapters, things got better. The pace picked up and the repetition dropped off for the most part. The book did not become incredibly difficult, trying to be everything to everyone, but did maintain an introductory style. At the same time the example application makes use of many Android features that are likely to be used by developers. How to set up and use tools was covered step by step. This is very nice but did cause some issues for the authors due to the rapid pace of development on Android. A visit to the book's errata page will show that many readers struggled with changes to the SDK tool set that came out very shortly after the book. The authors say that future editions will fix these issues, but this creates a dilemma for that reader needing introductory level materials. They are more dependent upon the book than a more advanced user and so these issues can be very trying. Based on the responses to the errata posts it became trying for the authors as well. This isn't a knock on the book itself but rather a limitation of the delivery method.

Once the reader is digging down into the example application the team approach to writing the book does become an asset. The authors bring a number of skills to the table that closely resemble the players that would be necessary to a team developing a real-world application. The reader is now being pulled into an example that benefits from the knowledge of each and does a good job of exploring the range of options an Android developer has available. This includes core functionality, UI options and how to best take advantage of the platform while at the same time taking performance and user expectations into account. I felt like I was getting something beyond the excellent documentation provided by Google. This is where I felt the book stood strongest.

Working with a single, large example application was a move that probably helped move things along on writing the book and I think it's an interesting approach. The problem is of course, that means that this example must be right. Right for the task and technically correct. Small issues in the code are inevitable but now their impact is book wide. The changes to the platform just made it just that much more difficult to sort out. On the whole I still found this to be a better approach primarily due to the fact that it gives the features highlighted a better sense of context. Stand-alone examples are often good at highlighting technical features but completely ignore the issues necessary to using the feature in a larger piece of code.

I'm a fan of O'Reilly books. Interestingly enough this doesn't mean that I'll gloss over issues with what they produce. The result is actually the inverse, in that I go into all their titles with a high level of expectation with regards to quality on every level. This may mean that though I strive to be neutral when I look at a book, I'm probably a little tougher on O'Reilly titles. This made my rough start with Android Application Development a bit jarring. The repetition and what felt like sloppy editing are not what I expect. I was quickly given a sense that this book may have been rushed to publication a little sooner than it should have been. As I moved deeper into the book, things improved and while I think there were still editorial issues, things did seem to smooth out to some degree.

There is an interesting tension that exists purely do to the nature of print books. I don't like to bring up print versus electronic in reviews as I don't think it is on topic, but here it is unavoidable. The book is aimed at people that need a little more hand holding and help getting going. It does a good job of providing step by step instructions, the problem is that some of those steps have changed. I don't think anything in the code itself needs to be different, but the tools have changed enough that getting the code to run in a development environment against the new SDK is different. That means that portion of the book is no longer of as much value without going to other sources to find the new steps.

That said, warts and all I found this to be a helpful way to get my feet wet with Android. I really look forward to future versions as I think just a little more time and work will move this from my 'good' list to my 'great' list. Making things a little tighter and cleaning up the few typos and errors would certainly make this an 8 instead of an 7, which is really substantial in my mind. I'm no super developer and I need stuff like this, that can take things a little more slowly and make it all clear. I think this guide is great for those of us in that category as long as the reader is o.k. with hopping to external sources for the information they'll need to get the newer tool set working.

You can purchase Android Application Development: Programming with the Google SDK from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

stoolpigeon writes "Google's mobile OS Android has received plenty of press. As with a lot of Google products, there was much anticipation before any devices were even available. Now a number of phones are available, with many more coming out world-wide in the near future. Part of the lure of Android is the openness of the platform and the freely available tools for development. The SDK and accompanying Eclipse plug-in give the would be creator of the next great Android application everything they need to make their idea reality. The bar to entry in the official Google Android Marketplace is very low and it doesn't seem to be much of a stretch to predict that the number of developers working on Android is only going to grow. As with any hot technology the number of books will grow as well and O'Reilly's Android Application Development has jumped into the fray, promising to help budding Android developers what they need to get started." Read on for the rest of JR's review. Android Application Development: Programming with the Google SDK author Rick Rogers, John Lombardo, Zigurd Mednieks, Blake Meike pages 332 publisher O'Reilly Media Inc. rating 7/10 reviewer JR Peck ISBN 978-0-596-52147-9 summary Programming with the Google SDK. The book begins with a brief introduction to Android followed by detailed instructions on procuring and installing the Android SDK. Space is given to Windows, Linux and Mac. The install is relatively simple on all three platforms, extra information is provided for Ubuntu users but no others distributions. Extra care is taken to help Windows users with items they may not use regularly, such as environmental variables. This is all pretty basic and gives the book very much of a 'for beginners' feel. Before I had the book I had already installed the SDK and Eclipse plug-in on Windows, Ubuntu and Fedora without any issues beyond getting a current version of Eclipse for the Ubuntu machine. The version I already had from the Ubuntu repositories was not able to run the plug-in. It's a short chapter and if someone really struggles with it, they probably should shift their focus from learning to code to learning how to use their platform of choice. This does set the tone though, that this is a book for those who are very new to development.

Chapter two steps the reader through the ever present "Hello World" and gives an overview of the structure of Android applications. Chapter three introduces the example application that will be used for the rest of the book. There is a lot of repetition here on just what directories and files make up the guts of an Android program. I was quickly worried ( the first four chapters are only fifty-six pages in ) that maybe four authors had been too many. The repetition made it feel as if separate work had been combined without enough editing to remove what was redundant. Fortunately this got better, though there was still a strange proclivity to list files while referring to earlier chapters that explained their purpose. This would be helpful to anyone jumping right into the middle of the book, but the index also serves the same purpose and saves space for more valuable content, as opposed to explaining the purpose of AndroidManifest.xml repeatedly.

Once I moved into the fifth chapter, Debugging Android Applications and the following chapters, things got better. The pace picked up and the repetition dropped off for the most part. The book did not become incredibly difficult, trying to be everything to everyone, but did maintain an introductory style. At the same time the example application makes use of many Android features that are likely to be used by developers. How to set up and use tools was covered step by step. This is very nice but did cause some issues for the authors due to the rapid pace of development on Android. A visit to the book's errata page will show that many readers struggled with changes to the SDK tool set that came out very shortly after the book. The authors say that future editions will fix these issues, but this creates a dilemma for that reader needing introductory level materials. They are more dependent upon the book than a more advanced user and so these issues can be very trying. Based on the responses to the errata posts it became trying for the authors as well. This isn't a knock on the book itself but rather a limitation of the delivery method.

Once the reader is digging down into the example application the team approach to writing the book does become an asset. The authors bring a number of skills to the table that closely resemble the players that would be necessary to a team developing a real-world application. The reader is now being pulled into an example that benefits from the knowledge of each and does a good job of exploring the range of options an Android developer has available. This includes core functionality, UI options and how to best take advantage of the platform while at the same time taking performance and user expectations into account. I felt like I was getting something beyond the excellent documentation provided by Google. This is where I felt the book stood strongest.

Working with a single, large example application was a move that probably helped move things along on writing the book and I think it's an interesting approach. The problem is of course, that means that this example must be right. Right for the task and technically correct. Small issues in the code are inevitable but now their impact is book wide. The changes to the platform just made it just that much more difficult to sort out. On the whole I still found this to be a better approach primarily due to the fact that it gives the features highlighted a better sense of context. Stand-alone examples are often good at highlighting technical features but completely ignore the issues necessary to using the feature in a larger piece of code.

I'm a fan of O'Reilly books. Interestingly enough this doesn't mean that I'll gloss over issues with what they produce. The result is actually the inverse, in that I go into all their titles with a high level of expectation with regards to quality on every level. This may mean that though I strive to be neutral when I look at a book, I'm probably a little tougher on O'Reilly titles. This made my rough start with Android Application Development a bit jarring. The repetition and what felt like sloppy editing are not what I expect. I was quickly given a sense that this book may have been rushed to publication a little sooner than it should have been. As I moved deeper into the book, things improved and while I think there were still editorial issues, things did seem to smooth out to some degree.

There is an interesting tension that exists purely do to the nature of print books. I don't like to bring up print versus electronic in reviews as I don't think it is on topic, but here it is unavoidable. The book is aimed at people that need a little more hand holding and help getting going. It does a good job of providing step by step instructions, the problem is that some of those steps have changed. I don't think anything in the code itself needs to be different, but the tools have changed enough that getting the code to run in a development environment against the new SDK is different. That means that portion of the book is no longer of as much value without going to other sources to find the new steps.

That said, warts and all I found this to be a helpful way to get my feet wet with Android. I really look forward to future versions as I think just a little more time and work will move this from my 'good' list to my 'great' list. Making things a little tighter and cleaning up the few typos and errors would certainly make this an 8 instead of an 7, which is really substantial in my mind. I'm no super developer and I need stuff like this, that can take things a little more slowly and make it all clear. I think this guide is great for those of us in that category as long as the reader is o.k. with hopping to external sources for the information they'll need to get the newer tool set working.

You can purchase Android Application Development: Programming with the Google SDK from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

We recently redesigned the Submission Form to make it (hopefully) a little easier for you to shovel news our way. The new system also will allow you to tag your submissions. A reminder that you can participate in rating stories and filtering spam from the recent submissions page. And by bookmarking this convenient bookmarklet you can submit stories from the comfort of whatever web page you are browsing.

miller60 writes "There's a vigorous debate among cloud pundits about whether the apparent loss of all Sidekick users' data is a reflection on the trustworthiness of cloud computing or simply another cautionary tale about poor backup practices. InformationWeek calls the incident 'a code red cloud disaster.' But some cloud technologists insist data center failures are not cloud failures. Is this distinction meaningful? Or does the cloud movement bear the burden of fuzzy definitions in assessing its shortcomings as well as its promise?"

miller60 writes "There's a vigorous debate among cloud pundits about whether the apparent loss of all Sidekick users' data is a reflection on the trustworthiness of cloud computing or simply another cautionary tale about poor backup practices. InformationWeek calls the incident 'a code red cloud disaster.' But some cloud technologists insist data center failures are not cloud failures. Is this distinction meaningful? Or does the cloud movement bear the burden of fuzzy definitions in assessing its shortcomings as well as its promise?"

sevarac writes "The latest release of Java Neural Network Framework Neuroph v2.3 comes with ready-to-use image recognition support. It provides GUI tool for training multi layer perceptrons for image recognition, and an easy-to-use API to deploy these neural networks in end-user applications. This image recognition approach has been successfully used by DotA AutoScript tool, and now it is released as open source. With this Java library basic image recognition can be performed in just few lines of code. The developers have published a howto article and an online demo which can be used to train image recognition neural networks online."

An editorial at GamesIndustry takes a look at a couple of problems many MMOs have failed to solve as the genre has evolved over the last decade: log-in queues and a split player base. The most recent example is Aion, which launched in Europe and North America a few weeks ago. Players on some of the game's servers had to deal with lengthy queues until enough people left the starting areas and spread throughout the game. To NCSoft's credit, the queues are mostly gone already, and it wasn't simply launching with too few servers that was the problem (nor was simply launching more servers a perfect solution, as Warhammer proved). In fact, several servers had no queues at all, but many players had set their sights on the more popular ones — a problem facing other MMOs as well. At this point, it becomes a matter of programming — how can the developers for these MMOs build the networking aspect of the game such that more hardware can easily be allocated when it's needed, and also make it easier for people to play together without the restriction of different shards or servers? EVE Online has done well with a single game universe, but it's not clear how far that model can scale upwards.

An editorial at GamesIndustry takes a look at a couple of problems many MMOs have failed to solve as the genre has evolved over the last decade: log-in queues and a split player base. The most recent example is Aion, which launched in Europe and North America a few weeks ago. Players on some of the game's servers had to deal with lengthy queues until enough people left the starting areas and spread throughout the game. To NCSoft's credit, the queues are mostly gone already, and it wasn't simply launching with too few servers that was the problem (nor was simply launching more servers a perfect solution, as Warhammer proved). In fact, several servers had no queues at all, but many players had set their sights on the more popular ones — a problem facing other MMOs as well. At this point, it becomes a matter of programming — how can the developers for these MMOs build the networking aspect of the game such that more hardware can easily be allocated when it's needed, and also make it easier for people to play together without the restriction of different shards or servers? EVE Online has done well with a single game universe, but it's not clear how far that model can scale upwards.

Expanding on the T-Mobile data loss mentioned in an update to an earlier story, reader stigmato writes "T-Mobile's popular Sidekick brand of devices and their users are facing a data loss crisis. According to the T-Mobile community forums, Microsoft/Danger has suffered a catastrophic server failure that has resulted in the loss of all personal data not stored on the phones. They are advising users not to turn off their phones, reset them or let the batteries die in them for fear of losing what data remains on the devices. Microsoft/Danger has stated that they cannot recover the data but are still trying. Already people are clamoring for a lawsuit. Should we continue to trust cloud computing content providers with our personal information? Perhaps they should have used ZFS or btrfs for their servers."

Darren Ginter writes "A group of Samba v4 developers recently spent a week in Redmond to work with Microsoft on Active Directory interoperability(?!). The result? Windows Server will now join, trust and replicate a Samba-based Active Directory using Microsoft-native protocols. Although Samba v4 is still in the alpha stages, this is a huge step for open source. Or it could be a trap."

An anonymous reader writes "A lengthy interview on Groklaw discusses the EU's case against Microsoft. The case is supported by Opera, Google, Mozilla, ECIS, and the Free Software Foundation Europe. The EU has demanded that users be offered a 'ballot screen' to make it easier for users to select other browsers. Microsoft has responded by implementing the ballot screen as a web page inside IE. While this may nominally satisfy EU's demand, it is unlikely to satisfy users who prefer other browsers. In order to select another browser, users must be running IE. Also, users will be shown security warnings when choosing from the ballot. Microsoft's ability to charge patent fees in Europe is also discussed: why are they allowed to charge patent fees where software patents are not recognized?"

Absolut187 writes "Gearbox Software CEO Randy Pitchford says Steam's domination of digital distribution is 'dangerous,' and exploits small developers. 'Steam helps us as customers, but it's also a money grab, and Valve is exploiting a lot of people in a way that's not totally fair. ... Valve is taking a larger share than it should for the service it's providing. ... There's so much conflict of interest there that it's horrid.' Pitchford's comments came as part of an interview with Maximum PC, and he thinks Valve should spin off Steam to its own company. Is he right? Is there a better answer?" Update: 10/10 at 02:00 GMT by SS: Randy has clarified his remarks in a comment here at Slashdot. He makes it clear that he likes Steam a lot, and for several reasons, but thinks stronger competition would benefit the industry as a whole.

Over the past few months, we've been following the FCC's inquiry into Apple and AT&T after they rejected Google Voice from the App store. A couple weeks ago, AT&T did their best to deflect the FCC by dangling a shiny object in front of them — the use of Google Voice to block calls. It now appears the FCC has taken the bait, as they've sent an official inquiry to Google asking why the service restricts connections. "In its letter, the FCC asked Google to describe how its calls are routed and whether calls to particular numbers are prohibited. It also asks for information on how restrictions are implemented, how Google informs customers about those restrictions, whether Google Voice services are free, and if Google ever plans to charge for them in the future." Richard Whitt has already posted a brief explanation on Google's Public Policy blog. "The reason we restrict calls to certain local phone carriers' numbers is simple. Not only do they charge exorbitant termination rates for calls, but they also partner with adult sex chat lines and 'free' conference calling centers to drive high volumes of traffic." The FCC also received a push from members of the House of Representatives on Wednesday.

Over the past few months, we've been following the FCC's inquiry into Apple and AT&T after they rejected Google Voice from the App store. A couple weeks ago, AT&T did their best to deflect the FCC by dangling a shiny object in front of them — the use of Google Voice to block calls. It now appears the FCC has taken the bait, as they've sent an official inquiry to Google asking why the service restricts connections. "In its letter, the FCC asked Google to describe how its calls are routed and whether calls to particular numbers are prohibited. It also asks for information on how restrictions are implemented, how Google informs customers about those restrictions, whether Google Voice services are free, and if Google ever plans to charge for them in the future." Richard Whitt has already posted a brief explanation on Google's Public Policy blog. "The reason we restrict calls to certain local phone carriers' numbers is simple. Not only do they charge exorbitant termination rates for calls, but they also partner with adult sex chat lines and 'free' conference calling centers to drive high volumes of traffic." The FCC also received a push from members of the House of Representatives on Wednesday.

theodp writes "Microsoft's Open Value Subscription offering didn't get the warmest reception. Nor did the follow-up announcement of Albany, a planned MS-Office Subscription Service. Now comes word from the USPTO that Microsoft feels it deserves a patent for the 'invention' of 'Time-Based Licensing,' which aims to make the traditional pay-once perpetual license model a thing of the past. Hey, if your customers were waiting nine years between OS upgrades, you'd try touting a three-year lease with a balloon buy-out payment, too!"

theodp writes "Microsoft's Open Value Subscription offering didn't get the warmest reception. Nor did the follow-up announcement of Albany, a planned MS-Office Subscription Service. Now comes word from the USPTO that Microsoft feels it deserves a patent for the 'invention' of 'Time-Based Licensing,' which aims to make the traditional pay-once perpetual license model a thing of the past. Hey, if your customers were waiting nine years between OS upgrades, you'd try touting a three-year lease with a balloon buy-out payment, too!"

eldavojohn writes "BoingBoing is reporting that, allegedly, Carl Sagan wrote a piece for 'Marihuana Reconsidered' under the pseudonym Mr. X that appears to look fondly upon the science of trippin' balls. Puff the Magic Sagan's full piece can be found here. It opens with 'It all began about ten years ago. I had reached a considerably more relaxed period in my life — a time when I had come to feel that there was more to living than science, a time of awakening of my social consciousness and amiability, a time when I was open to new experiences.' Too bad old Mr. Cosmos couldn't enjoy his latest vocals."

The rumor that we discussed a few months back is looking more real. Vigile writes "Once the darling of the enthusiast chipset market, NVIDIA has apparently decided to quit development of future chipsets for all platforms. This 'state of NVIDIA' editorial at PC Perspective first highlighted the fact that the company was backing away from its plans to develop a DMI-based chipset for Intel's Lynnfield processors due to legal pressure from Intel and debates over licensing restrictions. That effectively left NVIDIA out in the cold in terms of high-end chipsets, but even more interesting is the later revelation that NVIDIA has only one remaining chipset product to release, what we know as ION 2, and that it was mainly built for Apple's upcoming products. NVIDIA still plans to sell its current offerings, like MCP61 for AMD platforms and current generation ION for netbooks and nettops, but will focus solely on discrete graphics options after this final release."

Last month we discussed news that Valve's upcoming shooter Left 4 Dead 2 had been denied classification in Australia, which meant the game could not be legally sold there. Now, after a series of edits which removed "considerable amounts of gore from gameplay," Australia's classification board has given the game an MA15+ rating. Their new report (PDF) says, "No wound detail is shown and the implicitly dead bodies and blood splatter disappear as they touch the ground. ... The board notes that the game no longer contains depictions of decapitation, dismemberment, wound detail or piles of dead bodies lying about the environment." The unmodified version of the game may still be approved, pending a review that concludes on October 22nd.

Joren writes "In Japan, in a case that has been five years running, the Osaka High Court on Thursday overturned a lower court ruling that had convicted and fined the developer of controversial file-sharing software Winny of assisting violations of the Copyright Law. Originally charged in 2004, Isamu Kaneko, 39, a former research assistant at the University of Tokyo, was declared not guilty, and will not be required to pay a 1.5 million yen fine levied by a December 2006 Kyoto District Court ruling. 'Merely being aware of the possibility that the software could be abused does not constitute a crime of aiding violations of the law, and the court cannot accept that the defendant supplied the software solely to be used for copyright violations,' presiding judge Masazo Ogura said. Furthermore, in siding with the defense, the appeal ruling stated that 'Anonymity is not something to be looked on as illegal, and it is not something that applies specifically to copyright violations. The technical value of the software is neutral.'"

Dotnaught writes "Solid Oak Software, maker of Internet filter CYBERsitter, on Monday filed a $1.2 million copyright infringement lawsuit against CBS Interactive's ZDNet China for distributing the Green Dam Internet filtering software. Green Dam was going to be mandatory on all PCs in China starting in July, but widespread criticism, including reports of stolen code, forced the Chinese government to reconsider. The lawsuit, if it succeeds, could force companies to give more thought to the risks of complying with mandates from foreign governments that violate US laws."

Dotnaught writes "Solid Oak Software, maker of Internet filter CYBERsitter, on Monday filed a $1.2 million copyright infringement lawsuit against CBS Interactive's ZDNet China for distributing the Green Dam Internet filtering software. Green Dam was going to be mandatory on all PCs in China starting in July, but widespread criticism, including reports of stolen code, forced the Chinese government to reconsider. The lawsuit, if it succeeds, could force companies to give more thought to the risks of complying with mandates from foreign governments that violate US laws."

Reader oranghutan brings us another in Computerworld's series of interviews with icons of the programming world, this one with Brian Kernighan, who helped popularize C with his book (co-written with the creator Dennis Ritchie) The C Programming Language, and contributed to the development of AWK and AMPL. In the past we've chewed over a few other interviews in this series, including those with Martin Odersky on Scala and Larry Wall on perl. "In this interview, Brian Kernighan shares his tips for up-and-coming programmers and his thoughts on Ruby, Perl, and Java. He also discusses whether the classic book The Practice of Programming, co-written with Rob Pike, needs an update. He highlights Bill and Melinda Gates as two people doing great things for the world enabled through computer science. Some quotes: 'A typical programmer today spends a lot of time just trying to figure out what methods to call from some giant package and probably needs some kind of IDE like Eclipse or XCode to fill in the gaps. There are more languages in regular use and programs are often distributed combinations of multiple languages. All of these facts complicate life, though it's possible to build quite amazing systems quickly when everything goes right.' 'Every language teaches you something, so learning a language is never wasted, especially if it's different in more than just syntactic trivia.'"

Reader oranghutan brings us another in Computerworld's series of interviews with icons of the programming world, this one with Brian Kernighan, who helped popularize C with his book (co-written with the creator Dennis Ritchie) The C Programming Language, and contributed to the development of AWK and AMPL. In the past we've chewed over a few other interviews in this series, including those with Martin Odersky on Scala and Larry Wall on perl. "In this interview, Brian Kernighan shares his tips for up-and-coming programmers and his thoughts on Ruby, Perl, and Java. He also discusses whether the classic book The Practice of Programming, co-written with Rob Pike, needs an update. He highlights Bill and Melinda Gates as two people doing great things for the world enabled through computer science. Some quotes: 'A typical programmer today spends a lot of time just trying to figure out what methods to call from some giant package and probably needs some kind of IDE like Eclipse or XCode to fill in the gaps. There are more languages in regular use and programs are often distributed combinations of multiple languages. All of these facts complicate life, though it's possible to build quite amazing systems quickly when everything goes right.' 'Every language teaches you something, so learning a language is never wasted, especially if it's different in more than just syntactic trivia.'"

An anonymous reader writes "Nine weeks after Moxie Marlinspike presented at Defcon 17, null-prefix certificates that exploit the SSL certificate vulnerability are beginning to appear. Yesterday, someone posted a null-prefix certificate for www.paypal.com on the full-disclosure mailing list. In conjunction with sslsniff, this certificate can be used to intercept communication to PayPal from all clients using the Windows Crypto API, for which a patch is still not available. This includes IE, Chrome, and Safari on Windows. What's worse, because of the OCSP attack that Moxie also presented at Defcon, this certificate cannot be revoked." Update: 10/06 23:19 GMT by KD: Now it seems that PayPal has suspended Marlinspike's account.

vinodis and several other readers sent along the news that Eolas is suing 23 companies including Apple and Google for patent infringement. The company won $585M from Microsoft in a drawn-out, 9-year battle that the companies settled in 2007; in the course of it the USPTO upheld the "906" patent several times. Now, Eolas is also in possession of a newly-issued patent that they claim covers the use of any browser plugin with AJAX. Let's see how far this lawsuit gets before the Supreme Court plays its wildcard in the Bilski case, which we have been discussing for a while now.

vinodis and several other readers sent along the news that Eolas is suing 23 companies including Apple and Google for patent infringement. The company won $585M from Microsoft in a drawn-out, 9-year battle that the companies settled in 2007; in the course of it the USPTO upheld the "906" patent several times. Now, Eolas is also in possession of a newly-issued patent that they claim covers the use of any browser plugin with AJAX. Let's see how far this lawsuit gets before the Supreme Court plays its wildcard in the Bilski case, which we have been discussing for a while now.

ChiefMonkeyGrinder writes "This summer, the London Stock Exchange decided to move away from its Microsoft .Net-based trading platform, TradElect. Instead, they'll be using the GNU/Linux-based MillenniumIT system. The switch is a pretty savage indictment of the costs of a complex .Net system. The GNU/Linux-based software is also faster, and offers several other major benefits. The details provide some fascinating insights into the world of very high performance — and very expensive — enterprise systems. ... [R]ather than being just any old deal that Microsoft happened to lose, this really is something of a total rout, and in an extremely demanding and high-profile sector. Enterprise wins for GNU/Linux don't come much better than this."

Per Wigren writes in with news that Palm has just announced a number of changes to its webOS development platform that should really be welcomed by developers — especially after the chilly reception that Palm seemed to be giving to open source in recent days. OSnews notes that "This moves the webOS much closer to Android territory." Quoting TechCrunch: "The first is that they're allowing developers to fully distribute their apps via the web. What this means is that developers can simply submit their apps to Palm, and Palm will return to them a URL that they can then blog, tweet, do whatever they want to share it. When a person then clicks on that URL they can easily install the app, bypassing any kind of store. And while Palm is providing the URL, it is not going to be reviewing the apps in any way — a clear dig at Apple's approval process. The next announcement is that Palm is waiving the $99 yearly fee it normally charges to developers to make webOS apps if those apps are going to be open source."