Posts about cloud

La vita cloudy

August 4, 2014 by Jeff Jarvis
, , , , , , , ,

I’ve done it. I’ve moved entirely into the cloud. The process started a year ago when I bought my Chromebook Pixel. Well, actually, it started before that, when I shifted to Gmail and Google Calendar and Google Docs and that drove me to switch from iPhones to and Android phones and tablet and then to try a Chromebook. I still owned a Mac, but it did less and less, in the end just acting as a print server for my Google Cloud Print and as a Skype machine because (1) Microsoft refuses to make Skype for Chrome and (2) Leo Laporte whined about my using Google Hangouts on This Week in Google.

But last week, my Mac died. I/O error. I/O error. OK, OK, I get the point. It’s four or five years old; not worth fixing. It so happens that the moment it died I was trying to set up a Skype talk into a conference in Las Vegas. They couldn’t do Hangouts. So I had to call in on Skype from my Nexus 7 tablet and it worked. Check off one use for the old, dead Mac.

I went through a few false starts trying to check off the other function: printing. I got a Lantronix PrintServer for Google Cloud Print but it still required me to set up printers in Google and that still required having a Mac or PC. I’m using the Lantronix but I also wanted to make this test pure: no other computer required. I got a Brother printer that was alleged to be a Google Cloud Print ready but it wasn’t really. Then I got an Epson and it worked. The Epson has a web set-up I could handle on my Chromebook, arranging to print directly to it with no middleman. It even sends scans directly to my Google Drive.

Ding, dong, my personal computer is dead. I bought my first machine, an Osborne 1, in 1981. I turned off my last one 33 years later. Leo Laporte, Gina Trapani, and I talked about this at some length at the start of This Week in Google. Now Leo’s had some fun at the expense of my Pixel, though he has come around to like his. And so I asked whether for lots of people, we’ve moved past the idea of needing to own a computer that stores data and runs applications locally.

Of course, this move still depends on what you need to do with a computer. I write — in fact, I’ve just written a 55,000-word tome about the future of journalism (betcha can’t wait for that!) using my Chomebook and Google Docs and Drive. I use the web — Chrome, of course. I communicate — everything I could need except Skype. I share. I do basic photo editing. I don’t do rigorous photo or video editing; for that, I’d still need local storage and computing. Gina says she still needs to code locally. OK, but all that, too, could change as connections speed up to gigabit speed and as remote apps and servers continue to gain power over what a personal machine could do.

We also discussed the need for a security blanket: backup. As we chatted, folks in the TWiT chatroom gave us suggestions for local hard drives and for online services such as Backupify that can backup or sync data to another service, such as Dropbox. I’ll work that out next. (In the meantime, I backed up my tome to a thumbdrive.)

So now I live in the cloud. It doesn’t really matter what device I use to get to my stuff: my Chromebook, a computer anywhere with Chrome on it, my Android phone or tablet. I still run apps, but they, like my stuff, will follow me around.

Oh, and by the way, for the first time in decades, I no longer use any Apple or Microsoft products. That’s not because I have anything against either. I just don’t need them.

Welcome to the next era of personal computing without a personal computer.

News(paper) in the cloud

April 12, 2010 by Jeff Jarvis
, ,

I think it’s possible today to run a news organization — up to the point of publishing — from the cloud, changing not only the production process of news but also its culture. John Paton, CEO of Journal Register, is about to prove it with his Ben Franklin Project.

John and I were sitting in my CUNY office as he told me about the technology he’s saddled with at this orphaned newspaper company where he just took the helm. He used a term I swear I hadn’t heard in well more than a decade: “VDT.” That stand for “video display terminal,” the old, dumb box that was wired into newspaper mainframes. I was talking with a bunch of young journalists shortly afterwards and they’d never heard of VDTs (though they thought it could be cured with a shot). Well, Paton still has VDTs.

And so, as he was talking about having to buy new computers, I took to the whiteboard and drew out how I think a news(paper) can be produced from WordPress, Google Docs, and Flickr (or their equivalents). We’ll get to the other functions shortly.

This up-in-the-air production is made possible by Paton’s edict at JRC (as he dictated at ImpreMedia before) that digital comes first, print last. If print comes first, newspaper people will worry about H&J (hyphenation & justification — that is, fitting text to finite holes in print designs). That dictated their process.

But not JRC. By putting print at the end of the line, production for paper won’t dictate the rest of the line. So now a reporter can start blogging at the beginning of a story. And that makes a profound shift in the culture of news: it opens up the process to the public. “Here’s what I think I’ll work on,” the reporter says to the community she covers. “Good idea? Is there something else you think I should do instead? What’s the best use of my time? What do you want me to find out for you? If I do this story, what questions do you have? What do you know? Whom should I call?” As the process continues, the reporter can share what she learns — and doesn’t learn — and the community can help fill in blanks and make the reporting better.

At some point in this process, the reporter likely will write what we’d still recognize as an article. Indeed, writing it before publication opens the possibility of the community still helping by correcting and enhancing.

Then a print editor can grab the story and fit it for print. No longer a big deal.

At the same time, the reporter and editor can ask the community for photos to illustrate the story. They can be shared via Flickr. When it’s time to print, an editor can copy the high-resolution version of an image. If the photographer chooses, he can make the photo available under Creative Commons. If the paper chooses to (as Bild does in Germany), it can pay. That’s up to them. The taking of photos can become competitive: a reader says “I can beat that.”

There are still bureaucratic details that must be handled: schedules of stories, who’s working on what, and so on. Google Docs is perfect for that. My CUNY colleague Jeremy Caplan showed our faculty how much more Docs can do: enabling reporters to, for example, graph data and create their own illustrations. Docs can be used to publish documents to the web.

From these three streams, content can come to a print editor — who is now, remember, at the end of the line — to fill the paper (which my friend and fellow JRC advisor Jay Rosen points out, is the most expensive space). The readers can even help the editor decide what deserves ink.

Note the profound cultural shift this new process brings to a news organization. Rather than doing everything we do and then sharing it with the public — and allowing them to comment on (or snark at) our work — we become transparent, we view news as a process instead of a product, and we open up our process to constructive collaboration with the community we serve. Hallelujah.

The rest of the process of publishing a newspaper is more complicated — at least to me, as I don’t know the tools. I’m not sure all that can be done with free tools but I’ll bet it can all be done in the cloud. At a Salesforce.com event last week, I talked with an exec who said that his service can be used to handle ad order entry. Other systems can handle business tracking, payroll, H&R, and such. I don’t think JRC needs to be dogmatic about living in the cloud but I do think it can avoid huge expense of buying and integrating new systems and hardware.

All this is why I’m delighting in advising JRC and Paton. They are going to try to do the things I’ve been wanting to see news(papers) do — I’ve been writing about this since at least 2005 — the things that tradition and fear prevented other papers from doing. They’re not alone. AnnArbor.com (which I also advised) is entirely on Movable Type. Online news organizations, of course, operate on blogs. But here’s the chance to jump a newspaper company from the past — from the age of VDTs and discs — to the future. I can’t wait to watch and help.