Espaces Grand Ouverts — Translators Wanted

I’ve been relieved by the response to my recent EDUCAUSE Review article on wikis. I was terrified at the prospect of SeriousWikiHeads reading the piece and ripping it to shreds, but so far the feedback has been gentle. Among others, Clay Shirky made a positive reference, and Ross Mayfield wrote up a long and thoughtful post, focusing critique on my handling of anonymity and privacy:

Back when Ward [Cunningham] was an advisor, we had some good discussions about [private wiki spaces], how it was necessary for organizations, and I can tell you it wasn’t outside his vision. I can’t emphasize the obvious enough. That without some privacy for groups, participants can’t share. Similar to how AA members are able to open themselves up to strangers provided they are anonymous to the outside world. Heck, the US wouldn’t exist if anonymity wasn’t provided for contributors to the Federalist Papers.

Chris Allen defines four kinds of privacy: defensive privacy, human-rights privacy, personal privacy, and contextual privacy. For most spaces and cases, the issue for wikis is contextual privacy, or what danah called the ickiness factor when something is socially off-kilter when context shifts.

The point of providing privacy or anonymity may be moot if there isn’t a sustainable solution to online security and trust — thrusting us into a transparent society. But we still have a choice to submit to the always on panopticon.

Of course, privacy comes at an opportunity cost for others to build upon your contributions. Negotiating context shifts over time proves to be the most difficult, socially and even legally, to let resources accrete value. Setting the mission and vision of a space requires a great deal of forward looking imagination while balancing the basic need to define a social context for sharing.

Mayfield notes that though I quote a few of his weblog postings in the article, I never interviewed him directly. I wish I had been able to work through my diffidence and nervousness and approached him — these insights (and doubtless others) would have greatly improved the final result.

But perhaps the most gratifying response has come via Christophe Ducamp. He has gone to the effort to translate the text into French and posted it up on CraoWiki. Merveilleux! Merci beaucoup!

I wish my French was good enough to help out in this respect, but it’s not even close to that level. Christophe is inviting others to make changes or corrections, and if this is something that interests you I’d encourage you to get in touch with him.

This act of unexpected generosity illustrates to me the wonders of sharing content online — it’s not a one-way process from “creator” to “taker”…it’s more like a multi-directional exchange that benefits everyone.

I hope Christophe and anyone else who works on the translation doesn’t feel bound to a literal interpretation of the original text. Taking liberties where needed can only make the piece more readable…

And as Mayfield’s post demonstrates, it’s not as if the English version couldn’t be improved. I wonder if there would be any benefit to posting the article on a wiki and inviting revisions? Or would that just seem like a perverse form of ego-tripping?

About Brian

I am a Strategist and Discoordinator with UBC's Centre for Teaching, Learning and Technology. My main blogging space is Abject Learning, and I sporadically update a short bio with publications and presentations over there as well...
This entry was posted in wikis. Bookmark the permalink.

5 Responses to Espaces Grand Ouverts — Translators Wanted

  1. Sharing it to be built upon would be the opposite of ego tripping!

  2. Seb says:

    Christophe has been translating wiki lore here and there for many many months. He has put incredible energy into it. From what I’ve seen though his translations are quite literal.

    I’m thinking too of putting my future pieces on wikis and indicating from time to time my endorsement of the new revisions. I think it would make sense to license the content as primarily public domain so that contributors can pick up and reuse the content elsewhere.

  3. heather says:

    but, to seb and yourself, can academics looking to publish comfortably collaborate on wikis?

    at some point, it must become difficult if you’re in academia, and making efforts to publish… wiki is a wormhole of copyright problems, and messes with the rules that most academic journals have.

    i had discussions with a lecturer i know, and it basically came down to ‘talk the talk; walk the walk’…

    maybe if they were private wikis, with only certain people invited you’d be able to have them as co-authors, as you would with an academic paper that you sent around for comments?

    but i know very little about this stuff.

    my best experience in learning about wikis came from participating at CommunityWiki and Meatball. It really does feel like barn-raising, they weren’t joking… you put an idea out there, watch it change and grow, evolve without you… and it’s liberating. you realize that you probably don’t own a single thought in your head, and that you could not have had any apparently original thought if it weren’t for the spark from a collaborator.

    but that doesn’t make it very handy when you’re trying to ‘author’ documents, rather than ‘build’.

    hmmm. i wish i put this comment on your wiki.

  4. David Cary says:

    That sounds like an excellent idea. Why don’t you try it and see what happens ?

    I think somewhere on

    “a group of collaboratively editable websites focused on learning and technology.”

    would be appropriate.

    Please tell us (on this page of your blog) exactly where you posted it.

  5. I think you are quite right.

Comments are closed.