The Cloud Ate My Homework
theodp writes "Over at CNET, James Urquhart sings the praises of cloud computing, encouraging folks to 'really listen to what is being said, understand how the cloud is being used, and seriously evaluate how this disruptive model will change your projects, your organization, and even your career.' Fair enough. Over at the Google Docs Help Forum, some perplexed cloud computing users spent the month of November unsuccessfully trying to figure out why they've been zinged for inappropriate content. Among the items deemed inappropriate and unshareable include notes on Henry David Thoreau ('the published version of this item cannot be shared until a Google review finds that the content is appropriate'), homework assignments, high school yearbook plans, wishlists, documents containing botanical names for plants, a list of websites for an ecommerce class, and a list of companies that rent motorcycles in Canada. When it comes to support in the cloud, it kind of looks like you might get what you pay for."
This is exactly why I never want to move everything "in the cloud", or in to Internet services for that matter. Locally ran applications are there for a reason and things like this wouldn't happen for example with MS Office or Open Office. You're the one controlling your work, not some algorithms that suddenly decide to mark your work "inappropriate". And you don't have to wait for days for someone to answer to your support ticket with a copy-pasted "things to try" list.
Even if you're going for "cloud" services, get a reliable one that states exactly their backup plans and other things. And for gods sake, put out a few dollars for it if you're excepting any level of support or reliability.
Rule #1 of cloud computing: "Do not trust the cloud".
Why is Google even able to review the content? Content should be encrypted.
Ok, I understand that unencrypted content is never guaranteed to be safe, so don't put anything of value in there. But the general assumption people make is that there's just so much stuff in there and most of it is so uninteresting that nobody will probably bother looking at it, unless it happens to show up in debug traces by chance, or something of the sort.
But, "review" suggests somebody at Google *will* look at that content. Imagine that -- some drone at Google will be looking at your private work you want to share only with select people, or company data, and decide (when they get around it) that you can share it after all.
IMO just the possibility of this happening at all makes the whole thing suspect, and could bite you in the ass right in the worst moment. "Sorry boss, I can't share that report because Google thinks there's porn in it. We'll have to wait until somebody at Google looks at it". I'm sure that would make for an interesting day.
Exactly. If the word "cloud" means anything at all, it means that the server is owned and maintained by someone else. Thus "private cloud" is an oxymoron.
The fact that they are using any "filter" at all is a reason never to use the service.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
A technology that ends up dying a risible death, alone and unloved, can, at best, have been touted as a disruptive technology. Actually disruptive technologies have to do some disrupting.