theodp writes "With a gushing press release, Federal CTO Aneesh Chopra announced the launch of Text4baby, 'an unprecedented mobile health public-private partnership' designed to promote maternal and child health. Expectant women are instructed to 'Enter the date of the first day of your last menstrual period' to start receiving 'timely and expert health information through SMS text messages' until their child reaches the age of 12 months (limited to 3 free messages/week). The White House Blog has more information on the 'historic collaboration between industry, the health community and government.' Separately, the White House announced plans to spend $3,000 on 'Game-Changing' Solutions to Childhood Obesity. Once again, Dilbert proves to be scarily prescient."

theodp writes "Google has actually managed to patent displaying patents. The USPTO issued US Patent No. D603,866 to six Google inventors for their 'graphical user interface for display screen of a communications terminal.' Among the six inventors is the guy who introduced Google Patents. Ironically, Google Patents can't seem to find the new Google patent for Google Patents."

An anonymous reader writes "AV-Comparative recently released the results of a malware removal test in which they evaluated 16 anti-virus software solutions. The test focused only on the malware removal/cleaning capabilities, therefore all the samples used were ones that the tested anti-virus products were able to detect. The main question was if the products were able to successfully remove malware from an already infected/compromised system. None of the products performed at a level of 'very good' in malware removal or removal of leftovers, based on those 10 samples."

LinuxScribe tips a piece up at Linux.com with inside details on the design and construction of the Apollo 11 code. There are some analogies to open source development but they are slim. MIT drafted the code — to run on the Apollo Guidance Computer, a device with less grunt than an IBM XT — it had 2K of memory and a 1-MHz clock speed. It was an amazing machine for its time. NASA engineers tested, polished, simulated, and refined the code. "The software was programmed on IBM punch cards. They had 80-columns and were 'assembled' to instruction binary on mainframes... and it took hours. ... During the mission, most of the software code couldn't be changed because it was hard-coded into the hardware, like ROM today... But during pre-launch design simulations, problems that came up in the code could sometimes be finessed by... computer engineers using a small amount of erasable memory that was available for the programs. The software used a low-level assembly language and was controlled using pairs or segments of numbers entered into a square-shaped, numeric-only keyboard called a Display and Keyboard Unit... The two-digit codes stood for 'nouns' or 'verbs,' and were used to enter commands or data, such as spacecraft docking angles or time spans for operations." Reader Smark adds, "The Google Code Blog announced today that the Virtual AGC and AGS project has transcribed the Command Module and Lunar Excursion Module code used during the Apollo 11 moon landing. The code is viewable at the VirtualAGC Google Code Page."

Hmmm2000 writes "Recently several Visa card holders were, um, overcharged for certain purchases, to the tune of $23,148,855,308,184,500.00 on a single charge. The company says it was due to a programming error, and that the problem has been corrected. What is interesting is that the amount charged actually reveals the type of programming error that caused the problem. 23,148,855,308,184,500.00 * 100 (I'm guessing this is how the number is actually stored) is 2314885530818450000. Convert 2314885530818450000 to hexadecimal, and you end up with 20 20 20 20 20 20 12 50. Most C/C++ programmers see the error now ... hex 20 is a space. So spaces were stuffed into a field where binary zero should have been."

theodp writes "Slate's Farhad Manjoo would gladly pay a hefty monthly fee for immediate access to recent movies and TV shows — if someone would just take his money. In reality, he pays nothing because no company sells such a plan, and instead resorts to getting his programming from the friendly BitTorrent network.

explosivejared writes "Forbes is running a story discussing the verdict in the Pirate Bay case and its implications on file sharing, specifically with regard to Google. The article points out what most people on Slashdot already realize: Google provides essentially the same service that the Pirate Bay does. The Pirate Bay case may be far from over, accounting for appeals, but the Pirate Bay's assumption of being unchallengeable was shattered. The article raises the question of whether or not Google is untouchable in the matter. The story is quick to point out how the situation resembles a futile game of cat-and-mouse, but given how the Pirate Bay's confidence was ultimately broken, is Google beyond reproach?"

bonch writes "Windows 95 almost shipped with a technique for detecting whether a floppy disk was inserted without spinning up the drive. Microsoft's floppy driver developer discovered a sequence of commands that detected a disk without spinup — unfortunately, unspecified behavior in the floppy hardware specification meant that half the drives worked one way and half the other, each giving opposite results for the detection routine. Microsoft considered a dialog prompting the user to insert a disk to 'train' the routine, but the idea was scrapped."

The_AV8R writes "Jonathan Zdziarski showed that every time you press the Home button on your iPhone, a screen capture is taken in order to produce a visual effect. This image is then cached and later deleted. Zdziarski says that there have been cases of law enforcement looking up sex offenders' old data and checking recovered screenshots." This revelation occurred in the midst of a webcast on iPhone forensics, demonstrating how to bypass the iPhone's password security (not trivial, but doable). Video from the talk is not online yet but is promised soon over at O'Reilly.

cliffski writes "Indie game developer Cliff Harris has long waged war against games piracy, but has issued a call to pirates to tell him why he is wrong. Assuming that developers are missing out on potential sales from disgruntled pirates, Cliff wants to hear specifically from people who have pirated his games. Not to criticize or lecture them, but to answer a simple question. Why? The reasons people give for copyright infringement/piracy are many and varied, but much of the debate has centred around music and movies, with big 'Triple-A' games an occasional consideration. With specific application to the world of small budget 'indie' games like those Cliff makes, he wants to know the thought processes behind people pirating the games. What puts people off buying? Is it quality, cost, DRM, ease of access? Is there anything that can be done to convert those people to buyers? While many pirates often make good general points about the reasons for the widespread pirating of PC games, it's unusual to get a chance to address specific developers with specific reasons. If you knew 100% that the developer would read your email explaining why you pirated their game, what would you say?"