Slashdot Mirror

An anonymous reader writes "Officials at the Chinese Defense Ministry say hackers from the U.S. have been attacking Chinese military websites. 'The sites were subject to about 144,000 hacking attacks each month last year, two thirds of which came from the U.S., according to China's defense ministry. The issue of cyber hacking has strained relations between the two countries.' This follows recent hacks from people in China on high-profile U.S. sites, as well as a report accusing the Chinese government of supporting a hacking group. '[Defense Ministry spokesman Geng Yansheng] called on U.S. officials to "explain and clarify" what he said were recent U.S. media reports that Washington would carry out "pre-emptive" cyber attacks and expand its online warfare capabilities. Such efforts are "not conducive to the joint efforts of the international community to enhance network security," he said.'"

schwit1 writes "New Jersey Gov. Chris Christie signed a bill Tuesday legalizing Internet gambling. While the bill only allows Atlantic City casino companies to take online bets, the WSJ believes that those casinos will partner with overseas companies that provide services for online gambling, potentially opening up a bigger market. Furthermore, the bill (PDF) will allow bettors from other states to gamble online, so long as regulators determine that the activity isn't prohibited by any federal or state laws. They included setting a 10-year trial period for online betting, and raising the taxes on the Atlantic City casinos' online winnings from 10 to 15 percent. New Jersey became the third state in the nation to legalize gambling over the Internet. Nevada and Delaware have passed laws legalizing Internet betting, which also is going on offshore, untaxed and unregulated."

This is a Google Hangout interview with Keith Bergelt, Chief Executive Officer of the Open Invention Network (OIN), which was jointly founded by IBM, NEC, Novell, Philips, Red Hat, and Sony to share their relevant patents with all Linux and Open Source developers and users in order to prevent patent troll attacks on FOSS, such as the famous SCO vs. IBM lawsuits that hampered Linux adoption during the early 2000s. It costs nothing to become a an OIN licensee, and over 500 companies have done so. Few people know, however, that individual developers and FOSS users can become OIN licensees; that you are welcome to do so, and it costs nothing. Read their license agreement, sign it, and send it in. That's all it takes. They also buy patents and accept patent donations. And "...if your company is being victimized by any entity seeking to assert its patent portfolio against Linux, please contact us so that we can aid you in your battle with these dark forces." This OIN service is called Linux Defenders 911. We hope you never need to use it, but it's good to know it's there if you do need it.

An anonymous reader writes "Google is working on identifying Chrome tabs that are currently playing audio (or recording it). The feature is expected to show an audio animation if a tab is broadcasting or recording sound. François Beaufort spotted the new feature, a part of which is already available in the latest Chromium build."

bill_mcgonigle writes "I just bought bitcoins from the World's first Bitcoin ATM at Liberty Forum. I created an account using an Android Bitcoin client and held up its QR code to the Raspberry Pi-based device's optical scanner. After I fed in a $20 Federal Reserve Note, I got back a confirmation QR code on its display, which I then scanned and checked the third-party confirmation URL. The machine can function on any wireless network and will soon be available for purchase by merchants, who can make a commission on customers' Bitcoin purchases."

An anonymous reader writes "Google on Thursday released Chrome version 25 for Windows, Mac, and Linux. While Chrome 24 was largely a stability release, Chrome 25 is all about features, including voice recognition support via the newly added Web Speech API and the blocking of silent extension installation. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome." But if you're more interested in the growing raft of Google-branded hardware than running Google OSes, some good news (via Liliputing) about the newly released Pixel: Bill Richardson of Google posted on Thursday that the Pixel can boot Linux Mint, and explained how users can follow his example, by taking advantage of new support for a user-provided bootloader.

An anonymous reader writes "Google on Thursday released Chrome version 25 for Windows, Mac, and Linux. While Chrome 24 was largely a stability release, Chrome 25 is all about features, including voice recognition support via the newly added Web Speech API and the blocking of silent extension installation. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome." But if you're more interested in the growing raft of Google-branded hardware than running Google OSes, some good news (via Liliputing) about the newly released Pixel: Bill Richardson of Google posted on Thursday that the Pixel can boot Linux Mint, and explained how users can follow his example, by taking advantage of new support for a user-provided bootloader.

Dr Max writes "Ever wonder how al-Qaeda operates under the watchful eye of the U.S. Army? Well, the Associated Press found a list of 22 of their tips and tricks on avoiding drone strikes. Most of it consists of the obvious: stay in the shadows or under thick trees, don't use wireless communications. However, there are also some less obvious solutions, like the $2,595 Russian 'sky grabber, which can track the drones. Their document (PDF) also suggests covering your roof and car with broken glass. They also claim good snipers can take out the reconnaissance drones, which fly at a lower level. Now the question is: will all of this still be relevant during the robo-apocalypse?"

Bennett Haselton writes "Evgeny Morozov's forthcoming book To Save Everything, Click Here describes how an overly helpful 'kitchen of the future' might stifle the learning process and threaten culinary innovation. True, but we could certainly do better than the current state of how-to directions (in cooking and most other subjects) that you can find today on Google. I suggest that the answer lies not in intelligent kitchen technology, but in designing an algorithm that would produce the best possible how-to directions -- where the 'best' directions are judged according to the results that are achieved by genuine beginners who attempt to follow the directions without help." Read below for the rest of Bennett's review.
Editor's Note: This article was not intended as a full review, but rather a commentary on one point in the book. The author's actual review of the book will appear in March. To Save Everything, Click Here author Evgeny Morozov pages 432 publisher PublicAffairs rating 9/10 reviewer Bennett Haselton ISBN 1610391381 summary Argues that we badly need a new, post-Internet way to debate the moral consequences of digital technologies

Evgeny Morozov's new book To Save Everything, Click Here (due out in March), about "the folly of technological solutionism", is that rare animal: a book I would recommend to everyone even if I disagree with about 2/3 of the conclusions in the text. The arguments in the book didn't always change my mind, but they made me reformulate many of my own arguments in the other direction.

In most sections of the book, Morozov attacks the beliefs of "solutionists" who believe that a particular program or algorithm can solve a social program. Usually, I thought his criticisms of a given algorithmic "solution" were spot-on. But I often found myself thinking of a different algorithm that I thought would solve the problem much more effectively than the one Morozov was critiquing. This, naturally, could be construed as missing the point of the book. However, I'm prepared to defend any of the alternative algorithms that I came up with, or bet money on how it would fare in the real world. I'll have a full review of the book when it's released, but I think many of Morozov's argument are interesting enough to deserve an article in their own right.

For example, Morozov describes a new kitchen technology that guides would-be chefs through the process of preparing a meal, by illuminating pathways on the kitchen floor to show the cook where they're supposed to walk next, and then using laser pointers and visual aids to guide them through what they're supposed to do when they get there. If you want to know how to expertly carve a fish, for example, the ceiling-mounted lasers will trace out the exact cuts that you're supposed to make on the fish's skin. The description sounds like a parody of what people think the Big Bang Theory geeks would like their kitchen to do for them.

Morozov argues, not unreasonably, that "[t]o subject [cooking] fully to the debilitating logic of efficiency is to deprive humans of the ability to achieve mastery in this activity, to make human flourishing impossible and to impoverish our lives," and that "deviating from recipes is what creates culinary innovations." Well that's one of the 1/3 of his arguments that I agree with. Besides, if you can afford the cost of a laser-guided kitchen just to cook meals for yourself, you could probably use the same amount of money to take a professional cooking class, order takeout every day to tide you over until you know how to make decent stuff on your own, and still have money left over. If you're using it instead to try and cook to impress party guests, how's that going to work? If you're making the food where your guests can see you being guided around by lasers, they're going to think (correctly) that you don't know how to cook, and if you're making the food in a back room where you're out of sight of the guests, you might as well order takeout and have it smuggled in through the back door.

On the other hand, Morozov says in his next paragraph: "In a world where only a select few could master the tricks of the trade, such 'augmented' kitchens would probably be welcome, if only for their promise to democratize access to this art. But this is not the world we inhabit: detailed recipes and instructional videos on how to cook the most exquisite dish have never been easier to find on Google."

That's where he lost me. I have vastly different views on this, which can be summed up in three points:

• The qualify of most "how-to" instructions aimed at beginners, judged by the results they produce in the hands of actual beginners, is far worse than most people believe.

• Moreover, for reasons I'll describe later, the incentives created by the free market in general (and Google in particular) more or less guarantee this result: How-to directions exist that cover nearly every human activity, but most of the directions are not particularly good.

• I have an idea for a different algorithm (surprise!) that Google, or any other similarly positioned web titan, could use to change the incentives of web publishers, leading them to write how-to instructions that would produce much better results when followed by actual beginners.

The morass of cooking how-tos on the web are a good example. Partly from always having other things that I'd rather learn, and partly from being perfectly happy eating lots of plain fruits and vegetables (good for your health, but not for your cooking skills), I had survived to early adulthood hardly knowing anything about real cooking. Being a decently smart person, I figured that made me well suited to judge the effectiveness of the countless cookbooks written "for people who don't know how to cook". Because I firmly believe that if you follow a set of directions precisely (or, if the directions are written ambiguously, then if you follow some plausible interpretation of each step in the directions), and the result doesn't come out as predicted, then it's the directions that failed, not you. If another set of instructions would have produced better results, then those directions are better. This is not rocket science, but many cooking directions in cookbooks and on the Internet are glaringly missing key pieces of information that would have made the directions better, by the above definition.

Now, I understand the importance of experimenting and deviating from recipes and tailoring things to your own tastes, but I think that has to come after you've produced an edible dish that you can use as a baseline. I make scrambled eggs a little bit differently every time -- curry powder, mussels, capers, tabasco sauce, blue cheese (just not all in the same pan, please) -- but the only reason that's possible is because the simple directions for plain scrambled eggs actually work. When I say that most cooking directions don't work, I mean that if you follow them precisely (but without any prior cooking knowledge), they don't even get you to the baseline of an edible result that you can then use as a jumping-off point to try your own variations.

The odd thing about cooking is that of all the people whose cooking I liked so much that I asked them where they learned how to cook, all of them said that they learned from an in-person instructor (usually a family member); I have yet to meet any really good cooks who learned their skills from written recipes or web videos. This suggests that the learning materials on the Internet are falling short. (By contrast, I know plenty of people who have learned PHP programming or similar skills out of a book.)

And from my experiences helping out friends in the kitchen who had more cooking experience but who were trying to follow a particular recipe, it seemed that their most valuable skill was knowing the crucial parts of the recipe that were missing, or wrong. And then they would use their non-beginner knowledge fill in the missing steps or make the necessary corrections as we went along. With the current mediocre state of most cooking directions out there, that's surely a useful skill. However, it does mean that you could make most recipes produce much better results in the hands of a beginner, if you simply fixed all those parts that were missing, or wrong.

Take, for example, my misadventures making jalapeno poppers. Going to a friend's Super Bowl party, I figured that jalapeno poppers would be an easy thing to make, with just under 200 how-to videos on Youtube and about 600 matching recipe pages on Google, most of them calling for only four ingredients. How hard could it be?

Well, there are two important things that should be in every jalapeno popper recipe, or the recipe is doing more harm than good just by being out there on the web. One is that when you're slicing and handling the raw jalapenos, you have to wear gloves, or the capsaicin in the jalapeno -- which is also the active ingredient in pepper spray -- will leave a burning feeling on your fingers that lasts for about the next 24 hours. (If you touch your eye with your finger, you might even have to go to the emergency room.)

The other indispensable piece of information is that to make the jalapeno poppers edible, you have to remove the seeds and the white ribs from the inside -- not just the white center of the jalapeno (which slides out easily), but the white part of the ribs, which have to be scraped off of the outer wall (a grapefruit spoon works great, otherwise a paring knife or a regular sharp knife will do). Most recipes do tell you to remove the seeds. But the white ribs left inside the jalapeno are just as hot, and if you don't cut them out, the finished product will have a hotness that's too overpowering to taste anything else. (This video shows how to do it right.)

So what's the problem? Here's a table listing the first 10 Google matches for "jalapeno popper recipes", rated according to whether they contain those two must-have pieces of information that a beginner would need. (If the directions said to "devein" the jalapeno or "remove the membranes", I gave it an "Almost" in the second column -- because a first-timer is likely to think that this refers to removing the white center of the jalapeno, and not realize that you also have to remove the ribs attached to the edges. I'm being strict here, because it would have taken almost no effort for the recipe writers to be clear about this, and if you don't do that step correctly, you will have to throw out the finished product.)

Recipe source Tell reader to wear gloves? Tell reader to remove jalapeno ribs? Food Network (Emeril Lagasse) No Almost (instructions say "membranes removed") AllRecipes.com No No Food.com No No KraftRecipes.com No Almost (says to remove "veins") InspiredTaste.net Yes. (Sort of. The directions end halfway down the page, and then another set of written directions starts from the beginning. That's confusing, but I'll give it to them.) Yes. (In both sets of directions. Good job guys!) ThePioneerWoman.com No Yes Epicurious.com No Almost ("devein") About.com No (not counting the comments section, where someone warns other readers to use gloves because they burned their hands following the directions) No RecipeGirl.com No. (This is weird: gives tips on how to neutralize the stinging capsaicin once it gets on your hands, but never actually says to put gloves on.) Almost ("seeds and ribs") JalapenoMadness.com No No

Videos scored a little better, if you're generous and give full credit to any video that shows the scooping out of the jalapenos to include the ribs attached to the sides, even if the verbal directions don't spell that out precisely. Here are the ratings for the first 10 Youtube matches for "jalapeno poppers recipe":

Source (Youtube user) Tell viewer to wear gloves? Tell viewer to remove jalapeno ribs? allrecipes Yes No bettyskitchen No Yes PrincessDiana161 Yes Yes MudRFunR Yes Yes cookingwithcaitlin1 Yes Yes Michael Hultquist (Jalapeno Madness) No No BarbecueWeb No No kooktocook No No Adley Stump No No thatsletitia No No

In most of the videos that didn't explicitly include the step about putting gloves on, the cooks themselves were not wearing gloves. What did their hands feel like later?

eHow.com does have a helpful page about how to treat capsaicin burns from handling jalapenos. Perhaps that's their penance for the fact that half of their 'jalapeno poppers' recipes don't tell you to put gloves on.

If you could have made poppers based on these incomplete instructions, because you knew to put gloves on or to scrape the ribs out, good for you -- you possess the background knowledge to fill in the parts of the directions that were missing, or wrong. But that doesn't do the real newbies any good.

I went to this trouble because I want to beat you over the head with the crucial fact here: Most directions suck. They suck not just in absolute terms (burning your hands, or the mouths of people who eat the jalapenos with the ribs still in them) but they especially suck relative to how easily they could have been fixed. There is no excuse for putting up a recipe for jalapeno poppers that doesn't tell the reader to put gloves on, or that only tells the reader to "remove the seeds". And I've run into the same phenomenon over and over -- whether looking for directions on how to lower memory consumption of a web server, or how to get stains out of a carpet, or how to replace a 12V direct-current power supply with a cartridge of 8 AA batteries in series -- where not only did the directions not work, but I later found out that they could have worked if the author had simply added one or two key pieces of information.

However it seems that almost everyone believes that the quality of directions on the web is much higher than it actually is -- where, by "quality", I'm talking about the results that would be achieved by a beginner following the directions. (If I had asked you, "Where can I find a good recipe for jalapeno poppers?", is there about a 100% chance you would have said, "Google"?) I assume people overestimate the usefulness of all the how-tos out there, for two reasons: (a) they glance at the directions but don't try them themselves, so they just assume the directions work; or (b) they already know how to do the task being described, so when they read the directions, their brain automatically fills in the missing steps or makes the necessary corrections. That doesn't mean the directions would work in the hands of a true beginner.

Unfortunately, the quality of the directions on the web, is perfectly explained by the incentives created by Google. If there's any niche in the how-to space that is not already filled by some article on the web, an author can easily grab some extra web traffic by writing the first page about that topic. For a popular topic like how to make jalapeno poppers, there's enough traffic going around that dozens or hundreds of authors can put up their own how-to pages and each collect just enough web traffic to make it worthwhile. Thus, every "directional" niche will be filled, and some will be filled to overflowing.

Within a particular niche, however, there's not much incentives to make the directions particularly good -- where "good" means "produces good results when followed by someone with no prior knowledge in this area". Whether your directions work or not, they'll attract about the same level of traffic from Google. Even if the author later realizes that the insertion of a few key steps would make their instructions better, there's no incentive for them to do it -- that's not going to make your how-to page rise up in the Google rankings above the other pages on the same topic.

Which brings me to my proposed solution. It would take a company with a giant pre-existing web presence to pull it off (not quite on the level of Google, but at least an eHow or a Food.com). But it would take almost no maintenance on the part of the company themselves, once the process was put in place.

To incentivize people to create instructions that actually work, a given how-to guide would go through three phases:

1. After the directions are written, genuine newbies (recruited from the web site's usual visitors -- people who just want to learn something new in an area where they have no prior expertise) attempt to follow the directions and tell the author about any problems they ran into, or steps in the directions that seemed ambiguous. If the author thinks some reader is just being an overly nit-picky moron, they're free to ignore their questions and suggestions, but they would do so at the risk of their directions faring poorly in the next phase.

2. Once the initial wave of corrections and clarifications is finished, the directions are put into a pool marked "Ready to be rated!", where they are rated by the next group of genuine newbies who attempt to follow them. Each reader rates the directions simply: If they followed the directions and got the result they expected, then thumbs up, otherwise, thumbs down. If multiple readers spot a mistake or an omission that somehow got missed in the first phase, then the author can make the necessary changes and start the second phase over. (To prevent the author of the directions from "gaming the system" at this stage, the volunteer newbies should be selected at random from a large pool of people who sign up saying "I'm game for learning how to do anything new." If you let people self-select to go to the directions and rate them, then this enables the author to stack the deck by having all of their friends go to the page and give their directions a high rating.)

3. Finally, once the directions have reached some acceptably high percentage of positive ratings, they get released into the general pool of directions/how-tos/recipes of which the site can promise, "80% of newbies were able to follow these directions successfully." If the system works -- and if the volunteer readers in step #2 are representative of the skill level of the site's general readership -- it should be expected that most readers should be able to follow the directions and get good results at that point.

Almost all of the "how-to" directions that I've read, on any topic, could have benefited from being put through the wringer as described by the steps above. It's not merely that I think this algorithm would produce good directions; it's that my definition of good directions is precisely those directions that would pass the test in step #2.

As for what incentivizes the authors to produce directions that make it through this process, perhaps the hosting site could split the ad revenue with them from the pages containing the author's directions. Perhaps the hosting site could just reward them with a link from the article to the author's professional home page. Or maybe people would happily submit the instructions for free if it went towards a non-profit repository of helpful information, a la Wikipedia. (The huge difference from Wikipedia though, is that if you're an expert on George Washington, it's easy to write a good article about George Washington; but if you're an expert on cooking, that makes it hard to write a set of cooking directions that would fill in all the blanks needed by a beginner. Hence the multi-step vetting process above.)

It's tempting to think this is process would be "overkill" for a simple recipe, but that fails to consider the magnitude of the time savings when multiplied across the hundreds or thousands of people who will read the information over the course of its lifetime on the web. If the author spends an extra 10 minutes on the instructions to clarify things in such a way that saves just 1 minute of reading time for the average reader, when that 1 minute of time savings is multiplied by hundreds of readers, it's clearly an overall time-saver. (What disgusts me about the jalapeno popper recipes is that the authors could have saved me a whole day of painful burning on my fingers, if they had just taken 10 seconds to include the step about putting on gloves -- that would have been an overall time-saver even if only one person had read the recipe.)

So Morozov was right that we don't need laser-guided kitchens guiding us through the algorithm of carving a fish, but we should consider that an entirely different kind of algorithm could change everything for a beginning cook, or a person trying to learn any other skill from scratch. The Star Trek kitchen in To Save Everything, Click Here makes for an easy target for Morozov's argument, but that kitchen technology is hardly making enough inroads to threaten cooking as we know it -- I'll bet you'd never heard of it until this article. Bad directions, on the other hand, are so ubiquitous that we've accepted them as a part of our way of life, and we've all but forgotten to think how they could be made better. Like Robert Kennedy, I see people looking at their capsaicin-burned hands and their inedible jalapeno poppers with the ribs still attached and asking, "Why?", and I imagine eHow.com lining up newbies to critique their recipes until each recipe achieves a high rating from beginners based on the actual results that they got, and ask, "Why not?"

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

Bennett Haselton writes "Evgeny Morozov's forthcoming book To Save Everything, Click Here describes how an overly helpful 'kitchen of the future' might stifle the learning process and threaten culinary innovation. True, but we could certainly do better than the current state of how-to directions (in cooking and most other subjects) that you can find today on Google. I suggest that the answer lies not in intelligent kitchen technology, but in designing an algorithm that would produce the best possible how-to directions -- where the 'best' directions are judged according to the results that are achieved by genuine beginners who attempt to follow the directions without help." Read below for the rest of Bennett's review.
Editor's Note: This article was not intended as a full review, but rather a commentary on one point in the book. The author's actual review of the book will appear in March. To Save Everything, Click Here author Evgeny Morozov pages 432 publisher PublicAffairs rating 9/10 reviewer Bennett Haselton ISBN 1610391381 summary Argues that we badly need a new, post-Internet way to debate the moral consequences of digital technologies

Evgeny Morozov's new book To Save Everything, Click Here (due out in March), about "the folly of technological solutionism", is that rare animal: a book I would recommend to everyone even if I disagree with about 2/3 of the conclusions in the text. The arguments in the book didn't always change my mind, but they made me reformulate many of my own arguments in the other direction.

In most sections of the book, Morozov attacks the beliefs of "solutionists" who believe that a particular program or algorithm can solve a social program. Usually, I thought his criticisms of a given algorithmic "solution" were spot-on. But I often found myself thinking of a different algorithm that I thought would solve the problem much more effectively than the one Morozov was critiquing. This, naturally, could be construed as missing the point of the book. However, I'm prepared to defend any of the alternative algorithms that I came up with, or bet money on how it would fare in the real world. I'll have a full review of the book when it's released, but I think many of Morozov's argument are interesting enough to deserve an article in their own right.

For example, Morozov describes a new kitchen technology that guides would-be chefs through the process of preparing a meal, by illuminating pathways on the kitchen floor to show the cook where they're supposed to walk next, and then using laser pointers and visual aids to guide them through what they're supposed to do when they get there. If you want to know how to expertly carve a fish, for example, the ceiling-mounted lasers will trace out the exact cuts that you're supposed to make on the fish's skin. The description sounds like a parody of what people think the Big Bang Theory geeks would like their kitchen to do for them.

Morozov argues, not unreasonably, that "[t]o subject [cooking] fully to the debilitating logic of efficiency is to deprive humans of the ability to achieve mastery in this activity, to make human flourishing impossible and to impoverish our lives," and that "deviating from recipes is what creates culinary innovations." Well that's one of the 1/3 of his arguments that I agree with. Besides, if you can afford the cost of a laser-guided kitchen just to cook meals for yourself, you could probably use the same amount of money to take a professional cooking class, order takeout every day to tide you over until you know how to make decent stuff on your own, and still have money left over. If you're using it instead to try and cook to impress party guests, how's that going to work? If you're making the food where your guests can see you being guided around by lasers, they're going to think (correctly) that you don't know how to cook, and if you're making the food in a back room where you're out of sight of the guests, you might as well order takeout and have it smuggled in through the back door.

On the other hand, Morozov says in his next paragraph: "In a world where only a select few could master the tricks of the trade, such 'augmented' kitchens would probably be welcome, if only for their promise to democratize access to this art. But this is not the world we inhabit: detailed recipes and instructional videos on how to cook the most exquisite dish have never been easier to find on Google."

That's where he lost me. I have vastly different views on this, which can be summed up in three points:

• The qualify of most "how-to" instructions aimed at beginners, judged by the results they produce in the hands of actual beginners, is far worse than most people believe.

• Moreover, for reasons I'll describe later, the incentives created by the free market in general (and Google in particular) more or less guarantee this result: How-to directions exist that cover nearly every human activity, but most of the directions are not particularly good.

• I have an idea for a different algorithm (surprise!) that Google, or any other similarly positioned web titan, could use to change the incentives of web publishers, leading them to write how-to instructions that would produce much better results when followed by actual beginners.

The morass of cooking how-tos on the web are a good example. Partly from always having other things that I'd rather learn, and partly from being perfectly happy eating lots of plain fruits and vegetables (good for your health, but not for your cooking skills), I had survived to early adulthood hardly knowing anything about real cooking. Being a decently smart person, I figured that made me well suited to judge the effectiveness of the countless cookbooks written "for people who don't know how to cook". Because I firmly believe that if you follow a set of directions precisely (or, if the directions are written ambiguously, then if you follow some plausible interpretation of each step in the directions), and the result doesn't come out as predicted, then it's the directions that failed, not you. If another set of instructions would have produced better results, then those directions are better. This is not rocket science, but many cooking directions in cookbooks and on the Internet are glaringly missing key pieces of information that would have made the directions better, by the above definition.

Now, I understand the importance of experimenting and deviating from recipes and tailoring things to your own tastes, but I think that has to come after you've produced an edible dish that you can use as a baseline. I make scrambled eggs a little bit differently every time -- curry powder, mussels, capers, tabasco sauce, blue cheese (just not all in the same pan, please) -- but the only reason that's possible is because the simple directions for plain scrambled eggs actually work. When I say that most cooking directions don't work, I mean that if you follow them precisely (but without any prior cooking knowledge), they don't even get you to the baseline of an edible result that you can then use as a jumping-off point to try your own variations.

The odd thing about cooking is that of all the people whose cooking I liked so much that I asked them where they learned how to cook, all of them said that they learned from an in-person instructor (usually a family member); I have yet to meet any really good cooks who learned their skills from written recipes or web videos. This suggests that the learning materials on the Internet are falling short. (By contrast, I know plenty of people who have learned PHP programming or similar skills out of a book.)

And from my experiences helping out friends in the kitchen who had more cooking experience but who were trying to follow a particular recipe, it seemed that their most valuable skill was knowing the crucial parts of the recipe that were missing, or wrong. And then they would use their non-beginner knowledge fill in the missing steps or make the necessary corrections as we went along. With the current mediocre state of most cooking directions out there, that's surely a useful skill. However, it does mean that you could make most recipes produce much better results in the hands of a beginner, if you simply fixed all those parts that were missing, or wrong.

Take, for example, my misadventures making jalapeno poppers. Going to a friend's Super Bowl party, I figured that jalapeno poppers would be an easy thing to make, with just under 200 how-to videos on Youtube and about 600 matching recipe pages on Google, most of them calling for only four ingredients. How hard could it be?

Well, there are two important things that should be in every jalapeno popper recipe, or the recipe is doing more harm than good just by being out there on the web. One is that when you're slicing and handling the raw jalapenos, you have to wear gloves, or the capsaicin in the jalapeno -- which is also the active ingredient in pepper spray -- will leave a burning feeling on your fingers that lasts for about the next 24 hours. (If you touch your eye with your finger, you might even have to go to the emergency room.)

The other indispensable piece of information is that to make the jalapeno poppers edible, you have to remove the seeds and the white ribs from the inside -- not just the white center of the jalapeno (which slides out easily), but the white part of the ribs, which have to be scraped off of the outer wall (a grapefruit spoon works great, otherwise a paring knife or a regular sharp knife will do). Most recipes do tell you to remove the seeds. But the white ribs left inside the jalapeno are just as hot, and if you don't cut them out, the finished product will have a hotness that's too overpowering to taste anything else. (This video shows how to do it right.)

So what's the problem? Here's a table listing the first 10 Google matches for "jalapeno popper recipes", rated according to whether they contain those two must-have pieces of information that a beginner would need. (If the directions said to "devein" the jalapeno or "remove the membranes", I gave it an "Almost" in the second column -- because a first-timer is likely to think that this refers to removing the white center of the jalapeno, and not realize that you also have to remove the ribs attached to the edges. I'm being strict here, because it would have taken almost no effort for the recipe writers to be clear about this, and if you don't do that step correctly, you will have to throw out the finished product.)

Recipe source Tell reader to wear gloves? Tell reader to remove jalapeno ribs? Food Network (Emeril Lagasse) No Almost (instructions say "membranes removed") AllRecipes.com No No Food.com No No KraftRecipes.com No Almost (says to remove "veins") InspiredTaste.net Yes. (Sort of. The directions end halfway down the page, and then another set of written directions starts from the beginning. That's confusing, but I'll give it to them.) Yes. (In both sets of directions. Good job guys!) ThePioneerWoman.com No Yes Epicurious.com No Almost ("devein") About.com No (not counting the comments section, where someone warns other readers to use gloves because they burned their hands following the directions) No RecipeGirl.com No. (This is weird: gives tips on how to neutralize the stinging capsaicin once it gets on your hands, but never actually says to put gloves on.) Almost ("seeds and ribs") JalapenoMadness.com No No

Videos scored a little better, if you're generous and give full credit to any video that shows the scooping out of the jalapenos to include the ribs attached to the sides, even if the verbal directions don't spell that out precisely. Here are the ratings for the first 10 Youtube matches for "jalapeno poppers recipe":

Source (Youtube user) Tell viewer to wear gloves? Tell viewer to remove jalapeno ribs? allrecipes Yes No bettyskitchen No Yes PrincessDiana161 Yes Yes MudRFunR Yes Yes cookingwithcaitlin1 Yes Yes Michael Hultquist (Jalapeno Madness) No No BarbecueWeb No No kooktocook No No Adley Stump No No thatsletitia No No

In most of the videos that didn't explicitly include the step about putting gloves on, the cooks themselves were not wearing gloves. What did their hands feel like later?

eHow.com does have a helpful page about how to treat capsaicin burns from handling jalapenos. Perhaps that's their penance for the fact that half of their 'jalapeno poppers' recipes don't tell you to put gloves on.

If you could have made poppers based on these incomplete instructions, because you knew to put gloves on or to scrape the ribs out, good for you -- you possess the background knowledge to fill in the parts of the directions that were missing, or wrong. But that doesn't do the real newbies any good.

I went to this trouble because I want to beat you over the head with the crucial fact here: Most directions suck. They suck not just in absolute terms (burning your hands, or the mouths of people who eat the jalapenos with the ribs still in them) but they especially suck relative to how easily they could have been fixed. There is no excuse for putting up a recipe for jalapeno poppers that doesn't tell the reader to put gloves on, or that only tells the reader to "remove the seeds". And I've run into the same phenomenon over and over -- whether looking for directions on how to lower memory consumption of a web server, or how to get stains out of a carpet, or how to replace a 12V direct-current power supply with a cartridge of 8 AA batteries in series -- where not only did the directions not work, but I later found out that they could have worked if the author had simply added one or two key pieces of information.

However it seems that almost everyone believes that the quality of directions on the web is much higher than it actually is -- where, by "quality", I'm talking about the results that would be achieved by a beginner following the directions. (If I had asked you, "Where can I find a good recipe for jalapeno poppers?", is there about a 100% chance you would have said, "Google"?) I assume people overestimate the usefulness of all the how-tos out there, for two reasons: (a) they glance at the directions but don't try them themselves, so they just assume the directions work; or (b) they already know how to do the task being described, so when they read the directions, their brain automatically fills in the missing steps or makes the necessary corrections. That doesn't mean the directions would work in the hands of a true beginner.

Unfortunately, the quality of the directions on the web, is perfectly explained by the incentives created by Google. If there's any niche in the how-to space that is not already filled by some article on the web, an author can easily grab some extra web traffic by writing the first page about that topic. For a popular topic like how to make jalapeno poppers, there's enough traffic going around that dozens or hundreds of authors can put up their own how-to pages and each collect just enough web traffic to make it worthwhile. Thus, every "directional" niche will be filled, and some will be filled to overflowing.

Within a particular niche, however, there's not much incentives to make the directions particularly good -- where "good" means "produces good results when followed by someone with no prior knowledge in this area". Whether your directions work or not, they'll attract about the same level of traffic from Google. Even if the author later realizes that the insertion of a few key steps would make their instructions better, there's no incentive for them to do it -- that's not going to make your how-to page rise up in the Google rankings above the other pages on the same topic.

Which brings me to my proposed solution. It would take a company with a giant pre-existing web presence to pull it off (not quite on the level of Google, but at least an eHow or a Food.com). But it would take almost no maintenance on the part of the company themselves, once the process was put in place.

To incentivize people to create instructions that actually work, a given how-to guide would go through three phases:

1. After the directions are written, genuine newbies (recruited from the web site's usual visitors -- people who just want to learn something new in an area where they have no prior expertise) attempt to follow the directions and tell the author about any problems they ran into, or steps in the directions that seemed ambiguous. If the author thinks some reader is just being an overly nit-picky moron, they're free to ignore their questions and suggestions, but they would do so at the risk of their directions faring poorly in the next phase.

2. Once the initial wave of corrections and clarifications is finished, the directions are put into a pool marked "Ready to be rated!", where they are rated by the next group of genuine newbies who attempt to follow them. Each reader rates the directions simply: If they followed the directions and got the result they expected, then thumbs up, otherwise, thumbs down. If multiple readers spot a mistake or an omission that somehow got missed in the first phase, then the author can make the necessary changes and start the second phase over. (To prevent the author of the directions from "gaming the system" at this stage, the volunteer newbies should be selected at random from a large pool of people who sign up saying "I'm game for learning how to do anything new." If you let people self-select to go to the directions and rate them, then this enables the author to stack the deck by having all of their friends go to the page and give their directions a high rating.)

3. Finally, once the directions have reached some acceptably high percentage of positive ratings, they get released into the general pool of directions/how-tos/recipes of which the site can promise, "80% of newbies were able to follow these directions successfully." If the system works -- and if the volunteer readers in step #2 are representative of the skill level of the site's general readership -- it should be expected that most readers should be able to follow the directions and get good results at that point.

Almost all of the "how-to" directions that I've read, on any topic, could have benefited from being put through the wringer as described by the steps above. It's not merely that I think this algorithm would produce good directions; it's that my definition of good directions is precisely those directions that would pass the test in step #2.

As for what incentivizes the authors to produce directions that make it through this process, perhaps the hosting site could split the ad revenue with them from the pages containing the author's directions. Perhaps the hosting site could just reward them with a link from the article to the author's professional home page. Or maybe people would happily submit the instructions for free if it went towards a non-profit repository of helpful information, a la Wikipedia. (The huge difference from Wikipedia though, is that if you're an expert on George Washington, it's easy to write a good article about George Washington; but if you're an expert on cooking, that makes it hard to write a set of cooking directions that would fill in all the blanks needed by a beginner. Hence the multi-step vetting process above.)

It's tempting to think this is process would be "overkill" for a simple recipe, but that fails to consider the magnitude of the time savings when multiplied across the hundreds or thousands of people who will read the information over the course of its lifetime on the web. If the author spends an extra 10 minutes on the instructions to clarify things in such a way that saves just 1 minute of reading time for the average reader, when that 1 minute of time savings is multiplied by hundreds of readers, it's clearly an overall time-saver. (What disgusts me about the jalapeno popper recipes is that the authors could have saved me a whole day of painful burning on my fingers, if they had just taken 10 seconds to include the step about putting on gloves -- that would have been an overall time-saver even if only one person had read the recipe.)

So Morozov was right that we don't need laser-guided kitchens guiding us through the algorithm of carving a fish, but we should consider that an entirely different kind of algorithm could change everything for a beginning cook, or a person trying to learn any other skill from scratch. The Star Trek kitchen in To Save Everything, Click Here makes for an easy target for Morozov's argument, but that kitchen technology is hardly making enough inroads to threaten cooking as we know it -- I'll bet you'd never heard of it until this article. Bad directions, on the other hand, are so ubiquitous that we've accepted them as a part of our way of life, and we've all but forgotten to think how they could be made better. Like Robert Kennedy, I see people looking at their capsaicin-burned hands and their inedible jalapeno poppers with the ribs still attached and asking, "Why?", and I imagine eHow.com lining up newbies to critique their recipes until each recipe achieves a high rating from beginners based on the actual results that they got, and ask, "Why not?"

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

New submitter BetterThanCaesar writes "The Swedish Pirate Party and their ISP Serious Tubes have received a letter from 'The Rights Alliance' (formerly Antipiratbyrån, The Swedish Anti-Piracy Bureau), demanding they cease supplying Internet access to The Pirate Bay. Referring to the final sentence on the four Pirate Bay profiles, they threaten with legal action if access is not removed by February 26. On her blog, party leader Anna Troberg calls the letter 'extortion,' pointing out that (translated from Swedish) '[i]t is not illegal to provide The Pirate Bay with Internet access. There is no list of illegal sites that ISPs cannot provide access to.' (google translation to English)." The letter sent (in Swedish). Update: 02/20 14:58 GMT by U L : richie2000 notes that hosting isn't quite right; they're just routing traffic to TPB: "We're not hosting TPB, we're just routing traffic to them. Just like an ISP. Serious Tubes routes traffic to the Pirate Party, so they're even more removed. But, last night, Portlane, one of the ISPs that routes traffic to Serious Tubes, was pressured into cutting their transit to ST, even if they were just a provider to a provider to a provider to TPB."

rtoz writes with a quick bite from rtoz.org about Google's latest news about Project Glass: "Google has released video preview of its forthcoming Google Glass wearable headset, providing a fresh, and more realistic look at the device's user interface. Based on the demo, Google Glass will allow users to receive and execute onscreen directions, send voice-controlled messages, and search the web through speech. The UI also includes voice-controlled photos, and suggests that the device will offer onscreen translation support. And, it looks like the Google Glass will be water-resistant. Google has previously said it is aiming to launch Glass by early 2014, though it is already pushing out developer editions priced at $1,500." They're looking for developers, but only if you're hip enough.

An anonymous reader writes "We've watched patents slow down the smartphone and tablet markets. We've seen patent claims thrown against Linux, Android, and countless other software projects. Now, as 3-D printing becomes more capable and more affordable, it seems a number of patents threaten to do the same to the hobbyist and tinkerer crowd. Wired has highlighted some of the most dangerous ones, including: a patent on soluble print materials that support a structure while it's being printed; a ridiculously broad patent on distributed rapid prototyping, which could affect "every 3-D printing service that has launched in the past few years"; and an 18-year-old patent on 3-D printing using a powder and a binding material, held by MIT."

An anonymous reader writes "We've watched patents slow down the smartphone and tablet markets. We've seen patent claims thrown against Linux, Android, and countless other software projects. Now, as 3-D printing becomes more capable and more affordable, it seems a number of patents threaten to do the same to the hobbyist and tinkerer crowd. Wired has highlighted some of the most dangerous ones, including: a patent on soluble print materials that support a structure while it's being printed; a ridiculously broad patent on distributed rapid prototyping, which could affect "every 3-D printing service that has launched in the past few years"; and an 18-year-old patent on 3-D printing using a powder and a binding material, held by MIT."

An anonymous reader writes "We've watched patents slow down the smartphone and tablet markets. We've seen patent claims thrown against Linux, Android, and countless other software projects. Now, as 3-D printing becomes more capable and more affordable, it seems a number of patents threaten to do the same to the hobbyist and tinkerer crowd. Wired has highlighted some of the most dangerous ones, including: a patent on soluble print materials that support a structure while it's being printed; a ridiculously broad patent on distributed rapid prototyping, which could affect "every 3-D printing service that has launched in the past few years"; and an 18-year-old patent on 3-D printing using a powder and a binding material, held by MIT."

theodp writes "'The lack of interest, the disdain for history is what makes computing not-quite-a-field,' Alan Kay once lamented. And so it should come as no surprise that the USPTO granted Google a patent Tuesday for the Automatic Deletion of Temporary Files, perhaps unaware that the search giant's claimed invention is essentially a somewhat kludgy variation on file expiration processing, a staple of circa-1970 IBM mainframe computing and subsequent disk management software. From Google's 2013 patent: 'A path name for a file system directory can be "C:temp\12-1-1999\" to indicate that files contained within the file system directory will expire on Dec. 1, 1999.' From Judith Rattenbury's 1971 Introduction to the IBM 360 computer and OS/JCL: 'EXPDT=70365 With this expiration date specified, the data set will not be scratched or overwritten without special operator action until the 365th day of 1970.' Hey, things are new if you've never seen them before!"

Today at about 19:25 UTC (2:25 PM EST), Asteroid 2012 DA14 will make its closest approach to Earth, passing a mere 27,650 kilometers above the surface — closer than our satellites in geosynchronous orbit. NASA is broadcasting a live-steam showing the asteroid from an Observatory, and will have coverage on NASA TV starting about a half-hour before closest approach. The Planetary Society will be broadcasting a live webcast, and Phil Plait will be hosting a Google+ Hangout. NASA has also compiled a nice post filled with information about the asteroid, including trajectory diagrams, animated videos of the path, and answers to question about 2012 DA14. You can also watch it move at 50x actual speed through a telescope. They take pains to note that there is no danger of the asteroid striking the planet today, or any time in the forseeable future. Its next notably close approach in 2046 will only bring it about a million kilometers away. What makes 2012 DA14 significant is that it's rather large — it's 45 meters across and weighs about 130,000 metric tons. It's also moving about 7.8 kilometers per second relative to Earth. "To view the asteroid, you will need a good pair of binoculars, or even better, a moderately powered telescope. During the closest approach, and dependant on local weather, the asteroid will be visible from parts of Europe, Africa and Asia. The asteroid will appear to be moving relatively quickly as it crosses the sky from the south to the north." NASA says this morning's meteor event in Russia was unrelated.

New submitter dovf writes "The Bad Astronomer analyzes incoming reports about the apparent meteoric fireball over Russia: 'Apparently, at about 09:30 local time, a very big meteor burned up over Chelyabinsk, a city in Russia just east of the Ural mountains, and about 1500 kilometers east of Moscow. The fireball was incredibly bright, rivaling the Sun! There was a pretty big sonic boom from the fireball, which set off car alarms and shattered windows. I'm seeing some reports of many people injured (by shattered glass blown out by the shock wave). I'm also seeing reports that some pieces have fallen to the ground, but again as I write this those are unconfirmed." This is the best summary I've found so far, and links to lots of videos and images. He also clarifies something I've been wondering about: 'This is almost certainly unrelated to the asteroid 2012 DA14 that will pass on Friday.'"

Celarent Darii writes "Slashdot readers have undoubtedly heard of Google Docs and the many other online word processing solutions that run in the browser. However, as a long-time user of TeX and LaTeX, these solutions are not my favorite way of doing things. Wouldn't it be nice to TeX something in your browser? Well, look no further, there is now an online collaborative LaTeX editor with integrated rapid preview. Some fantastic features: quasi-instant preview, automatic versioning of source, easy collaboration and you can even upload files and pictures. Download your project later when you get home. Are you a TeX guru with some masterpieces? Might I suggest uploading them? For the beginner: you can start here."

vikingpower writes "Today, I decided to acquire a refurbished Sun Fire V1280 server, with 8 CPUs. The machine will soon or may already belong to a certain history of computing. This project is not about high-performance computing, much more about lovingly dusting off and maintaining a piece of hardware considered quirky by 2013 standards. And Now the question creeps to mind: what software would Slashdotters run on such a beast, once it is upgraded to 12 procs and, say, 24 GiB of RAM ?"

astroengine writes "The SETI Institute has launched a new website called 'Pluto Rocks!' intended to gather a public vote on the names of Pluto's smallest, and most recently discovered, moons P4 and P5. Discovered in 2011 and 2012 by Hubble, the two dinky satellites have concerned scientists managing the NASA New Horizons probe that will flyby the Plutonian system in 2015 — the presence of small rocky bodies in Pluto orbit might mean there is a significant collision risk to the high velocity spacecraft. This sinister back story will surely influence the naming outcome of the two new moons, where all the suggestions on Pluto Rocks! are related to Greek and Roman mythological characters from the underworld (but you can also make your own suggestions). If you want to get involved, there's also a special SETI Institute G+ Hangout planned for 11 a.m. PT Monday where two of the P4/P5 discovery scientists will hold a Q&A session."

sfcrazy writes "Google has declared Red Hat's RHEL 6 obsolete, showing a notification which says, 'Google Chrome us no longer updating because your operating system is obsolete.' Red Hat evangelist Jan Wilderboer says: 'We release new stable versions of RHEL every 2-3 years. The API/ABI stability is what sets it apart from community distros. Customers need long term stability. Google knows (and uses) that itself internally. By cutting the support of enterprise distributions they simply tell me to move elsewhere. That's not a very encouraging thing.'"

New submitter terbeaux writes "The documentary TPB AFK follows the creators of The Pirate Bay — Peter Sunde, Fredrik Neij and Gottfrid Svartholm — through their technical and logistical trials of keeping TPB online as well as their court appearances in Sweden. After its premiere at Berlin International Film Festival, TechCrunch is reporting that TPB AFK is now available under a Creative Commons license for purchase, download on TPB, or viewing on YouTube. The budget for the film was raised on Kickstarter, where the makers achieved twice the funding goal in the allotted month-long funding campaign. The film already has 40,000 YouTube views, 19,000 torrent seeders, and over 2,000 paid downloads. There are public screenings happening world-wide."

The Firefox and Chrome teams have announced that their respective browsers can now communicate with each other via WebRTC for the purpose of audio and video communication without needing a third-party plugin. WebRTC is a new set of technologies that brings clear crisp voice, sharp high-definition (HD) video and low-delay communication to the web browser. From the very beginning, this joint WebRTC effort was embraced by the open web community, including engineers from the Chrome and Firefox teams. The common goal was to help developers offer rich, secure communications, integrated directly into their web applications. In order to succeed, a web-based communications platform needs to work across browsers. Thanks to the work and participation of the W3C and IETF communities in developing the platform, Chrome and Firefox can now communicate by using standard technologies such as the Opus and VP8 codecs for audio and video, DTLS-SRTP for encryption, and ICE for networking. To try this yourself, you’ll need desktop Chrome 25 Beta and Firefox Nightly for Desktop. In Firefox, you'll need to go to about:config and set the media.peerconnection.enabled pref to "true." Then head over to the WebRTC demo site and start calling."

Zordak writes "Micron has recently landed U.S. Patent 8,352,745, which claims priority back to a February 2000 application---well before Apple's 2004 slide-to-unlock application. While claim construction is a highly technical art, the claims here are (for once) almost as broad as they sound, and may cover the bulk of touch screen smart phones on the market today. Dennis Crouch's Patently-O has a discussion."

pigrabbitbear writes "It's been nearly a decade since Shin Dong-hyuk, an ex-prisoner of North Korea's Camp 14, crawled over the electrocuted body of a friend lying dead on a fence, a boundary he was born inside of and lived within for 23 years. He made his way across the Chinese border on foot and was granted political asylum and citizenship in Seoul. Now, thanks to updated Google maps of the region, you can actually (if somewhat loosely) retrace the steps of his incredible escape. Through its Map Maker program, which crowdsources cartographic info, Google has published finer details of some North Korean roads. More notably, it has included shaded-in locations of the country's notorious prison camps. The data has flowed in from a few different sources, including defected North Korean expats now living in Seoul. Geographically-minded tourists and visitors of North Korea have weighed in, and historic map data from pre-partitioned Korea into has also been helpful. (Google maintains that the recent trip to Pyongyang by CEO Eric Schmidt had nothing to do with this project.)"

Okian Warrior writes with word that, as of Monday evening, multiple police agencies and the military were "conducting training exercises over Miami and elsewhere in the county. The exercise includes military helicopters firing machine-gun blanks while flying over highways and buildings. This YouTube video shows helicopters strafing highways with blank rounds near the Adrian Arts center. There are reports of similar actions in Houston From the Houston article: 'if you see the helicopters or hear gunfire, it's only a drill.'" Note: this time, it's not in The Onion.

Jakob Perry, today's interviewee, is a volunteer who helps make LinuxFest Northwest happen. This is an event produced by the Bellingham Linux Users Group that "has been a tradition in Bellingham, WA since 2000." Bellingham is a small town about a 1.5 hour drive away from Seattle, and a shorter distance from Vancouver, Canada. Last year they had 1200 people. They have a core group of about 10 year-round volunteers, with as many as 60 participating in the event itself, many of whom are students at Bellingham Technical College, which is where LinuxFest Northwest is held.

judgecorp writes "Linux kernel developer Alan Cox has left Intel and Linux development after slamming the Fedora 18 distribution. He made the announcement on Google+ and promised that he had not fallen out with Linus Torvalds, and would finish up all outstanding work." Also at Live Mint, which calls Cox's resignation notice a "welcome change from the sterility, plain dishonesty of CEO departure statements." Cox says in that statement that he's leaving "for a bit," and "I may be back at some point in the future - who knows."

An anonymous reader writes "Linux kernel developer veteran Alan Cox has lashed out at Red Hat's recent release of Fedora 18. Cox posted comments to his Google+ page saying 'Fedora 18 seems to be the worst Red Hat distro I've ever seen.' He encountered numerous problems with Fedora 18 and then decided to switch to Ubuntu."

Titus Andronicus writes "fuse-exfat, a GPLv3 implementation of the exFAT file system for Linux, FreeBSD, and OS X, has reached 1.0 status, according to an announcement from Andrew Nayenko, the primary developer. exFAT is a file system designed for sneaker-netting terabyte-scale files and groups of files on flash drives and memory cards between and among Windows, OS X, and consumer electronics devices. It was introduced by Microsoft in late 2006. Will fuse-exfat cut into Microsoft's juicy exFAT licensing revenue? Will Microsoft litigate fuse-exfat's developers and users into patent oblivion? Will there be a DKMS dynamic kernel module version of the software, similar to the ZFS on Linux project? All that remains to be seen. ReadWrite, The H, and Phoronix cover the story."

Titus Andronicus writes "fuse-exfat, a GPLv3 implementation of the exFAT file system for Linux, FreeBSD, and OS X, has reached 1.0 status, according to an announcement from Andrew Nayenko, the primary developer. exFAT is a file system designed for sneaker-netting terabyte-scale files and groups of files on flash drives and memory cards between and among Windows, OS X, and consumer electronics devices. It was introduced by Microsoft in late 2006. Will fuse-exfat cut into Microsoft's juicy exFAT licensing revenue? Will Microsoft litigate fuse-exfat's developers and users into patent oblivion? Will there be a DKMS dynamic kernel module version of the software, similar to the ZFS on Linux project? All that remains to be seen. ReadWrite, The H, and Phoronix cover the story."

judgecorp writes "The latest Google Transparency Report, which tallies the number of times personal data is requested from Google, shows that governments are becoming more inquisitive than ever. Requests for user data have gone up by 70 percent since Google started these reports in 2009 — but the report shows Google is getting better at saying no: in 2009 it complied — fully or partially — with 76 percent of requests, and that figure is now down to 66 percent." This report is the first to feature requests broken down by the legal process used.

Jörg Sprave's day job is as a manager in the world of consumer electronics. But he has been for many years making manifest the sort of things that once filled my school notebook margins with doodles: slingshots and other devices for launching bolts, steel balls, and other stuff at high speed at targets or just into the air. (Some of his "slingshots" are hard to recognize as such; he eschews the classic American wrist-rocket braced design as well as the old Tom Sawyer forked branch in favor of things a bit more elaborate.) Thanks to the Internet, hobbies that were once obscure are now easy to follow, and Sprave's homemade slingshots are no exception; you can follow his exploits through an ongoing series of YouTube videos and a forum site that builds on these videos. He's doing it in Germany, too, where firearms may be harder to come by than in the U.S., but giant honkin' firecrackers are available (at least for part of the year), and acts accordingly. Amazingly, he has yet to lose an eye; his goggles are a wise precaution. Sprave has agreed to answer your questions about his own take on physics as a hobby. As usual for Slashdot interviews, you're invited to ask as many questions as you'd like, but please divide them, one question per post.

Eric Schmidt attracted headlines when he visited North Korea, but until now he has said little about the trip. Today he broke his silence with a Google+ post. He says in part: "As the world becomes increasingly connected, the North Korean decision to be virtually isolated is very much going to affect their physical world and their economic growth. It will make it harder for them to catch up economically. We made that alternative very, very clear. Once the internet starts in any country, citizens in that country can certainly build on top of it, but the government has to do one thing: open up the Internet first. They have to make it possible for people to use the Internet, which the government of North Korea has not yet done. It is their choice now, and in my view, it’s time for them to start, or they will remain behind." His daughter had some interesting things to say as well, "The best description we could come up with: it's like The Truman Show, at country scale."

Eric Schmidt attracted headlines when he visited North Korea, but until now he has said little about the trip. Today he broke his silence with a Google+ post. He says in part: "As the world becomes increasingly connected, the North Korean decision to be virtually isolated is very much going to affect their physical world and their economic growth. It will make it harder for them to catch up economically. We made that alternative very, very clear. Once the internet starts in any country, citizens in that country can certainly build on top of it, but the government has to do one thing: open up the Internet first. They have to make it possible for people to use the Internet, which the government of North Korea has not yet done. It is their choice now, and in my view, it’s time for them to start, or they will remain behind." His daughter had some interesting things to say as well, "The best description we could come up with: it's like The Truman Show, at country scale."

Incarnate-VO writes "Long running space-MMO Vendetta Online, which debuted with Linux support back in 2002, has launched a Kickstarter campaign to support a major gameplay expansion, including player-owned stations, capships, and territorial conquest. If the Kickstarter succeeds, an upcoming iPad version could also gain some added polish, joining the existing mobile support for Android. (The Kickstarter video is also available on YouTube in HD)."

theodp writes "Harvard geneticist George Church recently told Der Spiegel he's close to developing the necessary technology to clone a Neanderthal, at which point all he'd need is an 'adventurous human woman' to be a surrogate mother for the first Neanderthal baby to be born in 30,000 years (article in German, translation to English). Church said, 'We have lots of Neanderthal parts around the lab. We are creating Neanderthal cells. Let's say someone has a healthy, normal Neanderthal baby. Well, then, everyone will want to have a Neanderthal kid. Were they superstrong or supersmart? Who knows? But there's one way to find out.'"

dstates writes "The Department of Health and Human Services has released newly revised rules for the Health Information Privacy and Accountability Act (HIPAA) to ensure patient access to electronic copies of their electronic medical records. Several years ago, there was a great deal of excitement about personalized health information management (e.g. Microsoft HealthVault and Google Health). Unfortunately, patients found it difficult to obtain their medical records from providers in formats that could easily be imported. Personalized health records were time consuming and difficult to maintain, so these initiatives have not lived up to their expectations (e.g. Google Health has been discontinued). The new rules should address this directly and hopefully will revitalize interest in personal health information management. The new HIPAA rules also greatly strengthen patient privacy, the ability of patients to control who sees their medical information, and increases the penalties for leaking medical records information. 'Much has changed in health care since HIPAA was enacted over fifteen years ago,' said HHS Secretary Kathleen Sebelius. 'The new rule will help protect patient privacy and safeguard patients' health information in an ever expanding digital age.'"

An anonymous reader writes "Microsoft on Wednesday launched a new mobile app powered by Windows Azure called HelpBridge that lets you both ask for help after a natural disaster, as well as offer to give it. In the wake of Hurricane Sandy, the launch is an excellent initiative to rally everyone around one cause: supporting each other during a time of need. You can download the app right now from the Google Play Store, the Apple App Store, and the Windows Phone Store. Unfortunately, it's only available in the US right now, but hopefully Microsoft will be expanding regional support soon."

New submitter thygate writes with news of more trouble for Apple with its warranty terms complying with E.U. regulations. From the press release: "For many years warranty issues are at the top of the charts of complaints dealt with by consumer organizations. One of the recurring problems are the complaints about Apple. 'Test-Aankoop/Test-Achats' found major problems fixed on the information provided by Apple and its authorized distributors regarding the legal guarantee, the commercial one year warranty, and the warranty extension through the 'AppleCare Protection Plan' of 2 or 3 years. A lawsuit against Apple has been filed (English translation; original)) with the Commercial Court of Brussels. In a precedent in Italy, The commercial practices of Apple were found to be misleading. Apple was sentenced to pay € 900,000 and was obliged to change their contractual legal warranty and guarantees to consumers."

Qedward writes "The Norwegian Ministry of Finance seems to be taking a bit of stick at the moment. It wants all the existing cash registers in the country thrown out and replaced with new ones. Not surprisingly, this massive upgrade is not popular. But it is apparently being pushed through in an attempt to prevent cash registers' figures being massaged downwards in use so as to reduce tax. The Norwegian association of tax auditors said: 'The source code must be opened.' 'Without source code it is not possible to determine whether or "hidden" functionality exists or not. Just knowing that the tax authorities have access to the source code of the application, will reduce the effort to implement hidden functionality in the software.'"

jfruh writes "When Android was first introduced, it got much of its buzz in the open source community, and despite it being a mobile juggernaut backed by huge companies, it remains an open source project that anyone can submit code to. Thus, when a community patch that claimed to reduce the lag that still plagues the platform was created, it rocketed around various community code sites and was widely praised. The only problem: it didn't actually speed Android up."

An anonymous reader writes "Google has released Chrome version 24 for Windows, Mac, and Linux. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome. The biggest improvement on the user side of things is the speed increase. Google's own Octane JavaScript test shows that this is the fastest Chrome release yet. When the beta came out in November, the company was touting that Chrome had become 26 percent faster on Octane than it was last year. Now it's even faster. Google also announced it is introducing a new Chrome beta channel for phones and tablets running Android 4.0 or higher. You can download version 25.0.1364.8 right now directly from Google Play (since this is a beta, it's not available via search; you'll need to use the link). The release of version 25 is significant because it means Google is attempting to bring Chrome for Android in line with the desktop version. The current release of Chrome for Android is version 18, last updated in November."

An anonymous reader writes "Google has released Chrome version 24 for Windows, Mac, and Linux. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome. The biggest improvement on the user side of things is the speed increase. Google's own Octane JavaScript test shows that this is the fastest Chrome release yet. When the beta came out in November, the company was touting that Chrome had become 26 percent faster on Octane than it was last year. Now it's even faster. Google also announced it is introducing a new Chrome beta channel for phones and tablets running Android 4.0 or higher. You can download version 25.0.1364.8 right now directly from Google Play (since this is a beta, it's not available via search; you'll need to use the link). The release of version 25 is significant because it means Google is attempting to bring Chrome for Android in line with the desktop version. The current release of Chrome for Android is version 18, last updated in November."

Many reporters go to the CES, AKA Consumer Electronic Show (warning - link landing page plays annoying sound) in Las Vegas to see the newest 42.001" LCD TVs, which are 0.001" bigger than last year's 42" models. And there are many boring Windows 8 devices, many of which both run Windows and can display the number 8. These items, along with keynotes from tech gurus like Bill Clinton (We're not making this up!) may be amazing to some news outlets, but not to Slashdot or to Our Man Timothy, who seeks out the new, the bizarre, and the unusual and -- without taking a dime from them -- lets their instigators talk to him about their wares. But it's got to be good stuff, not run of the mill incremental advances. Like the Good Night Lamp(tm), which was invented by Alexandra Deschamps-Sonsino, whose "work has been exhibited," says the goodnightlamp.com/team page, "at the Milan Furniture Fair, London Design Festival, The Victoria & Albert Museum and the Museum of Modern Art in New York." Now the Good Night Lamp people are showing off their product and trying to raise money through Kickstarter. But that's enough from us. We will now hand the microphone to Ms. Deschamps-Sonsino and let her tell you the rest.

vikingpower writes "As a previous Slashdot story already reported, Ruby on Rails was recently reported to suffer from a major SQL injection flaw. This has prompted the Dutch government to take the one and only national site for citizens' digital identification offline (link in Dutch, Google translation to English). Here is the English-language placeholder page for the now-offline site. This means that 16 million Dutch citizens cannot authenticate themselves anymore with government instances, and that those same government instances can not communicate anything to those same citizens anymore." Fixes were released, so it looks like it's on their sysadmin team now.

New submitter GavrocheLeGnou writes "The french ISP 'Free.fr' is now blocking ads from Adsense and other providers by default for all its subscribers. The option can be turned off globally, but there's no whitelist (Google translation of French original). From the article: 'Because the service doesn’t offer a whitelist (contrary to Adblock, a service I’ve used for years), this means that it is an all or nothing choice, activated by default to block everything. And since it is not only internet, but TV and phone lines running through the FreeBox, it’s possible that, if left unchecked, Free could beginning blocking TV ads, or phone calls from known spam hotlines. While this seems like a potentially beneficial service, there’s no doubt that it’s biting at the heels of several sectors who rely on advertisement to make money, let alone the advertisers themselves who pay to reach an audience, and are blocked at the door.'"

itwbennett writes "According to an ITworld report, 'Google has agreed to change some of its business practices, including allowing competitors access to some standardized technologies, to resolve a U.S. Federal Trade Commission antitrust complaint against the company.' This includes 'allow[ing] competitors access to standards-essential patents the company acquired along with its purchase of Motorola Mobility.' Also among the business practices Google has agreed to stop is 'scraping Web content from rivals and allegedly passing it off as its own, said FTC Chairman Jon Leibowitz.'" SlashCloud has some more details, including links to the agreement itself and Google's soft-pedaling description of "voluntary product changes."

Trailrunner7 writes with the news as posted at Threatpost (based on this advisory) that "All of the current versions of the Ruby on Rails Web framework have a SQL injection vulnerability that could allow an attacker to inject code into Web applications. The vulnerability is a serious one given the widespread use of the popular framework for developing Web apps, and the maintainers of Ruby on Rails have released new versions that fix the flaw, versions 3.2.10, 3.1.9 and 3.0.18. The advisory recommends that users running affected versions, which is essentially anyone using Ruby on Rails, upgrade immediately to one of the fixed versions, 3.2.10, 3.1.9 or 3.0.18. The vulnerability lies specifically in the Ruby on Rails framework, and its presence doesn't mean that all of the apps developed on vulnerable versions are susceptible to the bug."