Slashdot Mirror

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

Bennett Haselton contributes the following essay on the consequences of license choice as it applies to sites based on user contributions; read on below for more of his big idea for making Knol a more useful resource. "Google Knol should allow its writers to publish under a Creative Commons Share Alike license. The preceding sentence may not mean much to you, but if you've ever wanted to cite a Wikipedia article as a source, or simply read a Wikipedia article with some assurance that someone wasn't pulling your leg with some creative editing, or if you've wanted to contribute to Wikipedia but couldn't afford the time unless you received some modest compensation for it, then the addition of this one simple feature to Knol might make all the difference." (More below.)

I've been suggesting for some time that Wikipedia, or some fork of Wikipedia, should allow users to "sign off" on a version of an article, and then lock that article against future edits until the signer had approved them. The signing off would allow people to cite a Wikipedia article as a source that had been vetted by at least one person (with confidence in the source depending on that person's credentials). The signer's identity (and sometimes, their credentials) could be confirmed using several methods, such as verifying an .edu e-mail address. Users could still submit edits, but they would have to be approved by the article verifier. Different users could sign off on different versions of the same article, and readers would still have the option of viewing the latest version of an article, with all of its unmoderated edits (which is what you're looking at on Wikipedia most of the time).

Knol, which allows users to submit articles on any topic they want, has incorporated all of the above features (adding, for example, the ability to verify authors' real names using credit cards), and gone one step further by allowing users to place AdSense ads in their articles. However, there's one stumbling block to Knol incorporating all of Wikipedia's content and blessing it with the verification of credentialed experts: Currently, although you have to dig a bit deep to find this out, Knol's Terms of Service do not allow content to be copied from Wikipedia.

Content on Wikipedia is published under the GNU Free Documentation License -- when you click any of the "edit" links in a Wikipedia article and begin typing in new content, you're agreeing to submit your content under the terms of the GFDL. When you publish on Knol, on the other hand, your options are to publish under a Creative Commons Attribution 3.0 License (CC-BY), a Creative Commons Attribution-Noncommercial 3.0 License (CC-BY-NC), or a traditional "All Rights Reserved" copyright model. Both the GFDL and the Creative Commons Attribution licenses are popular with content creators who want to give content altruistically "to the world" -- these licenses all allow content to be redistributed freely without modification. The main difference is in the rights that they grant to people who want to create derivative works (modifying or expanding on the original work).

The GFDL is intended as a "viral" license -- if you take a work that is published under the GFDL, and publish a derivative work created from that, your derivative work must also be published under the terms of the GFDL -- that is, also allowing other users to redistribute your work freely and create derivative works from it as well. If a site mirrors Wikipedia articles without including the terms of the GFDL, Wikipedia encourages users to send notifications to those sites pointing out that they're violating Wikipedia's copyright, and if necessary to escalate the matter to their Web hosting provider for noncompliance. You can mirror Wikipedia all you want, and even put put ads all over your mirror site, but you cannot change the terms.

Creative Commons Attribution (CC-BY) licenses, on the other hand, allow users to create derivative works and publish them under almost any terms they want, including an "All rights reserved" model, provided that they give attribution to the author of the original work. If Susan publishes an article under CC-BY, you can create a derivative work by expanding on her article, and -- assuming your contributions are substantial enough to be copyrightable in themselves -- you can prohibit other users from redistributing your article or creating derivative works from it, something that would not be possible if Susan had published her article under the GFDL. (Obviously, you cannot prohibit others from redistributing Susan's article or creating their own derivative works from it, but you can restrict these rights as applied to your own derivative work.)

Russell Potter, a Professor of English at Rhode Island College and a Citizendium contributor who explained this difference to me, points out that CC-BY licenses are more friendly to academics who want to reuse content in a published book or in a conference presentation. "Say an academic (me) contributes a long article on London's Crystal Palace," he wrote. "Others edit it in modest ways, but the article is still about 90% my own work. Perhaps I want to give a paper at a conference based on this entry, or use large bits of it in a book I'm writing. GFDL would have made either impossible." (Impossible, that is, unless the book publisher released the book under the GFDL, but most book publishing companies are reluctant to do that.)

And therein lies the logical incompatibility between the GFDL and the CC-BY publishing options currently allowed by Knol. If you copy GFDL-licensed content from Wikipedia, you are agreeing that for any copies or derivative works that you create, you will not only permit other users to remix them, but that you will require those other users to agree to the same terms for the remixed works that they publish. If you published such content on Knol under the CC-BY option, you would be granting the reader permission to incorporate the work into their own derivative work which they could then publish under an All Rights Reserved license. And the GFDL doesn't allow you to grant that permission to the reader. Section 5.5 of Knol's Terms of Service explicitly states that GFDL content cannot be re-published under a CC-BY license, and Mike Linksvayer makes this point on the Creative Commons blog as well. Some authors have begun copying Wikipedia content to Knol anyway, and even though that particular article included a link to the GFDL, users have pointed out in the comments that it's still a TOS violation anyway. Google appears to be lax about policing these violations for now, but in the right-hand column, the links to "Similar Content on the Web" show that Google can trivially detect if content is copied from other sites, and may be planning to remove such content or demote it in search results if it's copied from a site like Wikipedia that doesn't allow copying under Knol's terms.

However, the Creative Commons family of licenses also includes the Creative Commons Attribution-Share Alike License (CC-BY-SA), which is written in the same spirit as the GFDL -- if a work is released under CC-BY-SA, any published derivative works created from that work must also be released under the same license. In fact the Free Software Foundation, which writes new versions of the GFDL, announced in December 2007 their intention to make the next version of the GFDL explicitly compatible with CC-BY-SA, so that any work published under the GFDL can be incorporated into a work published under CC-BY-SA, and vice versa. This new version of the GFDL has not been released yet, but the FSF replied by e-mail to say they're working on it.

(Perhaps you might be wondering, as I did, how already-existing content on Wikipedia can be said to be "licensed" under a new version of the GFDL when it comes out. How can past Wikipedia contributors have agreed to a future version of the license that didn't exist yet? The answer is that when you submit edits on Wikipedia, you're agreeing to submit your edits under the "GNU Free Documentation License, Version 1.2 or any later version", and it's the "or any later version" that means contributors are deemed to have agreed to the next version of the GFDL, which will presumably be CC-BY-SA-compatible.)

If Google Knol adds the ability to publish under a Creative Commons Attribution-Share Alike license, and the FSF releases a new version of the GFDL that is compatible with this license, then I think we will finally see what I hoped for in February 2008 -- a "gold rush" of users copying content from Wikipedia to Knol, where it can be verified by credentialed users and protected against vandalism. Some users' verifications will be more valuable than others -- a physics article verified by a physics professor is more trustworthy than the same article verified by an anonymous user, and even an article about The X-Files may be more trustworthy when it's verified by a physics professor, not because it's the professor's area of expertise, but because a professor with a valued reputation would be less likely to sign their name to unverified garbage.

Will Knol add the Share Alike option? Perhaps they may be nervous about what would happen if they allowed unlimited copying from Wikipedia, especially with financial incentives. At the moment, Knol seems to be downplaying the fact that you can make money from writing articles, even as everyone else buzzes about it. On their front page, under "Learn More", Knol lists the reasons you should contribute: "Visibility - We value and promote authorship. Great content will be visible on any search engine. Community - You can connect with other experts in your area of interest to share and grow knowledge," etc. Really? That's all? AdSense isn't mentioned in the FAQ, and only briefly at the end of a posting about "Knol bugs and workarounds". And officially the site never mentions Wikipedia at all, except in the knols about it.

But many of the articles on Wikipedia -- especially the kind of articles that academics would be willing to sign their names to -- would probably enhance the Knol site, not drag it down. Wikipedia founder Jimmy Wales correctly predicted that Knol would generate a lot of articles about Viagra. If Knol can tolerate that garbage (and under their own policies, there is little grounds for removing those articles, unless the authors lifted the content from some other site), they should welcome the addition of articles about stochiometry, Shakespeare, and Serbia, even if they were copied from Wikipedia and then vetted by a university professor or journalist. (None of those topics have their own Knol yet, although there was room for Knols about Simon Cowell, Superman, and sex addiction.)

After all, the incentives that AdSense creates for Knol writers are roughly the same as the incentives for Web publishers in general -- you can try to turn a quick buck, or you can invest in your site's reputation for the long run -- and while there is a new "made-for-AdSense" site born every minute, few would disagree that the rise of AdSense has been good for content on the Web in general.

While copying from Wikipedia to Knol is against the rules right now, there's no reason in principle to be against creating a Wikipedia sub-fork on Knol, if Google allows Knol writers to select the Creative Commons Attribution-Share Alike publishing option. One user, responding to the unauthorized use of Wikipedia articles, posted in the Knol users' group on Google Groups: "What I REALLY want to see Google do is crack down on these clowns who are copying and pasting articles from Wikipedia." I say, just change the rules and send in the clowns.

Slashdot welcomes original submissions; many thanks to Bennett for this one.

lucabrasi999 writes "Ahoy! Drink up the Grog, me hearties! Today is International Talk Like a Pirate Day! Grab yer wenches and stop being a bilge-rat." Cap'n Slappy and Ol' Chumbucket have even provided a short YouTube video to help those who might be a bit more pirate-speak challenged. Even Google is getting in on the action, those swarthy dogs.

Anil Kandangath writes with word that the Indian moon mission plans (mentioned earlier on Slashdot) are about to be put to the test. "While the spacecraft itself will not land on the Moon, it will act as an orbiter and land a rover on the surface. The spacecraft is being launched next month sometime between October 22 and October 26. The spacecraft payload includes 11 payloads (including one from NASA) and will perform remote sensing and studies of the lunar surface. The mission is estimated to cost Rs 386 crore (~ 84.3 million USD)." Update: 09/21 18:29 GMT by T : Thanks to reader Anil Gaddam for pointing out that this figure had been originally misstated as 7.7 million USD.

Ortega-Starfire writes "A 30-ton transformer in the Large Hadron Collider malfunctioned, requiring complete replacement on the day the LHC came online. No one at CERN reported any problems, and they only released this data once the Associated Press sent people to investigate rumors of problems. I guess it's hard to just sweep a 30-ton transformer breaking under the rug."

Andreaskem writes "Bavarian police searched the home of the spokesman for the German Pirate Party (Piratenpartei Deutschland) looking for an informant who leaked information about a government Trojan used to eavesdrop on Skype conversations. (The link is a Google translation of the German original.) There is a high probability that the Trojan is used illegally. A criminal law specialist said, 'The Bavarian authorities worked on the Trojan without a legitimate basis and now try to silence critics.' The informant need not worry since 'every information that could be used to identify him' is protected against unauthorized access by strong encryption. The Trojan is supposedly capable of eavesdropping on Skype conversations and obtaining technical details of the Skype client being used. It is deployed by e-mail or in place by the police. A Pirate Party spokesman said, 'Some of our officials seem to want to install the Big Brother state without the knowledge of the public.'"

hackingbear writes "According to a report by Hong Kong newspaper Mingpao Daily (poor Google translation), quoting the Director of Jiuquan Launch Center, China is set to build a space station by snapping together four spaceships (Shenzhou 7, 8, 9, and 10), to be launched sequentially. Though other reports indicates that taikonauts abroad SZ 7 will return to Earth on September 28, the official said the ship will remain in the orbit to be docked with unmanned Shenzhou 8 and 9. Finally, the manned spaceship Shenzhou 10 will be launched and dock with the other three, completing the space station." A story at Space.com also briefly mentions Shenzhous 8 and 9 (with no mention of number 10), and adds that China has selected its first spacewalker.

chromoZ writes with word that because of the serial blasts in Indian cities (and terrorist outfits claiming responsibility via email, often sent via Cyber Cafes and open Wi-Fi spots), sharing unsecured wireless access may get much tougher in India: "The Telecom Regulatory Authority of India (TRAI) after studying open Wifi networks is coming up with a set of guidelines and recommendations to secure them. 'All ISPs may be instructed to ensure that their subscribers using wireless devices must use effective authentication mechanisms and permit access to internet to only authorised persons using wireless devices.' An open Wi-Fi could be as much as illegal in India after this."

vimm writes "Senator Herb Kohl (D-Wis.) has started an inquiry on the rising prices of text messaging (up 100% since 2005) that has occurred almost in sync with the consolidation of 6 major carriers down to 4. In a letter sent to Verizon Wireless, AT&T, Sprint Nextel, and T-Mobile, Kohl said the increase 'does not appear to be justified by rising costs in delivering text messages.'"

SenFo writes "To many of the people who downloaded Google Chrome last week, it was a surprise to observe that each opened tab runs in a separate process rather than a separate thread. Scott Hanselman, Lead Program Manager at Microsoft, discusses some of the benefits of running in separate processes as opposed to separate threads. A quote: 'Ah! But they're slow! They're slow to start up, and they are slow to communicate between, right? Well, kind of, not really anymore.'"

hhavensteincw writes "On Monday Google detailed new plans to digitize millions of newspaper pages with articles, photographs, and headlines intact so they can be accessed and searched online. 'Around the globe, we estimate that there are billions of news pages containing every story ever written,' Google said in a blog post. 'It's our goal to help readers find all of them, from the smallest local weekly paper up to the largest national daily.' For example, Google noted the availability of an original article from the Pittsburgh Post-Gazette from 1969 about the landing on the moon." When you search the news archive for, e.g., "Chicago fire" or "Rosenberg trial," a significant fraction of the result pages cost money to view.

hhavensteincw writes "On Monday Google detailed new plans to digitize millions of newspaper pages with articles, photographs, and headlines intact so they can be accessed and searched online. 'Around the globe, we estimate that there are billions of news pages containing every story ever written,' Google said in a blog post. 'It's our goal to help readers find all of them, from the smallest local weekly paper up to the largest national daily.' For example, Google noted the availability of an original article from the Pittsburgh Post-Gazette from 1969 about the landing on the moon." When you search the news archive for, e.g., "Chicago fire" or "Rosenberg trial," a significant fraction of the result pages cost money to view.

tonsofpcs writes "On Monday, September 8, Wilmington, NC will be the first television market (#135) to make the switch to DTV by shutting off their analog transmitters. This forum will be posting updates throughout the coming months to keep everyone updated on how the transition works so that we are all prepared come February 17, 2009. So far, it seems Wilmington will still be going ahead as planned, despite Tropical Storm Hanna's proximity."

angelheaded tips a Wired story about the resignation of Bob Dykes, CEO of net eavesdropping firm NebuAd. NebuAd has encountered financial troubles lately as the privacy controversy surrounding the company's tracking methods has driven communications companies away. Over in the UK, Phorm responded to the NebuAd news by affirming that it is making progress with its advertising methods. From The Register: "In response to the outcry over our revealing its two secret trials, BT said in April it would re-engineer the planned deployment so traffic to and from customers who do not want their web use profiled for marketing purposes would not come into contact with the Phorm system. The original blueprint meant that a opt-out cookie would tell the technology to simply ignore refuseniks' browsing as it passed through. It's thought the change has proved tricky. Phorm did not immediately respond to a request for comment on the alleged technical problems, but [BT's chief press officer Adam Liversage] said: 'We have been working on some things with Phorm.'"

centuren writes "In response to the reaction to Chrome's terms of service, Google has truncated the offending Section 11, apologizing for the oversight. The new Section 11 contains only the first sentence included in their Universal Terms of Service, now stating: 'You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services.'"

nicholas.m.carlson writes "According to these five terms of service and EULA, Google owns any content you create using its Chrome browser and can filter your Gmail messages if it likes. Facebook says it can sell its users' uploaded images as stock photography. YouTube can keep footage of your kids forever, even after you've deleted it from the site. And AOL can ban you for using vulgar language on AIM. Funny, right? That's why Valleywag calls them 'The 5 most laughable terms of service on the Net.'" Reader dlaudel writes, regarding the previously-mentioned Google EULA for Chrome, "According to Ars Technica, Google's EULA for Chrome was just copy-and-pasted from its EULA for other services, a practice that is apparently common at Google."

nicholas.m.carlson writes "According to these five terms of service and EULA, Google owns any content you create using its Chrome browser and can filter your Gmail messages if it likes. Facebook says it can sell its users' uploaded images as stock photography. YouTube can keep footage of your kids forever, even after you've deleted it from the site. And AOL can ban you for using vulgar language on AIM. Funny, right? That's why Valleywag calls them 'The 5 most laughable terms of service on the Net.'" Reader dlaudel writes, regarding the previously-mentioned Google EULA for Chrome, "According to Ars Technica, Google's EULA for Chrome was just copy-and-pasted from its EULA for other services, a practice that is apparently common at Google."

eldavojohn writes "If you use Picasa (Google's photo sharing site), they have upgraded to 3.0 and are purportedly offering facial recognition. That's right, why tag photos of your friends when the software will group similar faces together for you? There's a new list of features including repairing old photographs by touching them up and even writing on your images. As expected, not everyone is 'ok' with Google automatically recognizing you in pictures."

Nathan Halverson writes "California claims copyright to its laws, and warns people not to share them. And that's not sitting right with Internet gadfly, and open-access hero, Carl Malamud. He has spent the last couple months scanning tens of thousands of pages containing city, county and state laws — think building codes, banking laws, etc. Malamud wants California to sue him, which is almost a given if the state wants to continue claiming copyright. He thinks a federal court will rule in his favor: It is illegal to copyright the law since people are required to know it. Malamud helped force the SEC to put corporate filings online in 1994, and did the same with the patent office. He got the Smithsonian to loosen its claim of copyright, CSPAN to stop forbidding people from sharing its videos, and most recently Oregon to quit claiming copyright on state laws." Malamud's talk at Google ("All the Government's Information") is also well worth watching.

Consumerist reports an Associated Press release that Steve Warshak, 42, was found guilty of 93 counts of conspiracy, fraud and money laundering. His 75-year-old mother, who has cancer, was found guilty of conspiracy and other charges, and was sentenced to 2-years, but is free pending appeal. US District Judge Arthur Spiegel, in Cincinnati, OH, denied Mr. Warshak's request to remain free pending appeal, but gave him 30 days to wrap up his affairs and report to prison. Besides Enzyte, Washak's company, Berkeley Premium Nutraceuticals, who also distributes products to boost energy, manage weight, reduce memory loss and aid sleep, will be allowed to stay in business — but must forfeit $500 million. Among their most egregious offenses was a requirement of a Notarized statement from a doctor certifying that they had a small penis. Amazingly, remarkably few customers availed themselves of the refund offer. Unfortunately, it looks like the commercials will still be able to continue...

Philipp Lenssen writes "Google announced their very own browser project called Google Chrome — an announcement in the form of a comic book drawn by Scott McCloud, no less. Google says Google Chrome will be open source, include a new JavaScript virtual machine, include the Google Gears add-on by default, and put the tabs above the address bar (not below), among other things. I've also uploaded Google's comic book with all the details (details given from Google's perspective, anyway... let's see how this holds up). While Google provided the URL www.google.com/chrome there's nothing up there yet."

J.Tatar and a number of other readers alert us to the shooting death of an anti-government webmaster while in police custody in Ingushetiya, a volatile province in southern Russia. Police took Ingushetiya.ru owner Magomed Yevloyev off a plane that had just landed in Ingushetiya. "Yevloyev ... was a prominent opponent of the pro-Kremlin president of Ingushetia, Murat Zyazikov [a close ally of Russian Prime Minister Vladimir Putin]. Prosecutors have opened a preliminary manslaughter investigation after Yevloyev was shot in a police car in Narzan, the capital of volatile Ingushetia, a mostly Muslim region that borders Chechnya, Russian media reported. A spokesman for the prosecutor's office, Vladimir Markin, said 'an incident' took place after Yevloyev was taken into a police car 'resulting in a shooting injury to the head and he later died in hospital,' Interfax reported."

An anonymous reader writes "A group of Canadian engineering students was one of 10 teams to win a $275,000 prize from internet search giant Google Inc. Their program, Ecorio, gives users the ability to reduce their environmental footprint with tools that provide transit options for trips, invest in carbon reduction projects, and share their tips with other users. Other winners included a taxi location app, a price comparison app, and a settings manager than changes your settings based on your location." Google has also started talking about their plans for Android Market, which is similar to the App store used for the iPhone. Ars Technica's coverage points out a blog post by Google's Eric Chu which notes that early handsets running Android will have a beta version of Android Market enabled.

CWmike writes "As Hurricane Gustav approaches the US Gulf Coast, IT lessons learned from the devastating Hurricanes Katrina and Rita that smashed New Orleans and other areas in 2005 are on the minds of many worried IT managers. David Avgikos, president of Digimation Inc., a 3-D digital animation software company in St. Rose, Louisiana, said, 'We don't have to be told twice.' Meanwhile, the nation's major cellular network providers say that they too are prepared, having learned from the devastation of Hurricane Katrina. Still, they offer some helpful tips for dealing with what is expected to be a category-three hurricane when it hits: use text vs. calling on your cell phone, and if you use a cordless for your landline, ditch it for a corded model so that it will still work if there are power outages."

CWmike writes "Google looks as if it's on top of the world right now, holding an ever-increasing lion's share of the search market. So why do I think it's lost its mojo? Let's start with the way it treats its employees, writes Preston Gralla. Another example: Google employees, such as Sergey Solyanik, have started deserting the company. And its share price is down double that of the Dow or Nasdaq since November 2007. Even if Google has lost its mojo, why should you care? It won't make your searches any less effective, will it? Nope. But Google has its eyes on bigger things than search, notably your IT department. It's looking to displace Microsoft with hosted services like Google Apps, Gmail and Google Docs. Solyanik warns that Google's engineers care more about the 'coolness' of a service than about the service's effectiveness." Of course Google employees version of being mistreated is often laughable, and quite a shock when they look for their massage therapist at wherever they end up next.

I Don't Believe in Imaginary Property writes "Attorney General Michael Mukasey has agreed to allow Congressional hearings, but not to delay, the implementation of new FBI regulations that would allow them to spy on American citizens who are not suspected of any crime. As an editorial in the New York Times points out, this is a power that has a history of abuse. In times past, it was used to wiretap Rev. Martin Luther King, Jr. and to spy on other civil rights and anti-war protesters." As Dekortage points out, "Several senators have formally complained that citizens could be investigated 'without any basis for suspicion,' which the Justice Department denies."

SkeptOlympics writes "A new chapter in the ongoing controversy surrounding China's women's gymnastics team opened today, as search engine hacker stryde.hax found surviving copies of official registration documents issued by China's General Administration of Sport of China. The incriminating documents, expunged by censors from the official site and from Google's document cache, still appear in the document translation cache of Chinese search giant Baidu, here (1) and here (2), showing the age of one of China's gold medal winning gymnasts to be 14 instead of 16, the minimum age for competition presented on her government-issued passport. Now that official government documentation is available, how long will the IOC be able to keep a lid on this scandal?" I imagine the answer is "Forever."

Davide Marney passes along an AP story about the thousands of voting machines gathering dust in warehouses across the country after states such as California, Ohio, and Florida have banned their use. Many of these machines cost $3.5K to $5K each. Local election boards are struggling to find ways to recover any of the cost of the machines, or even to recycle them. The picture in Ohio is the most confusing, as multiple court cases limit the state's options and result in a situation in which the discredited machines will nevertheless be used in the presidential election coming up in November. The state's new (Democratic) attorney general has just issued a rule banning the practice of election workers taking the machines home with them the night before elections.

Cycon writes "Google has announced, 'We're releasing a beta SDK. You can read about the new Android 0.9 SDK beta at the Android Developers' Site, or if you want to get straight to the bits, you can visit the download page.' A new Development Roadmap has also been released to help developers understand the direction the software is taking (as this is still only a Beta release). In addition, the FCC has approved the HTC Dream, and it is believed Google and T-Mobile will launch the phone in the US on November 10, since a confidentiality request attached to the application asks the FCC to keep details secret until that date."

Cycon writes "Google has announced, 'We're releasing a beta SDK. You can read about the new Android 0.9 SDK beta at the Android Developers' Site, or if you want to get straight to the bits, you can visit the download page.' A new Development Roadmap has also been released to help developers understand the direction the software is taking (as this is still only a Beta release). In addition, the FCC has approved the HTC Dream, and it is believed Google and T-Mobile will launch the phone in the US on November 10, since a confidentiality request attached to the application asks the FCC to keep details secret until that date."

Cycon writes "Google has announced, 'We're releasing a beta SDK. You can read about the new Android 0.9 SDK beta at the Android Developers' Site, or if you want to get straight to the bits, you can visit the download page.' A new Development Roadmap has also been released to help developers understand the direction the software is taking (as this is still only a Beta release). In addition, the FCC has approved the HTC Dream, and it is believed Google and T-Mobile will launch the phone in the US on November 10, since a confidentiality request attached to the application asks the FCC to keep details secret until that date."

Hugh Pickens writes "John Tierney poses the question in the New York Times 'what if we let athletes do whatever they wanted to excel?' Before you dismiss the notion, consider what we're stuck with today — a system designed to create a level playing field, protect athletes' health and set an example for children, that fails on all counts. The journal Nature, in an editorial in the current issue, complains that 'antidoping authorities have fostered a sporting culture of suspicion, secrecy and fear' by relying on unscientifically calibrated tests, like the unreliable test for synthetic testosterone that cost Floyd Landis his 2006 Tour de France victory and even if the authorities manage to correct their tests, they can't possibly keep up with the accelerating advances in biology." Read on for more. Hugh Pickens continues: "Bengt Kayser, the director of a sports medicine institute at the University of Geneva argues in an article that has been supported by more than 30 scholars in the British Medical Journal that legalizing doping would "encourage more sensible, informed use of drugs in amateur sport, leading to an overall decline in the rate of health problems associated with doping (pdf). In the competition between increasingly sophisticated doping — e.g. gene transfer — and antidoping technology, there will never be a clear winner. Consequently, such a futile but expensive strategy is difficult to defend.""

Two days ago, an AP interview with Cryptic Studios' Jack Emmert provided new details about Star Trek: Online, which was lost in developmental limbo for quite some time. Today, Cryptic released a game-play trailer and a forty-minute webcast discussing the game.

Yes, some US IT jobs are disappearing, but Linux.com (which shares a corporate overlord with Slashdot) has a recent story emphasizing the job advantage that involvement in open source projects can give young programmers who aren't planning to ditch their dreams of making a living in the field. The article focuses on one programmer's experience with Google's Summer of Code, which led directly to her job working on the Drupal content-management system. But the underlying message (that involvement in open source projects provides a background of experience otherwise difficult to obtain because of the chicken-and-egg problem of "experience required" job opportunities) is generalizable to many other forms of open-source involvement. Do you have a job that you landed because of your unpaid open-source programming?

A number of readers are sending in links to a video from the Fortune Brainstorm Tech conference last month, in which Lawrence Lessig recounts a conversation over dinner with Richard Clarke, the former government counter-terrorism czar. Remembering that the Patriot Act was dropped on Congress just 20 days after 9/11 — the Department of Justice had had it sitting in a drawer for years — Lessig asked Clarke if DoJ had a similar proposed law, an "i-Patriot Act," to drop in the event of a "cyber-9/11." Clarke responded, "Of course they do. And Vint Cerf won't like it." Lessig's anecdote begins at about 4:30 in the video.

Ian Lamont writes "The Industry Standard reports that Dell is trying to trademark the term cloud computing . The phrase entered the tech lexicon years ago, but Dell's application (serial number 77139082) was made in early 2007 to the US Patent and Trademark Office, apparently in connection with data center products and services that it was promoting around that time. A quick search of Google News indicates that Dell itself did not use the term in press releases or discussions with indexed English-language media sources from 1996 to 2006. Dell is not the first company to attempt to trademark this term: The Standard notes that NetCentric, a company that provided 'carrier-class Internet fax technology,' also gave it a shot in the late 1990s, but was rejected."

(0d0 writes "Some researchers at Columbia University's Computer Vision Labratory have developed software to automatically replace faces in batches of photos. Practical applications include protecting the identities of people in Google's Street View, coupling it with a digital camera's burst mode to create a perfect group photo, or protecting the identities of witnesses or law enforcement and military personnel. Other links to coverage include Boing Boing, American Public Media, and New Scientist."

Frosty Piss writes "Foreign-owned hotels in China face the prospect of 'severe retaliation' if they refuse to install government software that can spy on Internet use by hotel guests coming to watch the summer Olympic games. Republican Senator Sam Brownback produced a translated version of a document from China's Public Security Bureau that requires hotels to use the monitoring equipment. The Public Security Bureau order threatens that failure to comply could result in financial penalties, suspending access to the Internet or the loss of a license to operate a hotel in China. The policy was designed to 'ensure the smooth opening' of the Olympics, as well as 'promote the healthy and orderly development of the Internet, safeguard state security, maintain social order and protect public interests,' the translation of the one of the documents read."

jamie writes "The politicization of Bush's Justice Department, which this week was officially determined to be illegal, has a funny side too. Sometime in 2005-2006, White House Liaison Jan Williams attended a seminar on LexisNexis searches, and wrote one herself. When she left, she passed it on to her successor Monica Goodling in an email. Justin Mason, author of SpamAssassin, is skeptical about its accuracy:

[First name of a candidate]! and pre/2 [last name of a candidate] w/7 bush or gore or republican! or democrat! or charg! or accus! or criticiz! or blam! or defend! or iran contra or clinton or spotted owl or florida recount or sex! or controvers! or racis! or fraud! or investigat! or bankrupt! or layoff! or downsiz! or PNTR or NAFTA or outsourc! or indict! or enron or kerry or iraq or wmd! or arrest! or intox! or fired or sex! or racis! or intox! or slur! or arrest! or fired or controvers! or abortion! or gay! or homosexual! or gun! or firearm!

Needless to say, when asked about it, Williams first said she didn't remember ever seeing it, then said she'd used an edited version just once. LexisNexis records show she used it, as shown, 25 times." Note that 'sex!' appears twice in the query. Must be VERY important.

AmericanInKiev writes "Computer World posted a piece on Al Gore and his claim that solar cells will improve at the same rate as microprocessors. Vinod Khosla on the other hand has expressed disappointment that the doubling rate for price/performance of PV is 10 years rather than 18 months for transistors. Which of these two has the facts on their side?" Before anyone has him inventing the Internet again, note that Gore's claim as related in the article is much milder than that Moore's Law applies to solar cells per se -- namely, he's quoted as saying "We're now beginning to see the same kind of sharp cost reductions as the demand grows for solar cells." An optimistic statement, but not a flat-out silly one.

mi writes "The Academy of Motion Pictures Arts has won a judgment compelling Craigslist to reveal the identity of 'Daniel,' who tried to sell two tickets to the Oscar ceremony recently. The plaintiff's argument against such sales is scary and can be taken very far very quickly: 'If you don't know who's inside the theater, it's very difficult to provide security.' Craigslist's handling of the case may be even scarier, however — instead of fighting tooth-and-nail for the user's privacy, as we expect Google, Yahoo, and AOL, and even credit-card issuers to do, Craigslist simply did not show up in court and lost by default."

Many readers are sending in word that Randy Pausch has died at 47. The charismatic young college professor celebrated life despite a death sentence from pancreatic cancer in a remarkable speech widely known as the "Last Lecture." The video went viral and has been downloaded by over 10 million people.

RevWaldo contributes a link to an AP story carried by Google, according to which "The head of a prominent cancer research institute issued an unprecedented warning to his faculty and staff Wednesday: Limit cell phone use because of the possible risk of cancer. The warning from Dr. Ronald B. Herberman, director of the University of Pittsburgh Cancer Institute, is contrary to numerous studies that don't find a link between cancer and cell phone use, and a public lack of worry by the U.S. Food and Drug Administration." RevWaldo continues: "One possible solution offered? 'Use a wireless headset.' No risk of EM exposure from one of them, no sirree!"

Brian Jordan and other readers sent in word that Google has taken the wraps off Knol, its expert-written challenger to Wikipedia. (We discussed Knol when it was announced last year.) Wired has an in-depth look. Knol's distinctions from Wikipedia are that authors are identified by their real names (and verified), and that they can share in ad revenue if they choose to. The service initially features a lot of medical articles, which is interesting considering that Medipedia also launched today. This medical wiki is backed by Harvard's and Stanford's medical schools.

99luftballon writes "The British Museum is putting online the remaining fragments of the world's oldest Bible. The Codex Sinaiticus dates to the fourth century BCE and was discovered in the 19th century. Very few people have seen it due to its fragile state — that and the fact that parts of it are in collections scattered across the globe. It'll give scholars and those interested their first chance to take a look. However, I've got a feeling that some people won't be happy to see it online, since it makes no mention of the resurrection, which is a central part of Christian belief."On Thursday the Book of Psalms and the Gospel According to Mark will go live at the Codex Sinaiticus site. The plan is to have all the material up, with translations and commentaries, a year from now.

I Don't Believe in Imaginary Property writes "A Florida patent troll called Channel Intelligence is suing everyone from Lemonade to Remember the Milk for infringing on patent 6,917,941, which covers storing a wishlist in a database. Amazon and eBay are absent from the list of targets, even though they very likely store users' wishlists in a database. With any luck, perhaps one of the defendants will get to use that precedent PJ found the other day from In re Lintner, which said, '[c]laims which are broad enough to read on obvious subject matter are unpatentable even though they also read on non-obvious subject matter.'"