Granular Privacy Control (GPC) [en]

[fr] Google Reader permet maintenant à vos contacts GTalk d'avoir un accès facile à vos "shared items" (articles lus dans votre newsreader et que vous avez partagés). Il semblerait que beaucoup de personnes ont mal interprété cette nouvelle fonction, imaginant que leurs éléments partagés étaient privés, et qu'ils sont maintenant devenus publics. Nous voilà encore une fois face au même problème: l'internaute moyen (et même le pas-si-moyen) surestime complètement à quel point les informations qu'il publie ou partage en ligne sont confidentielles. Au risque de me répéter: internet est un espace public.

Cet incident nous montre aussi, à nouveau, à quel point nous avons besoin de pouvoir structurer de façon fine (Granular Privacy Control = GPC) les accès à nos données à l'intérieur d'un réseau social. Facebook est sur la bonne piste avec ses "listes d'amis", mais on ne peut pas encore les utiliser pour gérer les droits d'accès.

In response to Robert Scoble‘s post about how Google Reader needs to implement finer privacy controls. Let’s see what Robert says, first:

Oh, man, is the Google Reader team under attack for its new social networking features.

There’s a few ways I could take this.

  1. I could call people idiots for not understanding the meaning of the word “public.”
  2. I could call the Google Reader team idiots for not putting GPC into its social networking and sharing features.
  3. I could call the media idiots for not explaining these features better and for even making it sound like stuff that isn’t shared at all is being shared (which absolutely isn’t true).

I’m going to take #2: that the Google Reader team screwed up here and needs to implement GPC as soon as possible. What’s GPC? Granular Privacy Controls.

Here’s how Google screwed up: Google didn’t understand that some users thought that their shared items feeds were private and didn’t know that they were going to be turned totally public. The users who are complaining about this feature assumed that since their feed had a weird URL (here’s mine so you can see that the URL isn’t easy to figure out the way other URLs are) that their feed couldn’t be found by search engines or by people who they didn’t explicitly give the URL to, etc. In other words, that their feed and page would, really, be private, even though it was shared in a public way without a password required or anything like that.

Robert Scoble, Google Reader needs GPC

Wow, I really didn’t think that this feature was going to create trouble. I was personally thrilled to see it implemented. So, here are two thoughts following what Robert wrote:

  • I’ve noticed time and time again that you can tell people something is “public” as much as you like, they still don’t really grasp what “public” means. Because things are not “automatically found” on the internet, they still tend to consider public stuff as being “somewhat private”. This is a general “media education” problem (with adults as much as teenagers). So, Robert is completely right to point this out.
  • GPC is a very important thing we need much more of online (see my SPSN and Ethics and Privacy posts) but I disagree with Robert when he says that Facebook has it. Facebook isn’t there yet, though they are on “the right path”. I can’t yet use my friend lists to decide who gets to see what on my profile. That would truly be GPC (in addition to that, their friends list interface is clunky — I need to blog about it, btw).

BlogTalk 2008 Proposal — Being Multilingual: Blogging in More Than One Language [en]

Here’s the proposal I just sent for BlogTalk 2008 (Cork, Ireland, March 3-4):

The strongest borders online are linguistic. In that respect, people who are comfortable in two languages have a key “bridge” role to play. Blogging is one of the mediums through which this can be done.

Most attempts at bilingual (or multilingual) blogging fall in three patterns:

  • separate and independent blogs, one per language
  • one blog with proper translation of all content, post by post
  • one blog with posts sometimes in one language, sometimes in another

These different strategies and other attempts (like community-driven translation) to use blogging as a means to bridge language barriers are worth examining in closer detail.

Considering that most people do have knowledge (at least passive, even if incomplete) of more than one language, multilingual blogging could be much more common than it is now. The tools we use, however, assume that blogs and web pages are in a single language. Many plugins, however, offer solutions to adapt existing tools like WordPress to the needs of multilingual bloggers. Could we go even further in building tools which encourage multilingualism rather than hindering it?


Extra material:

I’ve gathered pointers to previous talks and writings on the topic here: https://climbtothestars.org/focus/multilingual — most of them are about multilingualism on the internet in general, but this proposal is for a talk much more focused on blogging. Here is a video of the first talk I gave in this series (by far not the best, I’m afraid!) http://video.google.com/videoplay?docid=2096847420084039011 and which was about multilingual blogging — it can give you an idea of what this talk could look like, though I’ve refined my thinking since then and have now fallen in the grips of presentation slides. I also intend to base my talk on real-world examples of what bloggers are doing in the field.

Please don’t hesitate to get in touch if you would like more details for evaluating this proposal.

We had a long discussion on IRC about the fact that the submission process required a 2-page paper for a talk (in all honesty, for me, almost the same amount of sweat and tears as preparing the talk itself — I’ll let you figure that one out yourself). BlogTalk is a conference which aims to bridge the space between academics and practitioners, and a 2-page paper, I understood, was actually a kind of compromise compared to the usual 10-15 page papers academics send in when they want to speak at conferences.

The form was changed, following this discussion, to make the inclusion of the paper optional. Of course, this might reflect badly on proposals like mine or Stowe’s which do not include a paper. We’ll see!

I’ll also be speaking on structured portable social networks during the workshop on social network portability, the day before the conference.