actually, lessig isn't working on copyright any longer.

so his blog would be good for past stuff, but not going forward.

scott
--
R. Scott Granneman
[EMAIL PROTECTED] ~ www.granneman.com
Full list of publications @ http://www.granneman.com/publications
   My new book: Linux Phrasebook @ http://www.granneman.com/books

"Mistakes are a part of being human. Appreciate your mistakes for what  
they are: precious life lessons that can only be learned the hard way.  
Unless it's a fatal mistake, which, at least, others can learn from."
       ---Al Franken

On Sep 4, 2008, at 1:50 PM, Sean Burns wrote:

>
> On Thu, Sep 4, 2008 at 1:36 PM, Scott Granneman  
> <[EMAIL PROTECTED]> wrote:
>>
>> Here ya go.
>>
>> http://googleblog.blogspot.com/2008/09/update-to-google-chromes-terms-of.html
>
> And just as I suspected, that stuff is there because of copyright law:
>
> "This section is included because, under copyright law, Google needs
> what's called a "license" to display or transmit content."
>
> If anyone really wants to see the kind of legalese that's in these
> "contracts" go away, maybe  do something about copyright.
>
> Here's a good PDF on the public domain and why it's important:
>
> http://www.publicknowledge.org/pdf/why_the_public_domain_matters.pdf
>
> A couple good blogs to follow:
>
> http://www.sivacracy.net/
> http://www.lessig.org/blog/
>
> And Lawrence Lessig has an awesome presentation on copyright history:
> http://randomfoo.net/oscon/2002/lessig/
>
> And Siva Vaidhyanathan has a great book on copyright:
>
> Copyrights and Copywrongs: The Rise of Intellectual Property and How
> it Threatens Creativity
>
> http://www.worldcat.org/oclc/46856111&referer=brief_results
>
> Sean
>
> >


--~--~---------~--~----~------------~-------~--~----~
Central West End Linux Users Group (via Google Groups)
Main page: http://www.cwelug.org
To post: [email protected]
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
More options: http://groups.google.com/group/cwelug
-~----------~----~----~----~------~----~------~--~---

Reply via email to