Betanews

Rhapsody to become an independent company

Tim Conneally — Tue, 09 Feb 2010 17:33:12 -0500

Now nearly a decade old, RealNetworks' online music service Rhapsody is going to be spun off into an independent company. The spin-off will mean that RealNetworks will no longer have operating control over the service, and it will have no single majority owner.

Currently, Rhapsody is a joint venture with RealNetworks and Viacom subsidiary MTV Networks, with real owning 51% of the equity of Rhapsody and Viacom owning 49%.

Robert Kimball, president and acting CEO for RealNetworks today said, "Separating Rhapsody into its own independent company is a significant first step in making RealNetworks a more focused and profitable company. Rhapsody will be the largest pure play digital music service in the market. We have provided Rhapsody with the right team, and financial and intellectual property assets to succeed in the competitive market for digital music."

Real expects the spin-off will be complete late in the first quarter of 2010.

Google Buzz: Another attempt to harness the content firehose

Tim Conneally — Tue, 09 Feb 2010 15:31:59 -0500

By Tim Conneally, Betanews

Rather than create another new destination social network like Facebook, Twitter or Foursquare, Google today announced that it has added social networking and location-based features into Gmail, Google Profiles, and Google Maps with a new service called Google Buzz.

Late last week, rumors surfaced that Google was debuting a new "Social Gmail" this week, and that really is kind of what Buzz is. With it, you can post status updates and share links, photos, and location-based updates with your Gmail contacts, and the content being posted by your contacts is automatically ranked according to your interactions with that contact. Ultimately, it's a lot like FriendFeed but with a Google flavor.

Buzz updates are read directly in Gmail just like an e-mail thread, and posts can be kept only between friends or be published to the Web at large under the user's Google Profile like a Twitter feed. All posts and comments appear in real time, and they can come from Twitter, Picasa, Flickr, and Google Reader. Location-based posts can be sent from buzz.google.com through the user's mobile browser. Additionally, the Google Maps app for Android and Symbian received an update today which adds a Buzz layer for plotting buzzed-about spots. In the Google Search widget in Android, users can simply do a voice search where they say "Post Buzz" and their location will automatically be posted.

The service will be rolled out to Gmail inboxes this week, the mobile site is currently live, and the updated Maps app is available now. Users who already have a Google Profile and Gmail account don't need to sign up for anything, and can immediately begin posting.

Jeremiah Owyang, Web Strategist for the Altimeter Group said today, "To Facebook, this is a direct threat, these features emulate Friendfeed and the recently-designed Facebook newsfeed. Expect Google to incorporporate Facebook connect, commoditizing Facebook data as it gets sucked into Google and displayed on Google SERP...This is good for Twitter in the short term, as it'll amplify tweets, and suck them into a new system and give additional reach. Yet over time, status features will become a commodity, and Twitter as a destination will fade into the background."

Nvidia debuts new dynamically-switched graphics card technology

Tim Conneally — Tue, 09 Feb 2010 11:56:04 -0500

By Tim Conneally, Betanews

The idea behind notebooks with switchable graphics processors is that the most common tasks are handled by the lower power integrated GPU; but should the user need more complex graphics, a discrete graphics processor will be able to kick in to take care of the hard work.

It's been an option in certain notebooks for more than three years, and it has certainly grown more common as the technology has aged. But it has never quite been a perfect, on-demand solution. In the earliest switchable setups, the computer had to be rebooted for the swap to take place, and in later iterations, it required a physical switch to be thrown or sessions to be reset. and still others could turn on the discrete GPU, but not switch back to integrated once the change was made.

Today, Nvidia debuted its Optimus technology for GPU switching, which will soon be available in a handful of Asus notebooks (UL50Vf, U30Jc in the "ultra slim and light" series, and N61Jv, N71Jv, N82Jv in the Multimedia N series) Instead of requiring a conscious effort on the part of the user, Optimus-powered graphics processors balance the graphical processor load as a background task. Unlike ATI's switchable graphics platform, which uses the discrete card when under AC power and the integrated graphics processor to be used in battery mode, Optimus switches dynamically based upon the needs of the running applications.

"We needed hardware support to quickly move the graphics data around in the system, so we created a fast copy engine. The Optimus Copy Engine is a new alternative to traditional DMA (Direct Memory Access) transfers between the GPU frame buffer memory and system memory used by the IGP. With Optimus we also removed multiplexers, called MUXs, so we use the integrated graphics as a display adapter or pass through," Sasha Ostojic, Nvidia's Senior Director of Notebook Software, wrote in Nvidia's blog today. "The discrete GPU can do the heavy lifting and pass through the results to the integrated graphics chip to be displayed. By doing this, Optimus eliminated the need for hardware multiplexer and completely removed glitches associated with switching the display from IGP to GPU. Optimus transfers the display surface from the GPU frame buffer over the PCI Express bus to the system memory-based frame buffer used by the IGP. The key to performing the display transfer without negatively impacting 3D performance is the Optimus Copy Engine."

Asus' notebooks featuring Optimus are expected to begin availability some time in mid-March, with specifics pending.

Success: Google's Nexus One shipping support line takes tech support questions

Scott M. Fulton, III — Tue, 09 Feb 2010 11:06:12 -0500

By Scott M. Fulton, III, Betanews

11:35 am EST Tuesday, February 9, 2010 · In a test of Google's willingness to take customer concerns this morning, Betanews Editor-in-Chief Nathan Mook -- a new Nexus One owner himself who has not experienced either the 3G connectivity problem or the touchscreen tracking problem -- contacted the Nexus One shipping support line with a technical concern. After getting off the phone with a live Google support staffer in San Francisco, Nate reported very positive results.

The problem Nate was having, he says, is minor: The phone's automatic brightness isn't working well, remaining too dark when auto-brightness is turned on. Plus, the phone's touch-sensitive panel buttons at the bottom appear non-sensitive if you touch too close to the bottom.

Nate tells us Google's representative very kindly put his concern into the system, and offered to set up an exchange of phones with him; he responded it was not necessary.

"She was really quite nice," Nate reports. "She put my concerns into the system. Best customer support experience I've ever had from a big company. Better than Apple. I had zero wait time." His previous phone was an iPhone 3G S.

10:46 am EST · With hopes of being able to talk to a real, live person for the first time, to address not only 3G connectivity issues but an emerging, separate problem with poorly tracking touchscreens, Google Nexus One phone users had hopes today of being able to dial a toll-free phone number and speak with a Google representative. But despite headlines blazing through the blog-O-square this morning, that number is only "for questions about your existing order," as Google's support page clearly states.

Immediately below the newly posted instructions for shipping questions, the "Technical Support" section now directs customers with problems with the phone to HTC, the phone's manufacturer: "For technical support, please contact HTC customer care at 1-888-216-4736. For additional details and international support, please visit HTC's website."

This despite Google executives having told analysts during the phone's premiere event last month that Google was the "vendor of record," implying that it would be responsible for managing customer concerns.

"I knew it was too good to be true," writes Nexus One customer xsyclubs to Google's support forum early this morning. "However, I am still going to call daily."

That may be just a symbolic act for now, as xsyclubs and others may end up being transferred to HTC. Over on HTC's support forums, a bold message appears to have declared the 3G connectivity issue resolved. But an unusual message from Google employee Ry Guy yesterday told Nexus One customers that HTC was, in fact, declaring a different issue resolved: "The message...on HTC's website concerns a previous temporary data outage, not the 3G connectivity issues that some users have been experiencing," he wrote.

As 3G connectivity issues continue for many customers even after the distribution of an over-the-air software update, a growing number of owners are experiencing trouble with their touchscreens. In fact, defective touchscreens appears to be becoming a popular subject of YouTube videos, where owners everywhere are letting Google and the rest of the world see these symptoms for themselves.

The video above shows the touchscreen failing to respond to browser functions, but responding nominally to the home menu. Another YouTube video from a different customer shows the drawing program registering repeated taps on the screen as vertical lines starting the same distance (about an inch) below the fingertip, and ending at the fingertip location.

In the wake of scrutiny not only from Nexus One customers but Congress as well, Google decided yesterday to reduce its "equipment recovery fee" from as high as $350, as stated in its original Terms of Sale, to a maximum $150. However, that fee is in addition to whatever T-Mobile (for now, Nexus One's exclusive carrier) may charge; and as Google's revised terms state, the customer must agree that $150 is necessary to compensate for a kind of depreciation Google only describes as "market changes."

Google lowers 'unusually high' early termination fee on Nexus One

Tim Conneally — Tue, 09 Feb 2010 09:24:17 -0500

By Tim Conneally, Betanews

At the end of January, the Federal Communications Commission's Consumer Task Force launched an inquiry into the Early Termination Fees (ETFs) of the major wireless providers with a special focus on the Google Nexus One handset.

The Nexus One is unlike other smartphones in that it is sold only by Google and available on multiple carriers. As such, if a customer terminated his contract, he faced early termination fees from both Google and his wireless provider.

The Consumer Task Force's Inquiry said: "Consumers have been surprised by this policy and by its financial impact. Please let us know your rationale(s) for these combined fees, and whether you have coordinated or will coordinate on these fees and on the disclosure of their combined effect."

Google's response appeared quite plainly yesterday evening: it has lowered its early termination penalty from $350 to $150.

Responses from the FCC and Google this morning are pending.

Netgear and Ericsson introduce a mobile broadband hotspot with a twist

Tim Conneally — Tue, 09 Feb 2010 01:20:50 -0500

By Tim Conneally, Betanews

We have seen a couple of mobile broadband hotspots come to market in the last year, the Novatel MiFi on Sprint and Verizon, and the recent Sprint Overdrive from Sierra Wireless. They're pocket-sized, battery-powered devices with a 3G connection that can connect a handful of devices to the Internet wherever they're plopped down.

Today, Netgear and Ericsson announced that they have created a 3G mobile broadband-connected router like these devices, except that it's not pocketable and battery powered.

Instead, the new mobile broadband router, called the MBRN3300, is designed for fixed or semi-nomadic use. For example, it can provide a broadband connection to rural homes that don't have the appropriate infrastructure for a DSL, Cable or Fiber; or it can be set up in mobile homes, boats, automobiles and trains.

It provides an HSPA connection to the Internet and both 802.11n and Ethernet LAN for home networking. The broadband speeds depend, of course, upon the service providers' capabilities, but the current peak in U.S. speeds is 7.2Mbps and the average is around 4Mbps.

Though a number of companies have been pushing WiMAX as the solution to rural connectivity in North America, Southeast Asia and Africa (with 519 deployments in 146 countries), HSPA is showing strong growth across the world as well. According to the GSA's latest survey (February 4, 2010) 315 network operators in 133 countries have upgraded to HSPA.

The companies will be showing off the new wireless hotspot at Mobile World Congress in Barcelona next week, but carrier partnerships haven't been mentioned yet.

Goodnight, moon: What I learned from a space shuttle

Carmi Levy — Mon, 08 Feb 2010 17:19:27 -0500

By Carmi Levy, Betanews

Like many nighthawks across the continent, I found myself glued to more than one screen...all right, three. Plus my BlackBerry...as I watched this morning's launch of the Space Shuttle Endeavour. I observed the spectacle with a curious mixture of excitement and sadness because after the current STS-130 mission, the shuttle program has only four more scheduled flights before it's grounded for good.

It's not the retirement that gets me. Every technology has its day, and it's fair to conclude that a system largely designed in the early 1970s has now served its purpose and should logically be replaced. It's also fair to conclude that this same system was and is too complex to ever be fiscally feasible. Despite the orbiters' reusability, which was supposed to drive down the cost of spaceflight, extensive maintenance in-between missions made the program even more expensive to fly than conventional expendable rockets. The shuttle's inherent design flaws (you'll never see humans riding below any other part of a space vehicle again) pretty much sealed its fate.

The absent successor

What irks me about the whole thing is the fact that when the shuttle program is over and done, there won't be another program waiting in the wings to take over. President Obama's 2010 budget announcement last week virtually killed funding for the Constellation program, which would have resulted in new hardware to take humans more safely into orbit, to the moon and beyond.

We've been down this road before. After the Apollo program ended with the Apollo/Soyuz Test Project in 1975, nearly six years passed before the US once again launched its own astronauts into space. Then as now, NASA lacked the funds because the US lacked the national will to prioritize spending on sending humans into space. Then as now, NASA found itself going up against a wartime government dealing with frightfully uncertain economic conditions. Then as now, NASA lost the battle and spent years twiddling its thumbs waiting for its new ride to be ready.

With Constellation now virtually dead, NASA doesn't even have that comfort anymore. Had the key components for the regularly scheduled program already in progress -- the Ares I rocket and Orion capsule -- survived the axe, NASA would have had at least a five-year gap before its next launch. Now, it could be buying seats on Russian Soyuz rockets indefinitely while it waits for commercial space interests to fill the giant void. While thousands of NASA employees wonder what tomorrow might bring (hint: it won't be pretty) I can't resist the urge to draw a personal connection.

Liftoff of Space Shuttle STS-130, perhaps the final nighttime liftoff in the shuttle program's history. [Courtesy: NASA]

Of cars and spaceships

My wife and I cart our kids around in a vehicle we affectionately call the "wondervan." Despite our guilt over contributing to global warming, our car is an essential pillar of life for us and our kids. Like all vehicles, it has a finite lifespan, and we're already planning for its replacement over the next couple of years. The plan will be relatively simple: Save up a lot of money, do a lot of research and preparation, drive to the dealer in the old car, and return home (somewhat poorer) in the new one.

The same process applies in the real world. Planning for any technology platform's end-of-life is a fundamental requirement of any business in any sector. The laptops that your employees use and the servers they connect to can only last for so long. When they reach the inevitable point of no return -- where the costs and risks of keeping them in service outweigh an investment in followon technology -- it's time to take the plunge. Your business can't afford to be without laptops and servers until you decide you've got enough money saved up. The time to get off your duff and do something about it is not just before the thing dies an inglorious death or the vendor pulls its support. If you fail to bake lifecycle planning into your operations, your fate may be even more bleak than NASA's. The agency, despite countless layoffs, will exist in some form by the time this is all over. Your business? Don't hold your breath.

For a variety of self-inflicted and externally influenced reasons, NASA's new business model will see it walking the proverbial five miles to school for a whole lot of years before a new vehicle, likely developed by commercial partners, is ready. The agency failed to anticipate upcoming change, and now thousands of its employees will pay the ultimate price. I'm going to guess the former Can-Do organization will have a tough time convincing us to stay engaged while its human spaceflight capability remains grounded.

Who do you trust?

Despite their obvious differences, businesses and government agencies are equally dependent on trust. Once stakeholders lose trust, it's over. Would you willingly do business with an organization that failed to anticipate end-of-life for its core competency?

As you scope out potential partners, supply chain members and, yes, even customers, you're making one judgment call after another, typically revolving around whether you think this outfit has the brains and the moxie to stick with you for mutual benefit. If its leadership is so blind that it can't anticipate normal technology turnover, do you really want to be aligning yourself with it in the first place? Would you have any trust in its ability to balance near-term and long-term goals? I'm going to guess letting something like this happen would erode your confidence a bit.

In a year or two, my wife and I will take that infrequent trip to the dealer and return home with something newer, nicer, and safer than the vehicle it replaces. By then, NASA will be well into its human spaceflight stand down, waiting for the figurative bus while nations with bigger budgets and different priorities pass them by. I do hope businesses are studying this monumental gaffe and revisiting their technology investment roadmaps to ensure they, too, don't get caught without the basic ability to keep themselves relevant.

Carmi Levy is a Canadian-based independent technology analyst and journalist still trying to live down his past life leading help desks and managing projects for large financial services organizations. He comments extensively in a wide range of media, and works closely with clients to help them leverage technology and social media tools and processes to drive their business.

Netflix to FCC: NBCU + Comcast could bypass net neutrality

Scott M. Fulton, III — Mon, 08 Feb 2010 15:02:02 -0500

By Scott M. Fulton, III, Betanews

In a world where Federal Communications Commission Chairman Julius Genachowski's six principles for net neutrality are enforced, everyone who makes a living on the Internet could conceivably be "unburdened by the unnecessary intervention of network operators or government regulators." The exception would be when a pipeline provider such as Comcast merges with a content provider such as NBC Universal, to make certain classes of content viewable online only when it designates. That's the opinion of attorneys for video rental service Netflix, in a filing last month with the FCC and recently made public.

"Netflix believes that the codification of the existing network neutrality principles, together with the addition of nondiscrimination and transparency, create an effective framework for preserving an open Internet," begins Netflix' filing, written last January 14 (PDF available here). "These rules will allow all parts of the industry -- network operators, consumer electronics manufacturers, and edge providers of content, applications, and services -- to continue to innovate at a rapid pace, unburdened by the unnecessary intervention of network operators or government regulators."

The exception is when a dominant network operator like Comcast puts together a service like TV Everywhere, its lucrative on-demand platform for Internet streaming of content to subscribers. In a strangely familiar sounding refrain, Netflix warns that a bundling of the operating system, so to speak, with content makes it difficult for other distributors of content to compete at the same level.

"By bundling the traditional cable TV offering with Internet delivery of content, vertically integrated MVPDs and network operators are potentially extending and expanding their dominant market position at the expense of competitive online offerings," Netflix' attorneys write. "Moreover, the recent announcement of the proposed merger of Comcast and NBC Universal serves to exacerbate the growing concern that MVPDs will use their control over programming networks to stifle competition, including the growing competition from online video providers like Netflix."

The company's attorneys particularly point to a clause in the FCC's notice of proposed rulemaking last October. There, the commission acknowledged that certain classes of service that use the Internet as their backbone, probably shouldn't be managed the same way as the Web (based on HTTP, just one of the Internet's many applications). So the FCC proposed the creation of a service class called either managed services or specialized services, that it describes as industries unto themselves, and as such, deserving of special recognition and treatment. VoIP service such as what Vonage provides, and multi-channel video offered by AT&T U-verse and Verizon FiOS, are obvious examples.

As the Commission wrote at the time (PDF available here), it was interested in public comment regarding how such services could remain managed while the Internet stays open: "We recognize that these managed or specialized services may differ from broadband Internet access services in ways that recommend a different policy approach, and it may be inappropriate to apply the rules proposed here to managed or specialized services. However, we are sensitive to any risk that the growth of managed or specialized services might supplant or otherwise negatively affect the open Internet. In this section, we seek comment on whether and, if so, how the Commission should address managed or specialized IP-based services in order to allow providers to develop new and innovative technologies and business models and to otherwise further the goals of innovation, investment, competition, and consumer choice, while safeguarding the open Internet."

That's precisely the section to which Netflix' attorneys responded: "Netflix is concerned that network operators will use so-called managed services in a way that harms unaffiliated content or service providers that compete directly with services provided by the network operator, owing either to their vertical integration...or resulting from competitive threats to their legacy 'managed services' business. This concern is heightened in light of the fact that such 'managed services' are offered over the same physical network as broadband Internet access."

The danger, Netflix believes, is that by even creating the exception class in the first place, the FCC could inadvertently create the very "fast lane" for the Internet that lawmakers in 2005, coining the phrase "net neutrality" for the first time, sought to avoid.

As legislative momentum for passing Pres. Obama's ambitious public agenda has slowed, public support for the President's policies as a whole, has waned. As a result, even net neutrality -- something seemingly unrelated to health care, jobs, and the fiscal deficit -- appears to have become yet another can to be kicked down the avenue, as yet another topic tied to Mr. Obama. Last week, as House members discussed the Comcast + NBCU consolidation proposal, even net neutrality's principal backers appeared unwilling to take their own side, enabling Republican opponents to resume their counterattack.

House Telecommunications and the Internet ranking member Cliff Stearns (R - Florida) began last Thursday's hearings by suggesting the entire net neutrality issue was being raised in the context of Comcast and NBCU just to be anti-competitive. Rep. Stearns cited the DC Court of Appeals, which last month indicated the FCC may not have enforcement rights with respect to how Comcast may deploy its Internet services.

"The Court, in fact, seemed skeptical that the FCC even had legal authority to impose these mandates. One of the judges asked the FCC counsel 'whether he wanted to lose on process or jurisdiction.' Unless a condition is narrowly tailored to a transaction's specific harm to competition, it does not belong in this negotiation," stated Stearns. "Since this deal will not materially increase concentration in either the distribution or programming markets, demonstrating such harm would be difficult, especially in light of the robust competition in the video sector...If Comcast and NBCU are right that this deal creates a stronger entity that can better serve viewers, I think it can succeed. If they're wrong, it will fail."

The ranking member of the Energy and Commerce Committee, Rep. Joe Barton (R - Texas, a former chair of the Committee), didn't have much to add besides a smile and a wink: "It's good to see NBC and Comcast sitting side by side. That doesn't break my heart."

Report: Streaming video drove 72% global increase in mobile data consumption

Tim Conneally — Mon, 08 Feb 2010 12:27:29 -0500

By Tim Conneally, Betanews

A new study from subscriber management company Allot Communications today says that worldwide mobile broadband consumption increased approximately 72% in just the second half of 2009.

Though the Federal Communications Commission is worried that there won't be enough bandwidth in the United States to support the growth in mobile broadband use, the Americas are actually being outpaced by both the Asia Pacific region (APAC) and the Europe/Middle East/Africa region (EMEA) in terms of growth rate. APAC experienced an 86% growth in mobile broadband consumption, and EMEA experienced 70% growth, while use in the Americas grew by 59%.

Allot's study says that streaming video is "the single most influential factor driving the need for increased mobile network capacity," and that consumption of streaming video grew by 99% in the second half of '09. YouTube alone accounted for 10% of the world's mobile bandwidth consumption in the third and fourth quarters of last year.

"Mobile broadband networks are still facing the same challenges as fixed networks -- growing bandwidth demands, congestion, as well as finding ways to enhance the user experience and to lessen the negative impact of a few [P2P users] on the network," a statement from the company said today.

Stymied by continuing Nexus One 3G issues, Google blames the environment

Scott M. Fulton, III — Mon, 08 Feb 2010 11:59:00 -0500

By Scott M. Fulton, III, Betanews

For the most part, last week's over-the-air software update to Google Nexus One phones, which was intended to address the 3G connectivity issues with certain versions of the phone's firmware (with a gift of added multitouch), appears unsuccessful for many commenters to Google's support forums. Very few customers reported improvement, and some who did in the early going are now saying their flip-flop problems between 3G and EDGE have returned.

Meanwhile, although Nexus One manufacturer HTC has typically referred phone issues to Google -- the self-proclaimed "vendor of record" when the device premiered -- as of now, it has declared the issue resolved, suggesting that customers still experiencing problems "restart their Nexus One device to restore their T-Mobile data connection."

The entry of new customers into the Google support forum who report having purchased their phones in the last week, only to be confronted with the issues some others have faced since last month, suggests that Google may continue to be selling phones containing the firmware suspected of having the connectivity defect.

"I just recently purchased the Nexus One and discovered that I am unable to make calls and access the internet at the same time," reports new entrant Mayo1 on Saturday. "Once I make a voice call, I am unable to browse the Internet or use any apps that require Internet connectivity. I am mostly in a 3G area. Initially, I'm browsing or using my apps just fine then I decide to make a voice call and all of a sudden Internet connectivity is gone. The minute I hang up the voice call, I can go right back to browsing."

Besides this and the flip-flop problem, the other prominent symptom users are reporting is that connectivity seems high until someone touches the phone, then it drops to zero -- which suggests a problem with the phone's antenna. Although the common thread among customers with these symptoms appears to be the same firmware version, customers are beginning to suspect that these issues are actually unrelated -- that they are separate problems that afflicted a certain strain of the phone, but may not be caused by the firmware in that strain.

Last Sunday afternoon before the Super Bowl, Google employee Ry Guy posted a perplexing message. Citing the fact that "there's still a lot of interest here," he began by reminding customers of the existence of the OTA software fix "that will improve 3G connectivity for many Nexus One users." No one continuing to report negative symptoms had claimed to have refrained from installing the fix.

"However," Ry Guy continued, "there are a variety of factors which feed into the quality of 3G connectivity on mobile phones, a number of which are dependent on the environment rather than the phone itself. For instance, a software update can't address the experience of users on the edge or outside of 3G coverage areas. We're going to continue to track 3G performance closely with HTC and T-Mobile and will post any updates we've got."

Customers responded as though Google had just fumbled in the fourth quarter. "Just face facts: There is something significantly wrong with the software or hardware," wrote andrewrchick. "If you just tell us you will fix it but you need time, most of us will hang on in there. But don't insult us and blame it on T-Mobile as too many people here have enough experience to say otherwise."

And customer olypdd noted the trend of some technology news services following the forums lately: "Please remember...many, many entities, some who research and report on these technologies, are following these blogs. I would be careful to not blow smoke. It doesn't do anything to save Google (and HTC) from what is already an embarrassing Superphone release, and anything that looks patronizing will be reported as such elsewhere."

Over on the T-Mobile forums, customers who had not reported 3G connectivity problems appreciated the "pinch-to-zoom" multitouch addition in the latest OTA fix. For them, it certainly didn't hurt. For others who did report troubles, not only were their connectivity symptoms unchanged, but multitouch seemed to be crashing their browsers.

Writes T-Mobile customer polobear this morning, "Overall, I'm happy with the phone. Specifically however, I'm not happy with the 3G. As luck would have it, I live in an area with fantastic T-Mobile coverage. I get 5 bars (EDGE) in my basement no matter what phone is used. But on the N1, I can't pick up 3G anywhere around here (not in the house, not outside). I've never actually seen a 3G connection on the phone, ever."

Judging from T-Mobile's support forum, there did not appear to be any similar 3G connectivity issues affecting its other Android brands, including the MyTouch 3G, which is co-branded with Google.

Microsoft Confessions: 'There were a ton of bozos'

Joe Wilcox — Mon, 08 Feb 2010 00:15:00 -0500

By Joe Wilcox, Betanews

Do middling, middle managers run Microsoft? That's the consensus among the former Microsofties who shared their work stories with me over the last couple months. The new work week starts with another Microsoft Confessional -- the fourth in four days -- from 13-year company veteran Boris, which isn't his real name, of course. Boris was smart enough to see the end coming, and he made preparations in the days before his May 2009 layoff. He learned to read middle managers the way a genuine fortune teller might read tea leaves.

People being asked to leave are one view of Microsoft. But those leaving voluntarily are another perspective. In looking at Microsoft, I'm hugely concerned about the departures of two important and long-time Microsoft executives: Mike Nash and Bill Veghte, revealed on February 4 and January 14, respectively. Both men are 19-plus years veterans working for the Windows and Windows Live groups. Nash is headed to Amazon, and Veghte departs following last year's executive shuffle that put Steven Sinfosky in charge of the group (as one of five Microsoft presidents).

Historically, successful shipment of a new Windows version ends with big promotions. Windows Vista was the exception, leading to demotions, sideways transfers and departures (Microsoft wouldn't call them firings). But Windows 7 is a huge success, so what gives with Nash and Veghte leaving Microsoft?

The departures of Nash, Veghte and also Chris Liddell, Microsoft's former chief financial officer, are canaries in the coal mine. They signal something fundamentally wrong. Boris' story and the three before it -- "Killed over politics," "Deeply dysfunctional family" and "Poor worker bees" -- offer some insight into what is part of the problem.

Boris' story is the longest of the quartet of confessionals; as such, I've added subheads to make it easier reading. With that introduction, Boris' story:

My career out of college started with working as a technical writer for a few now-defunct engineering software firms. I recall my first day on the job, being assigned a massive Compaq 'portable' as my workstation, and teaching myself MS-DOS and batch file programming via the Compaq's user manual. We had a cool array of hardware around the office for porting: IBM AS/400, Silicon Graphics Iris and Indigo, some of the early Sun SPARCstations, and my favorite, a NeXT Cube.
During the next five years I moved up from a junior writing position to managing an entire department of writers and illustrators. I was largely self-taught as a manager. We made some good hires, got the work done on time, wrote what I still think were some actually helpful manuals, and introduced a bit of publishing innovation with on-demand printing, electronic distribution of documentation on the Web (in 1995!) and CDs, highly modular content, and so on.
In the mid-90's, on a goof, I applied for a job with Microsoft. I was convinced a friend was pulling a fast one when they called for an interview. A month later I was a full-time, blue-badge Microsoft employee.
Through most of my career at Microsoft I worked as an editor of one sort or another, working on both developer and end-user content. In the early years, I was aligned with the Developer Evangelism team and got to work with a really amazing cross-section of smart, influential people in the software industry. Jeff Richter, Don Box, Aaron Skonnard, Charles Petzold, Mark Russinovich -- the list goes on and on.
For a few years I was part of the user assistance team for one of the big orgs, working on UI, help, SDKs, articles, books -- whatever they threw at us. We shipped some very good products and got a lot of recognition in the form of industry awards. I worked on launching a few companywide internal tools and standards projects that made important contributions to the way we build products and communicate with customers. One is still in active use today, almost 7 years after we started. That's a long time in MSFT years. I'm very proud of that since I was a key contributor from the very beginning.
Hamstrung by Ineffective Management
My career trajectory slowed a bit at Microsoft, in part because I mostly worked on small teams and there simply wasn't room for advancement. Also in part because, during the first few years, I didn't understand how the MSFT review and promotion system worked. The reality is quite a bit different from many people's expectations.
It was clear to me at a certain point that Microsoft had turned the corner. There were still a lot of smart people beavering away on various projects, but they were largely hamstrung by multiple levels of largely ineffective management. Who you knew, or how well you could influence those above you, counted more than results.
There were a ton of bozos. Arrogant bozos. Not to suggest that I'm some sort of genius. Far from it. But the intellectual rigor demonstrated by much of the management -- and strategy -- was sadly lacking. In some ways it was funny, but mostly depressing.
The end of the road came in early 2009. Half of my team was let go in the January layoffs. We scrambled forward with vendors for a few months until the remaining editors were canned in May (me included). Out of a starting staff of nearly 20, four remained, all managers. I'm not sure what they manage.
The End -- a Relief
Some of us saw the end coming. I was working on a post-Microsoft business plan, but had envisioned another 12 months of employment for planning and scraping together a bankroll. In the event, on a Thursday afternoon, a friend and I intuited -- partly from sudden, unnanounced travel status of certain managers -- that the end was much closer. Friday we brought in suitcases and took home our personal items. I used my StayFit allowance to buy a gym membership. Monday we printed out any important personal papers. Tuesday we sat down with our GM and got the news.
In my case it was a relief. I wanted to leave many times over the years -- and in fact did once -- but the salary, the benefits and to be honest the good people, too, kept me there. Devil you know. But I walked out the door that day knowing it was for the best and, though it might take a while, I'd come out of the experience OK.
I spent the summer with my family, relaxing, and taking a wider look around the industry. It was much needed, much appreciated time away from the Microsoft hot house. Thanks to the severance package, unemployment and some careful budgeting, we haven't yet needed to dip into our savings. In the longer term we may need to move somewhere less expensive to reduce our housing costs.
Of my former colleagues, only two of us are now employed fulltime in the industry, though at significantly lower compensation. Another seems to have steady consulting work. Clearly the tech publishing industry (including tech writing/editing) has changed significantly, and probably permanently. I don't think the need for communication experts has vanished, but it remains to be seen how we fit into the changing landscape of the industry.
From six to 13 Management Layers
It's a bit hard to equate the different [Microsoft compensation] level systems over the years, but I basically started at what today would be a level 59 and finished a level 61. That's not much of a bump in a dozen or so years. Assume what you will. I know what went down. I know the value of what my team accomplished (we measured it, with business-relevant, industry-relevant metrics). I know what my contribution was to the team. I am more than satisfied that I pulled my weight and more.
When I started at MSFT in 1996, there were six people between me and Bill Gates. In 2009, there were 13 people between me and Steve Ballmer. My inability to climb the corporate ladder cannot alone explain that away. When layoffs hit my team, only the bottom two layers of the org were affected -- the entire bottom layer of individual contributors (ICs) and two first-level managers. Who's working here?
Ironically, I once wanted to climb up that ladder. But I'm glad it never happened. Through friends, I saw the costs: Huge amounts of additional hassle, not a lot of additional pay, effectively no training or support, unbelievable politics, etc.
On the other hand, MSFT philosophy is up or out. Review depends more on managing perception up the chain of command than actual results. (I tested this theory and it's true. I managed a single set of metrics up the management chain, just spinning the results differently depending on who I talked to and what they cared about. The metrics were useless as the tools they came from were broken. Result = promotion.)
There's little or no interest in sustainability. No recognition for doing a job consistently well over time. No incentive for effective cross-team work (unless you can get another team to do work you can take credit for).
Swimming Against Reward-Driven Culture
Interestingly, [internal] MS Poll results show that the ability to work effectively across teams has been consistently one of the lowest-scoring poll items for over a decade. (Yes, I looked it up.) I've seen managers bend over backward to bring a poll score from 75 percent to 80 percent. I've never seen anyone try to address the cross-team problem.
There are good managers at MSFT. I've seen them. There just aren't very many, and they're swimming against an internally focused, reward-driven culture that puts the highest value on visibility.
It can also be very, very difficult to work in a non-engineering role or organization within an engineering-dominated company. Management focus was just on completely different things than what my teams were doing. Successful or not, it was seen as a distraction. Arguably, good management should be able to multitask, look at the world through different lenses, make situation-specific decisions, strategize in a diverse and complicated world. Realistically, that's a rare set of skills.
Long story short, there were many good and bad experiences over the years. The bad stuff made me stronger and more confident in my abilities. The good stuff is work, friendships, and experience I'm still proud of. I know, for a fact, that we helped people. So that's my story. I remain proud of what I did and [I am] hopeful for the future.

I'm still collecting stories. Please e-mail joewilcox at live dot com. Stories can be anonymous, but I will need to verify identities.

Microsoft Confessions: 'Poor worker bees'

Joe Wilcox — Sun, 07 Feb 2010 01:02:03 -0500

By Joe Wilcox, Betanews

Today's Microsoft Confession comes from a woman let go during the first round of layoffs, in January 2009. I'll call her Amanda, which, of course, isn't her real name. Amanda shared key elements of her story on deep background, but she also provided a reflective portion that she hopes will give deeper insight to anyone looking to work for Microsoft or to HR departments looking to hire former employees.

By telling this story, Amanda wants to give some meaning to her layoff, or so I detected from what she shared for private and public consumption. Amanda's story is consistent with every other I received. She sharply criticizes Microsoft's culture of reorganization, but also emphasizes the heavy workload. I detect deep frustration in her story about Microsoft management problems that won't easily be fixed.

Amanda's story follows two other confessionals -- "Killed over politics" and "Deeply dysfunctional family." As explained on Friday, after the last round of Microsoft layoffs, I asked former employees to tell their stories, which are presented anonymously to diminish risk of repercussions -- either to work elsewhere in the tech industry or to any Microsoft severance arrangement.

I challenge current or former Microsoft employees to either confirm or contradict two key points from Amanda's story: That some Microsoft divisions demand overlong work weeks and that employees who can't keep pace are penalized. From my experience, long hours are standard among many software companies. Does Microsoft demand too much? Current or former employees, please answer the question in comments. With that introduction, Amanda's story:

A lesson and caution to the masses is found in how quickly I went from rising star with a bright future to yesterday's dishwater that couldn't be tossed out quickly enough, without changing how I approached my work! In summary, it was all due to the arrival on the scene -- all praise the holy reorg, which is an approximately annual religious festival in certain sects, I mean divisions, of Microsoft -- of a particular manager...The organizational culture in many parts of MS is such that one manager, even one with a history of their own performance problems, can spell doom for even the most diligent, accomplished, well-intentioned and politically-savvy employee.
The opportunities? [They] can be among the most amazing for your career that you'll ever encounter. This is balanced, however, by the reality that merit isn't always the primary criteria by which opportunities are given out, and that opportunities that are given in the blink of an eye can be -- and sometimes are -- taken away in the blink of an eye for no apparent reason at all.
The culture of the work environment? Let's talk about that, because while people need to know that the culture of working like a dog for 5 years to retire a millionaire is long gone, they also need to know that the culture of working like a dog for 5 years for your regular wages isn't, in some departments.
My former team required 60-90+ hours a week of its employees for several years straight. The average across many weeks was 80-90 [hours], for months on end. If you were unwilling to do the hours any more, you became persona non grata. This meant the least desirable assignments, poor reviews and so on. While the conventional answer to a bad team situation in a big company is to transfer teams, it didn't work for people on that team.
Multiple people on the team wanted to transfer off the team and away from its overtime commitment but management exercised their prerogative to retain them on the team out of urgent business need so that they could not leave. This justification was used to delay their departures 3-6 months, with the effect of causing them to miss the opportunity they'd wanted to pursue [elsewhere in Microsoft] and requring them to continue to do the excessive hours.
Meanwhile, the rest of us poor worker bees had to listen to them complain about the situation until they were allowed to leave. It's not good for morale to be reminded every day that when you get tired of the excessive commitment required by the team, you're likely to be just as trapped, and just as unhappy about it, as your peers are.
In some cases, overassignment of work was used to cause competent employees to appear to be failing at completing their required responsibiltiies. In other cases, people who had not been with the company long enough to be eligible to transfer to another team had to just quit to get out of the unpaid overtime without a permanent black mark in the form of a bad review on their Microsoft record.
Pregnant women ended up on early bedrest from the stress. People slept at the office in order to use the commute time for more work. For some, there were weekly all-nighters in the schedule. A capable contributor on my former team, whose name I know, experienced the indignity of a second-level manager suggesting that they go out on disability if they couldn't handle the stress of the workload, as the manager insisted they should be able to get that workload done in a 40-hour week. Given my background as the longest-term member of the team, including management, I'd call the assertion that that was a 40-hour load shamefully ludicrous to the point of professional negligence.
Anyone in the industry knows about crunch times right before ship. But this was three years of crunch times. After a year had elapsed, the "we don't have the luxury of time to train additional staff to help us get this done" justification for it started to smell kind of bad.
Few teams are like this, but it only takes ending up on one to end your career as a blue badge. It's good for people who are considering Microsoft employment to know. It's also good for people who are considering ex-Microsoft employees for roles in other organizations to know, because among those cut loose are some smart, dedicated, hard workers who were simply asked to do too much, for too long to be able to succeed at it forever in the eyes of the organization -- and who'd be an asset to just about any company in the industry. I know that if I ever, in the future, receive a résumé from someone who left Microsoft during one of the layoff timeframes in 2009, I'll give them the benefit of the doubt.

I'm still collecting stories. Please e-mail joewilcox at live dot com. Stories can be anonymous, but I will need to verify identities.

Microsoft Confessions: 'Deeply dysfunctional family'

Joe Wilcox — Fri, 05 Feb 2010 19:38:15 -0500

By Joe Wilcox, Betanews

The next former Microsoft employee story comes from someone I'll call Fred, which, of course, is not his real name. Fred took a job right out of college and might still work at Microsoft today, if not for the elimination of his group during layoffs last year. Like the former Microsoftie from the first post in this former employee "confession" series, Fred helplessly watched as the exciting and flexible workplace he joined bogged down in increasing layers of middle management.

When Microsoft hired Fred nine years ago, the company employed a little more than 47,000 people. When he was laid off in May 2009, the number was around 93,000. That number is for full-time employees and doesn't include contractors. According to Microsoft's fiscal 2010 10-K, the breakdown on June 30, 2009: "56,000 in the United States and 37,000 internationally. Of the total, 36,000 were in product research and development, 26,000 in sales and marketing, 17,000 in product support and consulting services, 5,000 in manufacturing and distribution, and 9,000 in general and administration."

How many more layers of middle management did Microsoft add when more than doubling headcount during the last decade -- before more than 5,000 layoffs? Fred has an answer for that.

As I explained yesterday, following the last round of Microsoft layoffs, I asked former employees to tell their stories. Responses came from recent departures and others long ago. No identities will be intentionally revealed, although I have verified each one. Fred understands that there is enough detail in his story for Microsoft to possibly identify him. But he is willing to take the risk (and hopefully not risk work elsewhere).

Fred's story is the second posted in this short series running for the next couple days. His account is first-hand, but I will string some other stories together as narrative for better readability and to protect identities.

Something is missing from Fred's story that I would like to encourage some commenters to fill in. Microsoft hiring and compensation follows a scale of levels. While I have some information about the levels and associated salaries, I would prefer some existing or former Microsoft employees pipe in with current salary information for level 63. I ask in hopes of generating discussion. If no one does, I'll later add the information to this introduction or in comments. Four years ago, WashTech News offered an excellent review of Microsoft's complicated compensation system.

Now for Fred's story:

I started with Microsoft in June 2001, right out of college (I received a BS in information technology from Rensselaer Polytechnic Institute). I was hired as a level 59. My first role was with Microsoft Consulting Services as an IT Infrastructure Consultant based in the Mid-Atlantic region of the US. I stayed in that role for four years, traveling around the country (mostly on the East Coast, but with a few exceptions) to help large organizations design/plan/implement Microsoft technology -- mostly Windows desktops, Active Directory and Exchange. My clients included Fortune 100 companies in the retail, financial services, higher education and government sectors. Even a branch of the US military.
In 2005, rather tired of the Monday-Friday travel schedule, I started searching for a new role. That June, I accepted a role in the MSDN & TechNet organization -- the part of the company responsible for communicating with developers and IT professionals. I was a level 61 at that point. Over the following four years, our business grew -- we were reaching millions of IT pros with high levels of customer satisfaction -- the team grew and my role grew as well. The role of the group was really one of audience marketing -- to take a post-sales approach to the dissemination of technical information, with the intent of making the job of IT professionals easier, and hopefully as a result making them more satisfied with Microsoft.
Unfortunately, over the course of reorg after reorg, our group got buried in an IT infrastructure group. We were 15 people doing audience marketing, as part of a larger group of 450 responsible for the Microsoft.com web infrastructure. Our group had proposed a number of times to be moved into a more appropriate organization, like global marketing, that was better aligned with our mission. But our management chain, which grew deeper with every reorg, resisted the idea of giving up headcount or budget.
At the time I was laid off in May 2009, I was a level 63. I had never received anything other than exemplary reviews (I received an "Exceeded" rating in the three consecutive review cycles leading up to the time I left.) The size of the company more than [doubled] in my eight years there. The number of managers between me and the CEO went from six to 10.
Processes became more bureaucratic and individuals were less empowered to take action. In fact, oftentimes the incentive structure encouraged individual contributors not to do the right thing, but just to do what they committed to in their review the year prior. In other words, if you committed to include Feature A in Windows, and half-way through the year you realized that was a bad thing for Windows and Microsoft customers, the incentive structure actively discouraged you from trying to kill the feature, because then you wouldn't have achieved your commitments. That sort of behavior just got easier and more engrained as the organizations grew.
Our entire group was laid off in two rounds. The first half were let go in January [2009]. Their roles were taken up by an outsourcing company based in India. The rest of us were let go four months later, and the remaining operation was outsourced. Four months after that, the majority of our work was dismantled. At the time I was laid off, I was given a choice of accepting a different role within the company, but it would have required my relocation, so I refused. My understanding is that I was the only member of the staff offered that chance (because of my technical background; the rest of the staff was purely marketing).
There's a part of me that can actually understand our group being laid off. An argument could reasonably be made that non-Microsoft employees can be just as effective at fulfilling our mission and could do so at a lower cost (though that's proving to not be true in the aftermath; it was a disaster). Some of the other people I knew around the company who were let go, though, made my jaw drop to the floor. While areas like Search and Zune continued to received astounding resources, areas focused on customer satisfaction and connection, evangelism, and program management were decimated.
One of the better examples where fat ended up cutting muscle, was someone like Steve Riley, who was a noted security expert and one of the best public faces Microsoft had to the IT Pro audience. He was the only person from his group let go. He never had anything other than stellar reviews, and [he] was one of the few people Microsoft had who could pack a ballroom and hold their attention for as long as he wanted. That one really shocked me.
To be honest, as much as I miss many of the individuals I worked with -- and the steady paycheck and benefits, which were always great -- I'm glad to not be a part of Microsoft any more. It bares very little resemblance in my mind to the company I joined 8 years ago. It's hard to describe the atmosphere of excitement and innovation that existed when I first started. But over time, that certainly diminished, seemingly in an inverse relationship to the size of the company.
The company as a whole seemed more and more focused on chasing competitors into any business where they might someday present a threat -- which to me always felt like ego on the part of SteveB [CEO Steve Ballmer]-- and seemed to completely lose sight of its core strengths and where it could deliver the most value to its customers (see the investment in Zune and Live Search as it correlates to Windows Vista).
If I had to sum up my feelings about the whole experience though, it really boils down to sadness and disappointment -- not over the loss of my job, which, for the most part I enjoyed, but am happy to move past, but rather over the failed efforts, missed opportunities and wasted potential of Microsoft as a whole. I've never met so many talented, passionate individuals. But it felt like everyone was part of a deeply dysfunctional family, and in the end, that dynamic trumped what could have been astounding achievements.

I'm still collecting stories. Please e-mail joewilcox at live dot com. Stories can be anonymous, but I will need to verify identity.

Wolfram|Alpha makes a strong argument for virtual keyboards

Tim Conneally — Fri, 05 Feb 2010 19:01:18 -0500

By Tim Conneally, Betanews

I don't keep my personal preference for mobile devices with physical keyboards a secret; the sensation of hitting real keys is an indivisible part of the text entry experience for me, and it's not likely to change any time soon.

But there is one area where physical keyboards are woefully inferior to virtual ones: adaptability. A virtual keyboard can represent any alphabet or be arranged in any configuration the user or software needs, and a physical keyboard simply can't keep up with that.

There is no better example than Wolfram|Alpha's iPhone/iPod Touch app, which now has four full-screen keyboards to accommodate all the various mathematical symbols that it includes in its searches and computations.

Today, Wolfram Research pushed out the 1.1 update to its $49.99 application in the iTunes App Store, which has been redesigned to provide a more useful interface with the "answer engine."

"To determine the optimal keyboard layout, we scoured Wolfram|Alpha's server logs for the most commonly entered phrases that have characters with meaning in Wolfram|Alpha," the team's blog says today. "Given that Wolfram|Alpha is built on Mathematica, one of its core strengths is advanced mathematics. True to form most of the commonly typed characters are related to math."

In addition to the standard keyboard, Wolfram|Alpha includes specialized ones labeled "Math," "Greek," and "Symbol" to simplify the act of querying the app.

"Whether people are converting currency, locating positions of planets, or performing advanced mathematical computations far beyond the capabilities of scientific and graphing calculators, this new functionality provides a natural mobile computation experience," the team said this evening.

DOJ: Google can't leverage class action to settle with future authors

Scott M. Fulton, III — Fri, 05 Feb 2010 17:39:56 -0500

By Scott M. Fulton, III, Betanews

Last September, the US Justice Dept. objected to the proposed terms of a settlement between Google and the Authors' Guild, which would have enabled Google to publish out-of-print titles in its Google Books catalog. The theory of the settlement at the time was, if authors or rights holders are given enough time to respond to a request to stand up for their rights -- say, at least several months -- and they don't do so, then that's as good as acquiescence.

Since that time, on orders of US District Judge Denny Chin, the two disputing groups have worked on a revised settlement. But yesterday, the Justice Dept. -- representing the United States' interests in the matter -- filed a second objection to the settlement. Although Google and the Authors' Guild made progress, US attorneys say, Google still appears to take the position not only that it can strike bargains on behalf of copyright holders, but that only Google can do so -- a position which they say the law does not allow them to take.

"The ASA [amended settlement agreement] suffers from the same core problem as the original agreement: It is an attempt to use the class action mechanism to implement forward-looking business arrangements that go far beyond the dispute before the Court in this litigation," write the attorneys, on behalf of Deputy Assistant Attorney General for Antitrust William Cavanaugh. "As a consequence, the ASA purports to grant legal rights that are difficult to square with the core principle of the Copyright Act that copyright owners generally control whether and how to exploit their works during the term of copyright. Those rights, in turn, confer significant and possibly anticompetitive advantages on a single entity -- Google. Under the ASA as proposed, Google would remain the only competitor in the digital marketplace with the rights to distribute and otherwise exploit a vast array of works in multiple formats. Google also would have the exclusive ability to exploit unclaimed works (including so-called 'orphan works') without risk of liability."

Orphan works were one of the principal problems with the settlement agreement as originally proposed, which attorneys concede was slightly improved upon in the amended form. Originally, Google intended to claim the right to act on behalf of the authors or rights holders of orphan works, unless they spoke up for themselves.

But a kind of Catch-22 managed to unravel the rest of the amended agreement, from the attorneys' perspective: Because Google has never expressed any intent to sell the books it intends to publish -- only make them available for free reading electronically -- it avoided taking any position on the matter of claiming any rights to sell that material. Such a claim, the attorneys concede, "would have been legally indefensible, and thus would have been at odds with Google's entire pre-settlement book search strategy, which was premised upon staying within colorable 'fair use' grounds."

Apparently in an attempt to be thorough, the amended settlement deals explicitly with the same rights Google tried to avoid -- the rights to sell orphan works, among others. And because it does so even though Google didn't intend to, the settlement may fail one of the critical legal tests of any such settlement: specifically, by attempting to settle in the future a claim that Google is not making at present.

But later, the attorneys return to their original claim: that Google is claiming rights it might not have exclusively:

"A core issue that arises out of the parties' effort to resolve this matter is the ability of Google, and no other entity, to compete in a marketplace that the parties seek to create. Nothing in the ASA addresses this concern...There is no serious contention that Google's competitors are likely to obtain comparable rights independently. For example, Amazon -- Google's likely chief rival digital book distributor were the ASA to be approved -- began scanning copyright-protected books in 2002, after first securing permission of the works' rightsholder(s). To date, Amazon has amassed a library of approximately three million digital titles...This impressive number pales in comparison to the tens of millions of books Google has scanned or is poised to scan if the ASA is approved. The suggestion that a competitor should follow Google's lead by copying books en masse without permission in the hope of prompting a class action suit to be settled on terms comparable to the ASA is poor public policy and not something the antitrust laws require a competitor to do."

Another tenet of Google's claim of exclusive rights was the focus of an objection to the amended settlement filed last week by the Free Software Foundation. It's a unique objection, in that the FSF would prefer to not have its due royalties negotiated on its behalf, even if the amount is tallied at zero. Doing so, it claims, would go against the spirit of the free licenses which cover open source documentation and manuals.

"When a copyright holder's license allows Google to distribute and display a work such that it may be included in Google Book Search, Google should be obligated to follow those terms," writes FSF license compliance engineer Brett Smith. "If those terms are unacceptable to Google, the company should simply refrain from including the work in the Google Book Search database. The proposed settlement agreement generally allows Google to include works in Google Book Search unless a specific reason exists to disallow it. The FSF has no objection to this approach for works that have been published under terms that never contemplated inclusion in a large digital database, as is the case with most works in the agreement's scope. However, copyright holders using Free licenses have demonstrably considered such a possibility, and set forth terms for such inclusion. Google should respect the freedoms that these licenses offer to the public and comply with their terms."

Motorola Droid gets its first official multi-touch gesture

Tim Conneally — Fri, 05 Feb 2010 15:40:31 -0500

By Tim Conneally, Betanews

The Droid has gotten pinch-to-zoom in Google Maps.

Immediately after Google introduced the multitouch gesture on the HTC Nexus One browser, photo gallery, and maps applications, owners of the popular Motorola Droid began to ask if their devices would receive the same update, since it is widely known to support multi-touch input.

It looks like Google has delivered...partially, at least.

The update to Google Maps (v.3.4.0) which rolled out this week adds pinch to zoom to the Droid, but is the sole app to do so. Interestingly, it was not advertised with the update.

Devices without multi-touch capability received the same update, but naturally, it did not include the added gesture recognition.

For these devices it is a somewhat mundane update, adding deeper synchronization with the user's Google account. For example, a user's Google searches on the desktop can now affect the location-based suggestions in his mobile queries. Similarly, when a user "stars" a location as a favorite, it is now synchronized with his Google account.

Arguably the most important place to add the feature is in the Browser, but there are currently no updates available to the Droid's browser (or photo gallery, for that matter.)

Original Xbox being phased out of Xbox Live online play, but alternatives exist

Tim Conneally — Fri, 05 Feb 2010 13:16:30 -0500

By Tim Conneally, Betanews

Microsoft today confirmed the long-running rumor that support for the original Xbox will be terminated on the Xbox Live online game servers. The company announced that April 15, 2010 will be the last day legacy Xboxes will be able to play on Xbox Live.

"This isn't a decision we made lightly, but after careful consideration, it is clear this will provide the greatest benefit to the Xbox Live ommunity," Marc Whitten, General Manager of Xbox Live announced today. Whitten noted that Halo 2, a version of the popular first person shooter for the original Xbox still retains a dedicated community of players.

The creators of the Halo franchise, Bungie, have forums dedicated to each version of the game, and users are already begun waxing nostalgic about the "classic" Xbox Live.

One user wrote, "Words don't describe the memories I've had on this title over the past roughly half decade... not just this game, but loads of others as well. I'll tip my hat to just that said fact any day. I'm sad to see the service go, I don't want to see it go, but so be it if it's in the best interest of future engagements for the Xbox Live community."

But there are still alternatives for the most devoted Halo 2 players. Users can connect to online games outside of Xbox Live with XbConnect or Xlink Kai, online game servers which support the legacy consoles, but require them to be connected to a PC.

While neither offer the same level of playability as the Xbox Live version, they will be the only options diehards will have after the April retirement of legacy Xbox Live.

Would you pay to read this?

Carmi Levy — Fri, 05 Feb 2010 13:08:36 -0500

By Carmi Levy, Betanews

Everyone's got an opinion surrounding Engadget's decision to temporarily deactivate user comments because of its editors said things had gotten "mean, ugly, pointless, and frankly threatening in some situations." While I find the reaction to Engadget's decision engaging and often amusing (Betanews reader comments, in particular, often make for fun late night reading) I'm a little surprised at the near-universal lack of understanding of how the Internet works in 2010.

I have three fundamental thoughts on Internet publishing that may help put the Engadget brouhaha in perspective:

Web sites need comments, period. Engagement between publishers and readers is a prime creative lifeblood of the publishing industry. Writers and editors can't do what they do unless they directly understand who's reading them and what they're thinking. Comments are a critical element of this feedback loop, and a site without them rather misses the point.
Trolls happen. It's a given that not everyone likes to play by the rules. Large groups of people, whether they're taking in a baseball game or reading a tech site, cover a wide range of capabilities and motivations. Happily, the most readers choose to be positive contributors to the process, while only a small minority either lack the ability or the will to play nice. The comments section reflects the reality of the human condition, and it won't ever change. Readers can choose to not read, while publishers can choose to ban the trolls. Or, as Engadget decided to do this week, take their ball and go home.
This Internet thing costs money. The rise of the Web over the last 15 years or so has conditioned us into believing that all of this is and should forever be free. The current argument over Engadget's decision to suspend commenting has shed light on the realities of publishing on the Web. As much as we all like to get something for nothing, it takes resources -- money, people, and time -- to launch and run a server, populate it with content, and find ways to convert it into a self-sustaining business. Since readers don't pay the shot, advertisers do. But they'll only pay if there's an audience. Bigger audiences are, of course, better, but numbers are only part of the equation. Quality counts, too, and a site overrun with trolls doesn't just consume the resources of whoever's publishing it. Advertisers balk at paying money to connect with readers who are too focused on flinging the online equivalent of bat guano at each other to ever consider going out and buying what these companies are offering.

With these basic truths in mind, it's clear that Engadget's publishers felt the need to stop the flow of nastiness for a bit while they figured out their next move. We can slice them a new one if we wish, but Engadget's goal is not to make friends with the largest number of commenters. Rather, its entire reason for existence is to sell a particular audience to a particular set of advertisers. And if those advertisers don't feel that either the numbers or the demographic criteria fit their respective business needs, they'll pull their support.

Which brings us to the iPad launch, which delighted the folks who pay the bills because it meant they were delivering their message to a larger-than-usual audience. Apple's announcement gave online publishers a unique opportunity to enjoy higher-than-usual advertising revenues as a direct result of this audience. When big stuff happens in the tech world, people go online to learn about it and decide whether or not it makes sense for their needs. Traffic spikes as newbies and old-timers alike hit the Web looking for information, insight, and guidance. Everything else -- like run-of-the-mill news stories in the wake of the earthquake in Haiti -- gets shunted off to the side as sites do their best to meet demand. And drive it even further.

Is it fair that a touchscreen device trumps the very real drama unfolding in a certain Caribbean nation? No. But no one ever said publishing had to be fair.

Write what's hot, or don't get paid

Which largely explains the all-iPad-all-the-time philosophy that Engadget had followed in the days leading up to Apple's much anticipated announcement. Criticism in the comments notwithstanding, the site was merely reflecting what its readers were asking for -- if not directly, then certainly through their online readership patterns. The site capitalized on a golden opportunity to increase readership and the closely-linked, all-important advertising revenues. Likewise writers, some of whom are paid on a traffic-based formula, focused their efforts on the topic that would return the greatest number of page views.

Speaking for myself, the simple truth is, I typically get lots more page views when I write about Apple than when I write about, say, how social media is helping Haiti's recovery. To wit: My column last week about the iPad prompted 82 comments, as of the time of this writing. My Haiti piece? One. Based on this outcome, where do you think I'm going to focus my efforts in future to maximize reader response and, consequently, advertising value and revenue for my employer? Do you think I'm interested in writing stuff that no one reads? Do you think we'll be able to support a business that doesn't optimize its output for the largest, most desirable audience possible?

As I go through the ongoing process of coming up with topics that I think readers want to read, and that I think advertisers will appreciate, I focus on stuff that's hot and, yes, conversation-generating. If techies are discussing it around the water cooler, I want to write about it. I suppose if I wrote for a site whose readers paid for the privilege, I'd be able to back off the max-the-audience-please-the-advertiser mantra. But until the Web shifts to that model -- and the announcement by The New York Times that it will return to charging for access in 2011 signals a possible change in direction for the industry -- we'll continue to see wall-to-wall coverage of the most in-demand topics.

Because for now, advertisers call the shots. Not readers. And Engadget's decision to kill commenting for now is solid proof that Engadget listened to those who pay the bills before it pulled the plug.

Engadget restored users' commenting ability Thursday afternoon. In a blog post, its editor-in-chief, Joshua Topolsky, wrote, "Making personal attacks against other commenters, publications, or our own editors seriously degrades the community and quality of the discussion, and it won't be tolerated."

Apple asks developer to remove Android mention from App Store

Tim Conneally — Fri, 05 Feb 2010 12:37:21 -0500

By Tim Conneally, Betanews

Apple has asked one mobile app developer to refrain from mentioning Google's Android mobile operating system in its iTunes App store descriptions, or face rejection.

The description of the 99¢ "Flash of Genius" flash card app included the text: "Finalist in Google's Android Developer's Challenge!"

Apple contacted Flash of Genius, LLC and asked it to change the description.

"During our review of your application, we found that your application contains inappropriate or irrelevant platform information in the Application Description and/or Release Notes sections," the message from Apple said.

"Providing future platform compatibility plans or other general platform references are not relevant in the context of the iPhone App Store. While your application has not been rejected, it would be appropriate to remove 'Finalist in Google's Android Developer's Challenge!' from the Application Description," Apple's review team said. (The entire message can be found in Flash of Genius blog.)

Flash of Genius' Tim Novikoff willingly changed the description and said, "I suppose it's logical, and I'm not complaining; Apple is a wonderful company to work with."

Silicon Alley Insider's Jay Yarow agreed with the sentiment today, "It sounds harsh, but makes sense. It doesn't matter if it's a great Android application, this is a different platform."

But is it logical?

Yes, the Android Developer Challenge concerns a different platform, but the nomination still carries weight as an honorific. When an actor is nominated for an Oscar, don't we frequently hear that the actor is an "X-time nominee?" Those nominations were for different roles, so it has no impact on the current nomination, but it speaks to the overall quality of the performer. This is a similar case. The Android platform is different, but when a product excels somewhere, it is worthwhile to let potential buyers know.

For example, on the back of the box of the PlayStation 3 version of Bethesda Softworks' Fallout 3, it says "Best of E3 2008 Winner" for Best RPG. When it got this award, the game did not even exist on PlayStation 3 yet...it was shown on an Xbox 360. Now, it would have been closer to the Flash of Genius situation if "Best Xbox 360 RPG," was printed on the game box, but ultimately, an award is an award and helps the customer actualize the quality of a product.

Microsoft Confessions: 'Killed over politics'

Joe Wilcox — Fri, 05 Feb 2010 03:47:41 -0500

By Joe Wilcox, Betanews

Yesterday's Dick Brass commentary, "Microsoft's Creative Destruction," the company's response to the op-ed and Tuesday's Don Dodge pro-Mac post have put Microsoft in the hot seat. The blogosphere is abuzz about the extent of Microsoft innovations. More former Microsofties are ready to speak out, and they will get their chance here at Betanews.

After the last round of Microsoft layoffs, I asked former employees to tell their stories. I got plenty of responses and not just from people recently leaving the company. No identities will be revealed, although I have verified each one. Two main reasons: Either the former employees still work in the technology industry and don't want to risk their current jobs; or they're receiving severance from Microsoft and don't want to risk losing it. Some of these people have returned to working for Microsoft as contractors, which is another reason to remain anonymous.

Over the next three days, I will present some of the stories in different ways. We start with a first-hand account, and it's more stream-of-conscious than the others I received. Please expect more first-hand accounts and some others strung together as narratives.

What's most surprising about the stories received: Whether they left by will or layoff, most of the former Microsofties worked for the company for a long time, typically no less than eight years. This first account comes from a senior manager who willingly left Microsoft during the last decade after nearly 20 years:

When I left, I told Steve [Ballmer] my reasons. Microsoft [had] lost its competitive edge. Too much politics, too much BS, too much 'what can I do to you today, to make myself look better tomorrow.'
The strength of Microsoft has always been small, heavily empowered teams. Teams that could move fast, make lighting quick decisions and trust the people that made them -- and actually create real schedules, not what management wants you to tell them.
In early 2000, and towards the end of Y2K, the corporate landscape was changing. All the small teams were being eaten up by these uber teams -- complete with politics, backstabbing and posturing. I wanted no part of it. Even today MS is mostly Windows, mobile and Office. Decisions I used to make in 10 minutes, took weeks in Office.
I watched a revolutionary product killed over politics. The moment someone mentioned in a high level-meeting we were better than one of MS's cash cows, I told my [general manager] we were screwed. He didn't believe until the team was disbanded and moved where? Into that cash cow. Where 90 percent of the functionality was cut.
I've watched over the years, [as] poor managers work their way up the ladder, merely because they could play the game. They didn't want the truth, they wanted the answer they wanted to hear.
When Bill Gates first started the 'aggressive schedule' mantra to get people to work harder, [it was] tell folks we only had 2 months left, when we knew it was six. How could I as a manager look my people in the face and seriously tell them we're two months from shipping -- work your ass off -- knowing the bug count was high, the find rate was high and undercover dev work was still being completed?
I finally had enough when my last reorg had me put under a brand new manager, with less weeks experience than I had years doing his job, telling me I wasn't doing my job properly. I asked him how many products he shipped. A couple was the answer. Meanwhile, I had three full Lucite blocks packed with ship-it awards on my desk. At that point, I gave my notice.
How many [Microsoft] reorgs have ever benefited anyone except the folks on top? In all my reorgs, I only ever had one that actually benefited the troops; and that was a super good manager that said if you take me, you take my team. He was one of the best I'd ever worked for -- and, of course, he is no longer at MS either. To me, that speaks volumes.
The people that need to be cut at MS are the managers that don't support their teams and only support their own careers. I've watched countless super visionary managers get bogged in politics and leave.
While I love Steve [Ballmer] to no end, he's too removed from what's really happening, and only gets info from the politically motivated ass kissers that just want to keep their jobs, not do the right thing.

I'm still collecting stories. Please e-mail joewilcox at live dot com. Stories can be anonymous, but I will need to verify identities.