AlistairCharlton writes "Facebook has made yet another amendment to its S-1 filing, adding a further 96 million shares, pushing its initial public offering up to a potential maximum of $18.4bn (£11.5bn). In what is the eighth amendment to its S-1 filing with the Securities and Exchange Commission, Facebook has also increased the number of shares allowed for over allotment, up from 50.6 million to 63.2 million." Facebook will have a lot of pressure to increase revenue after it goes public. jfruh writes in with a story about how that will impact their privacy policies. "There's been a steady drumbeat of panics over the past few years involving how Facebook uses the personal information you give it; nevertheless, someday you'll look back at 2012 as the golden age of Facebook privacy. That's because, once Facebook has its IPO, it'll come under huge pressure from the markets to extract more revenue from its business. And with display advertising not generating game-changing amounts of money, Facebook has only one valuable resource: your data, which is going to be monetized as hard as possible."

MrSeb writes "Researchers at the Tokyo Institute of Technology have developed a new wireless transmission system that works above all currently regulated spectrum frequencies. The new system works at the range of 300GHz to 3THz (terahertz), which is the Far Infrared (FIR) frequencies of the infrared spectrum. That spectrum is currently totally unregulated by any country or standards organization in the world, making it ripe for development of new technologies. So far the Japanese researchers have transmitted data at 3Gbps, but in theory speeds of up to 100Gbps should be possible."

judgecorp writes "Apple has changed the answer Siri gives to the question 'what is the best smartphone ever?' to prevent the voice-driven assistant from promoting the Nokia Lumia 900. Originally Siri trawled online reviews on the web using the wolfram Alpha search engine, to come up with the Lumia, much to Apple's embarrassment. Now, apple has intervened, replacing that answer with a joke: 'Wait there are other phones?'"

New submitter BLT2112 writes "Inspired by the Oracle of Bacon, the Oracle of Wikipedia finds the shortest path between two Wikipedia articles, as in Wikipedia Golf. As explained in the site, 'One selects one article as the tee and another article as the hole and then completes the course between them clicking as few links as possible. No typing is allowed. . . . The Oracle also allows you to search for the most challenging potential Wikipedia Golf courses. Can you find a longer course and merit a place in the "records" section?'"

MoldySpore writes "If anyone has tried to get to The Pirate Bay in the last 24 hours, they have most likely been met with a timeout. As an article on TorrentFreak notes, only a week ago The Pirate Bay scolded Anonymous for its attack on ISP Virgin Media, and now the site is currently the victim of a DDoS attack that is effectively keeping people from viewing the site. There is a lot of speculation as to whether this is retaliation from Anonymous, the work of an agency such as the RIAA and their associates, or an anti-pirate company such as PiratePay." Cyberwarfare? Pimple-faced teenagers? Someone screwed up the routing tables?

mikejuk writes with an update on the Oracle vs Google Trial. From the article: "One month into the Oracle v Google trial, Judge William Alsup has revealed that he has, and still does, write code. Will this affect the outcome? I think so! After trying to establish that the nine lines in rangeCheck that were copied saved Google time in getting Android to market the lawyer making the case is interrupted by the judge which indicates he at least does understand how straightforward it would be to program rangeCheck from scratch: 'rangeCheck! All it does is make sure the numbers you're inputting are within a range, and gives them some sort of exceptional treatment. That witness, when he said a high school student could do it — ' And the lawyer reveals he doesn't: 'I'm not an expert on Java — this is my second case on Java, but I'm not an expert, and I probably couldn't program that in six months.' Perhaps every judge should be a coding judge — it must make the law seem a lot simpler..." From yesterday; the Oracle lawyer was attempting to argue that Google profited by stealing rangeCheck since it allowed them to get to market faster than they would have had they wrote it from scratch. Groklaw, continuing its detailed coverage as always, has the motions filed today.

CowboyRobot writes "Ward Cunningham developed the first wiki, wrote the Fit test framework, is the co-inventor of CRC cards, and is now promoting the concept of technical debt. He recently won the Dr. Dobb's Excellence in Programming Award and was interviewed by that publication. 'The creator of the Wiki dishes on the Wiki, Wikipedia's policies, OO design, technical debt, CoffeeScript and Perl, how to survive as a veteran programmer, and doing the simplest thing that could possibly work.' Cunningham is given the chance to explain his philosophy of coding: 'I like the picture and I like the look of the code. It's only 40 lines, but every line carried some careful thought. There was a learning curve there that surprised me because the programs looked short. The most rewarding work I've done this year is digging through that code and understanding what it does and understanding what it didn't do, and how to approach the problem.'"

zacharye writes, quoting BGR: "The launch of Sprint's flagship EVO 4G LTE has been delayed indefinitely and supply of AT&T's flagship HTC One X will be constrained as a result of ongoing patent disputes between HTC and Apple. HTC confirmed in a statement emailed to BGR on Tuesday evening that shipments of its new EVO 4G LTE and One X smartphones have been held up by United States Customs as part of an International Trade Commission investigation. Before the phones can clear Customs, the ITC will need to determine that HTC's new handsets are in compliance with an earlier ruling..."

New submitter slashbill writes "MIT's working on a way to measure network capacity. Seems no one really knows how much data their network can handle. Makes you wonder about how then do you calculate expense when building out capacity? From the article: 'Recently, one of the most intriguing developments in information theory has been a different kind of coding, called network coding, in which the question is how to encode information in order to maximize the capacity of a network as a whole. For information theorists, it was natural to ask how these two types of coding might be combined: If you want to both minimize error and maximize capacity, which kind of coding do you apply where, and when do you do the decoding?'" This is a synopsis of the first of two papers on the topic.

Fluffeh writes "General Motors spends around $40 million per year on maintaining a Facebook profile and around a quarter of that goes into paid advertising. However, in a statement, they just announced that 'it's simply not working.' That's a bit of bad news just prior to the Facebook IPO — and while Daniel Knapp tries to sweeten the news, he probably makes it even more bitter by commenting 'Advertising on Facebook has long been funded by marketing budgets reserved for trying new things. But as online advertising investments in general are surging and starting to cannibalize spend on legacy media, advertisers are rightfully asking whether the money spend is justified because it has reached significant sums now.'"

itwbennett writes "Sauce Labs had outgrown CouchDB and too much unplanned downtime made them switch to MySQL. With 20-20 hindsight they wrote about their CouchDB experience. But Sauce certainly isn't the first organization to switch databases. Back in 2009, Till Klampaeckel wrote a series of blog posts about moving in the opposite direction — from MySQL to CouchDB. Klampaeckel said the decision was about 'using the right tool for the job.' But the real story may be that programmers are never satisfied with the tool they have." Of course, then they say things like: "We have a TEXT column on all our tables that holds JSON, which our model layer silently treats the same as real columns for most purposes. The idea is the same as Rails' ActiveRecord::Store. It’s not super well integrated with MySQL's feature set — MySQL can’t really operate on those JSON fields at all — but it’s still a great idea that gets us close to the joy of schemaless DBs."

jd writes "2012 promises to be a fun year for hardware geeks, with three new 'Aptiv-class' MIPS64 cores being circulated in soft form, a quad-core ARM A15, a Samsung ARM A9 variant, a seriously beefed-up 8-core Intel Itanium and AMD's mobile processors. There's a mix here of chips actually out, ready to be put on silicon, and in last stages of development. Obviously these are for different users (mobile CPUs don't generally fight for marketshare with Itanium dragsters) but it is still fascinating to see the differences in approach and the different visions of what is important in a modern CPU. Combine this with the news reported earlier on DDR4, and this promises to be a fun year with many new machines likely to appear that are radically different from the last generation. Which leaves just one question — which Linux architecture will be fully updated first?"

CWmike writes with news of a significant change in Google's strategy for Android. According to a Wall Street Journal report, "Google plans to give multiple mobile-device makers early access to new releases of Android and to sell those devices directly to consumers, said people familiar with the matter. That is a shift from Google's previous practice, when it joined with only one hardware maker at a time to produce 'lead devices,' before releasing the software to other device makers. Those lead devices were then sold to consumers through wireless carriers or retailers." JR Raphael adds, "Signs of something big have been brewing in AndroidLand for some time now: First, we've had the increasingly loud buzz about Google's top-secret mission to build an inexpensive Nexus-like tablet. Then, last month, Google opened the door to selling unlocked Nexus devices directly to consumers, eliminating the need for carrier meddling and contract commitments. Now, at long last, we're getting a glimpse at what's likely the final piece of the puzzle."