Tag Archives: googledocs

Crowdsourcing Alternatives To Delicious

Posted on by

Twitter was abuzz with the news that Yahoo! will be shutting down Delicious, the popular social bookmarking site. Delicious has been a very valuable tool to me for several years now, and I, like others, will be sad to see it go.

However, rather than dwell on the news, it’s better to move on, and find a viable alternative, especially one that will allow the migration of data from a Delicious account to a new host. Rather than trying to find a solution on my own, I thought I would crowdsource an alternative through the sharing of a collaborative Google Document. This crowdsourced approach was very successful back in April when Ning announced their service would no longer be free, so I thought it would be worthwhile to try it again.

I set up the shared Google Doc, shared it, sent out a tweet, and the magic began!

Tweet for Collaboration

In literally seconds, the document began to fill out as people arrived to collaborate or observe. On many occasions, people were booted out as the maximum number of editors had been reached (a number that seems to be around 50 simultaneous users). It was interesting to watch the information emerge. As well, I was fascinated to see others who focused on the formatting and readability of the document. Individuals decided what they could contribute, and worked together for a common goal.

Below is a screencast recorded by Sean Nash of the document as it was being edited minutes after it was tweeted out.

Six hours later, we have hundreds of edits, at least 40 authors (evidenced by the authors that wrote their names on the bottom of the document), and at least sixteen viable alternatives to Delicious with pros/cons listed.

This is a wonderful way to get things done. To me, it’s truly breathtaking to watch and think about what is going on here, and really to consider the geographic distribution of this effort.

However, amazed as I am by what I saw here, this and the Ning example are relatively easy-to-solve problems. I wonder – how well does this kind of crowdsourcing work with deeper, more difficult, or perhaps, more meaningful questions? Thoughts?

You can find the Delicious Alternatives document here.

Google. Where’s Our Doc?

Posted on by

A few days ago, there were several of us on Twitter discussing the possibilities for a new open journal. Twitter is often not great for deep conversations, so following the success of the Ning Alternatives document, I thought I would tweet out a public, real-time Google Doc so people could write and share characteristics of a model, open (academic) journal.

The creation of the document moved quickly, and within minutes, we had several pages of information that helped to outline possibilities and partnerships that would help make this open journal a reality. Off the top of my head, collaborators included (I think): Jon Becker, GNA Garcia, Ira Socol, Jeremy Brueck, Tom Fullerton, George Veletsianos, Cole Camplese & Rob Wall (if you were involved, please let me know). Cole actually took a photo from his iPad while he edited from Twitterfic (see below).

Editing Document with the iPad

But then, all of a sudden, we could no longer access the document. The document now produces the following error:

Google Docs Error
Uploaded with plasq‘s Skitch!

So, I am writing this for a couple of reasons. First, we want this document back, and I’m hoping that someone at Google Docs will actually respond and help us recover it. There does not seem to be a straightforward way of getting Google’s attention, and thus, no easy way to resolve this problem. Second, I am using this as an example as a possible pitfall of depending on cloud computing. What if this was your dissertation? An important grant proposal? That book you’ve been working on? Or a document with some of your most important memories? While in this case, the issue happened so quickly that we didn’t really get a chance to take alternative measures – I hope this prompts you to keep a back up. The cloud can’t be trusted.

In any case, please forward this message along, and hopefully it gets the attention of a Google engineer that can actually do something about this, or get us some answers.

Thanks!

Update: As of May 4, 2010, the document is now working. Thanks everyone who passed this one. On May 3, the issue reached the Product Manager of Google Docs, and the team attacked the problem almost immediately. I received an apology, status reports, and finally, a detailed report of what had happened and how it had been fixed for the future. Overall, I am very satisfied with response I received from Google.