Home | About | RSS Feed | Contact and Publicity Guidelines | Comment Policy the Law, the Universe, and Everything 

Search


Concurring Opinions is a
general-interest legal blog
operated by Concurring
Opinions LLC, a Pennsylvania
Limited Liability Corporation.

jr_114_9780195367195_bnr

jr_114_9780195383768_bnr

advertise-here4


FC-CO(SS)

Our Podcast

Subscribe to Law Talk

law-rev-contents2.jpg


  • Posts by Author

  • Categories

  • Archives


  • Recent Comments

    • Observer on Ricci: Color-Blind Standards in a Race Conscious Society?

    • RJ on Ricci: Color-Blind Standards in a Race Conscious Society?

    • RJ on Ricci and Briscoe as Disparate Impact Cases

    • Mike Rich on Negligent Corpse Mishandling

    • anon on Privacy and Tattletales

    • orly lobel on At CELS, Hoping to Blog

    • harry brooks on Ricci: Color-Blind Standards in a Race Conscious Society?

    • RJ on Ricci: Color-Blind Standards in a Race Conscious Society?

    • Michael H Schneider on Negligent Corpse Mishandling

    • flood pictures on Public opinion on same-sex marriage

    • gtownstudent on And Justache For All at GW Law

    • AF on Ricci and Briscoe as Disparate Impact Cases

    • RJ on Ricci and Briscoe as Disparate Impact Cases

    • Maryland Conservatarian on Ricci: Color-Blind Standards in a Race Conscious Society?

    • Daniel S. Goldberg on Negligent Corpse Mishandling

  •  

    Site Meter

Debate on the Future of the Internet

posted by Frank Pasquale

I think Deven’s advice is great, but for those who want to sample Zittrain’s new book (The Future of the Internet and How to Stop It) before buying it, it’s excerpted in the Boston Review this month. (There’s also an outline of its ideas in this Harvard Law Review article.) It’s a very thoughtful analysis of some of the most difficult issues affecting internet policy. I will have more to say in future posts, but I just wanted to highlight this work, and the all-star respondents who comment on it in the same issue.

One of the biggest problems that Zittrain spots is that “bad code is now a business:”

So long as spam remains profitable, [many crimes] will persist. . . [including] viruses that compromise PCs to create large zombie “botnets” open to later instructions. Such instructions have included directing PCs to become their own e-mail servers, sending spam by the thousands or millions to e-mail addresses harvested from the hard disk of the machines themselves or gleaned from Internet searches, with the entire process typically proceeding behind the back of the PCs’ owners.

Botnets can also be used to launch coordinated attacks on a particular Internet endpoint. For example, a criminal can attack an Internet gambling Web site and then extort payment to make the attacks stop. The going rate for a botnet to launch such an attack is reputed to be about $50,000 per day.

What to do? I’ll just append a very brief excerpt of the Boston Review piece below the fold.


After considering the shortcomings of “appliancization” of personal computers (i.e., making them as tamper-proof as TiVos and cellphones), Zittrain states:

We need a strategy that addresses the emerging security troubles of today’s Internet and PCs without killing their openness to innovation. This is easier said than done, because our familiar legal tools are not particularly attuned to maintaining generativity. A simple regulatory intervention—say, banning the creation or distribution of deceptive or harmful code—will not work because it is hard to track the identities of sophisticated wrongdoers, and, even if found, many may not be in cooperative jurisdictions. Moreover, such intervention may have a badly chilling effect: much of the good code we have seen has come from unaccredited people sharing what they have made for fun, collaborating in ways that would make businesslike regulation of their activities burdensome for them. They might be dissuaded from sharing at all. . . .

We can find a balance between needed change and undue restriction if we think about how to move generative approaches and solutions that work at one “layer” of the Internet—content, code, or technical—to another. Consider Wikipedia, the free encyclopedia whose content—the entries and their modifications—is fully generated by the Web community. . . .

The effectiveness of the social layer in Web successes points to two approaches that might save the generative spirit of the Net, or at least keep it alive for another interval. The first is to reconfigure and strengthen the Net’s experimentalist architecture to make it fit better with the vast expansion in the number and types of users. The second is to develop new tools and practices that will enable relevant people and institutions to help secure the Net themselves instead of waiting for someone else to do it.

Generative PCs with Easy Reversion. Wikis are designed so that anyone can edit them. This creates a genuine and ongoing risk of bad edits, through either incompetence or malice. The damage that can be done, however, is minimized by the wiki technology, because it allows bad changes to be quickly reverted. All previous versions of a page are kept, and a few clicks by another user can restore a page to the way it was before later changes were made. So long as there are more users (and automated tools they create) detecting and reverting vandalism than there are users vandalizing, the community wins. (Truly, the price of freedom is eternal vigilance.) Our PCs can be similarly equipped.

****

Building on . . . ideas about measurement and code assessment, Harvard University’s Berkman Center and the Oxford Internet Institute—multidisciplinary academic enterprises dedicated to charting the future of the Net and improving it—have begun a project called StopBadware, designed to assist rank-and-file Internet users in identifying and avoiding bad code. The idea is not to replicate the work of security vendors like Symantec and McAfee, which for a fee seek to bail new viruses out of our PCs faster than they pour in. Rather, these academic groups are developing a common technical and institutional framework that enables users to devote some bandwidth and processing power for better measurement of the effect of new code.

I’ll try to summarize and respond to Zittrain’s arguments later this week. But for now I offer these excerpts as a taste of the challenging ideas now on offer in his new book.


 April 14, 2008 at 4:12 pm   Posted in: Cyberlaw   Print This Post Print This Post

Responses (1)

  1. A.J. Sutter - April 16, 2008 at 10:24 am

    Encouraged by your and Deven’s posts, I checked out the HLR article. Also, I had no idea what a “generative technology” is. I can’t say that I can share your enthusiasm based on what I’ve dipped into, or that I am much enlightened about what makes something “generative”.

    The first definition is “Generativity denotes a technology’s overall capacity to produce unprompted change driven by large, varied, and uncoordinated audiences.” Barbed wire is generative by this criterion, as are explosive devices.

    Then Prof. Zittrain refines this by presenting four other criteria: ease of leverage, adaptability, ease of mastery and accessibility. One problem I had with those is that it is unclear *for how many people* something must meet these criteria in order to be “generative.” Depending on what tasks are pertinent, I might or, more likely, might not have “mastered” PCs, the Internet, etc. Depending on how small a group is sufficient, CMOS design, genetic engineering and microimprint lithography might fit this definition — so what’s special about the Internet? And then, a fortiori, cooking, woodworking and agriculture would also fit the definition since they have been mastered by millions — so again, why single out the Internet? (Indeed, explosive devices probably fit these criteria as well — there are many applications of blowing things up — in which case is “generative” apt?)

    All in all, the category of generativity seemed kind of slippery, and not at all easy to master (so not particularly ‘generative’?). It seems mainly to be a scholar’s marketing device: first, to make the author’s pet interests sound special and ultra-worthy, and second, to create a buzzword that might capture some of the “disruptive technology” lustre — though at least Clayton Christensen had a well-limned practical definition.

    I hope the analysis in the book is much clearer than in this HLR article. Also, I hope Prof. Zittrain wrote the book with a lighter style; as for the article, limpid it isn’t.

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word


  • « Previous post
  • Next post »

Authors

Daniel J. Solove

Website
Understanding Privacy

Kaimipono Wenger

Website
SSRN Page

Dave Hoffman

Website
SSRN Page

Nate Oman

Website
SSRN Page

Frank Pasquale

Website
SSRN Page

Deven Desai

Website
SSRN Page

Danielle Citron

Website
SSRN Page

Lawrence Cunningham

Website
SSRN Page

Sarah Waldeck

Website
SSRN Page

Jaya Ramji-Nogales

Website
SSRN Page

Solangel Maldonado

Website
SSRN Page

Gerard Magliocca

Website
SSRN Page


Guests

Rachel Godsil
Alex Kreit
Anita Krishnakumar
Matthew Sag
Michael Zimmer






Previous Guests

Michael Abramowicz
Michelle Adams
Robert Ahdieh
Michelle Anderson
Laura Appleman
Ann Bartow
Francesca Bignami
Jeremy Blumenthal
Kathleen Boozang
Bruce Boyden
Donald Braman
Al Brophy
Neil H. Buchanan
Bill Burke-White
Scott Burris
Paul Butler
Naomi Cahn
Anupam Chander
Miriam Cherry
Jack Chin
Jennifer Collins
Allison Danner
Brannon Denning
Deven Desai
Mike Dimino
Mark Edwards
David Fagundes
Christine Haight Farley
Kim Ferzan
Dan Filler
Michael Froomkin
Amanda Frost
Timothy Glynn
Rachel Godsil
Eric Goldman
David Gray
Craig Green
Tristin Green
Jeffrey Harrison
Erica Hashimoto
Carissa Hessick
Laura Heymann
Robert Hillman
Christine Hurt
Darian Ibrahim
John Ip
Kevin Johnson
Dan Kahan
Brian Kalt
Sam Kamin
Michael Kang
Chimène Keitner
Orin Kerr
Nancy Kim
Heidi Kitrosser
Adam Kolber
Russell Korobkin
Anita S. Krishnakumar
Susan Kuo
Greg Lastowka
Sarah Lawsky
Erik Lillquist
Jeff Lipshaw
Jonathan Lipson
Jacqueline Lipton
Joseph Liu
Michael Madison
Solangel Maldonado
Jason Mazzone
Linda McClain
William McGeveran
Salil Mehra
Carrie Menkel-Meadow
Max Minzner
Scott Moss
Eric Muller
Jaya Ramji-Nogales
Helen Norton
Elizabeth Nowicki
Paul Ohm
Michael O'Shea
David Opderback
Kristen Osenga
Rafael Pardo
Marcy Peek
Eduardo Peñalver
Robert Percival
David Post
Shruti Rana
Geoffrey Rapp
Neil Richards
Lori Ringhand
Alice Ristroph
Susan Scafidi
Paul Secunda
Jonathan Siegel
Jessica Silbey
Peter Smith
Charles Sullivan
Rick Swedloff
Steph Tai
Andrew Taslitz
Robert Tsai
Jenia Turner
Steve Vladeck
Sarah Waldeck
Melissa Waters
Alfred Yen
David Zaring
Timothy Zick
Spencer Weber Waller
Howard Wasserman
Frank Wu
Corey Yung
Jonathan Zittrain

Blogroll

Above the Law
ACS Blog
Althouse
Balkinization
Becker-Posner Blog
BlackProf
BoingBoing
Chicago Law Faculty Blog
Conglomerate
CrimLaw
Crime & Federalism
CrimProf Blog
Crooked Timber
Discourse.net
Dorf on Law
Election Law
Emergent Chaos
The Faculty Lounge
Feminist Law Profs
43(B)log
Freakonomics Blog
Freedom to Tinker
Google Blogoscoped
How Appealing
Ideoblog
Info/Law
Instapundit.com
Juris Novus
Jurisdynamics
Law and Humanities Blog
Law and Letters
Law Librarian Blog
Legal Profession Blog
Legal Theory Blog
Legal Times Blog
Leiter Reports
Brian Leiter's Law School Reports
Lessig Blog
Madisonian Theory
Media Law Blog
Mirror of Justice
The Moderate Voice
National Security Advisors
Opinio Juris
Point of Law
PrawfsBlawg
ProfessorBainbridge.com
Property Prof Blog
Red Tape Chronicles
The Right Coast
Schneier on Security
SCOTUSBlog
Security Dilemmas
Sentencing Law and Policy
Simple Justice
Sivacracy.net
The Situationist
Susan Crawford
TalkLeft
Talking Points Memo
TaxProf Blog
Tech & Marketing Law
Truth on the Market
Volokh Conspiracy
WorkPlace Prof Blog
WSJ Law Blog
Wonkette
The Yin Blog


© Concurring Opinions

Powered by WordPress