I feel like I'm not the only researcher circling Facebook like a vulture, anxiously awaiting its grand fall to see what will happen and what brings it about and how users deal with the mass exodus. That's going to make a great conference some day.<br>
<br>But the QWERTY example is an interesting one, since, I think, we are beginning to see a shift away from it already. As texting becomes more and more prominent, large numbers of people are learning to type using the cell phone keyboard + T9 in addition to texting, which is certainly as radically different from QWERTY as Dvorak. In this example and in that of the shift from typewriter to word processor, it seems that the essential catalyst for such drastic changes is the introduction of a "new" system: while Dvorak is seen as simply an alternative to QWERTY, cell phones and their crazy keyboards offer a functionality (portability) that normal laptops don't offer. Of course, with the iPhone and whatnot, QWERTY is definitely making a comeback in the mobile device world, but it'll be interesting to see how this plays out...<br>
<br>P.S. Hi Chris!<br><br><br><div class="gmail_quote">On Thu, Dec 4, 2008 at 4:49 PM, Christopher Kelty <span dir="ltr"><<a href="mailto:ckelty@gmail.com">ckelty@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Frank,<br>
<br>
This language of exit, voice and loyalty (All Hail Albert Hirschman!)<br>
is in the background of my thinking, and one way to think about why<br>
the public sphere is the appropriate concept here is that it can be<br>
compared with Hirschman's corporation. The structure of that choice<br>
(exit voice or loyalty) is different in a corporation than it is for a<br>
sovereign people, who may or may not take the form of an organization.<br>
<br>
there is another crypto-economic notion that makes sense of your<br>
observation here, which is the notion of path-dependency, which got a<br>
lot of play in the 1990s, and which is often used to make claims about<br>
the advantages of standardization in technology (QWERTY being the<br>
canonical object lesson). In terms of exit, then, it may ultimately<br>
become very difficult for an entire group to exit from something like<br>
Linux (to say nothing of something like Facebook) because of path<br>
dependency. However, Charles Sabel once had a very nice counter<br>
example, which is that even though we are all locked-in to the QWERTY<br>
keyboard, we somehow engaged in a massive conversion from typewriters<br>
to word processing software, arguably a bigger and more expensive<br>
shift than converting to a new keyboard layout. The lesson therefore,<br>
is that depending on the cultural value of the difference between the<br>
options, some kinds of exit are more likely than others... the danger<br>
that free software recursive publics try to guard against is that of<br>
simply maintaining a meaninful technical and legal possibility for<br>
exit, even if no one chooses to go there...<br>
<font color="#888888"><br>
ck<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
On Tue, Dec 2, 2008 at 6:28 AM, Frank Pasquale <<a href="mailto:frank.pasquale@gmail.com">frank.pasquale@gmail.com</a>> wrote:<br>
> Your points about moving from a "privacy-protecting" paradigm to a<br>
> "publicity promoting" one are very important. People using these new<br>
> technologies need to recognize a basic asymmetry of information: as many<br>
> proprietary software providers accumulate more and more data on individuals,<br>
> their own uses of that data become increasingly opaque due to trade secrecy<br>
> protections.<br>
><br>
> One solution would be to make individual privacy as protectible as corporate<br>
> trade secrecy. But the "fast capitalism" of a neoliberal order makes it<br>
> almost impossible for anyone with a job and family to take the time to<br>
> meticulously tend a garden of privacy and fend off myriad marketers' coaxing<br>
> and cajoling. The privacy problem has to be assimilated into a larger<br>
> public debate on how to regulate projects like 23andMe so they serve public<br>
> ends.<br>
><br>
> You've asked "why are all these versions of openness, sociality,<br>
> distributedness and so forth<br>
> considered good?" Let me try a response, based on some of your ideas on the<br>
> recursive public, which you've defined as "a public that is vitally<br>
> concerned with the material and practical maintenance and modification of<br>
> the technical, legal, practical, and conceptual means of its own existence<br>
> as a public."<br>
><br>
> Several scholars have recognize the importance of "groups" in social<br>
> software, but the term "public" appears both more expansive and more<br>
> political than the idea of a group. It reminds me of Habermas's work on The<br>
> Structural Transformation of the Public Sphere, which focused on the ways in<br>
> which new communication technology affected the self-organization and<br>
> recognition of new spaces of contestation in politics. Habermas's story is<br>
> largely one of missed opportunities, where the extraordinary technologies of<br>
> broadcasting and radio gradually fall into the hands of commercial interests<br>
> more interested in cultivating consumerism than creative citizenship.<br>
><br>
> Later reflections by Habermas (and works ranging from Ithiel de la Sola<br>
> Pool's to Benkler's) have been more optimistic about communication<br>
> technologies. The main justification for optimism has been the prevalence of<br>
> "exit" options–for example, if the software company enabling your group gets<br>
> too bossy or prying or commercial, you can always jump ship and try another.<br>
><br>
> But the difficulty of getting your entire group to switch may be the biggest<br>
> challenge to such exit options. To the extent the group is outwardly<br>
> directed, it pays for it to ignore "hiccups" (which can gradually accrete<br>
> into massive invasions of privacy and limits on corporate transparency) and<br>
> simply "muddle along" using existing the technology it's always used.<br>
> Kelty's work reminds us that, even as new technologies amplify "voice" by<br>
> allowing millions to connect, we may just be trading old masters for new<br>
> ones if we fail to demand voice. Their massiveness is almost dictated by the<br>
> laws of what David Grewal calls network power, so exit is not a scalable<br>
> solution.<br>
><br>
> PS: links at<br>
> <a href="http://madisonian.net/2008/12/02/the-structural-transformation-of-the-recursive-public-sphere/" target="_blank">http://madisonian.net/2008/12/02/the-structural-transformation-of-the-recursive-public-sphere/</a><br>
><br>
> On Mon, Dec 1, 2008 at 6:05 PM, Christopher Kelty <<a href="mailto:ckelty@gmail.com">ckelty@gmail.com</a>> wrote:<br>
>><br>
>> Trebor asked me to introduce myseflf to this list, which i'm very<br>
>> happy to do since it includes lo ts of people whose work I know and<br>
>> respect and a few people I know personally. For those who don't know<br>
>> me, I am trained in anthropology and history (science and technology<br>
>> studies, more specifically), and I wrote a book about Free Software<br>
>> called /Two Bits: The Cultural Significance of Free Software/<br>
>> (<a href="http://twobits.net" target="_blank">http://twobits.net</a>). Trebor and I had a very interesting discussion<br>
>> about one of the concepts central to that book, namely "recursive<br>
>> public" which was a way of trying to capture what made free software<br>
>> distinctive--and whether it remains distinctive in this way as its<br>
>> ideas and practices percolate into all kind of other areas of, as this<br>
>> list has it, distributed creativity (Michel Bauwens excerpted my<br>
>> explanation of this concept on the P2P foudation wiki<br>
>> <a href="http://p2pfoundation.net/Recursive_Public" target="_blank">http://p2pfoundation.net/Recursive_Public</a>).<br>
>><br>
>> For me, that concept was specific to free software, as it existed in<br>
>> the period from roughly 1998-2002. Lots of things have changed since<br>
>> then, obviously, some features of which are explored in part 3 of my<br>
>> book. But it's clear that the purity of the idea of a recursive<br>
>> public as I describe it doesn't apply to most of the current<br>
>> generation of "open" "free" "social" "web 2.0" etc. projects out<br>
>> there, whether facebook and myspace or the new generation of web<br>
>> services, clouds, grids and so on. Nonetheless, I like to think the<br>
>> concept remains diagnostic for new projects because it points to the<br>
>> role of democracy, participation and dialogue which increasingly<br>
>> occurs not only in discourse, but in software, infrastructures, and<br>
>> tools. In part, this comes from my desire to shift the discussion,<br>
>> occasionally, away from mechanism and towards function... why are all<br>
>> these versions of openness, sociality, distributedness and so forth<br>
>> considered good? And how can we more rigorously examine whether or<br>
>> not they are goods of the sort presumed?<br>
>><br>
>> My current projects are turning towards places where I think this will<br>
>> matter most in the future. One has been nanotechnology, which is both<br>
>> a collaboration (<a href="http://opensourcenano.net" target="_blank">http://opensourcenano.net</a>) and an academic project.<br>
>> Nano matters in this realm for a particular reason: distributed risk<br>
>> forecasting of new and unknown environmental and biological materials.<br>
>> Most of nano is focused on making fancy new toys and devices, but<br>
>> there is also a surprisingly large community of people trying to<br>
>> figure out how to forecast the risks of nanomaterials. The old<br>
>> paradigms associated with the FDA, EPA and chemical regualtion (in the<br>
>> US, the EU has REACH, which is much more interesting) are clearly<br>
>> insufficient, not only for nano, but for all kinds of new risks, like<br>
>> melamine in chinese milk products. I think there is a role here for<br>
>> "distributed creativity" whether that takes the form of DIY Nano, or<br>
>> something more like citizen science.<br>
>><br>
>> The other is the life sciences (especially genomics, post-genomics,<br>
>> epigentics, post-epigentics, etc). Current hype around companies and<br>
>> projects like 23andMe and the Personal Genome Project is focused on<br>
>> the applying the power of Google to our genomes. I think this is a<br>
>> good point to take a very critical approach, one grounded in the<br>
>> ideals of Free Software. One reason is to shift the discussion from<br>
>> Privacy, which dominates the ethical discussions, to publicity, which<br>
>> is virtually absent from discussions about these projects. What<br>
>> public function does commercial genome mapping serve, and how should<br>
>> it be configured? I'm at the beginning of these projects and I hope<br>
>> this will be a place to discuss them as they evolve.<br>
>><br>
>> ck<br>
>> _______________________________________________<br>
>> iDC -- mailing list of the Institute for Distributed Creativity<br>
>> (<a href="http://distributedcreativity.org" target="_blank">distributedcreativity.org</a>)<br>
>> <a href="mailto:iDC@mailman.thing.net">iDC@mailman.thing.net</a><br>
>> <a href="https://mailman.thing.net/mailman/listinfo/idc" target="_blank">https://mailman.thing.net/mailman/listinfo/idc</a><br>
>><br>
>> List Archive:<br>
>> <a href="http://mailman.thing.net/pipermail/idc/" target="_blank">http://mailman.thing.net/pipermail/idc/</a><br>
>><br>
>> iDC Photo Stream:<br>
>> <a href="http://www.flickr.com/photos/tags/idcnetwork/" target="_blank">http://www.flickr.com/photos/tags/idcnetwork/</a><br>
>><br>
>> RSS feed:<br>
>> <a href="http://rss.gmane.org/gmane.culture.media.idc" target="_blank">http://rss.gmane.org/gmane.culture.media.idc</a><br>
>><br>
>> iDC Chat on Facebook:<br>
>> <a href="http://www.facebook.com/group.php?gid=2457237647" target="_blank">http://www.facebook.com/group.php?gid=2457237647</a><br>
>><br>
>> Share relevant URLs on <a href="http://Del.icio.us" target="_blank">Del.icio.us</a> by adding the tag iDCref<br>
><br>
><br>
_______________________________________________<br>
iDC -- mailing list of the Institute for Distributed Creativity (<a href="http://distributedcreativity.org" target="_blank">distributedcreativity.org</a>)<br>
<a href="mailto:iDC@mailman.thing.net">iDC@mailman.thing.net</a><br>
<a href="https://mailman.thing.net/mailman/listinfo/idc" target="_blank">https://mailman.thing.net/mailman/listinfo/idc</a><br>
<br>
List Archive:<br>
<a href="http://mailman.thing.net/pipermail/idc/" target="_blank">http://mailman.thing.net/pipermail/idc/</a><br>
<br>
iDC Photo Stream:<br>
<a href="http://www.flickr.com/photos/tags/idcnetwork/" target="_blank">http://www.flickr.com/photos/tags/idcnetwork/</a><br>
<br>
RSS feed:<br>
<a href="http://rss.gmane.org/gmane.culture.media.idc" target="_blank">http://rss.gmane.org/gmane.culture.media.idc</a><br>
<br>
iDC Chat on Facebook:<br>
<a href="http://www.facebook.com/group.php?gid=2457237647" target="_blank">http://www.facebook.com/group.php?gid=2457237647</a><br>
<br>
Share relevant URLs on <a href="http://Del.icio.us" target="_blank">Del.icio.us</a> by adding the tag iDCref<br>
<br>
</div></div></blockquote></div><br>