Microsoft finally fusing Yammer-Office 365 sign-on systems

Well, that took longer than expected.

Although Microsoft began bundling Yammer with Office 365 shortly after acquiring the enterprise social networking (ESN) startup in mid-2012, users so far have had to log in separately to both suites, an inconvenience that will soon end. Microsoft will start to roll out single sign on for Office 365 and Yammer next month, and expects to finish by March of next year, the company said Thursday.

Acronis True Image 2015 review: Easy to use, at last

A comprehensive backup solution with local imaging, file and folder backup, online backup and syncing data across all your devices. Now with a friendly interface.  

Having reviewed Acronis’s True Image backup solution multiple times over the last decade or so, I’d given up hope that it would ever sport anything that even approximated a friendly user interface.

Microsoft Movie Creator finally brings needed video features to Windows Phone

In July, we dinged Microsoft’s Video Tuner editing app for Windows Phone because of a lack of video-stitching capabilities. A new beta app, Movie Creator, fixes that shortcoming.

The beta (at present, you’ll need to download the installation file, then sideload it to your phone) seems to provide what the average Windows Phone user wants from a video app: the ability to shoot short clips, import them, combine them via the use of pre-packaged themes, and even add a soundtrack and captions. There’s no limit on the length of the movie, either.

Motorola is winning the Lollipop race, rolling it out to 2nd gen Moto X, Moto G

Second-generation Moto X and G owners rejoice: Android Lollipop is on its way to your phone. Motorola is proclaiming the Pure Edition will be first out of the gate, with other models getting Lollipop once it gets the go-ahead from the carriers. The Moto G already has a release notes page, so that could be hitting your device anytime.

These updates are starting now, but the phased rollout can take time, so it may be a day or two before it hits your device. Either way, you’re still way ahead of your Nexus-using friends, who have yet to get such news even though they probably bought the phone directly from Google.

It also trumps LG, which claimed to be first with Lollipop for the G3, but it hasn’t quite started the rollout yet. It's coming this week, and to be fair, a few days' difference doesn't really matter. Both companies deserve kudos for moving so quickly on the latest Android OS.

Why this matters: Motorola is sticking to its promise to rapidly deliver Android updates. Hopefully these moves are the trickle before a deluge of Lollipop updates, as nearly all major phone manufacturers have promised rapid Android Lollipop updates for their most recent phones.

Source: http://www.pcworld.com

Lenovo Yoga 3 Pro review: A potential Surface Pro 3 killer with a fancy new hinge

It's the thinnest convertible laptop to date with a beautiful screen, and packs Intel's new Core M chip too.

Ahh, how the PC world turns so quickly. A year ago, the industry would have pondered whether the Yoga 3 Pro was a MacBook Air killer. Today, we have to wonder whether Lenovo’s new super-bendable computer is actually a Surface Pro 3 killer.

Facebook gives its server racks a Tesla touch

Matt Corddry, Facebook’s director of hardware engineering, should be grateful to Tesla. Not because he drives one (he doesn’t), but because the popularity of its electric cars could help Facebook take a little more cost out of running its data centers.

Corddry runs Facebook’s hardware engineering lab, which designs the cutting-edge servers, storage gear and other equipment that power its services. It shares those designs with the outside world through the Facebook-led Open Compute Project, and one of the technologies on his mind these days is lithium-ion batteries.

Amazon Lambda bridges functional programming and the cloud

Amazon Web Services intensifies developer push with cloud service leveraging lambda functions

Fresh from unveiling a series of developer tools yesterday, Amazon Web Services today is previewing Amazon Lambda, a new way to build applications and run them in the cloud by leveraging lambda functions.

BlackBerry bolsters its enterprise pitch

Launches partnerships with Samsung, Salesforce, officially releases BES12

BlackBerry announced a renewed enterprise focus on Thursday, including a partnership with Samsung that provides secure mobile software for certain Samsung Android smartphones and tablets.

The software, to be available early next year, will bring together BlackBerry's new BES12 EMM (Enterprise Mobility Management) software with Samsung smartphones and tablets that are embedded with Samsung's Knox security software. Models include the Galaxy S5 and Galaxy Note 4.

Malware doesn't discriminate when it comes to Web ads

Racy or benign, your favorite sites have likely exposed you to malware-laden ads

How likely are you to get hit with malware from an ad, even if you don't surf piracy or porn sites? Not very, but still more likely than you might think.

Microsoft open-sources server-side .Net, launches Visual Studio 2015 preview

In a dramatic shift, Microsoft takes a big step into open source, with the aim of spreading Microsoft development across iOS, Android, OS X, and Linux

Microsoft’s long and contentious relationship with open source reached a major milestone today, when the company announced at its invitation-only Connect() event for developers in New York that it would open-source the entire server-side .Net stack and launch a new open source version of its flagship IDE, dubbed Visual Studio Community. The company also gave a preview of Visual Studio 2015 and .Net 2015.

Complex tools, simple developers: A match made in hell

The developer shortage is coinciding with newer, more complicated tools that most workers can't really use

It is a weird American custom in which asking speakers difficult questions is considered “giving them a hard time,” and I am apparently famous for doing so. At nearly every meetup for event-based, nonblocking, asynchronous programming toolkits such as Node.js and Akka, I ask one question that goes something like, “Have you ever used this on a large team with differing skill levels and gotten the less skilled developers to use it correctly?”

Amazon hasn't quite locked down its encryption key service

Amazon's Key Management Service strives to offer all-in-one key management for enterprises, but right now, it's best for protecting data already in AWS

Key management is an unsung and underrated issue for encryption in enterprises; a poor understanding of it can lead to major problems. A new Amazon Web Services feature, KMS (Key Management Service), intends to reduce the hassle of managing encryption keys for Amazon resources like EBS or S3, as well as for an enterprise's on-premises resources.

Microsoft's Black Tuesday toll: KB 3003743, IE11, EMET 5, and security webcasts

Amid its patching woes, the demise of Microsoft's security webcasts and deployment priority info hits enterprises hard

With 14 security updates that include fixes for 33 separately identified security holes, 14 new nonsecurity patches, two changes to the installers for older security patches, and three changes for older nonsecurity updates, November's Black Tuesday is going down as one of the weightiest ever. But the patches themselves are only part of the story.

In-memory computing brings real-time intelligence to operational systems

In-memory data grids enable instant responses to financial transactions, shopping cart contents, monitoring streams, and other operational data

Operational systems manage our finances, shopping, devices, and much more. Adding real-time analytics to these systems enables them to instantly respond to changing conditions and provide immediate, targeted feedback. This use of analytics is known as operational intelligence, and the need for it is growing fast.

For example, financial trading applications must rapidly respond to fluctuating market conditions as market data flows through trading systems. E-commerce systems must reconcile orders with inventory changes on a second-by-second basis, and they need to quickly respond to shopping behavior to offer personalized recommendations. Smart grid-monitoring systems need to continuously analyze telemetry from many sources to anticipate and respond to unexpected changes in power grids.

Microsoft updates EMET security tool to fix compatibility issues, harden exploit mitigations

EMET 5.1 fixes incompatibilities detected between certain mitigations and popular software programs

Microsoft's Enhanced Mitigation Experience Toolkit (EMET), a security program popular with companies, was updated Monday to harden the exploit mitigations that it adds to other programs and to address compatibility issues with some of them.  

The compatibility issues affected popular applications including Internet Explorer, Adobe Reader, Adobe Flash, and Mozilla Firefox when EMET mitigations like Export Address Table Filtering Plus (EAF+) were applied to them.

Like most EMET mitigations, EAF+ is a set of safeguards and checks designed to block the execution of arbitrary code when memory corruption vulnerabilities are exploited. It was first added in EMET 5.0, released in July.

Functional languages rack up best scores for software quality

A study of GitHub projects and the languages used to build them finds that certain language characteristics are more likely to result in better software

Language design makes a difference in software quality, and functional languages offer an edge when it comes to building quality software, a study of programming languages and code quality in GitHub reveals.  

Researchers at the University of California, Davis, recently published their findings, which were based on an examination of projects hosted on GitHub and the languages used to build them. All told, the researchers studied 729 projects and 80 million lines of code, including project metadata about bugs, covering 17 top languages ranging from C to C++, Java to JavaScript, and Scala to Clojure.

Adobe fixes 18 vulnerabilities in Flash Player

Fifteen of the vulnerabilities addressed in the updates are critical and can result in remote code execution

Adobe Systems released critical security updates Tuesday for Flash Player to address 18 vulnerabilities, many of which can be remotely exploited to compromise underlying systems.

Fifteen of the patched vulnerabilities can result in arbitrary code execution, one can be exploited to disclose session tokens and two allow attackers to escalate their privileges from the low to medium integrity level, Adobe said in a security advisory.

Managing BYOD expenses: How to get it right

BYOD programs haven't always saved money. But, handled correctly, they can

Bring your own device (BYOD) has become an accepted practice in business. Gartner predicts that by 2017, half of all employers will require workers to supply their own devices for work. Yet there are mixed reports about whether BYOD actually saves businesses money.

Okta focuses MDM on users, not devices

Identity-management outfit Okta is prepping a mobile device management solution that puts users first in both its design and licensing

Okta, the identity-management startup created by former Salesforce engineering folks, has sought to make a name for itself by offering a one-stop ID management solution for enterprises turning to cloud-based apps. The company's newest move, though, is into a field that should have no room for a newcomer: mobile device management.

Okta Mobility Management works as an outgrowth of Okta's existing identity platform. With that system, a single user sign-on can be used to access multiple cloud-based applications. Knowing what applications are already used within a company makes it easier for Okta to provision the appropriate mobile apps for users' mobile devices.

Okta CEO Todd McKinnon discussed in a phone call his company's person-centric, rather than device-centric, approach. "When [an enterprise] hires a new employee, and they bring their own phone to work, they want to take the information that's already in the HR system and use that to drive which native apps get provisioned on the mobile device."

To its advantage, Okta knows how existing users have already allowed the software to build a working picture of the company's business processes -- what apps are used where. This information can then be leveraged automatically, along with custom-built deployment rules, when provisioning mobile devices. 

Provisioning isn't only about which features of the phone or what apps can be used, but can include automatic configuration for access to corporate email or other internal resources -- and the automatic de-provisioning of the device when the user leaves the company. Business-specific apps are placed and managed in a container, courtesy of existing OS-level hooks. This is done in lieu of, say, forcing the user to work with custom-built apps, an approach McKinnon describes as "completely broken."

"There's a lot of money going into [enterprise mobility management]," McKinnon said, "and a lot of our [identity management] customers didn't even have a solution, so we think it's still pretty early in this market. We also noticed the ones that had a solution, they hadn't deployed it fully or they weren't that wedded to it, because it's built on an old paradigm where the company would own the device." Many other MDM solutions, he noted, charge per device, whereas Okta is a flat per-user cost.

Okta's solution is reminiscent of an approach suggested by a 2013 Forrester analysis that condemned many of the conventional MDM approaches as "heavy-handed." In their stead, the report predicted, policy-based approaches over apps and data would gain precedence because they are seamless to the user. Much of this development, McKinnon noted, has only become possible because of recent platform-level additions to iOS and Android.

A common barrier for newcomers in a given field is convincing entrenched customers of existing solutions to switch. McKinnon doesn't see Okta making a dent by displacing in-place deployments: "I think we'll have a lot of success in greenfield [deployments]," he said, "where companies want a cloud solution, per-user, and haven't made a choice yet. I think we'll compete with the legacy vendors in some instances, and in some cases they might win and in some cases we'll win -- and in some cases we'll integrate with them."

To that end, Okta isn't competing directly with the likes of Ping Identity, which allows enterprises to use smartphones as an enterprise-wide single-factor authentication device. Nor is the company battling with enterprise app stores for mobile user: "We don't have every bell and whistle of an enterprise app store, but you can imagine we'll enhance it over time." 

Source: http://www.infoworld.com 

RHEL takes up Docker management with Atomic Host

RHEL 7 Atomic Host provides management for both legacy RHEL infrastructure and new container-based applications

How do you take a product that's widely and deeply deployed, and rework it to take advantage of a transformative but also disruptive new technology?

That's the issue Red Hat faces in trying to rework RHEL (Red Hat Enterprise Linux) to use Docker, the software-container tech that transforms most everything it touches. But the latest iteration of RHEL hints at how Red Hat can remake RHEL for containers without alienating its existing customer base. 

The new product, RHEL 7 Atomic Host Beta, appears to be two products in one. On the one hand, it's fully compatible with the existing RHEL 7 distribution, using the same hardware certifications and ecosystem. On the other hand, Red Hat says it also provides "a stable, optimized container host [for Docker] that isolates the container, including its application and dependencies from the host."

This construction is intended to allow "operations and development teams [to] focus on their core strengths," with the former using the original RHEL infrastructure and the latter using containers. Users can either deploy their own containers or opt for the containerized software available through Red Hat's Software Collections.

Clues to Red Hat's former Project Atomic came by way of its recent release of Fedora 21, which demonstrated how the experimental Fedora distribution could be reworked as a container host. Fedora 21 also included a new package-management and rollback system -- the source of the term "atomic" -- that appears in RHEL 7 Atomic Host.

The Docker side of RHEL 7 Atomic Host isn't deployed as a stripped-down mini-distribution like Fedora 21's Cloud version. Instead, the container host is part and parcel of RHEL. Fedora is being used as a proving ground for Red Hat's server technologies, but not necessarily in a one-to-one alignment. Some of the ideas may only show up in a drastically different form, due to the different demands of Fedora and Red Hat users.

RHEL 7 Atomic Host also can serve as a container orchestration platform by way of Google's Kubernetes project. Red Hat states in its press release that Atomic Host "integrates [Kubernetes] into its container stack providing a layer over the infrastructure ... [enabling] enterprises to build composite applications by orchestrating multiple containers as microservices on a single host instance." That is, it'll be easier for a company with an existing investment in Red Hat's technology to adopt containers since RHEL will be the container host -- and security-conscious admins can more easily reinforce protection on containers by way of SELinux.

Red Hat's approach contrasts with that of CoreOS, which built a new breed of Linux distribution using Docker containers as building blocks. For those concentrating on using containers or starting from scratch, CoreOS seems the better deal, since it incorporates very little other than the essentials. By contrast, RHEL 7 Atomic Host is aimed mainly at those who have already worked extensively with Red Hat.

There might be as-yet-undetermined downsides to Red Hat's forays into containers. InfoWorld's Paul Venezia was concerned that the increased emphasis on server (and container) options for Fedora would make the distribution less useful as the desktop and development environment popular with developers. But Red Hat seems confident Atomic Host will be a boon to IT, no matter how Fedora is reworked in the process of bringing Atomic Host to its core -- and paying -- audience. 

Source: http://www.infoworld.com

Office for iOS is a slap in the face for Windows Phone users

iPad, iPhone, and Android users get the excellent Office suite well before Windows Phone users do -- and that's not fair

I’m a Windows Phone user.

I’m not confessing. I’m not apologizing. I love my Windows Phone, and I wouldn’t trade it for an iPhone (my wife’s phone of choice) or an Android (my mother’s phone of choice). I’ve often defended my choice of phone based less on features and apps (iOS and Android have many more apps) and more on the ties to Office 365. As an Office 365 MVP, I need to have the latest and greatest set of tools for Office and for connecting back to Office 365. That’s where I’m starting to get a bit frustrated.

Last week Microsoft announced another wave of enhancements to Office for iPhone and iPad, along with a preview of Office apps for Android. That’s fantastic, but I’m not seeing the same effort going toward making sure the Windows Phone Office apps are enhanced with the same (or better) level of effort. The fact that we don’t have Office apps for Windows at all is equally frustrating.

Granted, some might say, “Well, you have Office for Windows -- why do you want the watered-down apps flavor?” The fact is that a lot of folks don’t need the whole application and would prefer to work through a lightweight app.

In addition, the apps offered for iPhone, iPad, and Android are now available for folks to create and edit content without a subscription. That can't be said for Windows users with an Office 365 subscription. They still need a subscription to get the full Office experience. There is no offered alternative to give them a free option like their iPhone/iPad/Android counterparts now have. It seems off that my wife can run Office for free on her iPad, but all of my four-colored flag devices need subscriptions.

Certainly, Microsoft has to make money. This is a business, I get that. With the number of iOS/Android devices in the market, it's smart to focus dev efforts on non-WP devices with the goal of tying folks more fully into the Microsoft service ecosystem and displacing solutions like Google Apps. I’m fine with that focus, but I don’t feel it should be the company's only -- or even its first -- goal.

I'm not alone. Exchange MVP Paul Robichaux had this to say:

"Microsoft" could solve the Office problem in a couple of ways, depending on what you think "Microsoft" means: The Office team could develop a WP version of Office, or the WP team could subsidize the cost of doing so by providing developers or otherwise covering the cost. If they aren’t doing that, it’s an indication that they feel their money is better spent elsewhere — because we know the WP team has subsidized the development of other major applications.

In my personal opinion, nothing is stopping the WP group from hiring 50 developers and parking them in the Office buildings to do what’s been done for the iOS Office apps. As Robichaux said above, they already have a good track record of throwing money at app developers to get major apps on the platform.

At the same time, Mr. Robichaux, in his use of air quotes, acknowledges part of the problem involves the way Microsoft is currently set up with different fiefdoms battling for supremacy:

When you say "there is no reason Microsoft cannot just…" you have to qualify which "Microsoft" you’re talking about. The Office client team? The Windows Phone team? They have very different priorities and strategies.

Also, we may be seeing a shift in this competitive mentality left over from the days of Bill Gates. New CEO Satya Nadella appears to be working to eliminate the competitiveness and accepting that the buck stops at his door with regard to success or failure. In that sense, Robichaux says, “… if 'Microsoft' means the CEO, then there’s no reason why 'Microsoft' can’t make product group X prioritize work for Windows Phone.”

Looking forward, it's important to say all of this now because new developmental pieces are coming down the wire. With the work occurring in MDM and the Enterprise Mobility Suite, an admin can't help but drool over the potentially cool tools. The suite of cloud services, according to the EMS site, includes Microsoft Azure Active Directory Premium, Microsoft Intune, and Microsoft Azure Rights Management. No doubt we’ll see a variety of tools released on various platforms. I, for one, would prefer all the Windows Phone pieces to sit front and center, but based on what I’m seeing in the dev space for WP I may not get what I want.

We’ll put a pin in this conversation and return at a later time. Hopefully, we’ll see much more from the WP dev team in the near future. I’m a Windows Phone user, and I’m tired of having to explain why. It should be a simple list of bullets that my phone can do that others cannot (yet).

Source: http://www.infoworld.com 

Mozilla offers browser tailor-made for developers

Firefox Developer Edition replaces the Aurora channel and provides access to tools and platform features months before general release

With its Firefox Developer Edition, Mozilla is offering what it calls the first browser specifically built for developers.
Developer Edition offers access to tools and platform features at least 12 weeks before they hit the main release channel, according to the Developer Edition Web page.
The browser is intended to overcome issues developers have had in dealing with different browsers and platforms and browsers, providing a streamlined workflow, said Dave Camp, director of developer tools at Mozilla, in a blog post. "It's a stable developer browser which is not only a powerful authoring tool but also robust enough for everyday browsing," he said. "It also adds new features that simplify the process of building for the entire Web, whether targeting mobile or desktop across many different platforms."
Downloadable from Mozilla's website, Developer Edition replaces the Aurora channel for early adopters in the Firefox release process. It integrates WebIDE and Valence features to improve workflow and debug other browsers and apps, and it includes a JavaScript debugger, style editor, Web audio editor, Web console, and Web page inspector.
No additional plug-ins or applications are needed to debug mobile devices, Camp said, and experienced developers will be familiar with the installed tools.
Developer Edition is to be updated every six weeks. It uses a separate profile from other Firefox versions installed on a developer's machine, enabling developers to run Developer alongside their release or a beta version of the browsers. Default preference values are set up for Web developers.

Source: http://www.infoworld.com 

Obama shows the way on Net neutrality

President Obama comes out swinging for Title II classification of ISPs; the FCC should follow his lead

If you’ve been reading these parts for even a little while, you’re sure to have come across one of my many Net neutrality discussions. As tiresome as it has been to pound on the same podium over and over, it has been necessary — and President Obama’s very public statement asking that Internet service providers be classified under Title II is a major step in the fight for an open Internet.

Of course, no reasonable person would think this fight should have to be fought. Common sense dictates that ISPs are telecom providers and should be held to the same open standards as electricity, phone, and other regulated utilities. The ISPs managed to get the FCC to classify them as "information services" instead of telecom utilities because they offered tokens such as email addresses to their customers alongside their data services, and that has allowed us to get to this point. It's a farce.

The Internet is as much of a utility as any other these days, and we cannot play fast and loose with those rules. Otherwise, we risk everything.

Of course, that didn’t stop Sen. Ted Cruz from coming out with a pants-on-head stupid comment about Net neutrality being "Obamacare for the Internet." Making a statement that amazingly dumb in public would probably have found him signed up for forced sterilization in the 1950s. It’s this kind of blatant, arrogant, willful ignorance that undermines our democracy. But enough about the dim, let’s look at the future.

With Obama very openly supporting Title II classification for carriers, FCC Chairman Tom Wheeler has a very difficult choice ahead. He must jettison either the hordes of ISP lobbying money thrown all around him or the president who appointed him and who has very clearly stated his wishes. It’s not a comfortable spot, but Wheeler arrived here on his own, buoyed by months of equivocation, refusal to participate in public hearings, and horrible “compromises” that weren’t compromises at all. Wheeler's actions will ultimately have a massive impact on the Internet and the United States for decades to come.

If we see carriers classified under Title II, you can expect competition in broadband markets where there hasn’t been competition before. You can expect to see rates go down and speeds go up. You can expect to see more rural areas lit up with actual broadband, not merely enough data to allow for the big ISPs to call it broadband and receive Universal Service Fund money.

The constant threat of ISPs blocking and prioritizing content based on who pays them enough on either end of their pipe will disappear. Data caps will vanish. This is a good thing for all concerned, except for the big ISPs who were salivating at being allowed to be the gatekeepers of the Internet.

Remember, two of those big ISPs are still making motions like they are going to merge into one gigantic disaster of a company, serving a massive portion of the U.S. Internet customers as a monopoly. As I was saying before, the fact that this idea is being entertained at any level is disturbing to the point of seeming like fiction. Yet here we are.

The next month will be hailed as a major crossroads in the history of the Internet and, with it, the history of the world. Decisions made here will have huge technological and financial repercussions across the globe. We are playing games not only with the service that delivers funny cat pictures and "Breaking Bad" episodes to our homes, but with the technology that forms the foundation of huge markets, lifts our economy, and supports millions and millions of jobs. This is a very big deal.

There are those who are ill-equipped with the facts about the need for this reclassification or blithely buy into the straight-up lies coming from those who would sabotage the country to favor their moneyed interests. They are told that this is the government trying to control the Internet, when it is in fact the opposite — it’s the government mandating that nobody controls the Internet and allows anyone to be able to supply Internet services on a level playing field, while maintaining that those services are free and clear of artificial obstruction.

Republicans and conservatives should be falling all over themselves to embrace Net neutrality, not fight it. Unfortunately, the money doesn't want it that way. Instead, it's unleashing geysers of misinformation in order to distort the discussion. The Verge has a pretty good take on this horror of modern politics.

Our electricity is so important that we regulate it this way — same with our telephone network. We need power, we need telephones, and in 2014, we need the Internet. To think otherwise is to defy reason.

Source: http://www.infoworld.com

Cloud storage in iOS 8.1 doesn't work as you expect

Box, Dropbox, and Google Drive all support Apple's cloud storage APIs, but only Box works with direct open and save for files

One of the big changes in iOS 8.1 was support for third-party cloud storage providers, using a new set of APIs in Xcode 6. With the new APIs, apps can directly open files from and save them to cloud storage providers like Box, Dropbox, and Google Drive. Apple implemented the feature in its iWork suite — Pages, Numbers, and Keynote — and in the last few weeks Box, Dropbox, and Google Drive implemented the APIs in their iOS apps.

If you run Box, Dropbox, and/or Google Drive on your iPhone or iPad, you should be able to access those cloud storage services directly from iWork and other apps that support the new cloud file APIs, right? 

Wrong.

If you use any of the iWork apps, you have the ability to enable Box, Dropbox, and Google Drive as supported cloud storage services, but when you actually try to open files, you can only access those on Box.

The issue is that the new iOS 8.1 APIs provide two ways to access cloud storage services, and not all cloud providers have done the work to implement the one that most people would prefer: open and save. Instead, they implement the simpler APIs to import and export.

In fact, of the four major cloud storage providers — Box, Dropbox, Google Drive, and Microsoft OneDrive — only Box supports open and save through the iOS 8.1 APIs. Dropbox and Google Drive support import and export, but not open and save; Microsoft OneDrive supports none of the iOS 8.1 file-management APIs.

The reason is complexity. The import and export APIs handle a simple task: move files into and out of app sandboxes. Remember, iOS apps are sandboxed, so they can't be infected with viruses and the like. That also means the communication with other apps is highly regulated and limited. In fact, until iOS 8.1, the only way to move data to other apps was through the Open In APIs that you typically access via the Share menu to copy that data to the destination app.

The import and export APIs are essentially a variation of Open In, with bidirectional file copying (that is, importing and exporting). They're easy to implement.

The open and save APIs are trickier, as Apple readily admits, because the data is not being copied from one sandbox to another but instead accessed across the sandbox boundaries. The cloud storage app thus has to implement a bevy of services around security and file management to let other apps work with files in the cloud app's sandbox. Apple's APIs enable direct access across sandbox boundaries, but the development work is much trickier. So far, only Box has done the heavy lifting to take advantage of them.

All the major cloud services have their own APIs that developers can use to provide direct file access from other apps (over Internet connections, not through the native cloud storage app). That direct approach is what, for example, Microsoft uses in its recent iOS update to Word, Excel, and PowerPoint to provide Dropbox access. GoodReader has long used that approach in iOS as well. 

Direct access through the provider's open APIs also works with other platforms, so it's a simpler method for developers who want to access cloud storage services from their apps. But it comes with a price: You must have an Internet connection to access files. If you use an iOS cloud storage app as the intermediary, it can store files locally, so you have access to them when offline — the app syncs the versions later when an Internet connection is reestablished.

We'll see if that offline convenience is enough for Dropbox and Google to add support for iOS 8.1's open and save APIs, not just the import and export APIs. (OneDrive is another case: To use the iOS 8.1 cloud access APIs for third parties, you must support Apple's iCloud Drive, which Microsoft has not wanted to do so far for its Office suite.)

App developers also need to follow suit to actually take advantage of the cloud services that do implement the new cloud storage APIs —as far as I can tell, only Apple's iWork suite does so today.

Until then, iOS 8.1's cloud APIs are more useful in theory than in practice.

Source: http://www.infoworld.com

Microsoft courts non-Windows Web developers with RemoteIE

Azure-based RemoteIE lets developers test with Internet Explorer from Windows PCs, Macs, and iOS and Android devices -- for 10 minutes at a time

Microsoft has a big problem. How does it get people to develop for its widely used Web browser, when most Web design and development is done on other platforms? Having learned the lesson of "Built for IE" banners the hard way, it's fighting hard on two fronts: encouraging developers to work with the latest Internet Explorer releases, and moving users away from older browsers.

The Internet Explorer team has been using its modern.ie site to explore ways of encouraging developers to target the latest, HTML5-ready IE. Part of that story is a status page that shows what Web standards are supported and, more important, which are being considered for support. Developers can download virtual machines loaded with browsers, so they can test sites on Mac and Linux, while an experimental tool lets developers run the next IE release on Windows PCs.

That experiment with side-by-side application virtualization has led to the release of RemoteIE, a way of delivering a preview of the next Internet Explorer release from Microsoft's Azure cloud. Accessible from Windows, Mac OS X, iOS, and Android devices, RemoteIE uses Microsoft's Azure RemoteApp to run the browser in a Windows Server VM on Azure, allowing developers to try IE against their test servers from any of these desktop or mobile platforms -- as long as those servers are accessible from the public Internet.

Announced at TechEd back in May, Azure RemoteApp is an answer to the latest iteration of the question, "Why do I need to deliver a full desktop to a tablet or a phone?" By using cloud-hosted VMs to deliver application UIs, there's no need to leave familiar ways of working for the Windows world. The technology has been slipstreamed into the latest versions of the cross-platform Remote Desktop client.

 
With RemoteIE, which is based on Azure RemoteApp, developers can test their Web apps in Internet Explorer by running IE in the Azure cloud.

Does it work? I signed up for the trial, chose an Azure instance close to my home, and waited for the activation email. It took about 15 minutes to arrive – enough time for Microsoft's automated provisioning tools to add an account to a pre-provisioned Azure VM. Using the RemoteApp client to connect to an instance was easy enough, and I could use it from an iPad, an Android tablet, and an iPhone, as well as from a PC. Drilling down into the VM I could see I was sharing it with about 200 other users – keeping Azure resource usage to a minimum.

RemoteIE isn't perfect, with an enforced time limit cutting you off after 10 minutes of idle time or after an hour of using the service. While it's easy enough to log back on, be aware of the 10-minute window if you're trying to debug a complex problem. You also can't use the GPU-acceleration features of the latest IE releases, so it's tricky to use RemoteIE to test WebGL and other GPU-intensive Web technologies.

Using RemoteApp to deliver a browser to developers makes a lot of sense. Microsoft has the scale in Azure to run the necessary VMs, and developers no longer need to worry about the licensing issues associated with running the latest Windows on their development Macs. It's not a complete panacea. RemoteApp only works on the latest versions of Windows Server, so there's no option of delivering older Internet Explorer releases this way – though there's scope for using it with IE10 and IE11, as well as the current developer preview.

While some may complain about the absence of older browsers in the RemoteIE release, this isn't about supporting older releases. It's more about getting rid of them. With IE6 well on the way out, Microsoft is now aiming to get rid of IE7 and IE8 as well. By encouraging high-profile sites to support IE10 and IE11, Redmond hopes to encourage Windows 7 and Windows 8 users to upgrade to these more modern browsers.

Recapturing Web developer mind share is going to be hard, but getting IE back onto the Macintosh desktop – even in this roundabout way – is a start. With RemoteIE, Internet Explorer is a click away, right beside Chrome, Safari, and Firefox – making it as easy to test sites in all browsers, not only one or two. It will be interesting to see what comes next.

Source: http://www.infoworld.com

Why all software needs a license

All software developers should add a copyright license. Why? Because open source licensing is all about granting permission in advance

If you want your code to be open source, it needs an OSI-approved copyright license. Code with no license to the copyright isn't open source.

That may sound basic (and obvious for OSI's president to say), but a surprising number of people disagree. In the last week, I've heard three misunderstandings expressed from across the open source "political" spectrum. Each is dangerous in its own way; together they are a threat to open source. 

Let's take a look at each misinterpretation.

• All software should be public domain. Every restriction is wrong. Adding a license is a restriction. This view has come from developers -- some associated with BSD -- who regard any use of a license as an attempt at unwarranted control. They would rather their code was "public domain," but most now realize that public domain does not make matters clear enough for developers outside the United States, where the concept is different or nonexistent. Falling back to using the BSD license is the least-worst solution. They see "licensing" as an unwelcome imposition on the recipients of their code.
• Anyone who can stop software being open is wrong. This license doesn't stop that proprietary use, so it's bad. This view has come from developers -- generally users of the GPL family of licenses -- who believe all code that starts out open source should always remain open source. They see licenses that allow others to take open source code and make it hidden and proprietary as wrong, and prefer licenses that require republication of source code. As such, they reject any licenses that aren't strong copyleft.
• When it's code that makes things, the result can't be copyrighted. Adding a license is overreach. This view arose in a conversation between lawyers talking about 3D printing. They saw applying a copyright license to source code used by a printer as a claim of ownership. As one correspondent wrote to me: "Chutzpah! We shouldn't overreach with copyright claims and put licenses on everything in sight."

All of these statements come from looking through the wrong end of the telescope. In open source, we "put licenses on everything in sight" not because we want to claim ownership but rather to give permission in advance. When the day arrives that someone becomes concerned about the existence of a copyright claim, there will already be a positive response. We go to great efforts to do so, though many regard it as obstructive bureaucracy.

Many would prefer to simply say their code is "public domain," but the concept is not recognized worldwide. That leaves doubts about sufficient permission-in-advance for some collaborators. We take these steps to guarantee the freedom to innovate without seeking permission first.

Seen through the lens of "granting permission in advance," the distance between the BSD license at one extreme and the GPL at the other does not seem so large. Both seek to set unknown future innovators and collaborators free to innovate by granting permission to use and change the code any way they want -- to everyone. Neither is seeking to claim ownership or restrict use according to their worldview, even if those worldviews differ on the nature of causality. I'm happy to respect their ideological differences and celebrate their shared intent to grant permission in advance.

All OSI-approved licenses grant permission to deploy code for any purpose without restriction, as well as to read, study, and improve the code and to pass it on to others. All those permissions are given in advance; no OSI-approved license withholds them. That's what OSI's work of the last 15 years has delivered -- a guarantee that "the four freedoms" are embodied in approved licenses so that you can simply go ahead and use the code if you see one.

Practitioners of other disciplines related to open source -- open hardware, 3D printing, and so on -- take a similar approach. They apply copyright licenses to their designs not necessarily to assert claims of copyright ownership or to limit the actions of any party, but so that their downstream collaborators are freed from concerns about the legality of their actions. Open source licensing is not about forcing others into your worldview; it's about giving permission in advance to others to create the greatest freedom to innovate. Applying an open source license is a work-around to counter the expected greed of others. 

Those over-reaching are not the developers who want to remove barriers to collaboration -- it's those whose expected behavior is to claim maximum rights in all cases. In the case of open hardware and the Internet of things, it seems rash to claim certainty about the ineligibility of copyright where the "object code" is hardware. The lack of involvement of humans in the generation of the source files is a leap, one I'd expect corporate counsel to be able to challenge in court -- silicon fabricators copyright the source files to their chip designs, for example.

Yes, a whole industry revolves around pursuing conformance breaches and using copyright law to suck money out of victims. But applying an open source license does far more to fix that than either leaving the license off (otherwise known as "reserving all rights") or using a proprietary license (the notorious EULA).

Society depends on a rich and deep commons of reusable culture, technology, and ideas. Innovation is rarely creatio ex nihilo but rather, as Newton is supposed to have commented, the act of "standing on the shoulders of giants." Innovators see new ways with old ideas; they envisage solutions to old problems framed by existing craft. Even the greatest of art exists framed in the context of its contemporaries and predecessors.

If we place the commons off-limits, by doing so we also ban most innovation and art and put the brakes on progress. If we want to see innovation in the emerging, meshed society, applying copyright licenses to source files is a necessary prophylactic, not a land-grab. Granting permission in advance so innovators can work their magic freely is grace, not chutzpah. 

Source: http://www.infoworld.com 

Red Hat confuses Linux users with latest Fedora moves

Fedora for servers? Red Hat's copious new Fedora community options seem odd at best

If nothing else, Red Hat has been extremely busy over the past year. Whether or not all of the activity will be good for Linux remains in question. 

Since 2013, we’ve seen Red Hat embrace CentOS, the previously community-supported, open source equivalent of Red Hat Enterprise Linux, and we’ve seen the release of RHEL 7 and its hard push to systemd exclusivity. Now we’re seeing the new road map for Fedora, which will come in three different flavors with Fedora 21. These are all major steps in a very short time period, and frankly, some of these moves seem awkward at best. 

Starting with Red Hat's embrace of CentOS, I'm of the mind this is ultimately a good development, if also inevitable. CentOS is widely used for Linux servers of every conceivable type, from tiny VPSes to big physical boxes. Often it can be found accompanying RHEL installations in the same infrastructures. Savvy groups use RHEL when and where they need Red Hat support, and CentOS for everything else, such as dev environments, noncritical systems, and so on. Even savvier groups eschew RHEL altogether and use only CentOS because they don’t need the support. This is how big server back ends have been built and operated for years now.

Then there’s Fedora and the recent announcement that it will henceforth ship in workstation, cloud, and server versions. Fedora has been Red Hat’s unstable proving ground for many years, offering a far faster refresh cycle and package inclusion at the expense of stability and compatibility. It is and always has been a sandbox distro. It’s also well known as a desktop distribution, competing with Ubuntu, Debian, Mint, and other desktop-centric distributions. For Linux desktop users who also run RHEL or CentOS, opting for Fedora is a natural move; the underlying architectures are very similar, unlike Debian-based distributions.

That’s where Fedora stays: as a desktop and dev sandbox. It has never been seriously considered as a production server operating system. The workstation focus seems obvious, as it's historically been a Fedora strength.

But with Red Hat announcing that Fedora will be offered in workstation, cloud, and server flavors, I have to wonder about the ultimate goal. Does Red Hat want Fedora to eclipse CentOS as the favored RHEL-like community server distribution? Is Red Hat aiming Fedora Server at small-business workloads? Why a cloud version? Most folks building out cloud server architectures definitely do not want unstable packages floating around, and the idea of using Fedora for production cloud workloads is highly questionable at best.

Given these three splits in Fedora — complete with a bunch of GUI-driven, small-business-level system and server management tools on the server version — Red Hat seems to be trying to appeal to everyone and everything, while lacking focus on any single strength. The bedrock of Red Hat has always been on the server side, with sufficient success to necessitate the creation and maintenance of CentOS by the server community. Supporting Fedora and having several different options is not a bad idea, but too many, aimed in so many directions, can negatively affect the brand.

Linux users are in a twist right now. We're facing significant changes within the mainstream commercial and community distros themselves, on top of dealing with the rapidly growing container frameworks, virtualization, and cloud services, all of which can run on one form of Linux or another.

Further, a significant number of Linux use cases don’t require what we think of as a Linux distribution. We’re moving away from the kitchen-sink approach with Linux servers, where every package that can be available is available, heading straight into specialized, purpose-built, minimal server instances that appear and disappear as loads dictate. There’s not a lot of room for either a general-purpose server or a desktop-centric distribution.

Perhaps that’s Red Hat’s goal — throw it all out there and see where things wind up. RHEL isn’t going away anytime soon, but if we are going to witness an uptick in Linux desktop usage, it could as easily be Fedora as any other, especially in the context of developer adoption. On the cloud front, I think we’re still missing the right solution for the next few years of cloud computing, and Fedora for cloud services will likely be a nonstarter.

I expect Linux server philosophy will undergo many changes in the next few years, along with gains made by distribution angles similar to CoreOS. This leads me to the most interesting piece of the Fedora announcement — the fact that apparently the working groups for each new Fedora flavor can make architectural decisions that do not impact the other flavors.

This means that the cloud or server group could decide to abandon desktop packages altogether and release a truly server-only distro, effectively eliminating all kinds of stability issues that might be caused by the inclusion of hundreds of desktop packages. That might be a compelling reason to look at Fedora for real server work, depending on how it's managed. It's an interesting speculation, to say the least. 

Source: http://www.infoworld.com

Why CoreOS is a game-changer in the data center and cloud

Offering Linux as a service, CoreOS has become the preferred distro for Docker -- and may go a long way toward making data centers more cloudlike

We're all accustomed to software updating itself. Windows has been pushing out auto-updates for more than a decade. Then browsers did it, then other client-side applications.

But server software? Servers are another story, particularly Linux servers. 

That's because we've treated servers like pets. We’ve carefully tended them and invested in redundant power supplies and so on -- anything to keep them up and running until we absolutely need to take them down. In the Linux and Unix world, a reboot has been an admission of defeat, and OS upgrades have been rolled out as part of a careful plan.

But today, in the cloud era, we’re starting to treat servers like cows: If one falls over, that's part of the business. Cloud architecture distributes applications and replicates data across many commodity servers, so you can pull the plug on one and everything still keeps running.

This tectonic shift in the way we view server infrastructure led Alex Polvi, CEO of the startup CoreOS, to a realization: If servers can go offline temporarily, that means you can push an OS update to them and reboot them without ruffling any feathers.

In essence, Polvi thought, this little downtime window would enable him to deliver a Linux operating system as a service.

Polvi derived the idea in part from observations of the browser world. When Google Chrome arrived, it automatically updated itself without the user's knowledge or permission, vastly accelerating security patching and feature additions. As Polvi puts it: "Over a relatively short period of time Chrome can move the whole Internet forward."

If you can do that to the front end of the Internet, why not the back end?

 

Docker to the rescue

As any horrified admin might tell you, the obvious argument against auto-updating a server OS is the unpredictable effect it might have on server applications.

Here's where Polvi got extraordinarily lucky: “We started working on this in about February 2013, right around when the Docker guys started working on their stuff.” Docker enables you to package applications and deploy them in Linux containers, a form of application virtualization. Containers isolate applications from the OS; if an element in the base changes, it doesn’t break all your applications.

But aren’t containers simply a feature of the Linux kernel? Here’s Polvi’s reply:

We shipped our first version in August 2013 and included Docker because we need containers to do what we do, so the momentum coming out of Docker created awareness of this whole ecosystem. From the very beginning, there’s been a CoreOS/Docker story going on: Two parts that merged somewhat serendipitously, but they’re both very complementary to one another.

In contrast to other Linux distros, which pile on features for admins, CoreOS is bare bones by design. CoreOS doesn’t even have versions: You decide whether your servers get updates through the Alpha, Beta, or Stable “channels.” The Alpha channel pushes out the absolute latest version; as Polvi notes, the Alpha channel pushed out Docker 1.3 two hours after it was in release. Beta and Stable are by turns further behind, but less likely to experience a glitch.

In creating a server OS that updates itself, Polvi says he’s constructed CoreOS around double-buffered updates so his service can atomically transition versions easily and roll back if there’s a failure.

You can see why InfoWorld contributor Matt Asay has called CoreOS an existential threat to conventional Linux distros: It completely commoditizes Linux. More than that, says Polvi:

We think we can make the OS effectively irrelevant. I mean, if it’s all auto-updating and takes care of itself, you shouldn’t have to worry about it anymore. CoreOS as an organization is maintaining it for you and you just worry about your application side. And we do it wherever you want it: On cloud, on bare metal, on your laptop. Don’t worry about it. Just focus on running applications.

Red Hat responded to the CoreOS threat by announcing in April that it would release Project Atomic, its own stripped-down, auto-updating distro. Not surprisingly, Polvi sees this as validation of his model.

The cloud computing proposition at its essence is an effort to vastly simplify the management of infrastructure -- but building so-called private clouds turned out to be very difficult. In offering Linux as a service and baking in Docker containers, CoreOS has gone a long way toward making data centers more cloudlike. 

Source: http://www.infoworld.com 

Device loss, not hacking, poses greatest risk to health care data

California DOJ report on data breaches shows most losses in health care revolve around stolen devices, due to weak use of encryption

If you're dealing with the security of a health care provider, hacking isn't your biggest worry, but rather the loss of devices storing your data. Lack of encryption on devices plus the value of stolen health care data combine to make for tempting targets.

The October 2014 California Data Breach Report, compiled by the California Department of Justice, analyzed data breaches across multiple industry sectors in California for the year 2013. Of all the industries profiled, two stood out with the greatest share of losses for a given type of breach. One was retail, where 88 percent of the losses came by way of malware or hacking, as opposed to physical thefts, misuse, or human error. (The largest share of losses in government, by the way, were human error -- 48 percent of the sector's total.)

But with health care, more than two-thirds of the losses -- 70 percent -- were attributable to physical theft, which the report defines as "lost or stolen hardware or portable media containing unencrypted data."

Bitglass, a security vendor that provides data-sanitization solutions, crunched Health and Human Services data to come up with similar figures. In health care, the company found, only 23 percent of data breaches since 2010 were hack-related; the rest were through "loss or theft of employee mobile devices with information on them."

Other sectors showed different breakdowns in the California report. The hospitality industry, for instance, was the second-largest vertical where malware/hacking was a source of breaches (58 percent of all incidents reported), and human error was attributed to almost half of the breaches in government and a third of the breaches in education.

  California Department of Justice

Data breaches in California for 2013, by industry and breach type. Health care's large number of physical breaches has been attributed to the theft or loss of devices that are mainly unencrypted.

But health care came in as the biggest source of physical breaches -- 40 percent -- among all industry types surveyed, with the vast majority coming from stolen hardware, both desktops and notebooks alike, and missing media, such a disks or USB drives. (Mobile devices were not implicated.)

The larger question is why health care providers are such vigorous targets for physical theft. Bitglass CEO Nat Kausik believes the answer lies in how effectively the stolen data can be monetized.

According to other research seen by Kausik, most stolen credit card numbers -- the type of data typically filched in a retail hack -- are worth only "50 cents or a dollar each" on the black market, in big part because credit card numbers can be invalidated and charges made on them can be reversed.

"But health care records are worth something like $50 each," he said in a phone interview, "because you actually get the person's identity. You can't really change a Social Security number, and that has lasting value to the thief."

To that end, as the California report noted, about 50 percent the time during any breach, the theft of a Social Security number was involved, with payment card thefts taking place in about 40 percent of the breaches.

Another complicating factor is the inconsistent mitigation of the loss or theft of Social Security numbers. The California report found that "in 29 percent of breaches of Social Security or driver's license numbers, where a mitigation service such as credit monitoring or a security freeze would have been helpful, the breached entity failed to offer such a service."

In a list of 12 recommendations to all industries, the California report said health care providers in particular "consistently use strong encryption to protect medical information on laptops and on other portable devices and should consider it for desktop computers."

Drive makers have stumped for full-disk encryption being less expensive and difficult to implement, with the costs being negligible and the encryption itself typically invisible to the end user. In an earlier 2013 California breach report (which covered data breaches in 2012), California Attorney General Kamala Harris warned that she "will make it an enforcement priority to investigate breaches involving unencrypted personal information," putting pressure on businesses -- regardless of their sector or vertical -- to encrypt or else.

Source: http://www.infoworld.com

Tech believes children are the future

Teach them well and let them lead the way, then throw them six-figure startup sums. Meet the baby Einsteins who make Zuckerberg look old

What were you doing when you were 13? I was busy discovering that girls weren’t disgusting after all, which led to a new appreciation for a locked bathroom door. Then there was the Dungeons & Dragons monkey that would ride my back for the next decade, an addiction fed by all the paperbacks in the fantasy and science-fiction section, as well as 10+ visits to the cineplex devoted solely to memorizing "Star Wars" and giving my Dad migraines.  

In other words, I belly-flopped into the deep end of Nerd World and pre-college celibacy. What wasn’t I doing? Raising funds for my first commercial venture, for starters.

Unlike Shubham Banerjee, the teenager who took in an undisclosed six-figure infusion from Intel’s VC arm to back the startup he founded using $35,000 from his mom and a big box of Lego. Worst of all, I can't even ding Intel for yet another blindingly stupid Silicon Valley-style money bath.

 

The youth brigade

Banerjee’s venture consists of a low-cost Braille printer, not a useless viral phone pollution that sends “yo” messages back and forth. He expects to eventually sell the prototype he built out of -- no kidding -- a Lego variant for about $350. That’s a double-scoop of cost-effectiveness when compared to most current Braille printers, which can run as high as $4,000. Intel surprised the kid with its support because he was working to incorporate the company's Edison chip into his invention.

It makes you wonder why Microsoft isn’t showering Pakistani Briton Ayan Qureshi with money now that he’s become the youngest Microsoft Certified professional ever, with another month to go before his sixth birthday. It also makes you wonder why Microsoft Learning hasn’t published a line of pop-up books entitled "How to Pass Our Oh-So-Challenging Exams if You’re Too Young to Read."

If I were still living with Pammy, I could expect another skillet-shaped dent in my forehead and a “Slacker” tattoo on my left buttock (once I regained consciousness) in response to this news. Then again, Silicon Valley and the tech industry in general have always bowed to the mythical genius of youth, due in part to tyke-turned-tycoons like the Zuck, who was once quoted as saying, “Young people are just smarter.” I'm sure a legion of AARP members would have a word or two for him, if only we could remember where we put our reading glasses.

Although I’m pretty sure 12 has to be a new funding record, it’s not surprising with financial freaks like Zuck setting the MegaPowerballLotto VC success standard. Based on that trend, my wrinkled behind is locked out of any self-respecting VC’s office permanently. On the other hand, this VC pederasty has also resulted in big chunks of our economy going down the flusher, thanks to disasters like Crinkle, Blippy, BricaBox, and LivingSocial, as well as demon-worshipping arrogance factories like Sean Rad or Jonathan Mills.

At least the aging techie demographic won't be alone in being usurped by a never-ending line of tweeners. President Obama should be sweating, too, now that Saira Blair entered the political game this past Tuesday at the tender age of 18 as a fiscally conservative Republican with an NRA endorsement and gleeful support from the antiabortion set. She’s in the West Virginia state senate for now, but once the Zuck backs her as part of his Old People Suck initiative, she’ll surely be going for the White House in 2034. Elise Stefanik and Tom Cotton also made political news as the youngest knife fighters ever elected to Congress and the Senate, respectively, but they’re both over 30, so they probably didn’t make Zuckie’s radar.

 

Help the aged

I could cite other examples of ageism in sports, entertainment, fashion, and weed farming, but I’m only redundant on the weekends. The trend gives new meaning to Amber Alert, and it’s very clear: Kids are worshipped no matter how great or ridiculous their startups might be, while old farts like me will soon be placed into barrels of amniotic fluid and launched into space to make room for an even younger generation of VC dazzlers.

I’d protest, but I’m too tired and I might miss the senior's dinner discount at Applebee's. Go ahead and launch me into space. I’m OK with it as long as Pammy’s skillet stays on earth and someone promises to beam me a YouTube video of Zuckerberg’s expression the day Facebook gets flattened by a middle-schooler’s social networking epiphany. 

Source: http://www.infoworld.com