Slashdot Mirror

MrLint writes "The City of Schenectady has decided that their laws are copyrighted, and that you cannot know them without paying for an 'exclusive license' for $200. This is not a first — Oregon has claimed publishing of laws online is a copyright violation." This case is nuanced. The city has contracted with a private company to convert and encode its laws so they can be made available on the Web for free. While the company works on this project, it considers the electronic versions of the laws its property and offers a CD version, bundled with its software, for $200. The man who requested a copy of the laws plans to appeal.

jamie writes with a follow-up to our recent discussion of social gaming scams: "Mark Pincus, CEO of the company that brought us Mafia Wars, says: 'I did every horrible thing in the book just to get revenues right away. I mean, we gave our users poker chips if they downloaded this Zwinky toolbar, which was like, I don't know... I downloaded it once and couldn't get rid of it.'" TechCrunch also ran a interesting tell-all from the CEO of a company specializing in Facebook advertisements, who provided some details on similarly shady operations at the popular social networking site.

jamie writes with a follow-up to our recent discussion of social gaming scams: "Mark Pincus, CEO of the company that brought us Mafia Wars, says: 'I did every horrible thing in the book just to get revenues right away. I mean, we gave our users poker chips if they downloaded this Zwinky toolbar, which was like, I don't know... I downloaded it once and couldn't get rid of it.'" TechCrunch also ran a interesting tell-all from the CEO of a company specializing in Facebook advertisements, who provided some details on similarly shady operations at the popular social networking site.

eldavojohn writes "From special organic molecules to organic surfaces with special properties to organic concrete, MIT's Technology Review takes a look at inspirations in nature that materials scientists are currently mimicking for human purposes. You may be able to name other fields that have turned to evolution for inspiration as well."

coreboarder writes "Recently it was divulged that the Brazilian power infrastructure was compromised by hackers. Then it was announced that it was apparently faulty equipment. A downplay to the global public or an honest clarification? Either way, it raises the question: how vulnerable are we, really? With winter and all its icy glory hurtling towards those of us in the northern hemisphere, how open are we to everything from terrorist threats to simple 'pay me or else' schemes?"

bonch writes "After apparently disabling and then re-enabling support for the Atom chipset in test builds of their 10.6.2 update, Apple has officially disabled support for the chipset in the final update. This makes it impossible for OSX86 users to run 10.6.2 on their Atom-based netbooks until a modified kernel shows up."

bonch writes "After apparently disabling and then re-enabling support for the Atom chipset in test builds of their 10.6.2 update, Apple has officially disabled support for the chipset in the final update. This makes it impossible for OSX86 users to run 10.6.2 on their Atom-based netbooks until a modified kernel shows up."

Sam notes an Ars story on Microsoft pulling the Windows 7 USB/DVD Download Tool from the Microsoft Store website after a report indicating that the tool incorporated open source code in a way that violated the GNU's General Public License. Whether the software giant is actually violating the GPL, a widely used (including by the Linux kernel) free software license, is not confirmed. "We are currently taking down the Windows USB/DVD Tool from the Microsoft Store site until our review of the tool is complete," a Microsoft spokesperson told Ars. The fact the company pulled the tool doesn't bode well, so we'll have to watch closely to see what the company puts back on its servers.

Trailrunner7 writes "US and international prosecutors have indicted a criminal ring that they allege was responsible for an ATM scam last November that stole about $9 million from RBS WorldPay. The criminals cracked payroll debit cards and withdrew money from ATMs in hundreds of cities around the world. A federal grand jury in Atlanta has indicted eight men in connection with the scheme, including five Estonians, one Russian, one Moldovan, and one unidentified man. Prosecutors allege that the men 'used sophisticated hacking techniques' to defeat the company's encryption system. The scam involved an elaborate plan in which the attackers first bypassed the encryption on the debit cards, which RBS WorldPay issues to customers for employee payroll purposes. They then raised the limits on the accounts attached to the cards, then provided a network of 'cashers' with 44 counterfeit payroll debit cards, which were used to withdraw more than $9 million from more than 2,100 ATMs in at least 280 cities worldwide, including cities in the United States, Russia, Ukraine, Estonia, Italy, Japan and Canada. The $9 million loss occurred within a span of less than 12 hours; 130 different ATMs in 49 cities were hit within one 30-minute period."

eldavojohn writes "The EC has presented Oracle and Sun with a statement of objections. Despite the promotion of former MySQL CEO Marten Mickos, the statement seems to focus entirely on what many have feared: MySQL vs. Oracle databases. From Sun's 8-K SEC filing: 'The Statement of Objections sets out the Commission's preliminary assessment regarding, and is limited to, the combination of Sun's open source MySQL database product with Oracle's enterprise database products and its potential negative effects on competition in the market for database products.' The EU and the EC are getting a rep for disagreeing with US counterparts." On Monday afternoon the DoJ reiterated its support for the deal. Matthew Aslett has a helpful timeline of the action from the EC.

eldavojohn writes "The EC has presented Oracle and Sun with a statement of objections. Despite the promotion of former MySQL CEO Marten Mickos, the statement seems to focus entirely on what many have feared: MySQL vs. Oracle databases. From Sun's 8-K SEC filing: 'The Statement of Objections sets out the Commission's preliminary assessment regarding, and is limited to, the combination of Sun's open source MySQL database product with Oracle's enterprise database products and its potential negative effects on competition in the market for database products.' The EU and the EC are getting a rep for disagreeing with US counterparts." On Monday afternoon the DoJ reiterated its support for the deal. Matthew Aslett has a helpful timeline of the action from the EC.

eldavojohn writes "In July, the Software Freedom Law Center (SFLC) leveled the finger at Microsoft for a GPL violation but how often does this actually happen? Sunday, Brad M. Kuhn (tech director at the SFLC) stated in his blog that since August of 2009 he has been finding about one per day. So why is it that we have only covered a handful of these cases in the news? Brad offers sage wisdom; surprisingly, he recommends, 'Don't go public first. Back around late 1999, when I found my first GPL violation from scratch, I wanted to post it to every mailing list I could find and shame that company that failed to respect and cooperate with the software freedom community. I'm glad that I didn't do that, because I've since seen similar actions destroy the lines of communication with violators, and make resolution tougher.' Public shame is evidently not always the best answer. Ars has a few more details and notes that (in accordance with Brad's advice) lawsuits are usually a dead last resort."

Trepidity writes "The US Supreme Court held oral argument Monday in Bilski, a business-methods patent case that might also have important implications for software patents (We have previously discussed the case several times). The tone of the argument appears to be good news, as the justices were very skeptical of the broad patentability claims. They even brought up a parade of absurd hypothetical patents quite similar to the ones Slashdotters tend to mention in these kinds of debates. Roberts surmised that 'buy low, sell high' might be a patentable business method, Sotomayor wondered if speed-dating could be patentable, Breyer questioned whether a professor could patent a lesson plan that kept his students from falling asleep, and Scalia brought up the old-time radio soap opera Lorenzo Jones, featuring a hare-brained inventor with delusions of getting rich." Patently O has good blow-by-blow coverage of the day's proceedings. Official argument transcripts will be up soon, they say.

Trepidity writes "The US Supreme Court held oral argument Monday in Bilski, a business-methods patent case that might also have important implications for software patents (We have previously discussed the case several times). The tone of the argument appears to be good news, as the justices were very skeptical of the broad patentability claims. They even brought up a parade of absurd hypothetical patents quite similar to the ones Slashdotters tend to mention in these kinds of debates. Roberts surmised that 'buy low, sell high' might be a patentable business method, Sotomayor wondered if speed-dating could be patentable, Breyer questioned whether a professor could patent a lesson plan that kept his students from falling asleep, and Scalia brought up the old-time radio soap opera Lorenzo Jones, featuring a hare-brained inventor with delusions of getting rich." Patently O has good blow-by-blow coverage of the day's proceedings. Official argument transcripts will be up soon, they say.

Trepidity writes "The US Supreme Court held oral argument Monday in Bilski, a business-methods patent case that might also have important implications for software patents (We have previously discussed the case several times). The tone of the argument appears to be good news, as the justices were very skeptical of the broad patentability claims. They even brought up a parade of absurd hypothetical patents quite similar to the ones Slashdotters tend to mention in these kinds of debates. Roberts surmised that 'buy low, sell high' might be a patentable business method, Sotomayor wondered if speed-dating could be patentable, Breyer questioned whether a professor could patent a lesson plan that kept his students from falling asleep, and Scalia brought up the old-time radio soap opera Lorenzo Jones, featuring a hare-brained inventor with delusions of getting rich." Patently O has good blow-by-blow coverage of the day's proceedings. Official argument transcripts will be up soon, they say.

yuveraj writes to mention that Pranav Mistry, the brain behind the innovative "SixthSense" application demoed earlier this year, plans to open source the technology in order to get this to the streets faster. "Mistry’s decision has meaning beyond Sixth Sense. The desire of inventors is always to get their work into the market as quickly as possible. Usually this means waiting for it to be turned into a useful, profitable invention. Mistry is bypassing this by going straight to open source. There is no report on which license he will use, but whichever one he does choose he has put paid to the canard that open source and innovation are incompatible, for all time."

Frequent Slashdot contributor Bennett Haselton changes things up today by reviewing The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics. Questions that big need a big review and you can learn what Bennett has to say about it all by reading below. The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics author Steven E. Landsburg pages 288 pages publisher Free Press rating 8/10 reviewer Bennett Haselton ISBN 978-1439148211 summary Steven Landsburg uses concepts from mathematics, economics, and physics to address the big questions in philosophy The first thing that I have to admit as a reviewer is that I enjoyed the book -- not just reading it, but scribbling out pages of scratch paper working on the puzzles inspired by the book -- that I probably would have paid up to about $200 for it (despite the fact that I disagreed with many of the conclusions, and even thought some of the arguments were pretty weak). I certainly don't mean that it's better than books by Richard Dawkins, Daniel Dennett, Steven Pinker, Malcolm Gladwell, or Steven Levitt and Steven Dubner (the Freakonomics and SuperFreakonomics team), but it will appeal to many of the same people.

Those authors' books typically marshall a large amount of research data and evidence in support of a thesis that seems contrarian but turns out to be probably true. The Big Questions (released November 3rd with a companion website and blog doesn't do that. The book is divided into many self-contained vignettes and side topics and independent arguments, which are based more on logic and reasoning than externally gathered evidence, and the arguments don't always convince you of the conclusions. But that's part of the fun: many of the arguments in the book are structured so rigorously, almost like mathematical proofs, that if you disagree the conclusion, the challenge is to figure out why you think the conclusion is wrong. (Nobody ever scribbled equations in the margins of Malcolm Gladwell's books trying to figure out if he was "right".)

You'll probably enjoy the book the most if the following are true for you:

• You enjoyed math all the way through high school, especially the paradoxes that seemed to grow out of elementary rules of logic or probability. Sometimes the paradoxes resulted from a flaw in one of the reasoning steps, so that identifying the flaw led to a deeper understanding of how to conduct those steps. And sometimes there really is no flaw in the reasoning, so that the conclusion, no matter how counterintuitive, must be true.
• Eventually, though, you ran out of "paradoxes" that could be described in the language of intermediate mathematics. There are other paradoxes lurking in mathematics, of course (like the celebrated Banach-Tarski paradox), but most of them require you to learn so much mathematics just to understand the paradox, that there aren't enough hours in the day.
• So, you'd be delighted to discover paradoxes in an entirely new field, where arguments built from elementary rules of logic, lead to a conclusion that seems at first to make no sense, but leads to a deeper understanding the more you think about it.

The core philosophy of The Big Questions -- not embodying any of the conclusions, but rather the rules of the game by which those conclusions should be reached -- is expressed in two lines near the end:

If you're objecting to a logical argument, try asking yourself exactly which line in that argument you're objecting to. If you can't identify the locus of your disagreement, you're probably just blathering.

(This quote makes Landsburg sound grumpier than he is; at this point in the book, he's just coming off of describing an exhausting round of e-mail argument with another professor who he felt was not playing by these rules.) I've believed this passionately for a long time, and to me it seems trivially true anyway: If an argument is organized into a series of steps, and you disagree with the conclusion, then some step in the argument must be the first step you disagree with, and if the author feels like each step in their argument follows by airtight logic from the previous step, then that's the point at which one of the two players is wrong. There's nothing more exasperating to me than writing what I think is a well-reasoned logical argument, sending it to the intended audience, and getting back a reply which makes it obvious that the recipient simply read my conclusion, disagreed with it, cleared their throat, and started typing out paragraphs describing their own view. Which they're entitled to, but they missed the point -- I was hoping that if they disagreed with my argument, they could pinpoint exactly what part they disagreed with. (If they had replied with their own argument structured like a sequence of logical steps, then that would at least be a tit-for-tat exchange, but that rarely happens -- people who believe in forming their arguments like rigorous proofs, usually also like to find the error in logical arguments that lead to the opposite conclusion.)

To give you some of the flavor: One chapter in The Big Questions contains an elegant argument against protectionist tariffs: Suppose that an American sells cameras for $80 but a foreigner wants to sell cameras in America for $60 apiece. An American who would have bought the $80 camera will now buy the $60 camera and hence is better off by $20. The seller now has to sell their own cameras for $60 to stay competitive, so they are worse off by at most $20 -- however, if they voluntarily switch to some other business, then they'll be better off than they were when they were selling cameras for $60, and therefore worse off by some amount less than $20 from their original position. So on balance, abolishing protectionist tariffs would be good for Americans. "Therefore," writes Landsburg, "it seems to me that the protectionist's position is even less respectable than the creationist's. If you're convinced that most scientists are liars -- that everything they say about fossils, for example, is false -- then you can be a logically consistent creationist. But you can't be a logically consistent protectionist."

But the best part of reading an argument like that is to try and come up with a counter-argument that is equally rigorous. I think Landsburg is right, but only insofar as it applies to benefits to Americans. That leaves out another part of the equation: whether the production of cheaper foreign goods is harmful to foreigners providing the cheap labor. The textbook answer from economic theory is that the factory jobs must make workers better off (or at least no worse off) than they were before, otherwise they wouldn't have taken the jobs voluntarily. On the other hand, conditions in overseas sweatshops are so notoriously dangerous and unpleasant that it seems hard to believe the opportunities leave workers better off on balance. So you could be a logically consistent protectionist if you believe that: (a) sweatshop workers systematically underestimate how much the factory jobs are harming them; and (b) the harm done to the workers outweighs the benefits of lower prices for Americans. I'm not sure if these statements are true, but they are logically consistent. Still, Landsburg's argument is about as concise as possible and seems to refute any argument that protectionism makes
Americans better off on average.

In another chapter, Landsburg discusses the recent atheist bestsellers such as Richard Dawkins's The God Delusion and suggests that these books are really directed against a non-existent enemy, because the evidence is quite strong that most adults do not really believe the tenets of any major religion anyway. There is the argument that "interfaith dialog" makes no sense if you really believe (as many major religions teach) that your own religion's tenets are settled beyond discussion. There is the argument that since economic theory consistently shows that people respond to threat of punishment, virtually no one behaves as if they actually believe in everlasting damnation after death as punishment for sin. And the fact that the voluntary martyrdom of suicide bombers is vastly more rare than most people believe, and a disproportionate number of those are children (as Landsburg says, "I do not deny that many children believe in God, just as I do not deny that many children believe in Santa Claus"). I'd wondered before about how many people really did believe in God, but in just a few pages this argument had me thinking that the number was a lot lower than I'd ever thought before.

On the other hand, there were some arguments that I didn't spend much time puzzling over at all. Landsburg summarizes the paradox of "free will", and his dismissal of the paradox, basically as follows: The interactions of atoms that make up our brains and our environments, are deterministic processes, so if you know the state of a system at a given point in time, you could predict the state at any future point in time if you had enough computational power (with a caveat about the randomness possibly introduced by quantum physics). "Where, then, is there room for free will?... Easy: There is room for free will on Tuesday, Wednesday, Thursday and Friday, as the human being in question engages in deliberations that ultimately cause his actions." He says that just as "weather" is shorthand for the aggregate of the interactions of trillions of water molecules, "free will" is the same kind of shorthand:

"What caused your decision to get drunk and watch Mystery Science Theater the night before your philosophy final? Free will. An insane person might object that free will can't be it at all, because free will is just a shorthand term for an indescribably complex process involving trillions of neurons, which in turn can be described in terms of quadrillions of atoms and quintillions of subatomic particles. So what? You still have free will, and you know it."

I wrote Landsburg to object that this misses what people really mean by "free will" -- it's not just a shorthand term for the aggregate of particle interactions that make up human choices. It means, very specifically, that you could possibly have done something other than what you did. Landsburg replied to this objection by e-mail: "I dispute that there is any way to make sense of a phrase like 'could possibly have done something else'. I know what it means to say you did something; spacetime consists of all the things that get done; it is what it is." And I agree; it's hard to pin down what the statement means. But it underlies all of our instincts and intuition about human choices and blame: "You could have called yesterday, but you didn't." "I should have studied harder last night." If determinism is true, then these statements make no sense, and therein lies what I think most people mean then they refer to the paradox of determinism vs. free will. I think the issue deserves more thought than it's given in the book.

This is followed by a passage arguing that the controversy over "ESP" is silly, because of course everyone knows certain things by "extra-sensory perception", if by that you mean "things perceived not through the senses" -- like mathematical truths, which are arrived at through thought and not sensory input. Writes Landsburg: "Some of those phenomena have one additional characteristic: They are physically impossible. But if you're going to define ESP by its impossibility, then of course there's no point in debating it... And if impossibility is not a criterion, then mathematical insight is as good an example of ESP -- in the everyday sense of the term -- as any instance of clairvoyance or telepathy." Actually, I think the everyday use of the word "ESP" refers to perceiving facts that do not logically have to be true (so mathematical facts are excluded) -- like "Someone is watching me right now" -- without sensory input. And, once you clarify the definition, most people agree there's no evidence for it, so the whole discussion seems uninteresting.

But even if you throw out 75% of the book's arguments (which is far more than I rejected), you should still enjoy puzzling through the remaining 25% and forming your own conclusions. The most interesting argument in the book, to me, is about how to properly answer the question: How much should the government be willing to spend, to save the life of one of it's citizens? Of course if you're Ayn Rand, the answer is zero, but if you want to answer the question according to the laws of economic efficiency, it's a tough one. Landsburg originally got into the debate by writing a column arguing that ventilator support was not the most efficient way to help the poor. (Unfortunately, he couched it in the language of "ventilator insurance", which I think clouded the issue. I think it would have been more clear to say: "If we're going to spend this money to help the poor at all, it would make more sense to spend it on groceries for a far larger number of people, than to spend it on ventilator support for one person.") Another more liberal economist, Robert Frank, responded with a New York Times editorial arguing with Landsburg's methods and coming up with his own reasoning. I think there are problems with the reasoning on both sides (not logical errors, but rather situations in which the rules that they have adopted, lead to paradoxes and untenable positions -- suggesting that both sides' axioms have to be thrown out), but I still don't know the answer. (My own opinion about the flaws in their logic, and an alternative answer, is at this link: "How much should government spend to save a single life?")

The Big Questions also has excursions into areas of science and mathematics that I had never fully understood before, and in some cases hadn't even thought about. Landsburg describes how he had first learned that colors could be arranged continuously into a color wheel, and later learned that they could be arranged continuously along a line according to their wavelengths, and then a friend pointed out the contradiction. Which is it? Do colors vary continuously in two dimensions (forming a wheel) or one (forming a line)? Or, wait a minute, we measure colors according to the strength of their red, green, and blue components, so don't they vary continuously in three dimensions? Well, the answer is in there.

There are also chapters on Heisenberg's uncertainty principle, Gödel's incompleteness theorem, and the quantum phenomenon of "spooky action at a distance", which explain all of the concepts more clearly than I'd ever heard them explained anywhere else. I think that most writers attempting to explain these concepts err either on the side of being too precise -- determined that everything they right be correct, with no regard for whether they reader grasps it or not -- or too vague -- giving the general air of mystery, but not explaining the rules governing how a phenomenon works, and how to work with those rules to derive other conclusions from them. Landsburg's chapter simply begins, "This chapter is full of lies. That's because I'll be explaining the foundations of quantum mechanics, and I assume that if you wanted a careful accounting of every detail, you'd be reading a textbook." The text then gives an example of considering an electron that moves in a conceptual "circle", where at some points on the circle it has a greater probability of manifesting itself in one location if you examine it, and at other points it has a greater probability of manifesting itself in another location. He uses this to dispel a common misconception about the uncertainty principle:

You're just idly wondering where the electron is. In most circumstances, quantum mechanics says that it's quite impossible for you to know the answer to that question.

Aha! A fundamental limitation on human knowledge, no? No. Here's why: Most of the time, the electron is nowhere. Asking "Where is the electron?" is akin to asking "What is the electron's favorite movie?". It's a nonsense question. The inability to answer nonsense questions is not a fundamental limitation on knowledge.

How can the electron be nowhere? Because electrons behave nothing at all like anything you're familiar with. Instead of a location, the electron has a quantum state.

This clarified something for me that had bugged me for years. I never took a course in quantum physics, but I had indeed always assumed that electrons did have a "location" and the uncertainty principle referred to a limit on our ability to determine that location. Unfortunately there are probably many people who get through an entire course in quantum physics without getting this cleared up.

Balanced against these valuable insights are some libertarian arguments that are probably nothing you haven't heard before, especially if you have read of one of Landsburg's earlier books, Fair Play -- subtitled "What your child can teach you about economics, values, and the meaning of life", although the book was clearly about what he was teaching to his daughter. Many reviewers of Fair Play took note of passages like this one:

Most people have instinctive sympathy for the man who says "I tried for months to get a job and nobody would hire me. Only in desperation did I turn to theft." The same people have only scorn for the man who says "I tried for months to get a date and nobody would go out with me. Only in desperation did I turn to rape."

While I think most rape victims would have some choice words about the comparison, I was more unpersuaded because the passage wasn't structured like a true argument. In a good argument -- like Landsburg's earlier argument against protectionist tariffs -- -- you start with premises that seem apparently true, proceed by steps that seem apparently valid, and end with a conclusion that may not have been obvious from the outset. But in this case, the premise is the argument -- either you think rape and theft are comparable, or you don't. I don't think they are, because (a) the harm to a rape victim is out of proportion to the "benefit" to the rapist, and (b) notwithstanding the claims of college males, you won't actually die without sex. (Just as a thought experiment, if you would die without sex, and a man hadn't been able to get any women to sleep with him, and the government didn't provide any sort of sex "safety net", more people probably would feel sympathy for the rapist, if he only did it to save his own life.)

Some passages in The Big Questions are recycled from Fair Play and require a (just) slightly more thoughtful rebuttal. Landsburg argues that most parents, deep down, must not believe in redistributive taxation because

"I have never, ever, heard a parent say to a child that it's okay to forcibly take toys away from other children who have more toys than you do. Nor have I ever heard a parent tell a child that if one kid has more toys than the others, then it's okay for those others to form a 'government' and vote to take those toys away."

OK, but... I have also never heard a parent tell their child that it was OK to build a "jail" and put other kids in that "jail" for wrongdoing. And yet almost everyone, even libertarians, supports some form of imprisonment for lawbreakers. The lesson here is that there are some powers that are appropriate to delegate to a democratically elected government, with all the right checks and balances, but that you don't want random vigilantes seizing for themselves. So if you want a principled argument against taxation, it would take more than that.

And other passages in Fair Play deservedly did not make the cut of being imported into The Big Questions:

The massacre at Waco took place only days after my daughter (then aged six) had asked me how the government uses our tax dollars. When she walked in on the television coverage of flamed and carnage, I told her that now she was seeing the answer to her question. And when she heard that there were children in there, that they were burning children, her eyes grew wide with horror, and I both hope and believe that she will never forget that moment.

If you want 230 pages of that, then Fair Play is the book for you!

Of the libertarian arguments that did get carried over into The Big Questions, I think the problem with most of them is not that I think the conclusion is wrong, but, again, that the whole argument is the premise, and if you disagree with the premise then there's nothing to think about. For example:

Bert wants to hire an office manager and Ernie wants to manage an office. The law allows Ernie to refuse any job for any reason. If he doesn't like Albanians, he doesn't have to work for one. Bert is held to a higher standard: If he lets it be known that no Albanians need apply, he'd better have a damned good lawyer.

These asymmetries grate against the most fundamental requirement of fairness -- that people should be treated equally, in the sense that their rights and responsibilities should not change because of irrelevant external circumstances.

But I think the laws do treat all people equally, because they apply equally whether Bert is discriminating in deciding whether to hire Ernie, or whether Ernie is discriminating in deciding whether to hire Bert. The laws don't apply equally to all roles that people play, which is the distinction that Landsburg is highlighting -- but laws never apply equally to different roles, since roles are defined by what we do, and what is the point of laws, except to draw distinctions based on behaviors? So there may be some other argument against anti-discrimination laws, but "symmetry" by itself wouldn't be enough.

A footnote in this chapter of The Big Questions says, "Portions of this chapter are adapted from my earlier book Fair Play." In the margin where I'd been scribbling all of my notes and equations and counterarguments, I wrote, "That's what's wrong with it!"

And yet, as I said, I would probably have paid up to about $200 for the book, based on how much I enjoyed the parts that I did like. At one point Landsburg praises an insight from Daniel Dennett and Douglas Hofstadter and adds, "You should read all their books." Yes, and all of Richard Dawkins's and Malcolm Gladwell's and Steven Pinker's and Dubner's and Levitt's books, for starters. Landsburg himself would probably agree that it's more important to read those books, than this one. But there's time in your life to read The Big Questions as well. It's even structured so you can consume it in bite-sized portions while taking a break from working your way through those other books -- which are, in truth, more valuable, but not as much fun.

You can purchase The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Frequent Slashdot contributor Bennett Haselton changes things up today by reviewing The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics. Questions that big need a big review and you can learn what Bennett has to say about it all by reading below. The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics author Steven E. Landsburg pages 288 pages publisher Free Press rating 8/10 reviewer Bennett Haselton ISBN 978-1439148211 summary Steven Landsburg uses concepts from mathematics, economics, and physics to address the big questions in philosophy The first thing that I have to admit as a reviewer is that I enjoyed the book -- not just reading it, but scribbling out pages of scratch paper working on the puzzles inspired by the book -- that I probably would have paid up to about $200 for it (despite the fact that I disagreed with many of the conclusions, and even thought some of the arguments were pretty weak). I certainly don't mean that it's better than books by Richard Dawkins, Daniel Dennett, Steven Pinker, Malcolm Gladwell, or Steven Levitt and Steven Dubner (the Freakonomics and SuperFreakonomics team), but it will appeal to many of the same people.

Those authors' books typically marshall a large amount of research data and evidence in support of a thesis that seems contrarian but turns out to be probably true. The Big Questions (released November 3rd with a companion website and blog doesn't do that. The book is divided into many self-contained vignettes and side topics and independent arguments, which are based more on logic and reasoning than externally gathered evidence, and the arguments don't always convince you of the conclusions. But that's part of the fun: many of the arguments in the book are structured so rigorously, almost like mathematical proofs, that if you disagree the conclusion, the challenge is to figure out why you think the conclusion is wrong. (Nobody ever scribbled equations in the margins of Malcolm Gladwell's books trying to figure out if he was "right".)

You'll probably enjoy the book the most if the following are true for you:

• You enjoyed math all the way through high school, especially the paradoxes that seemed to grow out of elementary rules of logic or probability. Sometimes the paradoxes resulted from a flaw in one of the reasoning steps, so that identifying the flaw led to a deeper understanding of how to conduct those steps. And sometimes there really is no flaw in the reasoning, so that the conclusion, no matter how counterintuitive, must be true.
• Eventually, though, you ran out of "paradoxes" that could be described in the language of intermediate mathematics. There are other paradoxes lurking in mathematics, of course (like the celebrated Banach-Tarski paradox), but most of them require you to learn so much mathematics just to understand the paradox, that there aren't enough hours in the day.
• So, you'd be delighted to discover paradoxes in an entirely new field, where arguments built from elementary rules of logic, lead to a conclusion that seems at first to make no sense, but leads to a deeper understanding the more you think about it.

The core philosophy of The Big Questions -- not embodying any of the conclusions, but rather the rules of the game by which those conclusions should be reached -- is expressed in two lines near the end:

If you're objecting to a logical argument, try asking yourself exactly which line in that argument you're objecting to. If you can't identify the locus of your disagreement, you're probably just blathering.

(This quote makes Landsburg sound grumpier than he is; at this point in the book, he's just coming off of describing an exhausting round of e-mail argument with another professor who he felt was not playing by these rules.) I've believed this passionately for a long time, and to me it seems trivially true anyway: If an argument is organized into a series of steps, and you disagree with the conclusion, then some step in the argument must be the first step you disagree with, and if the author feels like each step in their argument follows by airtight logic from the previous step, then that's the point at which one of the two players is wrong. There's nothing more exasperating to me than writing what I think is a well-reasoned logical argument, sending it to the intended audience, and getting back a reply which makes it obvious that the recipient simply read my conclusion, disagreed with it, cleared their throat, and started typing out paragraphs describing their own view. Which they're entitled to, but they missed the point -- I was hoping that if they disagreed with my argument, they could pinpoint exactly what part they disagreed with. (If they had replied with their own argument structured like a sequence of logical steps, then that would at least be a tit-for-tat exchange, but that rarely happens -- people who believe in forming their arguments like rigorous proofs, usually also like to find the error in logical arguments that lead to the opposite conclusion.)

To give you some of the flavor: One chapter in The Big Questions contains an elegant argument against protectionist tariffs: Suppose that an American sells cameras for $80 but a foreigner wants to sell cameras in America for $60 apiece. An American who would have bought the $80 camera will now buy the $60 camera and hence is better off by $20. The seller now has to sell their own cameras for $60 to stay competitive, so they are worse off by at most $20 -- however, if they voluntarily switch to some other business, then they'll be better off than they were when they were selling cameras for $60, and therefore worse off by some amount less than $20 from their original position. So on balance, abolishing protectionist tariffs would be good for Americans. "Therefore," writes Landsburg, "it seems to me that the protectionist's position is even less respectable than the creationist's. If you're convinced that most scientists are liars -- that everything they say about fossils, for example, is false -- then you can be a logically consistent creationist. But you can't be a logically consistent protectionist."

But the best part of reading an argument like that is to try and come up with a counter-argument that is equally rigorous. I think Landsburg is right, but only insofar as it applies to benefits to Americans. That leaves out another part of the equation: whether the production of cheaper foreign goods is harmful to foreigners providing the cheap labor. The textbook answer from economic theory is that the factory jobs must make workers better off (or at least no worse off) than they were before, otherwise they wouldn't have taken the jobs voluntarily. On the other hand, conditions in overseas sweatshops are so notoriously dangerous and unpleasant that it seems hard to believe the opportunities leave workers better off on balance. So you could be a logically consistent protectionist if you believe that: (a) sweatshop workers systematically underestimate how much the factory jobs are harming them; and (b) the harm done to the workers outweighs the benefits of lower prices for Americans. I'm not sure if these statements are true, but they are logically consistent. Still, Landsburg's argument is about as concise as possible and seems to refute any argument that protectionism makes
Americans better off on average.

In another chapter, Landsburg discusses the recent atheist bestsellers such as Richard Dawkins's The God Delusion and suggests that these books are really directed against a non-existent enemy, because the evidence is quite strong that most adults do not really believe the tenets of any major religion anyway. There is the argument that "interfaith dialog" makes no sense if you really believe (as many major religions teach) that your own religion's tenets are settled beyond discussion. There is the argument that since economic theory consistently shows that people respond to threat of punishment, virtually no one behaves as if they actually believe in everlasting damnation after death as punishment for sin. And the fact that the voluntary martyrdom of suicide bombers is vastly more rare than most people believe, and a disproportionate number of those are children (as Landsburg says, "I do not deny that many children believe in God, just as I do not deny that many children believe in Santa Claus"). I'd wondered before about how many people really did believe in God, but in just a few pages this argument had me thinking that the number was a lot lower than I'd ever thought before.

On the other hand, there were some arguments that I didn't spend much time puzzling over at all. Landsburg summarizes the paradox of "free will", and his dismissal of the paradox, basically as follows: The interactions of atoms that make up our brains and our environments, are deterministic processes, so if you know the state of a system at a given point in time, you could predict the state at any future point in time if you had enough computational power (with a caveat about the randomness possibly introduced by quantum physics). "Where, then, is there room for free will?... Easy: There is room for free will on Tuesday, Wednesday, Thursday and Friday, as the human being in question engages in deliberations that ultimately cause his actions." He says that just as "weather" is shorthand for the aggregate of the interactions of trillions of water molecules, "free will" is the same kind of shorthand:

"What caused your decision to get drunk and watch Mystery Science Theater the night before your philosophy final? Free will. An insane person might object that free will can't be it at all, because free will is just a shorthand term for an indescribably complex process involving trillions of neurons, which in turn can be described in terms of quadrillions of atoms and quintillions of subatomic particles. So what? You still have free will, and you know it."

I wrote Landsburg to object that this misses what people really mean by "free will" -- it's not just a shorthand term for the aggregate of particle interactions that make up human choices. It means, very specifically, that you could possibly have done something other than what you did. Landsburg replied to this objection by e-mail: "I dispute that there is any way to make sense of a phrase like 'could possibly have done something else'. I know what it means to say you did something; spacetime consists of all the things that get done; it is what it is." And I agree; it's hard to pin down what the statement means. But it underlies all of our instincts and intuition about human choices and blame: "You could have called yesterday, but you didn't." "I should have studied harder last night." If determinism is true, then these statements make no sense, and therein lies what I think most people mean then they refer to the paradox of determinism vs. free will. I think the issue deserves more thought than it's given in the book.

This is followed by a passage arguing that the controversy over "ESP" is silly, because of course everyone knows certain things by "extra-sensory perception", if by that you mean "things perceived not through the senses" -- like mathematical truths, which are arrived at through thought and not sensory input. Writes Landsburg: "Some of those phenomena have one additional characteristic: They are physically impossible. But if you're going to define ESP by its impossibility, then of course there's no point in debating it... And if impossibility is not a criterion, then mathematical insight is as good an example of ESP -- in the everyday sense of the term -- as any instance of clairvoyance or telepathy." Actually, I think the everyday use of the word "ESP" refers to perceiving facts that do not logically have to be true (so mathematical facts are excluded) -- like "Someone is watching me right now" -- without sensory input. And, once you clarify the definition, most people agree there's no evidence for it, so the whole discussion seems uninteresting.

But even if you throw out 75% of the book's arguments (which is far more than I rejected), you should still enjoy puzzling through the remaining 25% and forming your own conclusions. The most interesting argument in the book, to me, is about how to properly answer the question: How much should the government be willing to spend, to save the life of one of it's citizens? Of course if you're Ayn Rand, the answer is zero, but if you want to answer the question according to the laws of economic efficiency, it's a tough one. Landsburg originally got into the debate by writing a column arguing that ventilator support was not the most efficient way to help the poor. (Unfortunately, he couched it in the language of "ventilator insurance", which I think clouded the issue. I think it would have been more clear to say: "If we're going to spend this money to help the poor at all, it would make more sense to spend it on groceries for a far larger number of people, than to spend it on ventilator support for one person.") Another more liberal economist, Robert Frank, responded with a New York Times editorial arguing with Landsburg's methods and coming up with his own reasoning. I think there are problems with the reasoning on both sides (not logical errors, but rather situations in which the rules that they have adopted, lead to paradoxes and untenable positions -- suggesting that both sides' axioms have to be thrown out), but I still don't know the answer. (My own opinion about the flaws in their logic, and an alternative answer, is at this link: "How much should government spend to save a single life?")

The Big Questions also has excursions into areas of science and mathematics that I had never fully understood before, and in some cases hadn't even thought about. Landsburg describes how he had first learned that colors could be arranged continuously into a color wheel, and later learned that they could be arranged continuously along a line according to their wavelengths, and then a friend pointed out the contradiction. Which is it? Do colors vary continuously in two dimensions (forming a wheel) or one (forming a line)? Or, wait a minute, we measure colors according to the strength of their red, green, and blue components, so don't they vary continuously in three dimensions? Well, the answer is in there.

There are also chapters on Heisenberg's uncertainty principle, Gödel's incompleteness theorem, and the quantum phenomenon of "spooky action at a distance", which explain all of the concepts more clearly than I'd ever heard them explained anywhere else. I think that most writers attempting to explain these concepts err either on the side of being too precise -- determined that everything they right be correct, with no regard for whether they reader grasps it or not -- or too vague -- giving the general air of mystery, but not explaining the rules governing how a phenomenon works, and how to work with those rules to derive other conclusions from them. Landsburg's chapter simply begins, "This chapter is full of lies. That's because I'll be explaining the foundations of quantum mechanics, and I assume that if you wanted a careful accounting of every detail, you'd be reading a textbook." The text then gives an example of considering an electron that moves in a conceptual "circle", where at some points on the circle it has a greater probability of manifesting itself in one location if you examine it, and at other points it has a greater probability of manifesting itself in another location. He uses this to dispel a common misconception about the uncertainty principle:

You're just idly wondering where the electron is. In most circumstances, quantum mechanics says that it's quite impossible for you to know the answer to that question.

Aha! A fundamental limitation on human knowledge, no? No. Here's why: Most of the time, the electron is nowhere. Asking "Where is the electron?" is akin to asking "What is the electron's favorite movie?". It's a nonsense question. The inability to answer nonsense questions is not a fundamental limitation on knowledge.

How can the electron be nowhere? Because electrons behave nothing at all like anything you're familiar with. Instead of a location, the electron has a quantum state.

This clarified something for me that had bugged me for years. I never took a course in quantum physics, but I had indeed always assumed that electrons did have a "location" and the uncertainty principle referred to a limit on our ability to determine that location. Unfortunately there are probably many people who get through an entire course in quantum physics without getting this cleared up.

Balanced against these valuable insights are some libertarian arguments that are probably nothing you haven't heard before, especially if you have read of one of Landsburg's earlier books, Fair Play -- subtitled "What your child can teach you about economics, values, and the meaning of life", although the book was clearly about what he was teaching to his daughter. Many reviewers of Fair Play took note of passages like this one:

Most people have instinctive sympathy for the man who says "I tried for months to get a job and nobody would hire me. Only in desperation did I turn to theft." The same people have only scorn for the man who says "I tried for months to get a date and nobody would go out with me. Only in desperation did I turn to rape."

While I think most rape victims would have some choice words about the comparison, I was more unpersuaded because the passage wasn't structured like a true argument. In a good argument -- like Landsburg's earlier argument against protectionist tariffs -- -- you start with premises that seem apparently true, proceed by steps that seem apparently valid, and end with a conclusion that may not have been obvious from the outset. But in this case, the premise is the argument -- either you think rape and theft are comparable, or you don't. I don't think they are, because (a) the harm to a rape victim is out of proportion to the "benefit" to the rapist, and (b) notwithstanding the claims of college males, you won't actually die without sex. (Just as a thought experiment, if you would die without sex, and a man hadn't been able to get any women to sleep with him, and the government didn't provide any sort of sex "safety net", more people probably would feel sympathy for the rapist, if he only did it to save his own life.)

Some passages in The Big Questions are recycled from Fair Play and require a (just) slightly more thoughtful rebuttal. Landsburg argues that most parents, deep down, must not believe in redistributive taxation because

"I have never, ever, heard a parent say to a child that it's okay to forcibly take toys away from other children who have more toys than you do. Nor have I ever heard a parent tell a child that if one kid has more toys than the others, then it's okay for those others to form a 'government' and vote to take those toys away."

OK, but... I have also never heard a parent tell their child that it was OK to build a "jail" and put other kids in that "jail" for wrongdoing. And yet almost everyone, even libertarians, supports some form of imprisonment for lawbreakers. The lesson here is that there are some powers that are appropriate to delegate to a democratically elected government, with all the right checks and balances, but that you don't want random vigilantes seizing for themselves. So if you want a principled argument against taxation, it would take more than that.

And other passages in Fair Play deservedly did not make the cut of being imported into The Big Questions:

The massacre at Waco took place only days after my daughter (then aged six) had asked me how the government uses our tax dollars. When she walked in on the television coverage of flamed and carnage, I told her that now she was seeing the answer to her question. And when she heard that there were children in there, that they were burning children, her eyes grew wide with horror, and I both hope and believe that she will never forget that moment.

If you want 230 pages of that, then Fair Play is the book for you!

Of the libertarian arguments that did get carried over into The Big Questions, I think the problem with most of them is not that I think the conclusion is wrong, but, again, that the whole argument is the premise, and if you disagree with the premise then there's nothing to think about. For example:

Bert wants to hire an office manager and Ernie wants to manage an office. The law allows Ernie to refuse any job for any reason. If he doesn't like Albanians, he doesn't have to work for one. Bert is held to a higher standard: If he lets it be known that no Albanians need apply, he'd better have a damned good lawyer.

These asymmetries grate against the most fundamental requirement of fairness -- that people should be treated equally, in the sense that their rights and responsibilities should not change because of irrelevant external circumstances.

But I think the laws do treat all people equally, because they apply equally whether Bert is discriminating in deciding whether to hire Ernie, or whether Ernie is discriminating in deciding whether to hire Bert. The laws don't apply equally to all roles that people play, which is the distinction that Landsburg is highlighting -- but laws never apply equally to different roles, since roles are defined by what we do, and what is the point of laws, except to draw distinctions based on behaviors? So there may be some other argument against anti-discrimination laws, but "symmetry" by itself wouldn't be enough.

A footnote in this chapter of The Big Questions says, "Portions of this chapter are adapted from my earlier book Fair Play." In the margin where I'd been scribbling all of my notes and equations and counterarguments, I wrote, "That's what's wrong with it!"

And yet, as I said, I would probably have paid up to about $200 for the book, based on how much I enjoyed the parts that I did like. At one point Landsburg praises an insight from Daniel Dennett and Douglas Hofstadter and adds, "You should read all their books." Yes, and all of Richard Dawkins's and Malcolm Gladwell's and Steven Pinker's and Dubner's and Levitt's books, for starters. Landsburg himself would probably agree that it's more important to read those books, than this one. But there's time in your life to read The Big Questions as well. It's even structured so you can consume it in bite-sized portions while taking a break from working your way through those other books -- which are, in truth, more valuable, but not as much fun.

You can purchase The Big Questions: Tackling the Problems of Philosophy with Ideas from Mathematics, Economics and Physics from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

halfEvilTech writes "Five years ago today, Mozilla released Firefox 1.0. Ars celebrates the occasion by taking a trip back in time to revisit our classic coverage of the original release." For fun, we dug up the oldest Slashdot Firefox story, which was a Firebird story proclaiming yet another name change from Feb '04. At least this name change stuck.

TechnologyResource writes "More than two years ago in California, a police officer wrote Shaun Malone a ticket for going 62mph in a 45-mph zone. Malone was ordered to pay a $190 fine, but his parents appealed the decision, saying data from a GPS tracking system they installed in his car to monitor his driving proved he was not speeding. What ensued was the longest court battle over a speeding ticket in Sonoma county history. The case also represented the first time anyone locally had tried to beat a ticket using GPS. The teen's GPS pegged the car at 45 mph in virtually the same location. At issue was the distance from the stoplight — site of the first GPS 'ping' that showed Malone stopped — to the second ping 30 seconds later, when he was going 45 mph. Last week, Commissioner Carla Bonilla ruled the GPS data confirmed the prosecution's contention that Malone had to have exceeded the speed limit and would have to pay the $190 fine. 'This case ensures that other law enforcement agencies throughout the state aren't going to have to fight a case like this where GPS is used to cast doubt on radar,' said Sgt. Ken Savano, who oversees the traffic division. However, Commissioner Bonilla noted the accuracy of the GPS system was not challenged by either side in the dispute, but rather they had different interpretations of the data. Bonilla ruled the GPS data confirmed the prosecution's contention that Malone had to have exceeded the speed limit."

chill writes "Skype's co-founders, Janus Friis and Niklas Zennstrom, have agreed to transfer ownership of the remaining Skype technology that eBay didn't own, paving the way for eBay to complete its sale of a majority stake in Skype to an investor consortium. In exchange, Friis and Zennstrom will join the investor consortium and obtain a 14 percent stake in Skype. The other consortium partners, led by Silver Lake, will own a 56 percent stake in Skype, and eBay will hold on to 30 percent, eBay said Friday."

AndrewDBarker writes "Modern Warfare 2 will use a matchmaking setup powered by IWNet for online play (as we've discussed). It's too early to say what Rage will use, but Carmack indicated he believed the servers are something of a remnant of the early days of PC gaming. That said, he realizes the affinity many PC gamers have for them — and is glad Rage won't be leading the charge away from them. 'The great thing is we won't have to be a pioneer on that,' he says. 'We'll see how it works out for everyone else.'"

Michael J. Ross writes "Of the leading content management systems used by developers for creating websites, Drupal is highly regarded for many characteristics, including a much smaller initial footprint, compared to Joomla and other CMSs. Yet some developers find this a disadvantage as well, because one of the most common criticisms leveled against Drupal is its lack of built-in support for images and multimedia elements — thereby forcing new Drupal developers to choose from the thousands of contributed Drupal modules those that would be optimal for implementing their websites' multimedia functionality. Aaron Winborn's book Drupal Multimedia is intended as a guide to help such developers." Keep reading for the rest of Michael's review. Drupal Multimedia author Aaron Winborn pages 264 publisher Packt Publishing rating 7/10 reviewer Michael J. Ross ISBN 978-1-847194-60-2 summary A guidebook for adding images, videos, and audio content to Drupal sites The book was put out by Packt Publishing on 30 October 2008, under the ISBN 978-1-847194-60-2. On the publisher's book page, visitors can learn more details about the book and its author, purchase the electronic or print editions of the book (or both, at a discount), download the sample source code, send feedback or questions to the publisher, read the book's table of contents, or download a sample chapter for free ("Third Party Video") in PDF format. As with all other Packt Publishing titles, the errata is annoyingly not available directly from the book page; instead the visitor must go to the general Packt Publishing support page, find the title in a lengthy drop-down list box, click a button, and finally click another link (the one that should have been on the book page from the start) — only to have the errata displayed in a pop-up window. Among all the technical book publishers, Packt's procedure for accessing errata is surely the most tedious, and one can only hope it will be improved in the future. As of this writing, only one erratum has been reported. It is listed as being on "page 0," but that instead should read "page 34" (an erratum in an erratum!). Speaking of online resources, one would expect the author's own site to have further information on the book, but there does not appear to be any there.

Drupal Multimedia is a fairly slender volume, at 264 pages, no doubt because it focuses on a limited subject area — implementing multimedia with some key contributed modules — as opposed to most of the recent spate of Drupal books, some of which try to cover every major aspect of the CMS. The material in Aaron Winborn's book is organized into eleven chapters, addressing most if not all of the key topics within the chosen subject area: Drupal basics; images, galleries, and slideshows; image theming and effects; third-party and local video; file management; audio nodes and fields; theming audio; and the future of multimedia in Drupal. The book concludes with a skimpy five-page index, which fails to contain such basic entries as Flash, FLV, SWF, sprites, star ratings, slideshows, and countless others. A robust index is especially critical for any technical book, such as this one, that divides related topics among multiple chapters, and has section and subsection names that in some cases are quite similar to one another and thus could be easily confused.

Because this book is geared more toward programmers new to Drupal, and not well-versed veterans, the first chapter — the second longest in the book — introduces the reader to the core concepts of Drupal (nodes, regions, blocks, themes, and modules — core and contributed) as well as two essential modules (CCK and Views). The explanations do not go into any great detail, but should be enough to give any Drupal newbie a head start. Nonetheless, readers may be confused by the screenshots on pages 16 through 19, which appear to be from Drupal 5. Also, the brief coverage of views arguments is inadequate, and needs to be beefed to be useful later in the book. For creating a new theme, the author advises copying wholesale an existing theme; instead, a sub-theme is a much better approach. Chapter 1 wraps up with a discussion of some basic concepts in Drupal theming, which makes puzzling the title of the section, "Advanced Theming." Speaking of themes, readers should note that when the author refers to "theming" an image or video, he means making the uploaded file display as content on the node's page (and not just exist as an attachment to that node).

For many programmers new to Drupal, the first hurdle they encounter is how to add an image to the content of a page or story — a seemingly trivial task that is built into most major CMSs — without writing HTML and hard coding the path of an image file they FTP-ed to the server. Drupal version 6 and presumably all prior versions, do not have native support for uploading and embedding in-line images. In his second chapter, the author explains how one can create image galleries, teaser thumbnails, and images embedded in content. However, in the discussion on page 45, some details are incorrect, such as the label for the "Save" button (three times) and the presence of the galleries drop-down list. Readers will undoubtedly be confused by two additional inaccuracies: There is no Navigation menu item for displaying the "image galleries" created by default, because initially the image_gallery view has no menu assigned in the Gallery page settings. Secondly, the gallery description is not shown on the gallery page; in fact, it is not even listed as an available view field. The section titled "Image Gallery Settings" suggests that the author may have been using an older version of the Image module. But this probably does not explain the erroneous statement on page 56, that "image nodes created with Image attach will automatically be marked as not published." The chapter concludes with an explanation of how to embed an image in content, using manually inserted image tags, or the ImageAssist module, optionally supplemented with a WYSIWYG HTML editor, such as TinyMCE. The fourth chapter looks at how to theme images, and discusses — it greatly varying levels of detail — style overriding, the Firebug Firefox extension, the Theme Developer module, image nodes, image-based rollover menus, sprites, light boxes, star ratings, slideshows, and various special effects: drop shadows, magnification, and watermarks.

The subsequent chapter — oddly titled "Developing for Images" — extends the discussion by showing how to insert images as fields utilizing ImageField and several supporting modules. One of those modules is referred to as "FileField Tokens" (page 70), but there is no such module; the author probably meant ImageField Tokens. Also extending the previously noted problem of non-Drupal 6 content, is the screenshot for "Display fields," on page 83, as well as the narrative, which appear to be pre-version 6. The latter half of the chapter delves into how to create galleries and slideshows (using views), user pictures, and images associated with taxonomy terms.

With Chapters 5 and 6, the author shifts attention to what is perhaps the second most commonly used type of multimedia on websites nowadays — video — with the former of those chapters devoted to third-party videos (such as content hosted on YouTube), while the latter chapter is devoted to "local video" (local in the sense of hosted on one's own remote Web server — not one's local development machine). The author demonstrates how to utilize a YouTube-hosted video, first using core Drupal modules only, then using the Embedded Video Field module. For using local video files, the author shows how to use the FileField module so the user can upload QuickTime video files. Unfortunately, the instructions on page 146 may prove confusing to beginners, since it is not entirely clear as to whether the later, more-detailed paragraphs are repeating earlier instructions, or specifying something new. More significantly, the use of the FileField module necessitates writing theme PHP code, just to have the video display on the page — which less technical readers may not feel comfortable attempting on their sites. The second part of the chapter may be more useful to the typical reader, because it covers how to embed Flash videos, a more popular format. The author advocates the use of the jQuery Media module (which he created) in conjunction with the jQ module. Unfortunately for the reader, the details of implementing this approach are glossed over at the end of the chapter, with only meager instructions ("... add .node .content a to the classes."), and without any illustrative example. No explanation is provided as to why this particular JavaScript-dependent solution is recommended, as opposed to a more straightforward one, such as the Flash Node module — which is far less problematic for FLV files. (By the way, the author states that he and some other developers are creating a fully GPL media player module and that there is a development version available of this Media Player module. But there is no such version on that page, and the situation may never change, because the project appears to have fizzled in August 2008, judging by the comments on the Drupal.org site and the author's site.)

In written tutorials, videocasts, and other discussions of Drupal multimedia, one important area that is often neglected is asset management. This includes such seemingly mundane matters as where in a Drupal site's file system one should place plug-in files and even the uploaded multimedia files themselves. A more far-reaching topic is how to best associate multimedia assets with nodes so they can be accessed by various modules — for instance, as stand-alone content types versus CCK fields. Chapter 7 examines some of these topics, first discussing how to create and theme nodes whose associated videos can be used elsewhere on a site, such as in a gallery — using the Embedded Media Field and Node Reference modules. However, some readers may become frustrated because a couple critical steps are skipped, and, even worse, no guidance is provided as to how to make the video show up on a node reference content page, or what content provider selection to use (since "Local" is not an option). Next the author considers how to set access to videos by user role — using the Asset module. Unfortunately, the reader is apparently not shown how to do anything useful with video content uploaded and managed using the Asset module, including the scenario proposed at the beginning of the section. (Incidentally, one might assume that the author's solution would use the Asset Embedded Media submodule, but it is not compatible with the latest version of Drupal 6.) The Media Mover module, and its many submodules, offer an alternate method of video asset management, and the author shows how to e-mail a video from a mobile phone, to be automatically attached to a new blog post. The chapter concludes with a brief look at Kaltura, an open-source platform for storing and editing multimedia.

Some Web developers and end-users may consider online audio as the poor cousin of video. In truth, audio-only content plays a key role in many Web applications — from podcasts embedded in RSS feeds, to sample tracks on music sellers' websites. The subsequent three chapters of the book are devoted to managing audio content within Drupal using several resources and solutions — specifically, the Audio, getID3, FileField, jQuery Media, Embedded Media Field, XSPF Playlist, and Views modules

In the last chapter, titled "The Future of Drupal Multimedia," the author speculates as to what media-related capabilities he thinks we will likely find in Drupal 7 and beyond — such as native file handling (via hook_file) and multimedia support in core Drupal, the merging or deprecation of non-FileField modules, dissociation of data from nodes, improved module interfaces and usability, embeddable widgets (for data distribution), semantic multimedia (microformats, RDF, and taxonomy-powered tagging), mobile Web access, virtual reality (such as Second Life), tactile and olfactory media, and motion sensing (such as the Wii Remote controller).

One laudable feature of this book is the inclusion of numerous screenshots, which can be quite reassuring to a reader getting lost in the technical minutia of any particular recipe. Also helpful is the manner in which the author, for the most part, keeps the reader informed as to all configuration settings — and where to find them within the Drupal administration interface — that the reader must or may want to modify, depending on his or her needs. Technical books that fail to do this can be extremely frustrating to anyone trying to learn a nontrivial technology.

Yet there are some major flaws with the book: Far too much of the material suggests that the author was using Drupal 5. Aside from the screenshots mentioned earlier, sections of the text point in that direction, such as the statement, "The multiple image issue might be taken care of by Drupal 6" (page 56). Fortunately, none of these gaffes prevent the reader from learning how to perform the tasks using version 6. The second and more important flaw is the poor coverage of Flash content, as detailed above. A follow-up edition to the book, in which all of these problems are resolved, would be most welcome and valuable.

A revision would also be an opportunity to fix the grammatical errors that should have been caught in the proofreading process. For instance, the fourth complete sentence on page 11, is missing a verb. Errata include "Autrhor" (credits page), "you [have] learned" (page 2), ". you'll" (page 2), a ")" without a "(" to match it (page 17), "isin" (page 31), "it [is] installed" (page 32), "provide files" (page 33; should instead read "provide functions"), "hierarchal" (page 46), "formated" (page 57), "[the] FTP" (page 75), "menu — By" (page 117), "going a view" (page 119), "quicktime" (page 146), and "[Submit] Audio" (page 179). In addition, there are eight pairs of adjacent words missing their separating spaces — five on page 159, and three more on page 174.

As seen in many other Packt Publishing titles, this one contains excessive usage of inappropriate title case (e.g., several on page 8 and 9 alone), though occasionally title case is neglected (e.g., "Image attach" throughout the book). In addition, some of the phrasing is rather awkward, which may pose no barrier to a reader who already understands the particular idea being discussed in the text, but could prove a real detriment to anyone unfamiliar with that idea. For instance, on page 36, the author states that "Often you may wish to override a theme that is not provided as a file in the default theme." But no theme is contained within a single file, and one does not override themes anyway; rather, one can disable a theme, or modify a copy of it, or create a variation as a sub-theme.

Yet overall, this book's strengths outweigh its weaknesses. For Drupal developers who wish to add image, audio, and video content to their sites, Drupal Multimedia is a useful resource with which to begin.

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

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

Michael J. Ross writes "Of the leading content management systems used by developers for creating websites, Drupal is highly regarded for many characteristics, including a much smaller initial footprint, compared to Joomla and other CMSs. Yet some developers find this a disadvantage as well, because one of the most common criticisms leveled against Drupal is its lack of built-in support for images and multimedia elements — thereby forcing new Drupal developers to choose from the thousands of contributed Drupal modules those that would be optimal for implementing their websites' multimedia functionality. Aaron Winborn's book Drupal Multimedia is intended as a guide to help such developers." Keep reading for the rest of Michael's review. Drupal Multimedia author Aaron Winborn pages 264 publisher Packt Publishing rating 7/10 reviewer Michael J. Ross ISBN 978-1-847194-60-2 summary A guidebook for adding images, videos, and audio content to Drupal sites The book was put out by Packt Publishing on 30 October 2008, under the ISBN 978-1-847194-60-2. On the publisher's book page, visitors can learn more details about the book and its author, purchase the electronic or print editions of the book (or both, at a discount), download the sample source code, send feedback or questions to the publisher, read the book's table of contents, or download a sample chapter for free ("Third Party Video") in PDF format. As with all other Packt Publishing titles, the errata is annoyingly not available directly from the book page; instead the visitor must go to the general Packt Publishing support page, find the title in a lengthy drop-down list box, click a button, and finally click another link (the one that should have been on the book page from the start) — only to have the errata displayed in a pop-up window. Among all the technical book publishers, Packt's procedure for accessing errata is surely the most tedious, and one can only hope it will be improved in the future. As of this writing, only one erratum has been reported. It is listed as being on "page 0," but that instead should read "page 34" (an erratum in an erratum!). Speaking of online resources, one would expect the author's own site to have further information on the book, but there does not appear to be any there.

Drupal Multimedia is a fairly slender volume, at 264 pages, no doubt because it focuses on a limited subject area — implementing multimedia with some key contributed modules — as opposed to most of the recent spate of Drupal books, some of which try to cover every major aspect of the CMS. The material in Aaron Winborn's book is organized into eleven chapters, addressing most if not all of the key topics within the chosen subject area: Drupal basics; images, galleries, and slideshows; image theming and effects; third-party and local video; file management; audio nodes and fields; theming audio; and the future of multimedia in Drupal. The book concludes with a skimpy five-page index, which fails to contain such basic entries as Flash, FLV, SWF, sprites, star ratings, slideshows, and countless others. A robust index is especially critical for any technical book, such as this one, that divides related topics among multiple chapters, and has section and subsection names that in some cases are quite similar to one another and thus could be easily confused.

Because this book is geared more toward programmers new to Drupal, and not well-versed veterans, the first chapter — the second longest in the book — introduces the reader to the core concepts of Drupal (nodes, regions, blocks, themes, and modules — core and contributed) as well as two essential modules (CCK and Views). The explanations do not go into any great detail, but should be enough to give any Drupal newbie a head start. Nonetheless, readers may be confused by the screenshots on pages 16 through 19, which appear to be from Drupal 5. Also, the brief coverage of views arguments is inadequate, and needs to be beefed to be useful later in the book. For creating a new theme, the author advises copying wholesale an existing theme; instead, a sub-theme is a much better approach. Chapter 1 wraps up with a discussion of some basic concepts in Drupal theming, which makes puzzling the title of the section, "Advanced Theming." Speaking of themes, readers should note that when the author refers to "theming" an image or video, he means making the uploaded file display as content on the node's page (and not just exist as an attachment to that node).

For many programmers new to Drupal, the first hurdle they encounter is how to add an image to the content of a page or story — a seemingly trivial task that is built into most major CMSs — without writing HTML and hard coding the path of an image file they FTP-ed to the server. Drupal version 6 and presumably all prior versions, do not have native support for uploading and embedding in-line images. In his second chapter, the author explains how one can create image galleries, teaser thumbnails, and images embedded in content. However, in the discussion on page 45, some details are incorrect, such as the label for the "Save" button (three times) and the presence of the galleries drop-down list. Readers will undoubtedly be confused by two additional inaccuracies: There is no Navigation menu item for displaying the "image galleries" created by default, because initially the image_gallery view has no menu assigned in the Gallery page settings. Secondly, the gallery description is not shown on the gallery page; in fact, it is not even listed as an available view field. The section titled "Image Gallery Settings" suggests that the author may have been using an older version of the Image module. But this probably does not explain the erroneous statement on page 56, that "image nodes created with Image attach will automatically be marked as not published." The chapter concludes with an explanation of how to embed an image in content, using manually inserted image tags, or the ImageAssist module, optionally supplemented with a WYSIWYG HTML editor, such as TinyMCE. The fourth chapter looks at how to theme images, and discusses — it greatly varying levels of detail — style overriding, the Firebug Firefox extension, the Theme Developer module, image nodes, image-based rollover menus, sprites, light boxes, star ratings, slideshows, and various special effects: drop shadows, magnification, and watermarks.

The subsequent chapter — oddly titled "Developing for Images" — extends the discussion by showing how to insert images as fields utilizing ImageField and several supporting modules. One of those modules is referred to as "FileField Tokens" (page 70), but there is no such module; the author probably meant ImageField Tokens. Also extending the previously noted problem of non-Drupal 6 content, is the screenshot for "Display fields," on page 83, as well as the narrative, which appear to be pre-version 6. The latter half of the chapter delves into how to create galleries and slideshows (using views), user pictures, and images associated with taxonomy terms.

With Chapters 5 and 6, the author shifts attention to what is perhaps the second most commonly used type of multimedia on websites nowadays — video — with the former of those chapters devoted to third-party videos (such as content hosted on YouTube), while the latter chapter is devoted to "local video" (local in the sense of hosted on one's own remote Web server — not one's local development machine). The author demonstrates how to utilize a YouTube-hosted video, first using core Drupal modules only, then using the Embedded Video Field module. For using local video files, the author shows how to use the FileField module so the user can upload QuickTime video files. Unfortunately, the instructions on page 146 may prove confusing to beginners, since it is not entirely clear as to whether the later, more-detailed paragraphs are repeating earlier instructions, or specifying something new. More significantly, the use of the FileField module necessitates writing theme PHP code, just to have the video display on the page — which less technical readers may not feel comfortable attempting on their sites. The second part of the chapter may be more useful to the typical reader, because it covers how to embed Flash videos, a more popular format. The author advocates the use of the jQuery Media module (which he created) in conjunction with the jQ module. Unfortunately for the reader, the details of implementing this approach are glossed over at the end of the chapter, with only meager instructions ("... add .node .content a to the classes."), and without any illustrative example. No explanation is provided as to why this particular JavaScript-dependent solution is recommended, as opposed to a more straightforward one, such as the Flash Node module — which is far less problematic for FLV files. (By the way, the author states that he and some other developers are creating a fully GPL media player module and that there is a development version available of this Media Player module. But there is no such version on that page, and the situation may never change, because the project appears to have fizzled in August 2008, judging by the comments on the Drupal.org site and the author's site.)

In written tutorials, videocasts, and other discussions of Drupal multimedia, one important area that is often neglected is asset management. This includes such seemingly mundane matters as where in a Drupal site's file system one should place plug-in files and even the uploaded multimedia files themselves. A more far-reaching topic is how to best associate multimedia assets with nodes so they can be accessed by various modules — for instance, as stand-alone content types versus CCK fields. Chapter 7 examines some of these topics, first discussing how to create and theme nodes whose associated videos can be used elsewhere on a site, such as in a gallery — using the Embedded Media Field and Node Reference modules. However, some readers may become frustrated because a couple critical steps are skipped, and, even worse, no guidance is provided as to how to make the video show up on a node reference content page, or what content provider selection to use (since "Local" is not an option). Next the author considers how to set access to videos by user role — using the Asset module. Unfortunately, the reader is apparently not shown how to do anything useful with video content uploaded and managed using the Asset module, including the scenario proposed at the beginning of the section. (Incidentally, one might assume that the author's solution would use the Asset Embedded Media submodule, but it is not compatible with the latest version of Drupal 6.) The Media Mover module, and its many submodules, offer an alternate method of video asset management, and the author shows how to e-mail a video from a mobile phone, to be automatically attached to a new blog post. The chapter concludes with a brief look at Kaltura, an open-source platform for storing and editing multimedia.

Some Web developers and end-users may consider online audio as the poor cousin of video. In truth, audio-only content plays a key role in many Web applications — from podcasts embedded in RSS feeds, to sample tracks on music sellers' websites. The subsequent three chapters of the book are devoted to managing audio content within Drupal using several resources and solutions — specifically, the Audio, getID3, FileField, jQuery Media, Embedded Media Field, XSPF Playlist, and Views modules

In the last chapter, titled "The Future of Drupal Multimedia," the author speculates as to what media-related capabilities he thinks we will likely find in Drupal 7 and beyond — such as native file handling (via hook_file) and multimedia support in core Drupal, the merging or deprecation of non-FileField modules, dissociation of data from nodes, improved module interfaces and usability, embeddable widgets (for data distribution), semantic multimedia (microformats, RDF, and taxonomy-powered tagging), mobile Web access, virtual reality (such as Second Life), tactile and olfactory media, and motion sensing (such as the Wii Remote controller).

One laudable feature of this book is the inclusion of numerous screenshots, which can be quite reassuring to a reader getting lost in the technical minutia of any particular recipe. Also helpful is the manner in which the author, for the most part, keeps the reader informed as to all configuration settings — and where to find them within the Drupal administration interface — that the reader must or may want to modify, depending on his or her needs. Technical books that fail to do this can be extremely frustrating to anyone trying to learn a nontrivial technology.

Yet there are some major flaws with the book: Far too much of the material suggests that the author was using Drupal 5. Aside from the screenshots mentioned earlier, sections of the text point in that direction, such as the statement, "The multiple image issue might be taken care of by Drupal 6" (page 56). Fortunately, none of these gaffes prevent the reader from learning how to perform the tasks using version 6. The second and more important flaw is the poor coverage of Flash content, as detailed above. A follow-up edition to the book, in which all of these problems are resolved, would be most welcome and valuable.

A revision would also be an opportunity to fix the grammatical errors that should have been caught in the proofreading process. For instance, the fourth complete sentence on page 11, is missing a verb. Errata include "Autrhor" (credits page), "you [have] learned" (page 2), ". you'll" (page 2), a ")" without a "(" to match it (page 17), "isin" (page 31), "it [is] installed" (page 32), "provide files" (page 33; should instead read "provide functions"), "hierarchal" (page 46), "formated" (page 57), "[the] FTP" (page 75), "menu — By" (page 117), "going a view" (page 119), "quicktime" (page 146), and "[Submit] Audio" (page 179). In addition, there are eight pairs of adjacent words missing their separating spaces — five on page 159, and three more on page 174.

As seen in many other Packt Publishing titles, this one contains excessive usage of inappropriate title case (e.g., several on page 8 and 9 alone), though occasionally title case is neglected (e.g., "Image attach" throughout the book). In addition, some of the phrasing is rather awkward, which may pose no barrier to a reader who already understands the particular idea being discussed in the text, but could prove a real detriment to anyone unfamiliar with that idea. For instance, on page 36, the author states that "Often you may wish to override a theme that is not provided as a file in the default theme." But no theme is contained within a single file, and one does not override themes anyway; rather, one can disable a theme, or modify a copy of it, or create a variation as a sub-theme.

Yet overall, this book's strengths outweigh its weaknesses. For Drupal developers who wish to add image, audio, and video content to their sites, Drupal Multimedia is a useful resource with which to begin.

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

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

Several readers sent in an update on DTN, the interplanetary Internet protocol that Vint Cerf has been working on for many years (and we have been discussing for nearly as long). The news now is that Cerf has added a DTN stack to the open source Android code, seeing uses in mobile applications for a protocol that does not assume a continuous connection.

Several readers sent in an update on DTN, the interplanetary Internet protocol that Vint Cerf has been working on for many years (and we have been discussing for nearly as long). The news now is that Cerf has added a DTN stack to the open source Android code, seeing uses in mobile applications for a protocol that does not assume a continuous connection.

Several readers sent in an update on DTN, the interplanetary Internet protocol that Vint Cerf has been working on for many years (and we have been discussing for nearly as long). The news now is that Cerf has added a DTN stack to the open source Android code, seeing uses in mobile applications for a protocol that does not assume a continuous connection.

Several readers sent in an update on DTN, the interplanetary Internet protocol that Vint Cerf has been working on for many years (and we have been discussing for nearly as long). The news now is that Cerf has added a DTN stack to the open source Android code, seeing uses in mobile applications for a protocol that does not assume a continuous connection.

Philip K Dickhead writes "Is Douglas Adams scripting the saga of sorrows facing the LHC? These time-traveling Higgs-Boson particles certainly exhibit the sign of his absurd sense of humor! Perhaps it is the Universe itself, conspiring against the revelations intimated by the operation of CERN's Large Hadron Collider? This time, it is not falling cranes, cracked magnets, liquid helium leaks or even links to Al Qaeda, that have halted man's efforts to understand the meaning of life, the universe and everything. It now appears that the collider is hindered from an initial firing by a baguette, dropped by a passing bird: 'The bird dropped some bread on a section of outdoor machinery, eventually leading to significant overheating in parts of the accelerator. The LHC was not operational at the time of the incident, but the spike produced so much heat that had the beam been on, automatic failsafes would have shut down the machine.'"

Philip K Dickhead writes "Is Douglas Adams scripting the saga of sorrows facing the LHC? These time-traveling Higgs-Boson particles certainly exhibit the sign of his absurd sense of humor! Perhaps it is the Universe itself, conspiring against the revelations intimated by the operation of CERN's Large Hadron Collider? This time, it is not falling cranes, cracked magnets, liquid helium leaks or even links to Al Qaeda, that have halted man's efforts to understand the meaning of life, the universe and everything. It now appears that the collider is hindered from an initial firing by a baguette, dropped by a passing bird: 'The bird dropped some bread on a section of outdoor machinery, eventually leading to significant overheating in parts of the accelerator. The LHC was not operational at the time of the incident, but the spike produced so much heat that had the beam been on, automatic failsafes would have shut down the machine.'"

Riskable writes "Remember that $200,000 Contest For a Better Open-WRT Wireless Router GUI? Today Ubiquiti posted the winning entries to their support wiki. The grand prize was a tie between PyCI (written by yours truly) and NETSHe with OpenNET as the runner up. Source code and firmware images for each entry are available for download on their respective wiki pages. I'll be setting up a project page for PyCI (and l2sh) soon to make it a participatory open source product. Even if you don't have a RouterStation, or don't care about OpenWRT, there are numerous Python modules and tools inside of PyCI that could prove useful to other open source projects (e.g. iptables.py can read/interpret over 400 permutations of the iptables command). I'll also be checking the comments if anyone has any questions for me about PyCI or the contest in general. BTW: I'd like to thank all the commenters in the original article that insinuated that the technical requirements were impossible and/or that making a GUI to configure such complex things is a waste of time. I read every one and I wouldn't have made it such an obsession otherwise!"

Dan Jones writes "Google has open sourced several of its key JavaScript application development tools, hoping that they will prove useful for external programmers to build faster Web applications. According to Google, by enabling and allowing developers to use the same tools that Google uses, they can not only build rich applications but also make the Web really fast. The Closure JavaScript compiler and library are used as the standard Javascript library for pretty much any large, public Web application that Google is serving today, including some of its most popular Web applications, including Gmail, Google Docs and Google Maps. Google has also released Closure Templates which are designed to automate the dynamic creation of HTML. The announcement comes a few months after Google released and open sourced the NX server."

bonch writes "Contrary to previous reports, Atom chip support is working fine in the latest 10C535 build of OS X 10.6.2. Apple's EULA still states that OS X is licensed to run only on Apple hardware, but it looks like OSX86 hackers can breathe easy ... for now."

Trinity writes "Researchers from VUPEN have discovered critical vulnerabilities in Adobe Shockwave, a technology installed on over 450 million Internet-enabled desktops. The vulnerabilities could allow remote code execution by tricking a user into visiting a web page using Internet Explorer or even Mozilla Firefox. Version 11.5.1.601 as well as earlier ones are affected. The vendor recommends upgrading to version 11.5.1.602." Especially sobering when you consider Adobe's current push to be essentially required as an intermediary player for anyone who wants to see certain government data.

recoiledsnake writes "A few years after the Con Kolivas fiasco, the FatELF project to implement the 'universal binaries' feature for Linux that allows a single binary file to run on multiple hardware platforms has been grounded. Ryan C. Gordon, who has ported a number of popular games and game servers to Linux, has this to say: 'It looks like the Linux kernel maintainers are frowning on the FatELF patches. Some got the idea and disagreed, some didn't seem to hear what I was saying, and some showed up just to be rude.' The launch of the project was recently discussed here. The FatELF project page and FAQ are still up."

SerpensV passes along the news that German scientists have found direct evidence that the spinal cord is involved in the placebo effect (whose diminishing over time we discussed a bit earlier). "The researchers who made the discovery scanned the spinal cords of volunteers while applying painful heat to one arm. Then they rubbed a cream onto the arm and told the volunteers that it contained a painkiller, but in fact it had no active ingredient. Even so, the cream made spinal-cord neural activity linked to pain vanish. 'This type of mechanism has been envisioned for over 40 years for placebo analgesia,' says Donald Price, a neuroscientist at the University of Florida in Gainesville, who was not involved in the new study. 'This study provides the most direct test of this mechanism to date.'"

bth writes to let us know that Barnes & Noble has been sued by a company called Spring Design, which alleges that the recently announced Nook e-book reader infringes its intellectual property. This isn't a patent troll kind of situation; rather, the claim is misappropriation of trade secrets. Spring Design claims that they have been developing a dual-screen, Android-based e-book reader since 2006, filing patents all the while; and that they showed pretty much everything to Barnes & Noble in the expectation of working together with them to bring their reader to market.

waderoush writes "In May 2008, Nicholas Negroponte, chairman of the One Laptop Per Child Foundation, unveiled an e-book like design for the second-generation XO Laptop, consisting of a pair of facing touchscreens. In a new e-mail interview, Negroponte says that design has been thrown out, and that instead the foundation is working on version '1.75' of the existing green-and-white laptop with a more powerful processor, as well as a '3.0' version that would look 'more like a sheet of paper.' Negroponte also addressed a range of other questions about the OLPC project, including the significance of the project to make 1.6 million e-books readable on the XO laptop and the organization's push to reach more children in Latin America, Africa, Afghanistan, and Pakistan."

waderoush writes "In May 2008, Nicholas Negroponte, chairman of the One Laptop Per Child Foundation, unveiled an e-book like design for the second-generation XO Laptop, consisting of a pair of facing touchscreens. In a new e-mail interview, Negroponte says that design has been thrown out, and that instead the foundation is working on version '1.75' of the existing green-and-white laptop with a more powerful processor, as well as a '3.0' version that would look 'more like a sheet of paper.' Negroponte also addressed a range of other questions about the OLPC project, including the significance of the project to make 1.6 million e-books readable on the XO laptop and the organization's push to reach more children in Latin America, Africa, Afghanistan, and Pakistan."

itwbennett writes "'Nintendo is feeling the sting of competition from the iPhone,' writes Peter Smith in a recent post. 'At least, that's the feeling one gets when reading Nintendo president Satoru Iwata's thoughts on the future of Nintendo handhelds. According to a Financial Times piece, Iwata suggests the next Nintendo handheld (and to be clear, he isn't talking about the big screen DS launching in Japan next month) might include free 3G wireless, much like the Amazon Kindle does. The challenge is to offer the immediacy of downloading an inexpensive new game, anywhere, anytime, without forcing the user into some kind of monthly data plan.' From the FT piece: 'Only people who can pay thousands of yen a month [in mobile phone subscriptions] can be iPhone customers. That doesn't fit Nintendo customers because we make amusement products,' Mr Iwata said."

Frequent Slashdot contributor Bennett Haselton writes "A federal judge rules that government can obtain access to a person's inbox contents without any notification to the subscriber. The pros and cons of this are complicated, but the decision hinges on the assertion that ISP customers have lowered privacy interests in e-mail because they 'expose to the ISP's employees in the ordinary course of business the contents of their e-mails.' Fortunately for everybody, this is not true — most ISPs do not allow their employees to read customer e-mails 'in the ordinary course of business' — but then what are the consequences for the rest of the argument?" Read on for the rest of Bennett's analysis.

Federal Judge Michael Mosman has ruled that the government can read your e-mails stored with a third-party provider like GMail, without notifying you that a search warrant has been executed (PDF) against your account. (Actually, the judge ruled that there is no "notice" requirement triggered at all, so that in theory, neither GMail nor the subscriber would have to be notified — but that seems only of theoretical interest, since in practice GMail would have to cooperate in order to execute the warrant, unless the government is planning to have ninjas sneak into their server farm at night. The substantive impact of the ruling is that e-mails can be read without notifying the subscriber.)

Now, as I said when writing about the possibility of undetectable encryption being installed on people's computers, at the risk of incurring the wrath of civil libertarian allies, I am not 100% in favor of limiting governmental power in cases like these. Restraints on governmental power have their pros and cons, and many people who are targeted by government investigations really are evil. There may be cases where the government can only prevent harm from being done, by gaining access to someone's e-mail account, and by preventing the subscriber from finding out that their e-mails are being read. However, all of these arguments are also true when applied to governmental seizure of property from someone's home — and yet we still have Fourth Amendment protections against warrantless searches of your house. So should they, and do they, legally apply to e-mail? And under the "third party doctrine," should the government have to notify the subscriber of the search, or only the ISP?

Law Professor Orin Kerr of George Washington University Law School has written an article [click on the link and then press the download button to download a draft] arguing that the Fourth Amendment does apply to e-mail. But he has also written another article arguing in favor of the third-party doctrine — essentially, that when the government seizes property that is in the possession of a third party, it only has to notify the third party, not the property owner. To the extent that this is relevant to the GMail case, the argument would appear to support Judge Mosman's ruling. However, Kerr's paper also acknowledges that the third party rule has been the subject of scorching criticism of other Fourth Amendment scholars, calling it "dead wrong" and "making a mockery of the Fourth Amendment."

It will probably be a long time before courts are issuing consistent rulings on the third-party rule as it applies to e-mail. In the meantime, though, one statement in Judge Mosman's ruling sticks out in particular:

"[T]he defendants voluntarily conveyed to the ISPs and exposed to the ISP's employees in the ordinary course of business the contents of their e-mails."

This was the basis for further reasoning that the defendants had less of an expectation of privacy in their e-mail contents, and hence that there was a strong case for allowing the government to read the e-mails without notice to the defendants. (In this he was drawing an analogy to a previous ruling in which a court held that a bank's customer has "no legitimate expectation of privacy" in his bank records because they were "voluntarily conveyed to the banks and exposed to their employees in the ordinary course of business.")

But as applied to ISPs, this is a statement of fact, not a statement of law, and as a statement of fact it's simply wrong. ISP employees, even the most highly placed ones, do not have access to customers' e-mails "in the ordinary course of business." And even in the non-ordinary course of business, in the case where e-mails have to be inspected to satisfy a subpoena requirement or to investigate an abuse report, only employees with the proper business justification can read the e-mails. (At the e-mail provider that I use, SpeakEasy, employees can only access accounts with the explicit permission of the customer, and only then by resetting the password or obtaining the password from the customer. When I worked in MSN accounts, most employees didn't have the security clearance to access customer accounts at all.)

This tracks with what customers reasonably expect from banks versus what they reasonably expect from ISPs. If I called my bank to ask about the status of my account, and the customer service representative noted that I had a high number of overseas wire transfers and asked if I wanted to upgrade to a business account with a reduced wire fee, it probably wouldn't even occur to me to be offended that she had looked at my transaction records. On the other hand, if I called SpeakEasy and asked them to add more space in my inbox, and the tech support guy said, "Dude, you could do a lot better than Chloe," I might think he was overdue for a review of their customer privacy policy.

Judge Mosman uses several more analogies in arguing that the third-party doctrine applies to e-mails (beginning on page 12 of the ruling), analogies between e-mail and real-world situations that most of us are familiar with, like leaving documents out in the open at someone else's house. Now, most of us don't have the expertise to comment on the legal technicalities. But in the game of analogies, we're all experts, insofar as we're qualified to comment on whether we feel that one thing is "like" another, or whether our "expectations of privacy" in the two areas are similar. And under the rules of that game, I would disagree with the judge's analogies for several reasons:

1. There is a difference between leaving property in someone else's possession because you don't care very much about keeping it private, and leaving property in someone else's possession because you have no choice. The judge cites precedents in which courts ruled, variously: (a) that when a suspect left documents at his mother's house and the police executed a warrant there, they only had to provide notice to the mother, not the suspect, even though the mother was not the owner of the documents; (b) that a defendant had no grounds to object to the search of another person's purse, when the search turned up drugs belonging to the defendant; and (c) that defendants 'could not make a Fourth Amendment claim regarding a search of someone else's car because they had no "legitimate expectation of privacy in the glove compartment or area under the seat of the car in which they were merely passengers."' But all of those cases involved property that the defendants chose to leave in the possession of someone else, rather than keeping on their person or in their own houses. In all of these cases, the person X who left the property in the possession of person Y, could not have expected that person Y would keep their eyes off of that property, or would shield it from the view of casual acquaintances who happened to see it there. So by allowing the notice only to be served on person Y, these three cases are just specific implementations of a general rule: "If person X leaves property with person Y, with no expectation that person Y would refrain from examining the property, then the notice of warrant only has to be served on person Y."

This rule does not generalize to GMail accounts. If I send and receive messages through a GMail account, I know that they're stored on Google's servers, but that's out of necessity in order for them to provide web-based e-mail that can be accessed from multiple locations. By allowing the e-mails to be stored on their servers, I haven't conveyed that I care any less about their private contents, because I didn't have a choice. Now, if I had printed out an e-mail from GMail and left it lying around at my Mom's house, or in a friend's glove compartment, then that could be interpreted to indicate that I had less interest in keeping that e-mail private, and it would be more analogous to the situations above. In fact if I had sent an e-mail to someone working at Google, I would understand that my expectation of privacy had been lowered significantly, and that the recipient might forward it to their friends or leave a printout on their desk, or that the police might request for him to show it to them without notifying me. Simply having an e-mail stored in a GMail account is not the same thing.

2. E-mails are not like bank records, because you have a greater expectation of privacy for e-mails, even from the institutions that hold them. It's true that bank transactions are more closely analogous to web-based e-mails, because they're both stored on company servers by the nature of the business, so this analogy isn't as badly flawed as the previous ones. But in addition to the fact mentioned above, that ISP employees do not have access to your e-mails "in the ordinary course of business" despite what Judge Mosman wrote, there is the "inside/outside" distinction that Orin Kerr describes in his paper on the Fourth Amendment and e-mail. Essentially, police don't need a warrant to observe what goes on outside your home — whatever is visible from a public street — but they would need a warrant to take their inspection inside. Kerr argues for extending this analogy to the "content/non-content" rule for Internet transactions, so that Fourth Amendment protection would apply to the contents of e-mails, but not necessarily to the "outside" information such as sender, recipient, and transmission time. (Actually that still seems like rather weak privacy protection, to say that the Fourth Amendment doesn't protect information about who we exchange e-mails with, but even this watered-down argument still implies stronger privacy protection for e-mail contents.) Bank transaction records would be more like "outside" information and less deserving of privacy protection, so the analogy doesn't hold.

3. By analogy to the expectation of privacy in people's homes, the expectation of privacy for the contents of e-mail is possibly greater. Judge Mosman writes, "The sanctity of the home is often cited as the central purpose for this notice requirement, but the requirement has not been explicitly limited to searches of homes," and quotes from another court decision: "[t]he mere thought of strangers walking through and visually examining the center of our privacy interest, our home, arouses our passion for freedom as does nothing else." Well, since he brought it up, if it's relevant to compare the "passion" that's "aroused" by the invasion of various spheres of privacy, if I had a choice I would rather have a stranger wander through my house and inspect everything except the computer, than allow them access to my browser history and all the e-mails I'd sent and received in the past year. (And that's not even taking into account the violations of other people's privacy that would be entailed by someone looking through all of my e-mails.) Applying the test of "What would you rather have people see?", most people who make more than casual use of e-mail, seem to care more about the privacy of their e-mail than about the privacy of what's visibly lying around in their house — if a good friend drops by unannounced, you can usually lead them through your house without worrying about what they'd see, but you probably wouldn't give the same person a complete record of all your e-mails in the past year. (Remember, according to the judge's quote, we're comparing "visually examining" your house vs. your e-mail, not actually physically taking anything.)

As I said, I'm not necessarily opposed to the government having the authority to obtain records of people's e-mails if they have an extremely good reason, without necessarily having to notify the subscriber that their e-mails had been read. But the justification should not rest on wrong-headed assumptions like the notion that ISP customers "expose to the ISP's employees in the ordinary course of business the contents of their e-mails." I wonder if even Judge Mosman thinks that's true. If he got a call from his bank offering to upgrade his account based on recent transaction activity, he'd probably just politely get them off the phone like the rest of us. But if he got a call from his ISP tomorrow, saying that his e-mails were starting to sound cranky and they were wondering if there was anything they could do to cheer him up, would he just thank them for their concern and leave it at that?

judgecorp writes "ICANN is to be congratulated for succeeding in expanding the Internet beyond the Latin alphabet. However, the organization is facing a harder task in extending the Internet's global top-level domains (gTLDs) — its proposal to open up the gTLD space has been plagued by controversy and delays. INCANN faces struggles with trademark owners and competing businesses — but even so it is being criticized for acting slowly (as seen in transcripts from the recent meeting in Seoul). It now seems likely the body will have a pre-registration scheme to gauge demand and placate critics by getting something moving on new gTLDs."

judgecorp writes "ICANN is to be congratulated for succeeding in expanding the Internet beyond the Latin alphabet. However, the organization is facing a harder task in extending the Internet's global top-level domains (gTLDs) — its proposal to open up the gTLD space has been plagued by controversy and delays. INCANN faces struggles with trademark owners and competing businesses — but even so it is being criticized for acting slowly (as seen in transcripts from the recent meeting in Seoul). It now seems likely the body will have a pre-registration scheme to gauge demand and placate critics by getting something moving on new gTLDs."

Just over two years ago, fans of the Wheel of Time fantasy book series mourned the death of writer James Oliver Rigney Jr. — a.k.a. Robert Jordan. After much deliberation by Jordan's wife (who also edits the series), author Brandon Sanderson was chosen to finish the series. Sanderson familiarized himself with Jordan's notes and said that they would require three more books, which he hopes to release with about a year between them. On October 27th, the first new Wheel of Time book since Jordan's death was released, titled The Gathering Storm. Early reviews for the book seem quite positive, so here's a place to discuss it. Be warned: comments may contain spoilers.

Just over two years ago, fans of the Wheel of Time fantasy book series mourned the death of writer James Oliver Rigney Jr. — a.k.a. Robert Jordan. After much deliberation by Jordan's wife (who also edits the series), author Brandon Sanderson was chosen to finish the series. Sanderson familiarized himself with Jordan's notes and said that they would require three more books, which he hopes to release with about a year between them. On October 27th, the first new Wheel of Time book since Jordan's death was released, titled The Gathering Storm. Early reviews for the book seem quite positive, so here's a place to discuss it. Be warned: comments may contain spoilers.

9gezegen writes "Pepsi learned that if it wants to continue to 'Refresh Everything,' it needs an extra $1.26 billion. It looks like one of the secretaries forget to inform company lawyers about a trade secrets case in a Wisconsin state court. When nobody arrived to court, the judge gave $1.26 billion default judgement. According to Pepsi lawyers, they were not properly served because the secretary was 'so busy preparing for a board meeting.' One might imagine she was working on the refreshments. Perhaps Pepsi should learn more about the Spamhaus case."

Two9A writes "With the recent introduction of memorial accounts on Facebook, the potential arises for hilarity and abuse. Simon Thulbourn's Facebook page has been marked as 'in memorial' on the word of a report submitted by one of his friends; unfortunately, the closest the report gets to Simon is that the funeral service in question was officiated by 'Revd. Simon Thorburn,' which seems to be enough for Facebook to mark an unrelated user's profile as dead. Questions have previously been raised about the standard of proof required by Facebook for this service; it seems that those questions were pertinent, if the lax attention paid to these reports by Facebook staff continues."

xchg passes along a WiseAndroid piece on the drop in value of Garmin and TomTom shares following Google's announcement yesterday of Google Maps Navigation. "Shares of GPS device makers Garmin and TomTom plummeted... through a combination of their quarterly results and the launch of Google Maps Navigation. Following both low guidance for Garmin's next quarter as well as poor results from TomTom, shares for the two fell 16.4 percent and 20.8 percent respectively and remained low through the entire trading day after news of Google's free, turn-by-turn mapping service became public." Today Lauren Weinstein posted a number of reasons why standalone GPS won't go away any time soon.

KentuckyFC writes "Great things are expected of terahertz waves, the radiation in the electromagnetic spectrum between microwaves and the infrared. Terahertz waves pass through non-conducting materials such as clothes, paper, wood and brick and so cameras sensitive to them can peer inside envelopes, into living rooms and 'frisk' people at distance. That's not to mention the great potential they have in medical imaging. Because terahertz photons are not energetic enough to break chemical bonds or ionize electrons, it's easy to dismiss fears over their health effects. And yet the evidence is mixed: some studies have reported significant genetic damage while others, although similar, have reported none. Now a team led by Los Alamos National Labs thinks it knows why. They say that although the forces that terahertz waves exert on double-stranded DNA are tiny, in certain circumstances resonant effects can unzip the DNA strands, tearing them apart. This creates bubbles in the strands that can significantly interfere with processes such as gene expression and DNA replication. With terahertz scanners already appearing in airports and hospitals, the question that now urgently needs answering is what level of exposure is safe."

olahau writes "Two weeks ago, improvements to the previously reported attack on WPA/TKIP, were presented at the NorSec Conference in Oslo, Norway. In their paper coined 'An Improved Attack on TKIP,' Finn Michael Halvorsen and Olav Haugen describe the improvements, which enable an attacker to inject larger, maliciously crafted packets into a WPA/TKIP protected network, thus opening the probabilities for new and more sophisticated attacks against the well-established wireless security protocol."