Slashdot Mirror


Lessig Revises Book With Public Wiki

Silent_E writes "Always wanted to see your words in print? The San Jose Mercury News is reporting that Lawrence Lessig is revising his book 'Code and Other Laws of Cyberspace' using a wiki-based, public discussion. The proceeds from the sale of the book are being donated. . All royalties are going to Creative Commons, plus the advance. "

66 comments

  1. the records... by grub · · Score: 5, Funny


    Always wanted to see your words in print?

    Mine are, usually after "How do you plea?"

    --
    Trolling is a art,
    1. Re:the records... by Anonymous Coward · · Score: 0

      The proceeds from the sale of the book are being donated. . All royalties are going to Creative Commons, plus the advance.

      Since the author is the only person employed by CreativeCommons, it is clear to see his intentions.

      Why not just openly admit: "I'm writing this book and I am going to make money off it" instead of this hypocritcal bullshit.

    2. Re:the records... by Mettra · · Score: 1

      Plead. Just in case some don't know or aren't sure.

  2. Interesting by Anonymous Coward · · Score: 0

    Think of the comments....

  3. He better have it backed up on tape. by Anonymous Coward · · Score: 0

    Because that wiki is about to be destroyed!

    Open Wiki's still don't make sense and people still don't get it. Will there be Goatse on Lessig's Wiki?

    1. Re:He better have it backed up on tape. by Anonymous Coward · · Score: 0
      Open Wiki's still don't make sense and people still don't get it.

      But think of all the new possibilities! You can actually anonymously troll (as opposed to all the trolling that people like Karl Marx have done using their own name) in a book!

  4. Collaborative book writing by caluml · · Score: 4, Interesting

    I've always thought that writing a book collaboratively is an interesting idea. It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along.
    However, I always thought about a fictional book.

    1. Re:Collaborative book writing by FreeLinux · · Score: 3, Insightful

      Lots of technical books are collaborations. That's why so many suck! It's hard to read when the writing style changes from chapter to chapter, ideas do not carry through the book as they should and writing skills vary dramatically.

      I much prefer a single author.

    2. Re:Collaborative book writing by Tackhead · · Score: 2, Insightful
      > I've always thought that writing a book collaboratively is an interesting idea. It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along. However, I always thought about a fictional book.

      ...said the Slashdotter, as he posted feverishly to the message board upon reading the story about Lessig's Wiki.

      Yes, Lessig. The Lessig would come and save us all. Lessig, the Kwisatch Haderach of Copyright Law. Lessig, who'd written a cool book or two. Lessig, who had a Ph.D. without becoming a total asshat. Lessig, who'd totally gotten his ass handed to him by the vested interests that run the Supreme Cou[ahem, let's just edit that out in the next revision of the Wiki, shall we, but leave the stuff about the Kwisatch Haderach in. I like that bit.]

    3. Re:Collaborative book writing by IvyMike · · Score: 4, Funny

      It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along, purple monkey dishwasher.

    4. Re:Collaborative book writing by daniil · · Score: 1

      Many movies are written that way: one person comes up with the concept and then there's a whole bunch of others working on things like dialogue and so on. Not too surprisingly, most (if not all) of these movies are quite dull and unimaginative.

      --
      Man is a slave because freedom is difficult, whereas slavery is easy.
    5. Re:Collaborative book writing by kebes · · Score: 4, Interesting

      In practice I agree with you. However, that is because most collaborative books are self-contained chapters that some editor casually reads over and then glues together. The editor is, in fact, *not allowed* to make sweeping changes to the style of a particular chapter, since the author in question would legitimately get angry. Each author is given his own "right" to describe things as he sees fit.

      In a wiki project, the final editor can pick the version of each wiki article he likes best, and he can mercilessly modify and change the style so that it sounds good. If anyone doesn't like it, they can of course fork the book based on the version they liked better.

      The point is that the wiki style, by getting rid of this "ownership of the author" has the potential to make collaborative projects actually be better.

      In practice, of course, this requires quite a good editor... so we'll see how well it turns out.

    6. Re:Collaborative book writing by roman_mir · · Score: 1

      It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along. - let's hope that when a book is written the next person to write actually unfolds that paper and reads the previous paragraph :)

    7. Re:Collaborative book writing by zotz · · Score: 1

      "It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along, purple monkey dishwasher."

      I always preferred the "write a sentence, fold it over, pass it along" version.

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
    8. Re:Collaborative book writing by Anonymous Coward · · Score: 0

      Actually a friend showed me a starup he's doing called http://www.wiction.org/ or http://www.wiktion.org/? - that's supposed to allow online collaborative fiction writing. I really think this would be even more usefull for non-fiction, like textbooks for example . (wikipedia has shown this works pretty damn well for encyclopedias also!)

  5. Domino Theory by Anonymous Coward · · Score: 1, Funny

    This is like the domino effect. If America gives up property ownership in some cases, then the rest of property ownership will fall. We know what this means ... Communism !!!

  6. Why, I've already seen my words in print! by 14erCleaner · · Score: 4, Funny

    Slashdot does count as "print", doesn't it?

    --
    Have you read my blog lately?
    1. Re:Why, I've already seen my words in print! by Mercano · · Score: 2, Funny

      Hit Ctrl+P and it does.

      --
      #include <signature.h>
    2. Re:Why, I've already seen my words in print! by xutopia · · Score: 1

      I think it only counts as print if you get frist post! :)

    3. Re:Why, I've already seen my words in print! by Poppler · · Score: 1

      Hit Ctrl+P

      You mean enter lpr [filename], right?

      --
      What's the ugliest part of your body? Some say your nose, some say your toes, but I think it's your mind. -Zappa
  7. Maybe the RIAA & MPAA will write their own cha by hsmith · · Score: 4, Funny

    I can see the title of their chapter "Downloaders are dirty thieves."

  8. Revised Author by WaldoXX · · Score: 5, Funny

    Author's name should be revised to ..... Anonymous Coward

  9. ^^^ Freaking Best Seller!!! ^^^ by Anonymous Coward · · Score: 2, Funny

    I think you have a freaking best seller on your hand there.

  10. Hieraki by Tobias+Luetke · · Score: 4, Interesting

    Hieraki is a project which aims to create a wiki with pages hierarchically arranged instead of interlinked like on a traditional wiki. It uses the notion of Books, Chapters and Pages.

    Its the main means of documentation for the rubyonrails project and is used for writing documentation at several hosting services like textdrive and universities.

    Disclaimer: I'm the author.

    1. Re:Hieraki by Tobias+Luetke · · Score: 1

      Hrm, I thought it would be fair to make sure to set things straight.

      I'm not trying to get any extra traffic to my open source project. I just thought it would be a relevant and on topic comment.

    2. Re:Hieraki by Anonymous Coward · · Score: 0

      Adding a built-in hierarchy feature to the wiki is a great step, but wikis in general suffer from some limitations as project documentation tools.

      Even developers won't bother to learn the markup language if doing so is added to an existing roster of paid tasks. They will only do it for fun--hence getting most of them to contribute to paid-for-work project documentation using this stuff doesnt fly. Some form of (horrors) WYSIWYG is probably essential (at least in the business/government world) if one is to get past the initial experimental stage and into serious, scheduled production.

      Doesn't integrate Visio or equiv--you can't get complex live vector graphics into a Wiki without conversion to bitmaps. This eliminates a huge percentage of the useful technical information that could be included.

      Output to PDF is a great feature--input and output via something like Docbook would be even better: a variety of options including (horrors) RTF would be even better.

  11. Who read the submitted links then? by Anonymous Coward · · Score: 0

    Nice. Two links, one with a pesky registration. The second is an entire book.

    Meh!

    Can someone who has read the book comment on it?

  12. Re:Maybe the RIAA & MPAA will write their own by pHatidic · · Score: 2, Funny

    >I can see the title of their chapter "Downloaders are PENIS dirty thieves."

  13. I laughed. I cried. by Anonymous Coward · · Score: 1, Funny

    I laughed. I cried. I tore out the pages and used them for toilet paper.

    If you're interested in reading it for yourself, you are welcome to my copy.

  14. Article Text [slow, reg req'd] by Anonymous Coward · · Score: 5, Informative

    Professor's online publishing experiment

    LESSIG INVITES HELP TO UPDATE 1999 BOOK

    By Michael Bazeley

    Mercury News

    Further nudging outward the boundaries of online publishing, Stanford University Professor Larry Lessig will put his 1999 book ``Code'' online today and invite Internet users to help him write an updated version.

    A noted copyright expert and proponent of free software, Lessig is putting the 297-page treatise about technology, culture and regulation on the Web in the form of a ``wiki,'' a site that can allow people to freely edit its contents. The law professor will take the contributions at http://codebook.jot/ .com and edit them into a printed version of the book.

    ``Code has become a part of cyberspace law culture,'' Lessig said. ``And what I found most interesting is that people outside of the academic world talk about it and use it a lot. I was really trying to find a way to encourage them to contribute to the evolution of `Code.' ''

    Lessig said he also wanted to use the process to better understand the concept of wikis.

    Lessig is the latest in a string of authors -- often from the technology world -- to open up their writings to the public. Former Mercury News columnist Dan Gillmor published chapters of his book ``We the Media'' online as they were written and sought feedback. And East Bay author J.D. Lasica allowed online readers to edit chapters of his book ``Darknet: Remixing the Future of Movies, Music & Television.''

    Similarly, a project called Wikipedia has been building an online encyclopedia almost exclusively from contributions of users.

    Lessig's venture may be the most ambitious yet among book authors. Where feasible, he intends to use significant portions of reader contributions in the new edition. While he has not yet figured out how to handle authorship and credit contributors, Lessig intends to donate any book royalties to Creative Commons, a non-profit organization he founded to offer an alternative to traditional copyright licenses.

    Palo Alto start-up JotSpot is providing the wiki space for Lessig's project.

    Like Lessig, JotSpot founders Joe Kraus and Graham Spencer have an interest in consumer digital rights, dating back to their founding of the consumer-rights lobbying group Digitalconsumer.org in 2001.

    ``It was a nice alignment of the things I care about at a personal level,'' Kraus said. ``And it's an opportunity to showcase the technologies that JotSpot is developing.''

  15. Ctrl+P??? by game+kid · · Score: 1

    I might be using a voice-browsing-enabled PDA without a keyboard you insensitive clod!

    --
    You can hold down the "B" button for continuous firing.
    1. Re:Ctrl+P??? by RealAlaskan · · Score: 2, Funny
      I might be using a voice-browsing-enabled PDA without a keyboard you insensitive clod!

      You just might be. If you have your text to speech thingy going, and the voice recognition going too, you'll regret letting it read rm -rf ~/

  16. What's the dot about... Code v2 rather than v0.2 ? by D4C5CE · · Score: 3, Funny

    Looks like they've only been sure about the version numbering in the toolbar on the right: "CODE v2"
    Everywhere else, with the strange notation of "Code v.2" it looks like this is about trying to write a work that will never make it out of beta, stalling at v0.2 ... (which would be a strange kind of follow-up to a highly successful v1.0)

  17. Questionable by Ganellon · · Score: 5, Insightful

    While this may seem like a compelling idea, I suspect editors will be in much higher demand than contributors. I don't believe this is a successful strategy in producing a coherent volume, since paid authors have a hard enough time getting their works published. Accepting submissions from all comers, particularly those professing some "expertise" in the given subject, is bound to lead to massive quantities of unusable material.

    1. Re:Questionable by truthsearch · · Score: 3, Insightful

      Lessig is quite intelligent. He knows what he's doing is an experiment. He also knows we'll never really know if such a thing is a good idea until someone tries it. While some technical documentation is written this way a book such as his probably has not.

      Also, with a wiki a few good editors could go through what's entered and edit as desired. I'm sure Lessig will have no problems finding an editor or two to help.

      You're quite possibly right, but I hope you're wrong.

    2. Re:Questionable by KhaZ · · Score: 2, Interesting

      I agree with you somewhat, but in true Slashdot fashion, none of us monkeys can agree with each other completely... What fun would that be? One comment max, on every post!

      Anyhow, ideally a wiki should have every contributor be both contributing AND editting.

      But in theory, nobody will, they'll just throw their points together like the Portland Pattern Repository (http://c2.com/cgi/wiki) and have everything looking like crap.

      Sigh, too bad. Although I'd love to be proved wrong!

      --
      - - - -

      KickingDragon

    3. Re:Questionable by DogDude · · Score: 0, Flamebait

      Lessig, is, quite honestly, a media whore. It seems like he has a new stunt every week, most of which are relatively useless (like this), except that he gets more time in the limelight.

      If anything, he should write a book "How to be a Media Whore and Profit From It". That's a book I'd buy.

      --
      I don't respond to AC's.
    4. Re:Questionable by truthsearch · · Score: 2, Insightful

      You obviously haven't read any of his books or articles on his background. He gets more and more media attention as he finds more and more things going wrong with the legal system. His "stunts" draw direct attention to real problems. His contributions have helped software developers more than any other lawyer I can think of. Before most people knew his name he was helping convict Microsoft of illegal activities. He's also the first to really explain the problems in the legal system as relating to computers to everyone.

      Developers in the US are definitely better off with him in the spotlight.

  18. My words were in print long ago. by farmhick · · Score: 2, Insightful

    I wrote a letter to the editor of Science Fiction Age magazine in 1993. Not only was it printed, it closed a long running debate about the contents of the magazine. I had gotten tired of reading letters complaining about the one 'fantasy' story in a 'science fiction' mag, and the supporting letters were annoying too. One month, three of the four letters printed were on this topic. So I wrote in and told the guys at the magazine to just make a decision, tell us readers what it was, and stick to it. They would then at least have our respect, if not our agreement. I think they kept the one fantasy story, and I don't remember another letter about it.

    --
    I have to stop wasting so much time reading Slashdot. It's interfering with my crystal meth addiction.
    1. Re:My words were in print long ago. by Anonymous Coward · · Score: 0

      Meanwhile, the rest of us were busy having lives.

  19. Minor Correction by theGreater · · Score: 3, Funny

    Shouldn't that be, "Public revises book with Lawrence Lessig" or better yet, "Lawrence Lessig Invites Public to Edit Book."

    The way they write headlines around here, you'd think Public is some fancy new ncurses based word processor :D

    -theGreater Downmodded.

  20. Story should read by Anonymous Coward · · Score: 0

    "Always wanted to see your words in print? The San Jose Mercury News is reporting that Lawrence Lessig is hoping to get other people to do the hard work of revising his book 'Code and Other Laws of Cyberspace' using a wiki-based, public discussion. Feel free to contribute to his book safe in the knowledge there is no risk of seeing your name attached to it unless you write more than 4 new chapters"

  21. YHBT, YHL. HAND. by Anonymous Coward · · Score: 0

    [nt]

  22. metaweb by Anonymous Coward · · Score: 0

    Not quite the same, but Neal Stephenson set up a wiki called metaweb to discuss and correct errors in his book, Quicksilver...

    1. Re:metaweb by Silent_E · · Score: 2, Funny

      Perhaps not the same, but quite cool. I can imagine that when another edition comes out, he'll put the corrections in, and perhaps (if he's honest) he'll put in a special page of acknoweldgements to anonymous coward, byte me, etc!

  23. Re:^^^ Freaking Best Seller!!! ^^^ by maotx · · Score: 1

    It's just an extension of the childhood game where you write a word on a piece of paper, fold it over, and pass it along, purple monkey dishwasher.

    I think you have a freaking best seller on your hand there.


    He then sold his book and made millions only to purchase an Italian, lesbian monkey who would...
    Anyone care to finish?

    --
    I'm a virgo and on Slashdot. Coincidence? Yes.
  24. JotSpot is proprietary by Eloquence · · Score: 5, Interesting

    Given that Larry Lessig is on the board of the Free Software Foundation, it is a bit strange that he uses a wiki engine which is proprietary, even though free (and, in many ways, superior) alternatives such as MediaWiki (the engine used by Wikipedia) are readily available.

  25. Speaking of revising... by AntsInMyPants · · Score: 1

    "The proceeds from the sale of the book are being donated. . All royalties are going to Creative Commons, plus the advance."

    How about making that "The advance and all proceeds from the sale of the book are being donated to Creative Commons."?

    Yeah its a nit pick, but I'm in that kind of mood. (Now watch while some smartass, finds something wrong with my post).

    1. Re:Speaking of revising... by /dev/trash · · Score: 1

      Simpler to just change "plus" to "including".

    2. Re:Speaking of revising... by AntsInMyPants · · Score: 1

      Simpler, but it doesn't read as well. Proceeds and advance are two things that go together, and make more since to be grouped in the same clause. It reads clunky the other way.
      As if my language skills were perfect...

  26. What's the dot about... Code v2 rather than v0.2 ? by Anonymous Coward · · Score: 0
    Looks like they've only been sure about the version numbering in the toolbar on the right: "CODE v2"
    - but not about the spelling: CODE is not Code, for I'm on Unix, you case-insensitive clod!
  27. Re:Paid Authors by Anonymous Coward · · Score: 0

    Paid Authors generally are the ones who get published. It's the unpublished unpaid ones who have it hard!

  28. Wikis are the next step in internet (r)evolution. by Anonymous Coward · · Score: 1, Interesting

    The web is often viewed as a great information source (especially since finding informations got easier via *working* search engines).

    But it could be even FAR better, more correct, more complete, better interlinked, if publishing was easier, more collaborative and on a higher level than html.

    This is exactly what a public wiki does so easily.
    The main problem currently is, that about 95% of the web users still don't know wiki at all - it could make so much things so much more productive!

    It is a building block of free information and free collaboration.

  29. Re:^^^ Freaking Best Seller!!! ^^^ by Anonymous Coward · · Score: 0

    ..brutilly rip your fingers off so you can never post again...

  30. Re:^^^ Freaking Best Seller!!! ^^^ by Anonymous Coward · · Score: 0

    ...only to become a new slashdot editor. No one would ever be able to tell the difference.

  31. how about Code's CONTENT?! by rikb · · Score: 2, Insightful

    ok, so there is lots to say about authoring by a single individual vs. wiki-mediated hordes (and i suppose James Michener's enterprise falls somewhere in between?:).

    but what does the slashDot crowd make of Lessig's ARGUMENTS in Code, about code? what should CodeV2 make sure to address? are you going to weigh in?

  32. +10 Kick ass Dune Reference! by PotatoHead · · Score: 1

    Finally a reason to say Kwisatch Haderach! This is a perfect description of Lessig. Come to think of it, we really don't have any other compact term that describes the rare combination of vision, talent and selflessness Lessig demonstrates. --At least none that I can think of anyway.

    Good Call.

  33. Wikibooks by danila · · Score: 2, Informative

    There is actually an entire wiki dedicated to collaborative writing of books already.

    --
    Future Wiki -- If you don't think about the future, you cannot have one.