Slashdot Mirror

frisket writes "Definitive guides by the authors or maintainers of software systems tend to have the edge over other documentation because of the insight they provide. DocBook 5 — The Definitive Guide comes well up to scratch. DocBook has long been the de facto standard for computer system documentation in XML (and SGML before that), and Norm Walsh has revised and updated both the language and the documentation in a concise and valuable form, usable both by beginners and by tech doc experts." Read on for the rest of frisket's review. DocBook 5: The Definitive Guide author Norman Walsh pages 560 publisher O'Reilly in conjunction with XML Press rating 9/10 reviewer frisket ISBN 9780596805029 summary Examines and catalogs the entirety of the DocBook specification. DocBook is a rich XML vocabulary, primarily for the documentation of software systems. It provides markup both for the structure of your documents and for the descriptive detail of your writing, to an extent that few other XML systems match. Like XML itself, DocBook's popularity rests on its robustness, scope, and extensibility; and Walsh makes it clear that the Technical Committee has tried hard to balance stability and adaptability in releasing a new major version which does have a few backward-incompatible changes.

This is a reference book, so the initial chapters (1-5) are short (70 pages) but full of clear explanations of how DocBook works, what it does, and how to use it. Part II is 400 pages, covering every element type in the language, with a detailed description of what it is for, how and where to use it, and how it interacts with everything else. Both for the beginner and the expert, these descriptions are the key to effective use, and Walsh's explanations are clear and comprehensive.

For those of you who have been using DocBook in earlier incarnations, the changes are not deal-breakers, and many of them are welcome rationalizations of the way things have grown organically over the years. It still walks like a duck and quacks like a duck (and the book still has a duck on the cover), so it immediately feels like the same format that you're used to — the changes to element types are relatively few. Chapter 1 (Getting Started) has a brief history, a summary of the changes, and an explanation of the namespace and availability.

If you've never used DocBook before, its structure will still be familiar: in Chapter 2 (Creating DocBook Documents) Walsh explains the division of reference material like books, articles, and manuals into chapters, sections, and subsections, with all the conventional features like lists, figures, tables, and references, as well as the technically-oriented features like equations, programming constructs, interface descriptions, and code samples.

There is help in Chapter 3 (Validation) for those who construct or generate DocBook documents without the use of an XML editor (or even with them: more on editors below). The most common problems with misplaced markup (and the error messages they create) are clearly explained with examples.

Chapter 4 (Publishing) very briefly explains the role of stylesheets (CSS, XSL, and XQuery) in displaying and transforming your documents to other formats, but as these all have their own books and manuals, this book doesn't go into them in any detail.

Customizing DocBook is fairly commonplace, either to avoid the need to commit tag abuse, or to extend its structure into other fields (I added a new element type for typographical examples for my book on LaTeX, and it only took a few minutes). Chapter 5 provides some rules and explanation of customization layers and modularity for those who design schemas and DTDs.

The five Appendixes cover Installation, Variants, Resources, Interchange, and the GNU Free Documentation License — yes, you can read the whole thing online at docbook.org, for which Tim, Norm, and many others are to be thanked. It is a rare publisher who groks the need to be able to point someone at a reference, or quote it in email or a tweet, where a paper copy doesn't cut the mustard.

There isn't anything here about actually using an XML editor or about how to choose one. Editors do of course all come with their own documentation (much of it written using DocBook) and editor selection can be a complex business. However, there is a list of some common tools in Appendix C (Resources). Editors are a minefield, as my own research into the usability of editing software for structured documents is showing, so I can understand the omission, but some pointers to editor resources would have been useful.

The chapter on Publishing is useful for those who haven't been in the publication process before, but it could have emphasized more the need for accuracy and consistency. Experienced technical authors know this, but many other writers don't see the need for it, assuming that the publisher (or some elf) will automagically heal everything before publication. DocBook 5 and this book will help enormously, but author-edited documents sometimes unwittingly misuse or abuse the markup, no matter how exhaustive the manuals.

If you write computer documentation, or anything related to it, from a conference paper to a thesis to a book, DocBook 5 is probably what you should use if you want the document to survive and to be usable and reusable; and this is the book to help you do it.

You can purchase DocBook 5: The Definitive Guide from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

frisket writes "Definitive guides by the authors or maintainers of software systems tend to have the edge over other documentation because of the insight they provide. DocBook 5 — The Definitive Guide comes well up to scratch. DocBook has long been the de facto standard for computer system documentation in XML (and SGML before that), and Norm Walsh has revised and updated both the language and the documentation in a concise and valuable form, usable both by beginners and by tech doc experts." Read on for the rest of frisket's review. DocBook 5: The Definitive Guide author Norman Walsh pages 560 publisher O'Reilly in conjunction with XML Press rating 9/10 reviewer frisket ISBN 9780596805029 summary Examines and catalogs the entirety of the DocBook specification. DocBook is a rich XML vocabulary, primarily for the documentation of software systems. It provides markup both for the structure of your documents and for the descriptive detail of your writing, to an extent that few other XML systems match. Like XML itself, DocBook's popularity rests on its robustness, scope, and extensibility; and Walsh makes it clear that the Technical Committee has tried hard to balance stability and adaptability in releasing a new major version which does have a few backward-incompatible changes.

This is a reference book, so the initial chapters (1-5) are short (70 pages) but full of clear explanations of how DocBook works, what it does, and how to use it. Part II is 400 pages, covering every element type in the language, with a detailed description of what it is for, how and where to use it, and how it interacts with everything else. Both for the beginner and the expert, these descriptions are the key to effective use, and Walsh's explanations are clear and comprehensive.

For those of you who have been using DocBook in earlier incarnations, the changes are not deal-breakers, and many of them are welcome rationalizations of the way things have grown organically over the years. It still walks like a duck and quacks like a duck (and the book still has a duck on the cover), so it immediately feels like the same format that you're used to — the changes to element types are relatively few. Chapter 1 (Getting Started) has a brief history, a summary of the changes, and an explanation of the namespace and availability.

If you've never used DocBook before, its structure will still be familiar: in Chapter 2 (Creating DocBook Documents) Walsh explains the division of reference material like books, articles, and manuals into chapters, sections, and subsections, with all the conventional features like lists, figures, tables, and references, as well as the technically-oriented features like equations, programming constructs, interface descriptions, and code samples.

There is help in Chapter 3 (Validation) for those who construct or generate DocBook documents without the use of an XML editor (or even with them: more on editors below). The most common problems with misplaced markup (and the error messages they create) are clearly explained with examples.

Chapter 4 (Publishing) very briefly explains the role of stylesheets (CSS, XSL, and XQuery) in displaying and transforming your documents to other formats, but as these all have their own books and manuals, this book doesn't go into them in any detail.

Customizing DocBook is fairly commonplace, either to avoid the need to commit tag abuse, or to extend its structure into other fields (I added a new element type for typographical examples for my book on LaTeX, and it only took a few minutes). Chapter 5 provides some rules and explanation of customization layers and modularity for those who design schemas and DTDs.

The five Appendixes cover Installation, Variants, Resources, Interchange, and the GNU Free Documentation License — yes, you can read the whole thing online at docbook.org, for which Tim, Norm, and many others are to be thanked. It is a rare publisher who groks the need to be able to point someone at a reference, or quote it in email or a tweet, where a paper copy doesn't cut the mustard.

There isn't anything here about actually using an XML editor or about how to choose one. Editors do of course all come with their own documentation (much of it written using DocBook) and editor selection can be a complex business. However, there is a list of some common tools in Appendix C (Resources). Editors are a minefield, as my own research into the usability of editing software for structured documents is showing, so I can understand the omission, but some pointers to editor resources would have been useful.

The chapter on Publishing is useful for those who haven't been in the publication process before, but it could have emphasized more the need for accuracy and consistency. Experienced technical authors know this, but many other writers don't see the need for it, assuming that the publisher (or some elf) will automagically heal everything before publication. DocBook 5 and this book will help enormously, but author-edited documents sometimes unwittingly misuse or abuse the markup, no matter how exhaustive the manuals.

If you write computer documentation, or anything related to it, from a conference paper to a thesis to a book, DocBook 5 is probably what you should use if you want the document to survive and to be usable and reusable; and this is the book to help you do it.

You can purchase DocBook 5: The Definitive Guide 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 "On June 17th, the X.org team was notified by Invisible Things Lab of a critical security flaw (PDF) that affected both x86_32 and x86_64 platforms. The flaw deals with escalated privileges of a user process that has access to the X server. The founder of ITL said of the flaw, 'The attack allows a (unpriviliged) user process that has access to the X server (so, any GUI application) to unconditionally escalate to root (but again, it doesn't take advantage of any bug in the X server!). In other words: any GUI application (think e.g. sandboxed PDF viewer), if compromised (e.g. via malicious PDF document) can bypass all the Linux fancy security mechanisms, and escalate to root, and compromise the whole system.' This has apparently been a security flaw since kernel 2.6 was released. From the article, 'On 13 August, Linus Torvalds committed an initial fix, but several patches were added afterward for various reasons. The problem has been addressed in versions 2.6.27.52, 2.6.32.19, 2.6.34.4 and 2.6.35.2 of the kernel.'"

jamie writes "Federal prosecutors have decided not to file charges against a Philadelphia school district or its employees over the use of software to remotely monitor students. From the article: 'US Attorney Zane David Memeger says investigators have found no evidence of criminal intent by Lower Merion School District employees who activated tracking software that took thousands of webcam and screenshot images on school-provided laptops.'"

jamie writes "There he goes again, making up nonsense and making ridiculous claims that have no relationship to reality. Ray Kurzweil must be able to spin out a good line of bafflegab, because he seems to have the tech media convinced..."

eldavojohn writes "CVG is covering the controversy surrounding players' ability to play as a member of the Taliban in EA's Medal of Honor multiplayer. Fox News hopped on the wagon, interviewing a Gold Star mom whose son died in Iraq. She said, 'My son didn't get to start over when he was killed. His life was over and I had to deal with that every day. There's 1200 families from Afghanistan that have to live with this every day. And we live it — it's not a game... EA is very cavalier about it: "Well, it's just a game." But it isn't a game to the people who are suffering from the loss of the children and loved ones.' EA's response to this criticism of giving players the objective to 'gun down American troops' was this: 'Medal Of Honor is set in today's war, putting players in the boots of today's soldier... We give gamers the opportunity to play both sides. Most of us have been doing this since we were seven. If someone's the cop, someone's got to be the robber, someone's got to be the pirate, somebody's got to be the alien. In Medal Of Honor multiplayer, someone has to be the Taliban.' Of course the story recalls Six Days in Fallujah, which was dropped by Konami following similar controversy. It's clear at least a few people take issue with games surrounding modern conflicts."

snydeq writes "Deep End's Paul Venezia follows up on the Terry Childs sentencing, stating that the City of San Francisco is as much at fault in this case as Childs is. 'The way that the San Francisco IT department has been run is nothing short of abysmal, and that has been pointed out time and again by anyone paying attention to this case,' Venezia writes. 'Plenty of dirty laundry was aired out in court as well, yet through it all, the city has had a full-court press on Childs, and being both the plaintiff and the prosecution it spared no expense to drill Childs into the ground.' Worse, perhaps, is the disproportion of the sentence, when compared with recent convictions for intended malfeasance on the part of several notable rogue IT admins."

paxcoder writes "You have been informed about Diaspora, a (to-be) distributed free social network. What you may not have known is that it was inspired by an excellent talk by Eben Moglen called 'Freedom in the Cloud.' But it doesn't stop there. At Debconf 10 this month, Moglen went further, and shared his vision of a free, private, and secure Net architecture relying on ('for lack of a better term') freedom boxes — low-price, ultra-small, plug it into the wall personal servers. He believes they will catch on since they will eventually cost less than a router, provide more functionality and freedom to the user, and even help your friends bypass any censorship by encrypting and routing their traffic. Since hardware is being taken care of, we are called to assemble the software stack. The title of this sequel talk is How We Can Be the Silver Lining of the Cloud."

paxcoder writes "You have been informed about Diaspora, a (to-be) distributed free social network. What you may not have known is that it was inspired by an excellent talk by Eben Moglen called 'Freedom in the Cloud.' But it doesn't stop there. At Debconf 10 this month, Moglen went further, and shared his vision of a free, private, and secure Net architecture relying on ('for lack of a better term') freedom boxes — low-price, ultra-small, plug it into the wall personal servers. He believes they will catch on since they will eventually cost less than a router, provide more functionality and freedom to the user, and even help your friends bypass any censorship by encrypting and routing their traffic. Since hardware is being taken care of, we are called to assemble the software stack. The title of this sequel talk is How We Can Be the Silver Lining of the Cloud."

An anonymous reader writes "Readers of Slashdot might be familiar with Lakehead University's ban on WiFi routers a few years ago in Thunder Bay, Ontario because of 'health concerns,' a policy apparently still in effect. Now it seems a group of concerned parents in a number of communities in Ontario have petitioned the local school boards over similar concerns at public schools, where their kids are apparently experiencing 'headaches to dizziness and nausea and even racing heart rates' — symptoms that appear only when they are in school on weekdays, not on weekends at home. 'The symptoms, which also include memory loss, trouble concentrating, skin rashes, hyperactivity, night sweats and insomnia, have been reported in 14 Ontario schools in Barrie, Bradford, Collingwood, Orillia and Wasaga Beach since the board decided to go wireless ...' Besides Wi-Fi signals, could there possibly be any other logical explanation for kids having more symptoms of illness on school days than at home on weekends or in the summer?"

Meshach writes "As happened earlier in Saudi Arabia Blackberry has reached a deal that allows Indian authorities access to the transmissions of hand held devices. Much of the fear comes from worries about terrorists: Pakistani-based militants used mobile and satellite phones in the 2008 attacks that killed 166 people in Mumbai."

jamie passes along a story in the NY Times about how an unprecedented level of openness and data-sharing among scientists involved in the study of Alzheimer's disease has yielded a wealth of new research papers and may become the template for making progress in dealing with other afflictions. Quoting: "The key to the Alzheimer's project was an agreement as ambitious as its goal: not just to raise money, not just to do research on a vast scale, but also to share all the data, making every single finding public immediately, available to anyone with a computer anywhere in the world. No one would own the data. No one could submit patent applications, though private companies would ultimately profit from any drugs or imaging tests developed as a result of the effort. 'It was unbelievable,' said Dr. John Q. Trojanowski, an Alzheimer's researcher at the University of Pennsylvania. 'It's not science the way most of us have practiced it in our careers. But we all realized that we would never get biomarkers unless all of us parked our egos and intellectual-property noses outside the door and agreed that all of our data would be public immediately.'"

snydeq writes "Fatal Exception's Neil McAllister warns developers of the hidden risks of entering programming competitions, which are on the rise since NetFlix awarded $1 million to BellKor's Pragmatic Chaos in 2009. 'Web and software companies offer prizes for a variety of reasons. Chief among them is simply to raise awareness, interest, and participation in a given software platform or service,' McAllister writes. But the practice of offering and entering software prizes is not without concerns. Privacy implications, class-action lawsuits — many of the prizes leave participants vulnerable to prosecution. Worse is the possibility of handing hard work over to a company without reward. 'Contests like the Netflix Prize are sponsored by commercial entities that stand to profit from the innovations produced by the entrants. Those who participate invest valuable time toward winning the prize, but if they fail to meet the deadline (or to produce the leading results) their efforts could go completely unrewarded. Depending on the terms of the contest, however, the sponsor might still be able to make use of the runners-up's innovations — which, of course, would be a whole lot cheaper than hiring developers.'"

snydeq writes "Fatal Exception's Neil McAllister warns developers of the hidden risks of entering programming competitions, which are on the rise since NetFlix awarded $1 million to BellKor's Pragmatic Chaos in 2009. 'Web and software companies offer prizes for a variety of reasons. Chief among them is simply to raise awareness, interest, and participation in a given software platform or service,' McAllister writes. But the practice of offering and entering software prizes is not without concerns. Privacy implications, class-action lawsuits — many of the prizes leave participants vulnerable to prosecution. Worse is the possibility of handing hard work over to a company without reward. 'Contests like the Netflix Prize are sponsored by commercial entities that stand to profit from the innovations produced by the entrants. Those who participate invest valuable time toward winning the prize, but if they fail to meet the deadline (or to produce the leading results) their efforts could go completely unrewarded. Depending on the terms of the contest, however, the sponsor might still be able to make use of the runners-up's innovations — which, of course, would be a whole lot cheaper than hiring developers.'"

snydeq writes "Fatal Exception's Neil McAllister warns developers of the hidden risks of entering programming competitions, which are on the rise since NetFlix awarded $1 million to BellKor's Pragmatic Chaos in 2009. 'Web and software companies offer prizes for a variety of reasons. Chief among them is simply to raise awareness, interest, and participation in a given software platform or service,' McAllister writes. But the practice of offering and entering software prizes is not without concerns. Privacy implications, class-action lawsuits — many of the prizes leave participants vulnerable to prosecution. Worse is the possibility of handing hard work over to a company without reward. 'Contests like the Netflix Prize are sponsored by commercial entities that stand to profit from the innovations produced by the entrants. Those who participate invest valuable time toward winning the prize, but if they fail to meet the deadline (or to produce the leading results) their efforts could go completely unrewarded. Depending on the terms of the contest, however, the sponsor might still be able to make use of the runners-up's innovations — which, of course, would be a whole lot cheaper than hiring developers.'"

Stoobalou writes "A shareholding company launched a lawsuit against Hewlett-Packard's board of directors earlier this week, claiming they bungled their fiduciary duties over the departure of CEO Mark Hurd. 'The HP board put shareholders' finances at risk by not telling them about the sexual harassment inquiry, and then later rewarded Hurd with an estimated $40 million severance package, the suit said. The board also failed to adequately police insider trading by HP executives, allowing Hurd and chief financial officer Cathie Lesjak to sell off HP stock in the midst of the inquiry, according to the suit, which was filed in California Superior Court.'" HP is also facing increased scrutiny from the unrelated bribery probe that began earlier this year when their Moscow offices were raided.

Stoobalou writes "A shareholding company launched a lawsuit against Hewlett-Packard's board of directors earlier this week, claiming they bungled their fiduciary duties over the departure of CEO Mark Hurd. 'The HP board put shareholders' finances at risk by not telling them about the sexual harassment inquiry, and then later rewarded Hurd with an estimated $40 million severance package, the suit said. The board also failed to adequately police insider trading by HP executives, allowing Hurd and chief financial officer Cathie Lesjak to sell off HP stock in the midst of the inquiry, according to the suit, which was filed in California Superior Court.'" HP is also facing increased scrutiny from the unrelated bribery probe that began earlier this year when their Moscow offices were raided.

I Don't Believe in Imaginary Property writes "Google has written a defense of their joint Net Neutrality proposal with Verizon, responding to criticism like the EFF's recent review. Google presents its arguments as a list of myths and facts, but too many of them look like this one: 'MYTH: This proposal would eliminate network neutrality over wireless. FACT: It's true that Google previously has advocated for certain openness safeguards to be applied in a similar fashion to what would be applied to wireline services. However, in the spirit of compromise, we have agreed to a proposal that allows this market to remain free from regulation for now, while Congress keeps a watchful eye. Why? First, the wireless market is more competitive than the wireline market, given that consumers typically have more than just two providers to choose from. Second, because wireless networks employ airwaves, rather than wires, and share constrained capacity among many users, these carriers need to manage their networks more actively. Third, network and device openness is now beginning to take off as a significant business model in this space.'"

astroengine writes "In the wake of recent solar activity, some space cadets were very quick to point out a causal link between geomagnetic storms and the wildfires currently ravaging the landscape surrounding Moscow. Of course, this is patently false. But is there a scenario when the onset of a solar storm could have secondary effects, sparking fires in already arid regions? Possibly. What's more, it already happened, 150 years ago."

pq writes "In a paper published today (abstract) in Science, astronomers are reporting the discovery of a radio pulsar in data acquired at the world's largest radio telescope and analyzed by hundreds of thousands of volunteers in 192 countries for the Einstein@Home project. This is the first scientific discovery by a distributed computing project, and specific credit is being given to Chris and Helen Colvin of Ames, Iowa, and Daniel Gebhardt of Germany." The claim that this is the first discovery to be made through distributed computing is hard to swallow; there are quite a few distributed projects out there, several of which have reported positive results, such as the discovery of the 47th known Mersenne number.

An anonymous reader tips news that Valve Software has filed a trademark claim for the term "DOTA," fueling speculation that the company will soon reveal a new Defense of the Ancients game. Voice actor John St. John recently said he was recording for such a game in a post to Twitter. The tweet was subsequently deleted. Last year Valve hired 'Icefrog,' lead developer for the original DotA mod.

Trevor James writes "Finally, here's a Drupal book specifically for Drupal content editors and site managers, those folks responsible for posting new content and editing existing content on a Drupal site. While many of the Packt series of Drupal books focuses on code, development and are written for Drupal developers, this title is for anyone who is dealing with management of Drupal based content and any individuals or teams responsible for the management of Drupal sites on a daily and hourly basis. This book is also perfect for introductory Drupal classes and I will not hesitate to use it in my Drupal 101 classes in the near future." Read on for the rest of Trevor's review. Drupal 6 Content Administration author J. Ayen Green pages 179 publisher Packt Publishing rating 9/10 reviewer Trevor james ISBN 1847198562 summary A fun, informative, hands-on learning guide that uses an actual case study In Chapter 1, the author gives a concise and streamlined introduction to the Drupal CMS and the elements of a Drupal Web site from both the frontend and backend perspectives. I liked seeing the detailed explanations of a Drupal powered front end layout — explaining the differences between the site header, navigation areas, and content areas. I'd recommend this first chapter to anyone who is just starting to use Drupal and wants a basic introduction to the Drupal framework. It's hard to emphasize how important it is to understand the basic intro level concepts and functionality of the Drupal CMS and its all here in this intro section. To any of my intro Drupal users I would hand this chapter out and ask them to read it.

Chapter 2 moves into a detailed discussion of Drupal-based content and asks the simple question (but important one), what is content? In Drupal we know that content includes nodes and node types, node IDs (nid), comments, Blocks, and Views. The author defines the core node types including Story and Page. Note here to Drupal 7 users ... the story type is renamed "Article" and the Page type is "Basic Page" in the new D7 release. I also love the fact that Green defines what the Drupal front page or home page is and what that home page contains. I am asked this question all the time by new Drupal users — how do I post content to my home page and how do I customize the home page. Read the definition on p. 19 of this book.

At this point I'd encourage those readers who are using the book to go ahead and start creating content on their Drupal site following the author's instructions. It's a great book of examples of tutorials to follow along with hands-on. The author gets you creating story content and editing it quickly. He also spends a good deal of time discussing integrating a WYSIWYG text editor to your content node form so you can use the text editor buttons to format content.

Chapter 3 continues the content discussion by showing you a bunch of enhancements you can do to your posted content. The author aptly calls these "seasonings". This includes creating teasers, creating links to other node content using the text editor, uploading images using the text editors and manually via the Drupal node editor, linking your images, embedding audio content, and linking to downloadable files such as PDFs. My only concern here is that the author shows you how to link to PDF files via the text editor but there's actually simpler methods of doing this in Drupal using Drupal's default file attachments module (part of core). This is the preferred method since it easily opens up the attached file to be used in other areas of your site via the Views module for instance. I always encourage Drupal users to add attached files using the core Drupal file attachments since I think it's simpler and more streamlined and it's the "Drupal" way of attaching files. I would add this method first and then show the text editor option second.

The author shows us how to upload and embed video content using SWF Tools module. I would have spent a bit more time in this chapter showing the user more details about uploading Flash based content using a combination of the Flash node and the SWF tools modules and integrating various player options in SWF Tools such as the Flowplayer utility. But again these are technicalities. The information the author presents is great and detailed. It's a good starting point for more beginning Drupal users.

Chapter 4 moves into more advanced content editing topics. The author shows you how to use HTML and CSS to create table based layouts (without using table code) in your text editor and in a Drupal node. So for everyone who needs an introduction to CSS this is a great place to start. The author spends time showing us how to add the CSS files so they are recognized by our Drupal theme — this is going to be a bit more advanced for the new Drupal user but its good stuff to learn. He even shows us how to create a CSS file from scratch and how to build the table layout without using table code. Sticking to CSS is going to give you cleaner code and work better with Drupal so it's great that he emphasizes this here. For dealing with more table based code Green shows us some tricks to injecting this code using PHP. Again this is more advanced but good tips and tricks for those involved with code. He also shows us how revisions and workflow work in our Drupal site.

Chapter 5 deals with how to use tagging, tag clouds and how to re-name our URLs with human friendly path aliases using Drupal's core Path module. This will help our site become more searchable, browser and user friendly. Tagging is the focus here and he gives a nice walkthrough of Drupal's taxonomy system. Anyone interested in setting up tagging on their Drupal site should read this chapter. Chapter 6 moves into using Blocks, Views and setting up Blogs on your site. This chapter is the one to read if you're managing blocks and Views and want a good introduction to the Views module. Packt has published books specifically on using Drupal Views but I would start here first if you're just using Views for the first time.

The section on blogging is good too. Often I hear folks report that Drupal is only a fancy blogging tool or blogging application. This book actually shows that Drupal is a full scale and robust CMS and that blogging is only one minuscule part of the entire framework. If you're just going to be blogging on your site Drupal may actually be overkill. The author shows this by spending a smaller amount of time showing you how to set up your Drupal site for blogs, but of course it also shows you that Drupal does blogs too and you can easily use a Drupal site to just blog. I would argue that this is a great book to look at the overall impact of Drupal on building Web sites and how we can leverage it to build powerful, rich and robust content management driven sites. We can add a blog if we want to but it's not just a blogging-based piece of software.

Chapter 7 deals with setting up users, roles and permissions on your site. It's good to leave this chapter towards the end of the book since Drupal permissions can be a bit tricky and time consuming to set up. We moved through a bunch of fun material earlier in the book and now we have a chapter on permissions. I like the attention the author placed on how to organize this section into the overall book's theme and layout. Chapter 8 shows you some tricks for dealing with issues like pasting Word content into a Drupal node; and using the Blog API module to work on blog posts in remote software and then post those blog entries to your Drupal site via a Web service. A nice touch here to add a small section on using Web services to post content. Finally the Appendix shows you how to install Drupal.

This is definitely one of the best books I've read on Drupal from an introductory standpoint. It's up there with O'Reilly's Using Drupal book and I would recommend it to anyone who is installing Drupal for the first time. I'll use it in my introductory Drupal classes for sure. It will be nice to see this book revised for Drupal 7 soon. Excellent work again from J. Ayen Green.

You can purchase Drupal 6 Content Administration from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Trevor James writes "Finally, here's a Drupal book specifically for Drupal content editors and site managers, those folks responsible for posting new content and editing existing content on a Drupal site. While many of the Packt series of Drupal books focuses on code, development and are written for Drupal developers, this title is for anyone who is dealing with management of Drupal based content and any individuals or teams responsible for the management of Drupal sites on a daily and hourly basis. This book is also perfect for introductory Drupal classes and I will not hesitate to use it in my Drupal 101 classes in the near future." Read on for the rest of Trevor's review. Drupal 6 Content Administration author J. Ayen Green pages 179 publisher Packt Publishing rating 9/10 reviewer Trevor james ISBN 1847198562 summary A fun, informative, hands-on learning guide that uses an actual case study In Chapter 1, the author gives a concise and streamlined introduction to the Drupal CMS and the elements of a Drupal Web site from both the frontend and backend perspectives. I liked seeing the detailed explanations of a Drupal powered front end layout — explaining the differences between the site header, navigation areas, and content areas. I'd recommend this first chapter to anyone who is just starting to use Drupal and wants a basic introduction to the Drupal framework. It's hard to emphasize how important it is to understand the basic intro level concepts and functionality of the Drupal CMS and its all here in this intro section. To any of my intro Drupal users I would hand this chapter out and ask them to read it.

Chapter 2 moves into a detailed discussion of Drupal-based content and asks the simple question (but important one), what is content? In Drupal we know that content includes nodes and node types, node IDs (nid), comments, Blocks, and Views. The author defines the core node types including Story and Page. Note here to Drupal 7 users ... the story type is renamed "Article" and the Page type is "Basic Page" in the new D7 release. I also love the fact that Green defines what the Drupal front page or home page is and what that home page contains. I am asked this question all the time by new Drupal users — how do I post content to my home page and how do I customize the home page. Read the definition on p. 19 of this book.

At this point I'd encourage those readers who are using the book to go ahead and start creating content on their Drupal site following the author's instructions. It's a great book of examples of tutorials to follow along with hands-on. The author gets you creating story content and editing it quickly. He also spends a good deal of time discussing integrating a WYSIWYG text editor to your content node form so you can use the text editor buttons to format content.

Chapter 3 continues the content discussion by showing you a bunch of enhancements you can do to your posted content. The author aptly calls these "seasonings". This includes creating teasers, creating links to other node content using the text editor, uploading images using the text editors and manually via the Drupal node editor, linking your images, embedding audio content, and linking to downloadable files such as PDFs. My only concern here is that the author shows you how to link to PDF files via the text editor but there's actually simpler methods of doing this in Drupal using Drupal's default file attachments module (part of core). This is the preferred method since it easily opens up the attached file to be used in other areas of your site via the Views module for instance. I always encourage Drupal users to add attached files using the core Drupal file attachments since I think it's simpler and more streamlined and it's the "Drupal" way of attaching files. I would add this method first and then show the text editor option second.

The author shows us how to upload and embed video content using SWF Tools module. I would have spent a bit more time in this chapter showing the user more details about uploading Flash based content using a combination of the Flash node and the SWF tools modules and integrating various player options in SWF Tools such as the Flowplayer utility. But again these are technicalities. The information the author presents is great and detailed. It's a good starting point for more beginning Drupal users.

Chapter 4 moves into more advanced content editing topics. The author shows you how to use HTML and CSS to create table based layouts (without using table code) in your text editor and in a Drupal node. So for everyone who needs an introduction to CSS this is a great place to start. The author spends time showing us how to add the CSS files so they are recognized by our Drupal theme — this is going to be a bit more advanced for the new Drupal user but its good stuff to learn. He even shows us how to create a CSS file from scratch and how to build the table layout without using table code. Sticking to CSS is going to give you cleaner code and work better with Drupal so it's great that he emphasizes this here. For dealing with more table based code Green shows us some tricks to injecting this code using PHP. Again this is more advanced but good tips and tricks for those involved with code. He also shows us how revisions and workflow work in our Drupal site.

Chapter 5 deals with how to use tagging, tag clouds and how to re-name our URLs with human friendly path aliases using Drupal's core Path module. This will help our site become more searchable, browser and user friendly. Tagging is the focus here and he gives a nice walkthrough of Drupal's taxonomy system. Anyone interested in setting up tagging on their Drupal site should read this chapter. Chapter 6 moves into using Blocks, Views and setting up Blogs on your site. This chapter is the one to read if you're managing blocks and Views and want a good introduction to the Views module. Packt has published books specifically on using Drupal Views but I would start here first if you're just using Views for the first time.

The section on blogging is good too. Often I hear folks report that Drupal is only a fancy blogging tool or blogging application. This book actually shows that Drupal is a full scale and robust CMS and that blogging is only one minuscule part of the entire framework. If you're just going to be blogging on your site Drupal may actually be overkill. The author shows this by spending a smaller amount of time showing you how to set up your Drupal site for blogs, but of course it also shows you that Drupal does blogs too and you can easily use a Drupal site to just blog. I would argue that this is a great book to look at the overall impact of Drupal on building Web sites and how we can leverage it to build powerful, rich and robust content management driven sites. We can add a blog if we want to but it's not just a blogging-based piece of software.

Chapter 7 deals with setting up users, roles and permissions on your site. It's good to leave this chapter towards the end of the book since Drupal permissions can be a bit tricky and time consuming to set up. We moved through a bunch of fun material earlier in the book and now we have a chapter on permissions. I like the attention the author placed on how to organize this section into the overall book's theme and layout. Chapter 8 shows you some tricks for dealing with issues like pasting Word content into a Drupal node; and using the Blog API module to work on blog posts in remote software and then post those blog entries to your Drupal site via a Web service. A nice touch here to add a small section on using Web services to post content. Finally the Appendix shows you how to install Drupal.

This is definitely one of the best books I've read on Drupal from an introductory standpoint. It's up there with O'Reilly's Using Drupal book and I would recommend it to anyone who is installing Drupal for the first time. I'll use it in my introductory Drupal classes for sure. It will be nice to see this book revised for Drupal 7 soon. Excellent work again from J. Ayen Green.

You can purchase Drupal 6 Content Administration from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jamie writes "Incensed by a 'no tresspassing' sign, Jeff Deck launched a cross-country trip to right grammatical wrongs. He enlisted a friend, Benjamin D. Herson, and together they erased errant quotation marks, rectified misspellings and cut unnecessary possessive apostrophes. The Great Typo Hunt is the story of their crusade." We have already covered the duo's fight with The National Park Service.

jamie writes "Incensed by a 'no tresspassing' sign, Jeff Deck launched a cross-country trip to right grammatical wrongs. He enlisted a friend, Benjamin D. Herson, and together they erased errant quotation marks, rectified misspellings and cut unnecessary possessive apostrophes. The Great Typo Hunt is the story of their crusade." We have already covered the duo's fight with The National Park Service.

krou writes "Coming on the back of human rights groups criticizing WikiLeaks, American officials are saying that the Obama administration is pressuring allies such as Australia, Britain, and Germany to open criminal investigations against WikiLeaks founder Julian Assange, and to try limit his ability to travel. 'It's not just our troops that are put in jeopardy by this leaking. It's UK troops, it's German troops, it's Australian troops — all of the NATO troops and foreign forces working together in Afghanistan,' said one American diplomatic official, who added that other governments should 'review whether the actions of WikiLeaks could constitute crimes under their own national-security laws.'"

superapecommando noted an essay by Glyn Moody where he writes "In the early days of free software, the struggle was just to get companies to try this new and rather unconventional approach, without worrying too much about how that happened. That typically meant programs entering by the back door, surreptitiously installed by in-house engineers who understood the virtues of the stuff — and that it was easier to ask for forgiveness after the event than for permission before. [The Linux Foundation tries] to take all the fun out of free software. They are about removing the quirkiness and the riskiness that has characterized free software in business for the last decade and a half, and seek to replace it with nice, safe systems that senior management will instantly fall in love with. In a word, they seek to make open source boring for the enterprise. That's not only good news for companies, it's a really important step for the Linux Foundation."

An anonymous reader writes "We previously discussed news that Vinay Deolalikar, a Principal Research Scientist at HP Labs, wrote a paper that claimed to prove P is not equal to NP. Dick Lipton, a Professor of Computer Science at Georgia Tech, analyzed the idea of the proof on his blog. In a recent post, he explains that there have been many serious objections raised about the proof. The post summarizes the issues that need to be answered in any subsequent development, and additional concerns are raised in the comment section."

ideaMUX writes "NASA's solar dynamics observatory recently detected an M-class flare hurling a coronal mass ejection (CME) into space. The CME is not fully directed toward Earth, but some of the plasma cloud may be visible in the magnetosphere tonight, causing a geomagnetic disturbance and possible aurora. NASA said M-class flares are medium-sized, and can cause brief radio blackouts that affect Earth's Polar regions. Minor radiation storms sometimes follow M-class flares."

An anonymous reader writes "Apparently the Senate was in such a rush to get out of town that it forgot to name an 'important' bill that it passed, so the bill goes to the House as The ______Act of____. That's how it appears in the Congressional Record, though the Library of Congress has it listed as The XXXXXXAct ofXXXX. As for what's in the bill, well that appears to be as mysterious as the name. It was officially announced as a bill to tax bonuses to execs who received TARP money. But then someone simply deleted the entire bill and replaced it with text about aviation security. And then it was deleted again, and replaced with something having to do with education. However, because of these constant changes, many of the services that track the bill have the old details listed. On top of that, Nancy Pelosi called the House back for an emergency vote on this unnamed bill, and anyone trying to find out what it's about might be misled into thinking its about aviation security or something entirely unrelated to the actual bill. And people wonder why no one trusts Congress." It appears that the government's new martial law plans are being passed after all.

theodp writes "No stranger himself to sexual harassment allegations, Oracle CEO Larry Ellison has denounced HP's directors for forcing the resignation of HP CEO Mark Hurd. 'The HP board just made the worst personnel decision since the idiots on the Apple board fired Steve Jobs many years ago,' Ellison wrote. For now, it seems that Rupert Murdoch is also standing by Hurd, who sits on News Corp's Board of Directors and its Corporate Governance Committee. Less likely to survive the scandal is Hurd's relationship with HP General Counsel Mike Holston, who accepted Hurd's signed separation agreement after leading an investigation into Hurd's actions, which Holston told the NY Times 'showed a profound lack of judgment.' Quite a change from just last year, when Hurd and Holston teamed up to get their daughters' elite prep school a state-of-the-art HP Data Center."

langelgjm writes "Announced this afternoon in a joint conference call held by CEOs Eric Schmidt and Ivan Seidenberg, Google and Verizon have released a joint net neutrality proposal in the form of a 'suggested legislative framework for consideration by lawmakers.' This comes on the heels of last week's assertion (and subsequent denial) that Google and Verizon were close to concluding talks that would permit Verizon to prioritize certain content in exchange for pay. A look at the actual text of the framework shows some positive net neutrality principles, but there is also some more curious content: 'Wireless broadband' is singled out for exclusion from most of the agreement, and providers would be permitted to prioritize 'additional online services... distinguishable in scope and purpose.' Public Knowledge, a watchdog group based in Washington, has criticized the agreement for these provisions."

1sockchuck writes "Startup International Data Security says it is moving ahead with plans to build data centers on cargo ships docked in the San Francisco Bay. IDS first announced its plans in 2008, but they were postponed by the credit crunch. The company says it has now lined up funding and an anchor tenant for a proof-of-concept 'dataship' that will hold 500 racks of servers in its cargo holds. IDS isn't alone in contemplating ship-board server farms, as Google has applied for a patent for a 'water-based data center.'"

1sockchuck writes "Startup International Data Security says it is moving ahead with plans to build data centers on cargo ships docked in the San Francisco Bay. IDS first announced its plans in 2008, but they were postponed by the credit crunch. The company says it has now lined up funding and an anchor tenant for a proof-of-concept 'dataship' that will hold 500 racks of servers in its cargo holds. IDS isn't alone in contemplating ship-board server farms, as Google has applied for a patent for a 'water-based data center.'"

Slashdot regular Bennett Haselton writes in with an essay on a subject we've dealt with internally at Slashdot for years: user abuses of social news... this time at Digg. He starts "Alternet uncovers evidence of a 'bury brigade' coordinating efforts to 'bury' left-leaning stories on Digg. Digg had previously announced that the 'bury' button will be removed from the next version of their site, to prevent these types of abuses, but that won't fix the real underlying issue — you can show mathematically that artificially promoting stories is just as harmful in the long run. Here's a simple fix that would address the real problem."

Even if you just arrived from Mars and have never heard of Digg, that description of the service should make it obvious how easy it is to game the system, by rounding up groups of friends to vote on stories that you want to promote, or to bury stories that you want to kill. The former type of abuse (and it is abuse, under Digg's Terms of Use; search for "organized effort") is far more common, since people usually have more incentive (commercial or otherwise) to promote their own work than to bury someone else's. And in fact, Digg has announced that the next version of the service will remove the "bury" button, replacing it with a "Report" button for reporting bona fide cases of abuse, not just to bury boring stories.

The thinking seems to be that abusive "digging" to promote a story, is less harmful than abusive "burying", and this has the ring of plausibility — that a creative effort is better than a destructive one. After all, Alternet had previously highlighted several artificial right-wing "digg brigades" mentioned in their story (Diggs And Buries, theliberalheretic, etc.), but they didn't blow the lid off of the situation until their report on the Digg Patriots bury brigade, as if to say, "Now we've found something really scandalous!" Annalee Newitz cheekily reported on how she bought votes to boost a story to the front page of Digg, but probably would have felt guilty if she'd hired a service to bury someone else's story. And when a Digg user organized an effort to bury Ron Paul stories that he thought were "spamming" the system, Ron Paul supporters protested that they were merely organizing to vote up stories they agreed with — the clear implication being that this was more honorable than organizing to vote stories down.

But this, I think, is a fallacy. If a story's ranking is artificially inflated, then the extra eyeballs for that story have to come from somewhere, and they come from users paying less attention to the other stories that the phony up-and-comer pushed out of the way. Artificially bumping a story up is just as harmful as artificially burying a story, but the harm is distributed among many innocent victims, not just one. (By the same reasoning, in fact, you could argue that burying a story does no net harm to other users of the Digg site, because the harm done to one story is cancelled out by the benefit to all the other stories that rise in prominence when the victimized story is pushed out of the way. So by strict economic logic, recruiting friends to boost your own story at the expense of everyone else's, is actually more harmful than organizing a bury brigade!)

So I don't think that Digg's replacing the "bury" button with a "report" button will fix the problem. For one thing, obviously groups could abuse the "report" button in the same way — issuing calls to action to report a story for violating the TOU. Since a flurry of bona fide abuse reports is presumably what Digg uses to identify and remove truly abusive stories like MLM spam, how are they going to tell the difference between these cases and cases of abusive "reporting"? (My suggestion: See if there is a sudden change in the percentage of users who view a story and make an abuse report. For stories that are genuine TOU violations, the percentage of users who "report" it should remain steady; for stories that are victimized by a "report brigade," you'll see a sudden spike in viewers and in the percentage of those viewers who report the story for abuse. This might have worked for detecting and stopping the bury brigades as well, although we'll never know now.)

But more fundamentally, even if this change does stop the "bury/report brigades" from killing stories at will, that only fixes the most obvious symptom of the underlying problem, which is that the system can be gamed by recruiting your friends to vote either way. It won't stop "brigades" from artificially promoting shallow stories that agree with their opinions, which does the same net harm overall.

Indeed, the most long-term harm that the DiggPatriots Yahoo Group might have done is that their cheating was so egregious that it makes other examples of cheating look benign by comparison, and might prevent people from realizing that "benign cheating" is just as harmful. As detailed in the Alternet report, the DiggPatriots group talked openly about cycling through different Digg accounts and circumventing bans on their IP addresses. The welcome message to the Yahoo Group told new users that the group was operating "under the radar." The group leader, a woman with the handle "bettverboten," talked about how to prevent Digg from monitoring their actions. And of course the vast majority of posts were calls to bury stories. But what if all of that had been inverted? If the group had operated in the open, while still focusing on recruiting conservative members? If each user limited to themselves to only one Digg account like they were supposed to? And if they focused not on burying stories, but on digging stories that promoted their viewpoints? Just as bad. It just doesn't sound as bad.

I still think the only way to make Digg a true meritocracy, would be to use some version of an algorithm I outlined in an earlier article, inauspiciously titled "How to Stop Digg-cheating, Forever." The gist of it is that in addition to collecting votes from friends, stories should be shown to a random subset of users on the site (perhaps in a box that occasionally appears at the top of the screen when they're logged in), who are asked to vote it up or down. The votes of a random sampling of users would be more representative of how much value the story would have to the Digg community as a whole. Even if most users who are asked to vote on a "random story" simply ignore the request, all you need is to show the story to a large enough sample that you can measure the difference in responses to a truly good story vs. one that has been promoted by digg-cheaters. You don't necessarily have to run this procedure for every story, only the ones that are about to gain some benefit from a large number of diggs (such as being pushed to the front page), and you need to decide whether the story really deserves that big boost. The only way to game that system would be to organize a group of dedicated Digg users so enormous that they constituted a significant percentage of all users on the system — something pretty hard to do without getting caught.

Still, the only site that I know of, that uses a version of this "random sampling" algorithm is HotOrNot.com, which lets you recruit your friends to vote on the "hotness" of your picture on a scale of 1 to 10 (by sending them a link to that specific picture), but also shows a stream of random pictures to visitors, so that your picture can collect votes from strangers. If the votes from the users who visit your picture via the link are significantly different from the votes from users who see your picture via the random stream, then HotOrNot discounts the votes from users who view your page via the link. This prevents digg-style gaming from people who want all their friends to give them a 10. (Note that if you think about it, this is essentially the same as always throwing out the votes from people who visit your picture via the link. If you collect votes from group A and B, but you only count the votes from group A if they agree with the votes from group B, then you're really only counting votes from group B! All the extra votes really give you is the ability to brag that X many people voted on your picture.)

This seems like the simplest way to prevent Digg-cheating, although there may be others. Still unresolved is how to solve the general problem of "gaming" in traditional media and the blogosphere. For the foreseeable future, it's going to be the simple truth that if a major media outlet wants to run a story, it will be heard, and if no media outlet wants to run it, it won't be heard, regardless of how many viewers or readers would have voted in some hypothetical poll that, yes, they want to read that story, and yes, they liked it afterward. That's true for Internet articles as well, except to the extent that a deserving article might be rescued from obscurity by Digg, but the more that system can be gamed, the less it will reward articles that really deserve it. Digg is gameable because power users can recruit votes from their friends; the media and the blogosphere are so obviously "gameable" that we don't even call it "gameable," because "power users" — media outlets and A-list bloggers — can run whatever they want. Right now, the only way I can think of to change this situation that is even logically possible, would be for a site like Digg to adopt some version of the random-sampling algorithm, and to continue growing in power until a significant percentage of the public (not just Internet users, but everybody) relied on it for information. Then, if you had something important to say, people would hear it, but you wouldn't be able to cheat your way to the top.

The ultimate irony is that Alternet's story may never have seen the light of day, if it hadn't been the beneficiary of the same gameable, non-meritocratic inefficiencies that exist in the media-blogo-outrage-o-sphere, just as they exist on Digg. Yes, the Alternet story deserved to be heard, but you don't get the publicity you deserve, you get the publicity that you organize, and Alternet had the organizational publicity structure in place to get their voice heard. If a kid blogging from his bedroom had infiltrated the Digg Patriots group and made essentially the same discovery, would anybody ever have heard about it? (Well, maybe, because of the political hot-button factor — but even then, only after the story had been picked up by a major site like Alternet.) A truly meritocratic Digg algorithm could make it possible to get a good story out without a lot of organizational support behind it — and to ensure that an organized effort can't kill a good story either.

A few years ago we reported that it had been proven that Rubik's Cubes could be solved in 23 moves. Well now that number is down to just 20. Proving it required 35 years of computer time donated by Google to get it done.

As New York is putting Wi-Fi on wheels, reader Hugh Pickens notes a counter trend in Los Angeles coffee shops. (We remarked on a similar backlash in Seattle in 2005.) "Coffee shops were the retail pioneers of Wi-Fi, but Jessica Guynn reports in the LA Times that now some owners are pulling the plug after finding that Wi-Fi freeloaders who camp out all day nursing a single cup of coffee are a drain on the bottom line. Other owners strive to preserve a friendly vibe and keep their establishments from turning into 'Matrix'-like zombie shacks where people type and don't talk. 'There is now a market niche for not having Wi-Fi,' says Bryant Simon. After Dan and Nathalie Drozdenko turned off the Wi-Fi at their Los Angeles cafe, the complaints poured in, but so did the compliments: Lots of customers appreciated a wireless cup of joe at the Downbeat Cafe, a popular lunch spot in Echo Park. 'People come here because we don't offer it. They know they can get their work done and not get distracted.'"

As New York is putting Wi-Fi on wheels, reader Hugh Pickens notes a counter trend in Los Angeles coffee shops. (We remarked on a similar backlash in Seattle in 2005.) "Coffee shops were the retail pioneers of Wi-Fi, but Jessica Guynn reports in the LA Times that now some owners are pulling the plug after finding that Wi-Fi freeloaders who camp out all day nursing a single cup of coffee are a drain on the bottom line. Other owners strive to preserve a friendly vibe and keep their establishments from turning into 'Matrix'-like zombie shacks where people type and don't talk. 'There is now a market niche for not having Wi-Fi,' says Bryant Simon. After Dan and Nathalie Drozdenko turned off the Wi-Fi at their Los Angeles cafe, the complaints poured in, but so did the compliments: Lots of customers appreciated a wireless cup of joe at the Downbeat Cafe, a popular lunch spot in Echo Park. 'People come here because we don't offer it. They know they can get their work done and not get distracted.'"

bonch writes "Independent game Machinarium, released without DRM by developer Amanita Design, has only been paid for by 5-10% of its users according to developer Jakub Dvorsky. To drive legitimate sales, they are now offering a 'Pirate Amnesty' sale until August 12, bundling both the cross-platform game and its soundtrack for $5. Ron Carmel, designer of DRM-free puzzle game World of Goo, stated that his game also had about an 80-90% piracy rate, claiming that the percentage of those pirating first and purchasing later was 'very small.' He said, 'We're getting good sales through WiiWare, Steam, and our website. Not going bankrupt just yet!'"

pickens writes "Robert X. Cringley has an op-ed in the NY Times in which he contends that Google has found a way to get special treatment from Verizon without actually compromising net neutrality, by beginning to co-locate some of their portable data centers with Verizon network hubs. 'With servers so close to users, Google could not only send its data faster but also avoid sending it over the Internet backbone that connects service providers and for which they all pay,' writes Cringley. 'This would save space for other traffic — and money for both Verizon and Google, as their backbone bills decline (wishful thinking, but theoretically possible). Net neutrality would be not only intact, but enhanced.' So why won't Google and Verizon admit what they're up to? 'If my guess is right, then I would think they're silent because it's a secret. They'd rather their competitors not know until a few hundred shipping containers are in place — and suddenly YouTube looks more like HBO.'"

ColdWetDog writes "Computerworld reports that Mark Papermaster has left his job as Apple's Senior Vice President of Devices Hardware Engineering. He was the senior executive in charge of engineering for the iPhone 4 and thus responsible in some unknown fashion for 'antennagate.' His name may ring bells from previous coverage of his jump from IBM to Apple. From a brief blurb on Daring Fireball: 'From what I've heard, it's clear he was canned. Papermaster was a conspicuous absence at the Antennagate press conference. Inside Apple, he's "the guy responsible for the antenna" — that's a quote from a source back on July 23. (Another quote from the same source: "Apparently the antenna guys used to have a big chip on their shoulder. No more.")'" Update: 08/08 03:01 GMT by KD : Swapped out a registration-required NY Times link for a Computerworld one; corrected the direction of Papermaster's career move.

ColdWetDog writes "Computerworld reports that Mark Papermaster has left his job as Apple's Senior Vice President of Devices Hardware Engineering. He was the senior executive in charge of engineering for the iPhone 4 and thus responsible in some unknown fashion for 'antennagate.' His name may ring bells from previous coverage of his jump from IBM to Apple. From a brief blurb on Daring Fireball: 'From what I've heard, it's clear he was canned. Papermaster was a conspicuous absence at the Antennagate press conference. Inside Apple, he's "the guy responsible for the antenna" — that's a quote from a source back on July 23. (Another quote from the same source: "Apparently the antenna guys used to have a big chip on their shoulder. No more.")'" Update: 08/08 03:01 GMT by KD : Swapped out a registration-required NY Times link for a Computerworld one; corrected the direction of Papermaster's career move.

Late in 2008, the most sophisticated and well-coordinated international e-crime yet pulled off netted $9 million for its perpetrators. We discussed the RBS WorldPay heist when news about it emerged, and the indictments some months later. Now one of the accused ringleaders has been extradited from Estonia to face charges in the US. "...in the span of 12 hours around Nov. 8 [2008], the group hit 2,100 ATM terminals in 280 cities spanning the world, from the United States to Russia to Italy to Japan. ... Despite the technical and international challenges of the case, US investigators believe they were able to trace the scheme back to its origin. On Friday they brought one of the accused ringleaders from Estonia to Atlanta to face arraignment on several fraud charges — a rare appearance in US courts for an accused international hacker. Sergei Tsurikov, 26, of Tallinn, Estonia, pleaded not guilty at his arraignment to conspiracy to commit computer fraud, computer fraud, conspiracy to commit wire fraud, wire fraud and aggravated identity theft. ... The increasing scope of foreign attacks comes as college students around the world are focusing heavily on technology degrees only to emerge into a difficult job market with low pay, officials said."

Late in 2008, the most sophisticated and well-coordinated international e-crime yet pulled off netted $9 million for its perpetrators. We discussed the RBS WorldPay heist when news about it emerged, and the indictments some months later. Now one of the accused ringleaders has been extradited from Estonia to face charges in the US. "...in the span of 12 hours around Nov. 8 [2008], the group hit 2,100 ATM terminals in 280 cities spanning the world, from the United States to Russia to Italy to Japan. ... Despite the technical and international challenges of the case, US investigators believe they were able to trace the scheme back to its origin. On Friday they brought one of the accused ringleaders from Estonia to Atlanta to face arraignment on several fraud charges — a rare appearance in US courts for an accused international hacker. Sergei Tsurikov, 26, of Tallinn, Estonia, pleaded not guilty at his arraignment to conspiracy to commit computer fraud, computer fraud, conspiracy to commit wire fraud, wire fraud and aggravated identity theft. ... The increasing scope of foreign attacks comes as college students around the world are focusing heavily on technology degrees only to emerge into a difficult job market with low pay, officials said."

jamie found this piece, at Wired's Danger Room from a couple of days back, about an encouraging sign for the growth of open source in the military / intelligence sphere. "For three years, Matthew Burton has been trying to get a simple, useful software tool into the hands of analysts at the Central Intelligence Agency. For three years, haggling over the code’s intellectual property rights has kept the software from going anywhere near Langley. So now, Burton’s releasing it — free to the public, and under an open source license."

crimeandpunishment writes "There's a deal on the table to avert a ban on Blackberry's messenger service in Saudi Arabia. A Saudi regulatory official, speaking on the condition of anonymity, told the Associated Press the deal involves placing a server in Saudi Arabia ... and letting the government monitor users' messages, easing Saudi concerns over security and criminal usage. The deal could have wide-ranging implications, given how many other countries have expressed similar concerns, or in the case of the United Arab Emirates, have threatened to block Blackberry email and messaging services." Perhaps the governments of UAE and India would be satisfied, too, if only they had access to the messages transmitted.

jamie spotted this eye-opening presentation (here's a longer explanation) about how easy it is to access sensitive data on many sites using memcached, writing "If you already know what memcached is, skim to slide #17. The jaw-drop will happen around slide #33. Turns out many websites expose their totally-non-protected memcached interface to the Internet, including gowalla, bit.ly, and PBS."

Following up on its risible demand that Wikileaks return the Afghanistan documents, the Pentagon has banned military members from viewing the documents. The Washington Times obtained copies of Navy and Marine Corps messages to their troops saying that accessing the documents even from a personal computer is "willingly committing a security violation." Wired notes that terrorists everywhere are under no such restriction. Reader carp3_noct3m writes "I am personally left almost speechless at this disconnect from reality demonstrated by the military. I am a USMC Iraq war vet, and find these policies completely ridiculous. They show the inability of our supposedly technologically knowledgeable military to fuse this knowledge with policy, mostly due to the political pressure that has erupted to 'take care of' the Wikileaks problem."

eldavojohn writes "As expected, by a vote of 63 to 37 Elena Kagan has been appointed as the 112th member of the Supreme Court of the United States. Kagan, only 50 years old, has no judicial experience. The Washington Post explains: 'Other justices have corporate law backgrounds or a long record of arguing before the court. Kagan worked briefly for a law firm and argued her first case before an appellate court 11 months ago. It happened to be before the Supreme Court, the first of six cases she argued as the nation's first female solicitor general.' Her fair use views and free speech views have made her a focus of Slashdot recently."

eldavojohn writes "As expected, by a vote of 63 to 37 Elena Kagan has been appointed as the 112th member of the Supreme Court of the United States. Kagan, only 50 years old, has no judicial experience. The Washington Post explains: 'Other justices have corporate law backgrounds or a long record of arguing before the court. Kagan worked briefly for a law firm and argued her first case before an appellate court 11 months ago. It happened to be before the Supreme Court, the first of six cases she argued as the nation's first female solicitor general.' Her fair use views and free speech views have made her a focus of Slashdot recently."