Slashdot Mirror

mjasay writes "IDC has released a report looking into industry adoption of open software. In the study, analyst Matt Lawton stumbles across an intriguing trend: IT departments do most of the services around open source, rather than third-party consulting companies. While IDC believes this is a bad thing, the data in the report suggests otherwise. 70% of the enterprises surveyed did their own implementations, while roughly 90% supported their own open-source deployments. This might be a cause for alarm if the projects weren't so successful: 70% of the projects were deemed to be of "Critical" or "High Importance" compared to other IT projects and 90% plan to maintain or increase their investment in open source projects. Could it be that open source is liberating enterprises from an unhealthy dependence on vendors, and that early results suggest that this will be a Very Good Thing for the success of IT projects, many of which have failed historically."

Frequent Slashdot contributor Bennett Haselton sends in his latest, which begins like this and continues behind the link. "When Google's VP of Engineering announced their proposed Knol project, where users can submit articles on different subjects and share in the AdSense revenue from the article pages, he didn't mention "Wikipedia," but practically everyone else did who blogged about it. Here's what I think will happen, if Knol is implemented according to the plan: Even though it won't technically be a "Wikipedia fork," it will quickly become equivalent to one, with a "gold rush" of users copying content from Wikipedia to Knol articles hoping for a piece of the AdSense dollars. But I submit this will be a good thing, especially if bona fide experts in different fields join the gold rush as well and start signing their names to articles that they've vetted."
First, I've been saying for a while that someone should fork Wikipedia and start assigning "ownership" of articles to credentialed experts where possible, so that an article can be cited as a source that has been vetted by a recognized individual, and to guard against vandalism. Citizendium does something like this, but started from the ground up rather than fork Wikipedia. I argued that they should fork as much as possible from Wikipedia (having experts "bless" the content in the process); the project's official reason for not doing this was that authors are more motivated when starting with a clean slate than when taking over someone else's article. True, we all know the energizing feeling of a clean slate compared to the sluggish feeling of taking over a 50%-completed project with all of its flaws and compromises, but the "energizing feeling" often doesn't make up for the advantages of having 50% of the work already done for you (which is, in a nutshell, the only reason people ever finish 50%-completed projects instead of starting over!).

So could some other Wikipedia fork achieve the same thing? Programmer/blogger and Guardian columnist Seth Finkelstein, a frequent Wikipedia critic, has pointed out that other sites such as http://veropedia.com/ have tried to build a "verified" version of Wikipedia. "But," he writes, "it doesn't work for many reasons:

1) Maintenance
2) Nobody knows the site exists, or uses it.
3) Google will kill the site's ranking, because of "duplicate content"
4) Roughly 99% of Wikipedia's value is the Google-rank it has, and sites trying to copy its content don't have — or get — that Google-rank.

All true. But Knol has a shot at solving all of these problems. #1 should be mitigated if users earn money for maintaining articles — and besides, many articles like "Abraham Lincoln" won't need much maintenance anyway. #2 should not be an issue since it's a Google project. #3 and #4 depend on how Google lists Knol pages in its search results. The VP's blog post says only,

"Our job in Search Quality will be to rank the knols appropriately when they appear in Google search results. We are quite experienced with ranking web pages, and we feel confident that we will be up to the challenge."

Of course the question on everyone's minds, not answered directly by those sentences, is whether Knol pages will get any special treatment in search rankings. Google would probably be criticized if they manipulated the results outright. But they might achieve the same result indirectly — for example, having a tab across the top of their search results page for "Knol results," along with the tabs for Web, images, and news. Or if Knol results get killed for "duplicate content," Google might (legitimately) consider this a bug and tweak their duplicate-detection algorithm. Thus Knol would have the same advantage in Google that Microsoft's Media Player has on Windows: The operating system doesn't favor Media Player directly, but compatibility problems with Media Player will always get fixed first (while the RealPlayer people have to watch their programs get broken by Windows upgrades). One way or another, it's pretty certain that Knol results are not going to be "unfindable" on Google.

Now, I'm sure Knol will not formally fork Wikipedia. I wouldn't see any problem with them doing that, but it would be too controversial, after the VP announced it without ever mentioning "Wikipedia," and with Google already dealing with speculation that they're only creating Knol to complete with Wikipedia in their own search results. But with users having cash incentives to copy content from Wikipedia, probably most of the content would get replicated very quickly, and I would be surprised if many users didn't start writing scripts to robo-copy as much content from Wikipedia as possible.

Then you get to the point where experts start improving it. If the first couple of entries on "Physics" are just the robo-copied Wikipedia version, "signed" by users that nobody has ever heard of, this is barely an improvement over the unsigned article on Wikipedia itself. But then only one Physics professor in the entire world has to think it's worth their while to read the standard Wikipedia article, make any necessary corrections, and sign their name to it on Knol — and now you have a version that has been vetted by a credentialed expert, increasing its value many times to people who want to cite it as a source, or who want a higher degree of confidence that it's accurate. (Hopefully Knol will allow authors to confirm their e-mail addresses and display them — in an image, presumably, to stop them being scraped by spammers. This will allow professors to prove that they really have faculty .edu addresses and enhance the credibility of their articles, something I suggested for Citizendium.)

So, some criticisms of Wikipedia would not apply to Knol. Author Nick Carr has written of Wikipedia,

"Certainly, it's useful - I regularly consult it to get a quick gloss on a subject. But at a factual level it's unreliable, and the writing is often appalling. I wouldn't depend on it as a source, and I certainly wouldn't recommend it to a student writing a research paper."

When I asked if he would recommend Knol for the same purpose, he was more optimistic:

"Probably. Since a Knol would be written by an identifiable person at an identifiable point in time, I don't see why you wouldn't treat it, in doing research, in a similar way that you'd treat, say, an article by that person. Obviously, you'd need to judge the writer's expertise and authority when deciding whether or not to draw on his or her work, which becomes somewhat more problematic where no editorial or peer-review system applies, as in Knol."

This is where I think the value of a professor's .edu e-mail address comes in, which can at least establish a writer's authority in their subject. I asked Seth Finkelstein whether he would recommend Knol in those same circumstances (verified professor's .edu address, etc.), and his take was, "Of course I would, but you loaded the question in a way so as to remove any problem from it." Well, yeah. I just happen to think Knol actually could remove those problems.

Then there was a little-noticed phrase in Google's blog post that suggests another area where Knol could improve over Wikipedia: the inclusion of "how-to-fix-it instructions." Given that people often need how-to instructions a lot more badly than they need encyclopedia articles, it's surprising that there hasn't been an attempt to standardize around a "Wikipedia of how-to's." Perhaps it's because the Web itself actually does pretty well for that — type in the text of some error message, and you'll usually get some hits on support forums where people ran into the same problem. The trouble is that the ranking of search results depends on the popularity of the site, not on whether the thread ended with someone posting a solution to the problem, so you might have to read through a lot of search results to find an answer. And if you're an expert who happens to know how to do or fix something, there's not much incentive for you to post a page about it (even with AdSense ads), because your page will get buried in the search results beneath all the support forums discussing the same question, even if your post is more concise and useful. Some gurus like Dave Taylor and Leo Notenboom have written so many how-to articles that their own sites have risen through the Google rankings, so if they write a how-to article about something, it will get read (which, of course, creates an incentive for them to write more of them). But for a new expert just starting to write how-to articles, it would take a long time to reach that critical mass.

Knol, however, creates an incentive for experts to start posting how-to-fix-it advice and start reaping the rewards right away, since your how-to articles are just as easy to find under a given subject as anyone else's. Your earnings would start out small as you began to write articles, but they would rise in proportion to the number of articles you wrote, and you wouldn't have to slog along writing for no reward like a typical blogger or site creator, hoping to hit "critical mass" some day. You'd find out early on what the reward would be (financial and otherwise) for the work you were doing, and could decide if you wanted to continue.

Actually, the possibility of "instant rewards" does depend on how Knol articles are ranked against each other within a given topic. The Google blog post says, "For many topics, there will likely be competing knols on the same subject," and, "Knols will include strong community tools. People will be able to submit comments, questions, edits, additional content, and so on. Anyone will be able to rate a knol or write a review of it." Presumably the top-rated articles on a given topic will be displayed first by default, so I'm making the assumption that good articles really will get sorted to the top. But if there are already 50 articles on some topic, even if you know you can write a better one, how do you know it would rise to the top of the pile? If 10 people rate your article a 9, and all the other articles have been rated by 100 people each and got an average rating of a 7, then yours should still be listed as the highest in terms of average rating. But how do you get even those first 10 people to see your article? You could invite your friends, but then how do you stop anyone from gaming the system by inviting their friends and asking them all to rate their article a 10?

I'd written about this in the context of whether Wikia Search might try to solve these problems by allowing users to vote on search results, if they could prevent people from gaming the system. That was basically just me thinking out loud that something like that would be cool, before Wikia Search announced any specifics, and I haven't heard that Wikia is trying anything like that. But now that Google has stated that they will use voting and ranking systems in Knol, the question is how to reward new authors while preventing cheating. I suggested some ideas in an article about how to stop cheating and vote-buying on digg. One idea was that you could have a section on the page that showed people links to different articles at random, so that users couldn't self-select on what articles were shown to them, and if those randomly selected users followed the links and voted on the articles, count only those votes in determining the true "rating" of an article. (This is what HotOrNot does for people's picture ratings.) Even if few people rated those articles, the ratings that were collected, would be representative of real users, and not the horde of friends that you'd sent to rate your article. If that did not prove popular enough, then you could give authors the option to pay random users to rate their articles — as long as there was no way for authors to tie payment to higher ratings, the ratings would average out to reflect the article quality, and could be used to sort articles based on their actual merits.

So, I'd like to think that someone in the Googleplex is reading everything I write, but it's probably just a case where great nerds think alike. I wrote in Feb 07 that I thought Citizendium should allow authors to put their name next to articles, both for the "name up in lights" incentives factor and to enhance the article's credibility, and now Knol is going to do that (not to mention throwing in money as well). The same month I wrote that someone should build a search engine that groups together user-submitted articles under different topics, and provides a means for newly submitted articles to rise through the ranks as a result of user votes, and it sounds like Knol will attempt that too. Then in April 07 I wrote about the ways that you could prevent cheating in such a system, and even though Knol hasn't talked about what they will do to address that problem, they're almost certainly thinking about it, and have probably come up with some of the same ideas.

So let's do a test to find out if Google is reading these articles. There's one area where Wikipedia would beat Knol, and that is that everything on Wikipedia can be redistributed for free. That's something really special, and it's the one part of the Wikipedia hype that I actually buy into. I don't really care that Wikipedia articles were created as part of a "worldwide collaborative effort" unless that helps to achieve the goal of being useful. But Wikipedia, for all its flaws, represents the first time in human history that we have a compendium of a huge amount of human knowledge that can be copied freely, that literally belongs to the world, and because it's duplicated in so many places, it can literally never be taken away. That part of the hype really is true, and is quite heady when you think about it.

Google Knol has not declared this as one of their goals; a Knol article might not be freely distributable. When a proprietary project is hosted on a private site, there's always the risk that the company will pull the plug on it. They probably won't pull off the content offline, but they might shut the service down to stop new content from being added, the way Google did with Google Answers. Yes, Knol authors will retain ownership of their writings, so they could try to regroup and continue the project somewhere else, but it would be a huge mess to try and contact all of the authors and get their permission to copy all of their articles to the new location. As currently planned, Knol doesn't "belong the world," and Google never promised not to take it away.

So, I think that Google Knol should include a feature whereby authors can flag their articles as being freely distributable under the same terms as Wikipedia articles. (Any author who copied an article from Wikipedia and submitted it, would be required to set this flag, because under the terms of "copyleft", you can't copy something that's freely copyable and then try to stop others from copying it!) Then a user who wanted a copylefted, freely distributable article, could limit their search to articles that have this flag set. This would give Knol the best of both worlds: if the author of the top-ranked article did not wish for it to be freely redistributable, then they wouldn't put it on Wikipedia, but they could make it available on Knol, and users could choose either the top-ranked copylefted article or the top-ranked article overall, depending on what they wanted. If the best article on a given subject also happened to be flagged freely distributable, then so much the better.

Maybe the Knol people have had this idea already. But even so, if they end up implementing it, then I'm starting right away on articles about how Google should implement Google Anti-Censorware, Google Site Hijack Prevention, Google Security Compensation, and Google Sergey And Larry Give Bennett Their Airplane.

Frequent Slashdot contributor Bennett Haselton sends in his latest, which begins like this and continues behind the link. "When Google's VP of Engineering announced their proposed Knol project, where users can submit articles on different subjects and share in the AdSense revenue from the article pages, he didn't mention "Wikipedia," but practically everyone else did who blogged about it. Here's what I think will happen, if Knol is implemented according to the plan: Even though it won't technically be a "Wikipedia fork," it will quickly become equivalent to one, with a "gold rush" of users copying content from Wikipedia to Knol articles hoping for a piece of the AdSense dollars. But I submit this will be a good thing, especially if bona fide experts in different fields join the gold rush as well and start signing their names to articles that they've vetted."
First, I've been saying for a while that someone should fork Wikipedia and start assigning "ownership" of articles to credentialed experts where possible, so that an article can be cited as a source that has been vetted by a recognized individual, and to guard against vandalism. Citizendium does something like this, but started from the ground up rather than fork Wikipedia. I argued that they should fork as much as possible from Wikipedia (having experts "bless" the content in the process); the project's official reason for not doing this was that authors are more motivated when starting with a clean slate than when taking over someone else's article. True, we all know the energizing feeling of a clean slate compared to the sluggish feeling of taking over a 50%-completed project with all of its flaws and compromises, but the "energizing feeling" often doesn't make up for the advantages of having 50% of the work already done for you (which is, in a nutshell, the only reason people ever finish 50%-completed projects instead of starting over!).

So could some other Wikipedia fork achieve the same thing? Programmer/blogger and Guardian columnist Seth Finkelstein, a frequent Wikipedia critic, has pointed out that other sites such as http://veropedia.com/ have tried to build a "verified" version of Wikipedia. "But," he writes, "it doesn't work for many reasons:

1) Maintenance
2) Nobody knows the site exists, or uses it.
3) Google will kill the site's ranking, because of "duplicate content"
4) Roughly 99% of Wikipedia's value is the Google-rank it has, and sites trying to copy its content don't have — or get — that Google-rank.

All true. But Knol has a shot at solving all of these problems. #1 should be mitigated if users earn money for maintaining articles — and besides, many articles like "Abraham Lincoln" won't need much maintenance anyway. #2 should not be an issue since it's a Google project. #3 and #4 depend on how Google lists Knol pages in its search results. The VP's blog post says only,

"Our job in Search Quality will be to rank the knols appropriately when they appear in Google search results. We are quite experienced with ranking web pages, and we feel confident that we will be up to the challenge."

Of course the question on everyone's minds, not answered directly by those sentences, is whether Knol pages will get any special treatment in search rankings. Google would probably be criticized if they manipulated the results outright. But they might achieve the same result indirectly — for example, having a tab across the top of their search results page for "Knol results," along with the tabs for Web, images, and news. Or if Knol results get killed for "duplicate content," Google might (legitimately) consider this a bug and tweak their duplicate-detection algorithm. Thus Knol would have the same advantage in Google that Microsoft's Media Player has on Windows: The operating system doesn't favor Media Player directly, but compatibility problems with Media Player will always get fixed first (while the RealPlayer people have to watch their programs get broken by Windows upgrades). One way or another, it's pretty certain that Knol results are not going to be "unfindable" on Google.

Now, I'm sure Knol will not formally fork Wikipedia. I wouldn't see any problem with them doing that, but it would be too controversial, after the VP announced it without ever mentioning "Wikipedia," and with Google already dealing with speculation that they're only creating Knol to complete with Wikipedia in their own search results. But with users having cash incentives to copy content from Wikipedia, probably most of the content would get replicated very quickly, and I would be surprised if many users didn't start writing scripts to robo-copy as much content from Wikipedia as possible.

Then you get to the point where experts start improving it. If the first couple of entries on "Physics" are just the robo-copied Wikipedia version, "signed" by users that nobody has ever heard of, this is barely an improvement over the unsigned article on Wikipedia itself. But then only one Physics professor in the entire world has to think it's worth their while to read the standard Wikipedia article, make any necessary corrections, and sign their name to it on Knol — and now you have a version that has been vetted by a credentialed expert, increasing its value many times to people who want to cite it as a source, or who want a higher degree of confidence that it's accurate. (Hopefully Knol will allow authors to confirm their e-mail addresses and display them — in an image, presumably, to stop them being scraped by spammers. This will allow professors to prove that they really have faculty .edu addresses and enhance the credibility of their articles, something I suggested for Citizendium.)

So, some criticisms of Wikipedia would not apply to Knol. Author Nick Carr has written of Wikipedia,

"Certainly, it's useful - I regularly consult it to get a quick gloss on a subject. But at a factual level it's unreliable, and the writing is often appalling. I wouldn't depend on it as a source, and I certainly wouldn't recommend it to a student writing a research paper."

When I asked if he would recommend Knol for the same purpose, he was more optimistic:

"Probably. Since a Knol would be written by an identifiable person at an identifiable point in time, I don't see why you wouldn't treat it, in doing research, in a similar way that you'd treat, say, an article by that person. Obviously, you'd need to judge the writer's expertise and authority when deciding whether or not to draw on his or her work, which becomes somewhat more problematic where no editorial or peer-review system applies, as in Knol."

This is where I think the value of a professor's .edu e-mail address comes in, which can at least establish a writer's authority in their subject. I asked Seth Finkelstein whether he would recommend Knol in those same circumstances (verified professor's .edu address, etc.), and his take was, "Of course I would, but you loaded the question in a way so as to remove any problem from it." Well, yeah. I just happen to think Knol actually could remove those problems.

Then there was a little-noticed phrase in Google's blog post that suggests another area where Knol could improve over Wikipedia: the inclusion of "how-to-fix-it instructions." Given that people often need how-to instructions a lot more badly than they need encyclopedia articles, it's surprising that there hasn't been an attempt to standardize around a "Wikipedia of how-to's." Perhaps it's because the Web itself actually does pretty well for that — type in the text of some error message, and you'll usually get some hits on support forums where people ran into the same problem. The trouble is that the ranking of search results depends on the popularity of the site, not on whether the thread ended with someone posting a solution to the problem, so you might have to read through a lot of search results to find an answer. And if you're an expert who happens to know how to do or fix something, there's not much incentive for you to post a page about it (even with AdSense ads), because your page will get buried in the search results beneath all the support forums discussing the same question, even if your post is more concise and useful. Some gurus like Dave Taylor and Leo Notenboom have written so many how-to articles that their own sites have risen through the Google rankings, so if they write a how-to article about something, it will get read (which, of course, creates an incentive for them to write more of them). But for a new expert just starting to write how-to articles, it would take a long time to reach that critical mass.

Knol, however, creates an incentive for experts to start posting how-to-fix-it advice and start reaping the rewards right away, since your how-to articles are just as easy to find under a given subject as anyone else's. Your earnings would start out small as you began to write articles, but they would rise in proportion to the number of articles you wrote, and you wouldn't have to slog along writing for no reward like a typical blogger or site creator, hoping to hit "critical mass" some day. You'd find out early on what the reward would be (financial and otherwise) for the work you were doing, and could decide if you wanted to continue.

Actually, the possibility of "instant rewards" does depend on how Knol articles are ranked against each other within a given topic. The Google blog post says, "For many topics, there will likely be competing knols on the same subject," and, "Knols will include strong community tools. People will be able to submit comments, questions, edits, additional content, and so on. Anyone will be able to rate a knol or write a review of it." Presumably the top-rated articles on a given topic will be displayed first by default, so I'm making the assumption that good articles really will get sorted to the top. But if there are already 50 articles on some topic, even if you know you can write a better one, how do you know it would rise to the top of the pile? If 10 people rate your article a 9, and all the other articles have been rated by 100 people each and got an average rating of a 7, then yours should still be listed as the highest in terms of average rating. But how do you get even those first 10 people to see your article? You could invite your friends, but then how do you stop anyone from gaming the system by inviting their friends and asking them all to rate their article a 10?

I'd written about this in the context of whether Wikia Search might try to solve these problems by allowing users to vote on search results, if they could prevent people from gaming the system. That was basically just me thinking out loud that something like that would be cool, before Wikia Search announced any specifics, and I haven't heard that Wikia is trying anything like that. But now that Google has stated that they will use voting and ranking systems in Knol, the question is how to reward new authors while preventing cheating. I suggested some ideas in an article about how to stop cheating and vote-buying on digg. One idea was that you could have a section on the page that showed people links to different articles at random, so that users couldn't self-select on what articles were shown to them, and if those randomly selected users followed the links and voted on the articles, count only those votes in determining the true "rating" of an article. (This is what HotOrNot does for people's picture ratings.) Even if few people rated those articles, the ratings that were collected, would be representative of real users, and not the horde of friends that you'd sent to rate your article. If that did not prove popular enough, then you could give authors the option to pay random users to rate their articles — as long as there was no way for authors to tie payment to higher ratings, the ratings would average out to reflect the article quality, and could be used to sort articles based on their actual merits.

So, I'd like to think that someone in the Googleplex is reading everything I write, but it's probably just a case where great nerds think alike. I wrote in Feb 07 that I thought Citizendium should allow authors to put their name next to articles, both for the "name up in lights" incentives factor and to enhance the article's credibility, and now Knol is going to do that (not to mention throwing in money as well). The same month I wrote that someone should build a search engine that groups together user-submitted articles under different topics, and provides a means for newly submitted articles to rise through the ranks as a result of user votes, and it sounds like Knol will attempt that too. Then in April 07 I wrote about the ways that you could prevent cheating in such a system, and even though Knol hasn't talked about what they will do to address that problem, they're almost certainly thinking about it, and have probably come up with some of the same ideas.

So let's do a test to find out if Google is reading these articles. There's one area where Wikipedia would beat Knol, and that is that everything on Wikipedia can be redistributed for free. That's something really special, and it's the one part of the Wikipedia hype that I actually buy into. I don't really care that Wikipedia articles were created as part of a "worldwide collaborative effort" unless that helps to achieve the goal of being useful. But Wikipedia, for all its flaws, represents the first time in human history that we have a compendium of a huge amount of human knowledge that can be copied freely, that literally belongs to the world, and because it's duplicated in so many places, it can literally never be taken away. That part of the hype really is true, and is quite heady when you think about it.

Google Knol has not declared this as one of their goals; a Knol article might not be freely distributable. When a proprietary project is hosted on a private site, there's always the risk that the company will pull the plug on it. They probably won't pull off the content offline, but they might shut the service down to stop new content from being added, the way Google did with Google Answers. Yes, Knol authors will retain ownership of their writings, so they could try to regroup and continue the project somewhere else, but it would be a huge mess to try and contact all of the authors and get their permission to copy all of their articles to the new location. As currently planned, Knol doesn't "belong the world," and Google never promised not to take it away.

So, I think that Google Knol should include a feature whereby authors can flag their articles as being freely distributable under the same terms as Wikipedia articles. (Any author who copied an article from Wikipedia and submitted it, would be required to set this flag, because under the terms of "copyleft", you can't copy something that's freely copyable and then try to stop others from copying it!) Then a user who wanted a copylefted, freely distributable article, could limit their search to articles that have this flag set. This would give Knol the best of both worlds: if the author of the top-ranked article did not wish for it to be freely redistributable, then they wouldn't put it on Wikipedia, but they could make it available on Knol, and users could choose either the top-ranked copylefted article or the top-ranked article overall, depending on what they wanted. If the best article on a given subject also happened to be flagged freely distributable, then so much the better.

Maybe the Knol people have had this idea already. But even so, if they end up implementing it, then I'm starting right away on articles about how Google should implement Google Anti-Censorware, Google Site Hijack Prevention, Google Security Compensation, and Google Sergey And Larry Give Bennett Their Airplane.

Frequent Slashdot contributor Bennett Haselton sends in his latest, which begins like this and continues behind the link. "When Google's VP of Engineering announced their proposed Knol project, where users can submit articles on different subjects and share in the AdSense revenue from the article pages, he didn't mention "Wikipedia," but practically everyone else did who blogged about it. Here's what I think will happen, if Knol is implemented according to the plan: Even though it won't technically be a "Wikipedia fork," it will quickly become equivalent to one, with a "gold rush" of users copying content from Wikipedia to Knol articles hoping for a piece of the AdSense dollars. But I submit this will be a good thing, especially if bona fide experts in different fields join the gold rush as well and start signing their names to articles that they've vetted."
First, I've been saying for a while that someone should fork Wikipedia and start assigning "ownership" of articles to credentialed experts where possible, so that an article can be cited as a source that has been vetted by a recognized individual, and to guard against vandalism. Citizendium does something like this, but started from the ground up rather than fork Wikipedia. I argued that they should fork as much as possible from Wikipedia (having experts "bless" the content in the process); the project's official reason for not doing this was that authors are more motivated when starting with a clean slate than when taking over someone else's article. True, we all know the energizing feeling of a clean slate compared to the sluggish feeling of taking over a 50%-completed project with all of its flaws and compromises, but the "energizing feeling" often doesn't make up for the advantages of having 50% of the work already done for you (which is, in a nutshell, the only reason people ever finish 50%-completed projects instead of starting over!).

So could some other Wikipedia fork achieve the same thing? Programmer/blogger and Guardian columnist Seth Finkelstein, a frequent Wikipedia critic, has pointed out that other sites such as http://veropedia.com/ have tried to build a "verified" version of Wikipedia. "But," he writes, "it doesn't work for many reasons:

1) Maintenance
2) Nobody knows the site exists, or uses it.
3) Google will kill the site's ranking, because of "duplicate content"
4) Roughly 99% of Wikipedia's value is the Google-rank it has, and sites trying to copy its content don't have — or get — that Google-rank.

All true. But Knol has a shot at solving all of these problems. #1 should be mitigated if users earn money for maintaining articles — and besides, many articles like "Abraham Lincoln" won't need much maintenance anyway. #2 should not be an issue since it's a Google project. #3 and #4 depend on how Google lists Knol pages in its search results. The VP's blog post says only,

"Our job in Search Quality will be to rank the knols appropriately when they appear in Google search results. We are quite experienced with ranking web pages, and we feel confident that we will be up to the challenge."

Of course the question on everyone's minds, not answered directly by those sentences, is whether Knol pages will get any special treatment in search rankings. Google would probably be criticized if they manipulated the results outright. But they might achieve the same result indirectly — for example, having a tab across the top of their search results page for "Knol results," along with the tabs for Web, images, and news. Or if Knol results get killed for "duplicate content," Google might (legitimately) consider this a bug and tweak their duplicate-detection algorithm. Thus Knol would have the same advantage in Google that Microsoft's Media Player has on Windows: The operating system doesn't favor Media Player directly, but compatibility problems with Media Player will always get fixed first (while the RealPlayer people have to watch their programs get broken by Windows upgrades). One way or another, it's pretty certain that Knol results are not going to be "unfindable" on Google.

Now, I'm sure Knol will not formally fork Wikipedia. I wouldn't see any problem with them doing that, but it would be too controversial, after the VP announced it without ever mentioning "Wikipedia," and with Google already dealing with speculation that they're only creating Knol to complete with Wikipedia in their own search results. But with users having cash incentives to copy content from Wikipedia, probably most of the content would get replicated very quickly, and I would be surprised if many users didn't start writing scripts to robo-copy as much content from Wikipedia as possible.

Then you get to the point where experts start improving it. If the first couple of entries on "Physics" are just the robo-copied Wikipedia version, "signed" by users that nobody has ever heard of, this is barely an improvement over the unsigned article on Wikipedia itself. But then only one Physics professor in the entire world has to think it's worth their while to read the standard Wikipedia article, make any necessary corrections, and sign their name to it on Knol — and now you have a version that has been vetted by a credentialed expert, increasing its value many times to people who want to cite it as a source, or who want a higher degree of confidence that it's accurate. (Hopefully Knol will allow authors to confirm their e-mail addresses and display them — in an image, presumably, to stop them being scraped by spammers. This will allow professors to prove that they really have faculty .edu addresses and enhance the credibility of their articles, something I suggested for Citizendium.)

So, some criticisms of Wikipedia would not apply to Knol. Author Nick Carr has written of Wikipedia,

"Certainly, it's useful - I regularly consult it to get a quick gloss on a subject. But at a factual level it's unreliable, and the writing is often appalling. I wouldn't depend on it as a source, and I certainly wouldn't recommend it to a student writing a research paper."

When I asked if he would recommend Knol for the same purpose, he was more optimistic:

"Probably. Since a Knol would be written by an identifiable person at an identifiable point in time, I don't see why you wouldn't treat it, in doing research, in a similar way that you'd treat, say, an article by that person. Obviously, you'd need to judge the writer's expertise and authority when deciding whether or not to draw on his or her work, which becomes somewhat more problematic where no editorial or peer-review system applies, as in Knol."

This is where I think the value of a professor's .edu e-mail address comes in, which can at least establish a writer's authority in their subject. I asked Seth Finkelstein whether he would recommend Knol in those same circumstances (verified professor's .edu address, etc.), and his take was, "Of course I would, but you loaded the question in a way so as to remove any problem from it." Well, yeah. I just happen to think Knol actually could remove those problems.

Then there was a little-noticed phrase in Google's blog post that suggests another area where Knol could improve over Wikipedia: the inclusion of "how-to-fix-it instructions." Given that people often need how-to instructions a lot more badly than they need encyclopedia articles, it's surprising that there hasn't been an attempt to standardize around a "Wikipedia of how-to's." Perhaps it's because the Web itself actually does pretty well for that — type in the text of some error message, and you'll usually get some hits on support forums where people ran into the same problem. The trouble is that the ranking of search results depends on the popularity of the site, not on whether the thread ended with someone posting a solution to the problem, so you might have to read through a lot of search results to find an answer. And if you're an expert who happens to know how to do or fix something, there's not much incentive for you to post a page about it (even with AdSense ads), because your page will get buried in the search results beneath all the support forums discussing the same question, even if your post is more concise and useful. Some gurus like Dave Taylor and Leo Notenboom have written so many how-to articles that their own sites have risen through the Google rankings, so if they write a how-to article about something, it will get read (which, of course, creates an incentive for them to write more of them). But for a new expert just starting to write how-to articles, it would take a long time to reach that critical mass.

Knol, however, creates an incentive for experts to start posting how-to-fix-it advice and start reaping the rewards right away, since your how-to articles are just as easy to find under a given subject as anyone else's. Your earnings would start out small as you began to write articles, but they would rise in proportion to the number of articles you wrote, and you wouldn't have to slog along writing for no reward like a typical blogger or site creator, hoping to hit "critical mass" some day. You'd find out early on what the reward would be (financial and otherwise) for the work you were doing, and could decide if you wanted to continue.

Actually, the possibility of "instant rewards" does depend on how Knol articles are ranked against each other within a given topic. The Google blog post says, "For many topics, there will likely be competing knols on the same subject," and, "Knols will include strong community tools. People will be able to submit comments, questions, edits, additional content, and so on. Anyone will be able to rate a knol or write a review of it." Presumably the top-rated articles on a given topic will be displayed first by default, so I'm making the assumption that good articles really will get sorted to the top. But if there are already 50 articles on some topic, even if you know you can write a better one, how do you know it would rise to the top of the pile? If 10 people rate your article a 9, and all the other articles have been rated by 100 people each and got an average rating of a 7, then yours should still be listed as the highest in terms of average rating. But how do you get even those first 10 people to see your article? You could invite your friends, but then how do you stop anyone from gaming the system by inviting their friends and asking them all to rate their article a 10?

I'd written about this in the context of whether Wikia Search might try to solve these problems by allowing users to vote on search results, if they could prevent people from gaming the system. That was basically just me thinking out loud that something like that would be cool, before Wikia Search announced any specifics, and I haven't heard that Wikia is trying anything like that. But now that Google has stated that they will use voting and ranking systems in Knol, the question is how to reward new authors while preventing cheating. I suggested some ideas in an article about how to stop cheating and vote-buying on digg. One idea was that you could have a section on the page that showed people links to different articles at random, so that users couldn't self-select on what articles were shown to them, and if those randomly selected users followed the links and voted on the articles, count only those votes in determining the true "rating" of an article. (This is what HotOrNot does for people's picture ratings.) Even if few people rated those articles, the ratings that were collected, would be representative of real users, and not the horde of friends that you'd sent to rate your article. If that did not prove popular enough, then you could give authors the option to pay random users to rate their articles — as long as there was no way for authors to tie payment to higher ratings, the ratings would average out to reflect the article quality, and could be used to sort articles based on their actual merits.

So, I'd like to think that someone in the Googleplex is reading everything I write, but it's probably just a case where great nerds think alike. I wrote in Feb 07 that I thought Citizendium should allow authors to put their name next to articles, both for the "name up in lights" incentives factor and to enhance the article's credibility, and now Knol is going to do that (not to mention throwing in money as well). The same month I wrote that someone should build a search engine that groups together user-submitted articles under different topics, and provides a means for newly submitted articles to rise through the ranks as a result of user votes, and it sounds like Knol will attempt that too. Then in April 07 I wrote about the ways that you could prevent cheating in such a system, and even though Knol hasn't talked about what they will do to address that problem, they're almost certainly thinking about it, and have probably come up with some of the same ideas.

So let's do a test to find out if Google is reading these articles. There's one area where Wikipedia would beat Knol, and that is that everything on Wikipedia can be redistributed for free. That's something really special, and it's the one part of the Wikipedia hype that I actually buy into. I don't really care that Wikipedia articles were created as part of a "worldwide collaborative effort" unless that helps to achieve the goal of being useful. But Wikipedia, for all its flaws, represents the first time in human history that we have a compendium of a huge amount of human knowledge that can be copied freely, that literally belongs to the world, and because it's duplicated in so many places, it can literally never be taken away. That part of the hype really is true, and is quite heady when you think about it.

Google Knol has not declared this as one of their goals; a Knol article might not be freely distributable. When a proprietary project is hosted on a private site, there's always the risk that the company will pull the plug on it. They probably won't pull off the content offline, but they might shut the service down to stop new content from being added, the way Google did with Google Answers. Yes, Knol authors will retain ownership of their writings, so they could try to regroup and continue the project somewhere else, but it would be a huge mess to try and contact all of the authors and get their permission to copy all of their articles to the new location. As currently planned, Knol doesn't "belong the world," and Google never promised not to take it away.

So, I think that Google Knol should include a feature whereby authors can flag their articles as being freely distributable under the same terms as Wikipedia articles. (Any author who copied an article from Wikipedia and submitted it, would be required to set this flag, because under the terms of "copyleft", you can't copy something that's freely copyable and then try to stop others from copying it!) Then a user who wanted a copylefted, freely distributable article, could limit their search to articles that have this flag set. This would give Knol the best of both worlds: if the author of the top-ranked article did not wish for it to be freely redistributable, then they wouldn't put it on Wikipedia, but they could make it available on Knol, and users could choose either the top-ranked copylefted article or the top-ranked article overall, depending on what they wanted. If the best article on a given subject also happened to be flagged freely distributable, then so much the better.

Maybe the Knol people have had this idea already. But even so, if they end up implementing it, then I'm starting right away on articles about how Google should implement Google Anti-Censorware, Google Site Hijack Prevention, Google Security Compensation, and Google Sergey And Larry Give Bennett Their Airplane.

Frequent Slashdot contributor Bennett Haselton sends in his latest, which begins like this and continues behind the link. "When Google's VP of Engineering announced their proposed Knol project, where users can submit articles on different subjects and share in the AdSense revenue from the article pages, he didn't mention "Wikipedia," but practically everyone else did who blogged about it. Here's what I think will happen, if Knol is implemented according to the plan: Even though it won't technically be a "Wikipedia fork," it will quickly become equivalent to one, with a "gold rush" of users copying content from Wikipedia to Knol articles hoping for a piece of the AdSense dollars. But I submit this will be a good thing, especially if bona fide experts in different fields join the gold rush as well and start signing their names to articles that they've vetted."
First, I've been saying for a while that someone should fork Wikipedia and start assigning "ownership" of articles to credentialed experts where possible, so that an article can be cited as a source that has been vetted by a recognized individual, and to guard against vandalism. Citizendium does something like this, but started from the ground up rather than fork Wikipedia. I argued that they should fork as much as possible from Wikipedia (having experts "bless" the content in the process); the project's official reason for not doing this was that authors are more motivated when starting with a clean slate than when taking over someone else's article. True, we all know the energizing feeling of a clean slate compared to the sluggish feeling of taking over a 50%-completed project with all of its flaws and compromises, but the "energizing feeling" often doesn't make up for the advantages of having 50% of the work already done for you (which is, in a nutshell, the only reason people ever finish 50%-completed projects instead of starting over!).

So could some other Wikipedia fork achieve the same thing? Programmer/blogger and Guardian columnist Seth Finkelstein, a frequent Wikipedia critic, has pointed out that other sites such as http://veropedia.com/ have tried to build a "verified" version of Wikipedia. "But," he writes, "it doesn't work for many reasons:

1) Maintenance
2) Nobody knows the site exists, or uses it.
3) Google will kill the site's ranking, because of "duplicate content"
4) Roughly 99% of Wikipedia's value is the Google-rank it has, and sites trying to copy its content don't have — or get — that Google-rank.

All true. But Knol has a shot at solving all of these problems. #1 should be mitigated if users earn money for maintaining articles — and besides, many articles like "Abraham Lincoln" won't need much maintenance anyway. #2 should not be an issue since it's a Google project. #3 and #4 depend on how Google lists Knol pages in its search results. The VP's blog post says only,

"Our job in Search Quality will be to rank the knols appropriately when they appear in Google search results. We are quite experienced with ranking web pages, and we feel confident that we will be up to the challenge."

Of course the question on everyone's minds, not answered directly by those sentences, is whether Knol pages will get any special treatment in search rankings. Google would probably be criticized if they manipulated the results outright. But they might achieve the same result indirectly — for example, having a tab across the top of their search results page for "Knol results," along with the tabs for Web, images, and news. Or if Knol results get killed for "duplicate content," Google might (legitimately) consider this a bug and tweak their duplicate-detection algorithm. Thus Knol would have the same advantage in Google that Microsoft's Media Player has on Windows: The operating system doesn't favor Media Player directly, but compatibility problems with Media Player will always get fixed first (while the RealPlayer people have to watch their programs get broken by Windows upgrades). One way or another, it's pretty certain that Knol results are not going to be "unfindable" on Google.

Now, I'm sure Knol will not formally fork Wikipedia. I wouldn't see any problem with them doing that, but it would be too controversial, after the VP announced it without ever mentioning "Wikipedia," and with Google already dealing with speculation that they're only creating Knol to complete with Wikipedia in their own search results. But with users having cash incentives to copy content from Wikipedia, probably most of the content would get replicated very quickly, and I would be surprised if many users didn't start writing scripts to robo-copy as much content from Wikipedia as possible.

Then you get to the point where experts start improving it. If the first couple of entries on "Physics" are just the robo-copied Wikipedia version, "signed" by users that nobody has ever heard of, this is barely an improvement over the unsigned article on Wikipedia itself. But then only one Physics professor in the entire world has to think it's worth their while to read the standard Wikipedia article, make any necessary corrections, and sign their name to it on Knol — and now you have a version that has been vetted by a credentialed expert, increasing its value many times to people who want to cite it as a source, or who want a higher degree of confidence that it's accurate. (Hopefully Knol will allow authors to confirm their e-mail addresses and display them — in an image, presumably, to stop them being scraped by spammers. This will allow professors to prove that they really have faculty .edu addresses and enhance the credibility of their articles, something I suggested for Citizendium.)

So, some criticisms of Wikipedia would not apply to Knol. Author Nick Carr has written of Wikipedia,

"Certainly, it's useful - I regularly consult it to get a quick gloss on a subject. But at a factual level it's unreliable, and the writing is often appalling. I wouldn't depend on it as a source, and I certainly wouldn't recommend it to a student writing a research paper."

When I asked if he would recommend Knol for the same purpose, he was more optimistic:

"Probably. Since a Knol would be written by an identifiable person at an identifiable point in time, I don't see why you wouldn't treat it, in doing research, in a similar way that you'd treat, say, an article by that person. Obviously, you'd need to judge the writer's expertise and authority when deciding whether or not to draw on his or her work, which becomes somewhat more problematic where no editorial or peer-review system applies, as in Knol."

This is where I think the value of a professor's .edu e-mail address comes in, which can at least establish a writer's authority in their subject. I asked Seth Finkelstein whether he would recommend Knol in those same circumstances (verified professor's .edu address, etc.), and his take was, "Of course I would, but you loaded the question in a way so as to remove any problem from it." Well, yeah. I just happen to think Knol actually could remove those problems.

Then there was a little-noticed phrase in Google's blog post that suggests another area where Knol could improve over Wikipedia: the inclusion of "how-to-fix-it instructions." Given that people often need how-to instructions a lot more badly than they need encyclopedia articles, it's surprising that there hasn't been an attempt to standardize around a "Wikipedia of how-to's." Perhaps it's because the Web itself actually does pretty well for that — type in the text of some error message, and you'll usually get some hits on support forums where people ran into the same problem. The trouble is that the ranking of search results depends on the popularity of the site, not on whether the thread ended with someone posting a solution to the problem, so you might have to read through a lot of search results to find an answer. And if you're an expert who happens to know how to do or fix something, there's not much incentive for you to post a page about it (even with AdSense ads), because your page will get buried in the search results beneath all the support forums discussing the same question, even if your post is more concise and useful. Some gurus like Dave Taylor and Leo Notenboom have written so many how-to articles that their own sites have risen through the Google rankings, so if they write a how-to article about something, it will get read (which, of course, creates an incentive for them to write more of them). But for a new expert just starting to write how-to articles, it would take a long time to reach that critical mass.

Knol, however, creates an incentive for experts to start posting how-to-fix-it advice and start reaping the rewards right away, since your how-to articles are just as easy to find under a given subject as anyone else's. Your earnings would start out small as you began to write articles, but they would rise in proportion to the number of articles you wrote, and you wouldn't have to slog along writing for no reward like a typical blogger or site creator, hoping to hit "critical mass" some day. You'd find out early on what the reward would be (financial and otherwise) for the work you were doing, and could decide if you wanted to continue.

Actually, the possibility of "instant rewards" does depend on how Knol articles are ranked against each other within a given topic. The Google blog post says, "For many topics, there will likely be competing knols on the same subject," and, "Knols will include strong community tools. People will be able to submit comments, questions, edits, additional content, and so on. Anyone will be able to rate a knol or write a review of it." Presumably the top-rated articles on a given topic will be displayed first by default, so I'm making the assumption that good articles really will get sorted to the top. But if there are already 50 articles on some topic, even if you know you can write a better one, how do you know it would rise to the top of the pile? If 10 people rate your article a 9, and all the other articles have been rated by 100 people each and got an average rating of a 7, then yours should still be listed as the highest in terms of average rating. But how do you get even those first 10 people to see your article? You could invite your friends, but then how do you stop anyone from gaming the system by inviting their friends and asking them all to rate their article a 10?

I'd written about this in the context of whether Wikia Search might try to solve these problems by allowing users to vote on search results, if they could prevent people from gaming the system. That was basically just me thinking out loud that something like that would be cool, before Wikia Search announced any specifics, and I haven't heard that Wikia is trying anything like that. But now that Google has stated that they will use voting and ranking systems in Knol, the question is how to reward new authors while preventing cheating. I suggested some ideas in an article about how to stop cheating and vote-buying on digg. One idea was that you could have a section on the page that showed people links to different articles at random, so that users couldn't self-select on what articles were shown to them, and if those randomly selected users followed the links and voted on the articles, count only those votes in determining the true "rating" of an article. (This is what HotOrNot does for people's picture ratings.) Even if few people rated those articles, the ratings that were collected, would be representative of real users, and not the horde of friends that you'd sent to rate your article. If that did not prove popular enough, then you could give authors the option to pay random users to rate their articles — as long as there was no way for authors to tie payment to higher ratings, the ratings would average out to reflect the article quality, and could be used to sort articles based on their actual merits.

So, I'd like to think that someone in the Googleplex is reading everything I write, but it's probably just a case where great nerds think alike. I wrote in Feb 07 that I thought Citizendium should allow authors to put their name next to articles, both for the "name up in lights" incentives factor and to enhance the article's credibility, and now Knol is going to do that (not to mention throwing in money as well). The same month I wrote that someone should build a search engine that groups together user-submitted articles under different topics, and provides a means for newly submitted articles to rise through the ranks as a result of user votes, and it sounds like Knol will attempt that too. Then in April 07 I wrote about the ways that you could prevent cheating in such a system, and even though Knol hasn't talked about what they will do to address that problem, they're almost certainly thinking about it, and have probably come up with some of the same ideas.

So let's do a test to find out if Google is reading these articles. There's one area where Wikipedia would beat Knol, and that is that everything on Wikipedia can be redistributed for free. That's something really special, and it's the one part of the Wikipedia hype that I actually buy into. I don't really care that Wikipedia articles were created as part of a "worldwide collaborative effort" unless that helps to achieve the goal of being useful. But Wikipedia, for all its flaws, represents the first time in human history that we have a compendium of a huge amount of human knowledge that can be copied freely, that literally belongs to the world, and because it's duplicated in so many places, it can literally never be taken away. That part of the hype really is true, and is quite heady when you think about it.

Google Knol has not declared this as one of their goals; a Knol article might not be freely distributable. When a proprietary project is hosted on a private site, there's always the risk that the company will pull the plug on it. They probably won't pull off the content offline, but they might shut the service down to stop new content from being added, the way Google did with Google Answers. Yes, Knol authors will retain ownership of their writings, so they could try to regroup and continue the project somewhere else, but it would be a huge mess to try and contact all of the authors and get their permission to copy all of their articles to the new location. As currently planned, Knol doesn't "belong the world," and Google never promised not to take it away.

So, I think that Google Knol should include a feature whereby authors can flag their articles as being freely distributable under the same terms as Wikipedia articles. (Any author who copied an article from Wikipedia and submitted it, would be required to set this flag, because under the terms of "copyleft", you can't copy something that's freely copyable and then try to stop others from copying it!) Then a user who wanted a copylefted, freely distributable article, could limit their search to articles that have this flag set. This would give Knol the best of both worlds: if the author of the top-ranked article did not wish for it to be freely redistributable, then they wouldn't put it on Wikipedia, but they could make it available on Knol, and users could choose either the top-ranked copylefted article or the top-ranked article overall, depending on what they wanted. If the best article on a given subject also happened to be flagged freely distributable, then so much the better.

Maybe the Knol people have had this idea already. But even so, if they end up implementing it, then I'm starting right away on articles about how Google should implement Google Anti-Censorware, Google Site Hijack Prevention, Google Security Compensation, and Google Sergey And Larry Give Bennett Their Airplane.

anzha writes "It seems that that Linux Networx, the pioneering Linux supercomputing company, has gone belly up. SGI announced that it has bought the core assets of LNXI. Furthermore, the rumors are that the doors were locked and employees were just given their paychecks. This analysis, on the other hand, claims that SGI has 'made employment offers to many LNXI engineers.' It's unclear what kind of support will be extended to customers of LNXI's Clusterworx Advanced products. What does this mean for the future of Linux supercomputing?"

Stanislav_J writes "It happens to the best of us: you drop off your laptop at the local branch of some Super Mega Electronics McStore, go to pick it up, and they can't find it. Lost, gone, kaput — probably sucked into a black hole and now breeding with lost airline luggage. It would make any of us mad, but Raelyn Campbell of Washington, D.C. isn't just mad — she's $54 million mad. That's how much she is asking from Best Buy in a lawsuit that seeks 'fair compensation for replacement of the $1,100 computer and extended warranty, plus expenses related to identity theft protection.' Best Buy claims that Ms. Campbell was offered and collected $1,110.35 as well as a $500 gift card for her inconvenience. (I guess that extra 35 cents wasn't enough to sway her.) Her blog claims that Geek Squad employees spent three months telling her different stories about where her laptop might be before finally acknowledging that it had been lost. For those who follow economic trends, this means that a laptop's worth is roughly equivalent to that of a pair of pants."

NewYorkCountryLawyer writes "p2pnet.net reports that the RIAA has egg on its face. When the Electronic Frontier Foundation requested permission to file an amicus curiae brief on behalf of Boston University students challenging the RIAA's ex parte discovery order, the RIAA lawyers attacked the blog 'Recording Industry vs. The People' for its criticism of the RIAA as seeking to 'abuse the American judicial system, distort copyright law, and frighten ordinary working people and their children' and then falsely claimed that the blog's author is an EFF attorney — this despite the fact that they know that the blog's author (known on Slashdot as NewYorkCountryLawyer) is a partner in a New York law firm and not an EFF attorney. Judge Gertner apparently wasn't impressed, and granted the EFF's motion, rejecting the RIAA's objections, since she felt amici curiae might 'shed light' on the 'copyright law' and 'computer technology' issues before her."

NewYorkCountryLawyer writes "p2pnet.net reports that the RIAA has egg on its face. When the Electronic Frontier Foundation requested permission to file an amicus curiae brief on behalf of Boston University students challenging the RIAA's ex parte discovery order, the RIAA lawyers attacked the blog 'Recording Industry vs. The People' for its criticism of the RIAA as seeking to 'abuse the American judicial system, distort copyright law, and frighten ordinary working people and their children' and then falsely claimed that the blog's author is an EFF attorney — this despite the fact that they know that the blog's author (known on Slashdot as NewYorkCountryLawyer) is a partner in a New York law firm and not an EFF attorney. Judge Gertner apparently wasn't impressed, and granted the EFF's motion, rejecting the RIAA's objections, since she felt amici curiae might 'shed light' on the 'copyright law' and 'computer technology' issues before her."

NewYorkCountryLawyer writes "p2pnet.net reports that the RIAA has egg on its face. When the Electronic Frontier Foundation requested permission to file an amicus curiae brief on behalf of Boston University students challenging the RIAA's ex parte discovery order, the RIAA lawyers attacked the blog 'Recording Industry vs. The People' for its criticism of the RIAA as seeking to 'abuse the American judicial system, distort copyright law, and frighten ordinary working people and their children' and then falsely claimed that the blog's author is an EFF attorney — this despite the fact that they know that the blog's author (known on Slashdot as NewYorkCountryLawyer) is a partner in a New York law firm and not an EFF attorney. Judge Gertner apparently wasn't impressed, and granted the EFF's motion, rejecting the RIAA's objections, since she felt amici curiae might 'shed light' on the 'copyright law' and 'computer technology' issues before her."

memshankar writes "In an interview while he was in Hyderabad, India RMS praises for the One Laptop Per Child Project. He is even contemplating making a switch to XO, the flagship machine of the project, from his "old thinkpad". Stallman went on to say that the OLPC laptop has given people a way to use the free BIOS. He is, however dissatisfied with the wireless networking system used in the XO."

memshankar writes "In an interview while he was in Hyderabad, India RMS praises for the One Laptop Per Child Project. He is even contemplating making a switch to XO, the flagship machine of the project, from his "old thinkpad". Stallman went on to say that the OLPC laptop has given people a way to use the free BIOS. He is, however dissatisfied with the wireless networking system used in the XO."

NewYorkCountryLawyer writes "Lest there be anyone left who believes the RIAA's propaganda that its litigation campaign is intended to benefit the 'creators' of the music, Hollywood Reporter reports that the RIAA is asking the Copyright Royalty Board to lower songwriter royalties on song file downloads, from the present rate of 9 cents per song — about 13% of the wholesale price — down to 8% of wholesale. Meanwhile, the big digital music companies, such as Apple, want the royalty rate lowered even more, to something like 4% of wholesale. So any representations by any of these companies that they are concerned for the 'creators' of the music must henceforth be taken with a boxcar-load of salt."

watzinaneihm writes "In a blog post Google has called Yahoo/Microsoft merger bad for the future of the internet. It is worried about the number of email and IM accounts this merged entity would control. Microsoft has countered with the argument that Google is actually the big bully in this instance, with most of the search market already tied up. The New York Times, in the meantime, has accused Google of a Microsoft fixation."

NewYorkCountryLawyer writes "p2pnet.net has put together a fascinating retrospective on the RIAA's war against college students, commenced February 28, 2007. The campaign is described as one to 'force "consumers" to buy what they're told to buy — corporate "content," as the Big 4 call their formulaic outpourings.' In a scathing indictment not only of the major record labels, but of those schools, administrators, and educators who have yet to take a stand against it, Jon Newton reviews a number of landmark moments in the 11-month old 'reign of terror'. They include the announcement of the bizarre 'early settlement' sale, the sudden withdrawal of a case in which a 17 year old Texas high school student had been subpoenaed while in class during school hours to attend a deposition the very next day during his taking of a standardized test, the call by Harvard law professors for the university to fight back when and if attacked, and the differing reactions by other schools."

NewYorkCountryLawyer writes "MediaSentry, in an attempt to stonewall discovery in UMG v. Lindor, has turned over nothing other than a collection, apparently a complete collection, of its publicly filed affidavits. However, these do make interesting reading indeed, and as comments started trickling in on my blog, I realized that for the technically minded among you there are probably a number of good laughs in these materials. So in keeping with the Slashdot community's analysis of the RIAA's not very expert, 'expert' witness, I thought you might like to take a shot at its not very factual, 'fact' witness."

NewYorkCountryLawyer writes "MediaSentry, in an attempt to stonewall discovery in UMG v. Lindor, has turned over nothing other than a collection, apparently a complete collection, of its publicly filed affidavits. However, these do make interesting reading indeed, and as comments started trickling in on my blog, I realized that for the technically minded among you there are probably a number of good laughs in these materials. So in keeping with the Slashdot community's analysis of the RIAA's not very expert, 'expert' witness, I thought you might like to take a shot at its not very factual, 'fact' witness."

Heartless Gamer writes "Valve is rocking the boat in a big way, especially for PC gaming piracy. They have just announced the release of a complete collection of publisher tools, called Steamworks. They're making it available to developers and publishers completely free. Valve notes that beyond simply making the product available to consumers some of the tools can integrate copy protection, social networking services, or even server browsing features into a developing game."

NewYorkCountryLawyer writes "Once again the RIAA has dropped a case with prejudice, this time after concluding it was the defendant's daughter it should have sued in the first place. In the case of Lava v. Amurao, mindful that in similar scenarios it has been held liable for the defendant's attorney fees (Capitol v. Foster and Atlantic v. Andersen), the RIAA went on the offensive. In this case there was actually no attorney fee motion pending, making their motion all the more intriguing. The organization argued that it was the defendant's fault that the record companies sued the wrong person, because the defendant didn't tell them that his daughter was the file sharer they were looking for."

NewYorkCountryLawyer writes "Once again the RIAA has dropped a case with prejudice, this time after concluding it was the defendant's daughter it should have sued in the first place. In the case of Lava v. Amurao, mindful that in similar scenarios it has been held liable for the defendant's attorney fees (Capitol v. Foster and Atlantic v. Andersen), the RIAA went on the offensive. In this case there was actually no attorney fee motion pending, making their motion all the more intriguing. The organization argued that it was the defendant's fault that the record companies sued the wrong person, because the defendant didn't tell them that his daughter was the file sharer they were looking for."

NewYorkCountryLawyer writes "Once again the RIAA has dropped a case with prejudice, this time after concluding it was the defendant's daughter it should have sued in the first place. In the case of Lava v. Amurao, mindful that in similar scenarios it has been held liable for the defendant's attorney fees (Capitol v. Foster and Atlantic v. Andersen), the RIAA went on the offensive. In this case there was actually no attorney fee motion pending, making their motion all the more intriguing. The organization argued that it was the defendant's fault that the record companies sued the wrong person, because the defendant didn't tell them that his daughter was the file sharer they were looking for."

Hell Yeah! reminds us of a 2-week-old development that somehow escaped notice here. A team of Russian hackers has found a way to decipher a Yahoo CAPTCHA, thought to be one of the most difficult, with 35% accuracy. The Russian group's notice, posted by one "John Wane," is dated January 16. This site hosts a rapidshare link to what looks to be demonstration software for Windows, and quotes the Russian researchers: "It's not necessary to achieve high degree of accuracy when designing automated recognition software. The accuracy of 15% is enough when attacker is able to run 100,000 tries per day, taking into the consideration the price of not automated recognition — one cent per one CAPTCHA."

NewYorkCountryLawyer writes "Angered at the RIAA's 'gamesmanship' in joining multiple 'John Does' in a single case without any basis for doing so, a Magistrate Judge in Maine has suggested to the presiding District Judge in Arista v. Does 1-27 that the record companies and/or their lawyers should be fined under Rule 11 of the Federal Rules, for misrepresenting the facts. In a lengthy footnote to her opinion recommending denial of a motion to dismiss the complaint (PDF, see footnote 5), Judge Kruvchak concluded that 'These plaintiffs have devised a clever scheme to obtain court-authorized discovery prior to the service of complaints, but it troubles me that they do so with impunity and at the expense of the requirements of Rule 11(b)(3) because they have no good faith evidentiary basis to believe the cases should be joined.' She noted that once the RIAA dismisses its 'John Doe' case it does not thereafter join the defendants when it sues them in their real names. Arista v. Does 1-27 is the same case in which student attorneys at the University of Maine Law School, "enthusiastic about being directly connected to a case with a national scope and significance", are representing undergrads targeted by the RIAA."

NewYorkCountryLawyer writes "Angered at the RIAA's 'gamesmanship' in joining multiple 'John Does' in a single case without any basis for doing so, a Magistrate Judge in Maine has suggested to the presiding District Judge in Arista v. Does 1-27 that the record companies and/or their lawyers should be fined under Rule 11 of the Federal Rules, for misrepresenting the facts. In a lengthy footnote to her opinion recommending denial of a motion to dismiss the complaint (PDF, see footnote 5), Judge Kruvchak concluded that 'These plaintiffs have devised a clever scheme to obtain court-authorized discovery prior to the service of complaints, but it troubles me that they do so with impunity and at the expense of the requirements of Rule 11(b)(3) because they have no good faith evidentiary basis to believe the cases should be joined.' She noted that once the RIAA dismisses its 'John Doe' case it does not thereafter join the defendants when it sues them in their real names. Arista v. Does 1-27 is the same case in which student attorneys at the University of Maine Law School, "enthusiastic about being directly connected to a case with a national scope and significance", are representing undergrads targeted by the RIAA."

HighWizard writes with word from Engadget that the iPhone SDK Key has been leaked early. "We're not exactly sure how this all went down, but we trust Erica Sadun over at TUAW when she says that it appears that the iPhone's SDK key — which will probably be required by all 'official' third-party apps — has been leaked. Two different sites currently have the key posted, but it's all just for show until next month, when the SDK hits for real — and the code is undoubtedly changed."

DaMan writes "Here's something that isn't an urban legend — Snopes, the popular urban legends reference site, has been pushing adware, for at least 6 months, to users via ads displayed on its Web site. No one seems to have called them on it until recently."

Reverse Gear recommends a long and interesting article over at The Atlantic in which Walter Kirn talks about the scientific results that support his claim and his own experiences with multitasking: that it destroys our ability to focus. "Multitasking messes with the brain in several ways. At the most basic level, the mental balancing acts that it requires — the constant switching and pivoting — energize regions of the brain that specialize in visual processing and physical coordination and simultaneously appear to shortchange some of the higher areas related to memory and learning. We concentrate on the act of concentration at the expense of whatever it is that we're supposed to be concentrating on... studies find that multitasking boosts the level of stress-related hormones such as cortisol and adrenaline and wears down our systems through biochemical friction, prematurely aging us. In the short term, the confusion, fatigue, and chaos merely hamper our ability to focus and analyze, but in the long term, they may cause it to atrophy."

An anonymous reader tips us to a note up on the IPKat blog, written by one of the four law-professor types behind that venture. The British High Court has ruled on appeal that the UK Patent Office must not reject software patent applications out of hand, as it has been doing for some time now. "In a surprising (to this Kat at least) turn of events, the Honourable Mr Justice Kitchin has ruled today that the current UK Patent Office practice of flatly rejecting patent claims to computer program products is wrong... Kitchin J found that the appeals should be allowed. Each application concerned a computer related invention where the examiner had allowed claims to, in effect, a method performed by running a suitably programmed computer and to a computer programmed to carry out the method... The cases were remitted to the [UK Intellectual Property Office] for further consideration in light of the judgment."

SkiifGeek writes "Sophos claims that they are detecting 6,000 new sites daily that have been compromised to serve malware to unsuspecting site visitors, with 80% of site owners not aware that they have been compromised — though this figure is probably on the low side. With increasingly vocal arguments being put forward by security experts criticizing the performance and capability of site validation tools (though many of these experts offer their own tools and services for similar capabilities), and rising levels of blended attacks, perhaps it is time you reviewed the security of your site and what might be hiding in infrequently used directories."

NewYorkCountryLawyer writes "MIT's online newspaper, The Tech, reports that a student named as a John Doe by the RIAA is planning to fight back against their questionable legal tactics. The anonymous student told The Tech that he is 'the victim of a fishing expedition by the RIAA,' and is 'disappointed that MIT isn't going to step up ... Other schools like Boston University and the University of Oregon have resisted RIAA subpoenas of student records more actively than MIT has, he said'. Maybe his attorneys will be able to get some assistance from some of the Harvard Law School students in Professor Nesson's 'Evidence' class, who have been assigned — as part of their coursework — the drafting of a motion to quash an RIAA subpoena."

cpudney writes "An article in Computerworld UK reports on a new open source analysis initiative launched by Hewlett-Packard. The FOSSology Project's mission is to 'build a community to facilitate the study of Free and Open Source Software by providing free data analysis tools.' The first such tool reports how an open source project is licensed. Rather than simply collecting a project's advertised license, the tool analyzes all of the source code for a given project and reports all of the licenses being used, based on the license declarations and tell-tale phrases that identify software licensing. A video demonstrating the tool applied to abiword is available. The FOSSology source code is licensed under GPLv2."

arbitraryaardvark writes "NASA's Messenger probe flew past Mercury at a distance of 125 miles. The spacecraft took hundreds of pictures during the pass, updating photos from the now 30-year-old Mariner mission. According to an article at the International Business Times, the probe will eventually settle into orbit around Mercury in 2011. 'The images obtained by the $446 million MESSENGER mission (MErcury Surface, Space ENvironment, GEochemistry, and Ranging) this week contain some of those unexplored areas. One image released Saturday was taken after Messenger made its closest approach to Mercury last week. In the photos released this week, scientists have observed unexplored cratered areas of the planet. On Monday, Messenger made its closest approach to Mercury yet, aiming for new discoveries. Among its goals is to discover if Mercury has ice water in its polar craters and to complete the mapping of the whole planet.' Meanwhile here on Earth, a joint EU/Japan probe with an ion drive is set to head towards Mercury sometime in 2013."

Ian Lamont writes "Microsoft is apparently taking seriously a blogger's claim that a Microsoft tech support employee called back to check on a 10-year-old BSOD trouble ticket. The anonymous blogger suspects someone at Microsoft typed "1/8/08" into their tracking system for the date of a follow-up call, instead of "1/8/98." Microsoft told Computerworld support cases "are reviewed regularly so that we can ensure we're resolving customer issues in a timely fashion — regardless of the callback commitment set by the agent. Nonetheless, no system can ensure complete accuracy."" To be fair, this is all unverified, so choose to believe at your own risk.

NewYorkCountryLawyer writes "In Atlantic v. Howell, the Phoenix, Arizona, case in which a defendant who has no legal representation has been battling the RIAA over its theory that merely 'making files available for distribution' is in and of itself a copyright infringement, Mr. Howell has received some help from an outside source. On the last day allowed for the filing of supplemental briefs, the Electronic Frontier Foundation filed an amicus curiae brief agreeing with Mr. Howell, and refuting the RIAA's motion for summary judgment. The brief (PDF), which is recommended reading for anyone who wants to know what US copyright law really says, points out that 'contrary to Plaintiffs' arguments, an infringement of the distribution right requires the unauthorized, actual dissemination of copies of a copyrighted work.' This is the same case in which the RIAA claimed that Mr. Howell's MP3s, copied from his CDs, were themselves unlawful."

NewYorkCountryLawyer writes "In Atlantic v. Howell, the Phoenix, Arizona, case in which a defendant who has no legal representation has been battling the RIAA over its theory that merely 'making files available for distribution' is in and of itself a copyright infringement, Mr. Howell has received some help from an outside source. On the last day allowed for the filing of supplemental briefs, the Electronic Frontier Foundation filed an amicus curiae brief agreeing with Mr. Howell, and refuting the RIAA's motion for summary judgment. The brief (PDF), which is recommended reading for anyone who wants to know what US copyright law really says, points out that 'contrary to Plaintiffs' arguments, an infringement of the distribution right requires the unauthorized, actual dissemination of copies of a copyrighted work.' This is the same case in which the RIAA claimed that Mr. Howell's MP3s, copied from his CDs, were themselves unlawful."

NewYorkCountryLawyer writes "In Atlantic v. Howell, the Phoenix, Arizona, case in which a defendant who has no legal representation has been battling the RIAA over its theory that merely 'making files available for distribution' is in and of itself a copyright infringement, Mr. Howell has received some help from an outside source. On the last day allowed for the filing of supplemental briefs, the Electronic Frontier Foundation filed an amicus curiae brief agreeing with Mr. Howell, and refuting the RIAA's motion for summary judgment. The brief (PDF), which is recommended reading for anyone who wants to know what US copyright law really says, points out that 'contrary to Plaintiffs' arguments, an infringement of the distribution right requires the unauthorized, actual dissemination of copies of a copyrighted work.' This is the same case in which the RIAA claimed that Mr. Howell's MP3s, copied from his CDs, were themselves unlawful."

MrCopilot writes "As I noted yesterday (and was joined by many others)... in an offhand observation xkcd has singlehandedly changed a small section of the Internet. Changing the results from a Google search for "Died in a Blogging Accident" from 2 to (at this writing) over 7,170 in a little more than 24 hours." If you aren't reading xkcd, you're missing out.

bloosqr writes "Dan Heller, in a series of three articles, claims to have found a number of problems with the Creative Commons license, particularly within the realm of photography. In the first article he states there is a problem with people relicensing copyrighted work under the CC license and having subsequent users of that copyrighted work sued by the original owner. In the second article he fleshes out these ideas and states that there is an increased risk of being sued if you use a CC license. Finally, in the third article, he states that people can 'game the CC license' for profit, by suing people who use your CC'd work which you have subsequently revoked from the CC license. This series of blogs has generated a fair amount of discussion on several photography forums, and I would like for the Slashdot community to clarify matters."

An anonymous reader writes "Tens of thousands of Web sites have been compromised by an automated SQL injection attack, and although some have been cleaned, others continue to serve visitors a malicious script that tries to hijack their PCs using multiple exploits, security experts said this weekend. Hacked sites included both .edu and .gov domains, the SANS Institute's Internet Storm Center reported in a warning posted last Friday. The ISC also reported that several pages of security vendor CA's Web site had been infected. Roger Thompson, the chief research officer at Grisoft, pointed out that the hacked sites could be found via a simple Google search for the domain that hosts the malicious JavaScript. On Saturday, said Thompson, the number of sites that had fallen victim to the attack numbered more than 70,000. 'This was a pretty good mass hack,' said Thompson, in a post to his blog." By Sunday a second round of the same attack had infected over 90,000 servers.

NewYorkCountryLawyer writes "David Kravetz of Wired.com covered last year's Capitol v. Thomas trial gavel-to-gavel. It's worth noting, then, his article saying that the RIAA's recent statement — that Sony's top litigation lawyer 'misspoke' during the trial. She said that making a copy from one's own cd is 'stealing', which (in his words) may have caused a major miscarriage of justice. Wired further points out that later on in the trial, during the RIAA's examination of Ms. Thomas, 'On the hard drive she [turned] over were thousands of songs Thomas said she ripped from her CDs. The RIAA's Gabriel suggested to jurors that copying one's purchased music was a violation of the Copyright Act. Gabriel, for example, asked Thomas whether she had ever burned CDs, either for herself, or to give away to friends.' Gabriel, the RIAA's lead attorney, apparently misspoke too — prejudicing jurors along the way."

NewYorkCountryLawyer writes "David Kravetz of Wired.com covered last year's Capitol v. Thomas trial gavel-to-gavel. It's worth noting, then, his article saying that the RIAA's recent statement — that Sony's top litigation lawyer 'misspoke' during the trial. She said that making a copy from one's own cd is 'stealing', which (in his words) may have caused a major miscarriage of justice. Wired further points out that later on in the trial, during the RIAA's examination of Ms. Thomas, 'On the hard drive she [turned] over were thousands of songs Thomas said she ripped from her CDs. The RIAA's Gabriel suggested to jurors that copying one's purchased music was a violation of the Copyright Act. Gabriel, for example, asked Thomas whether she had ever burned CDs, either for herself, or to give away to friends.' Gabriel, the RIAA's lead attorney, apparently misspoke too — prejudicing jurors along the way."

Cassanova writes "Weave is the newest Mozilla Labs project. It allows the user to save browser settings on Mozilla servers (Favorites, sessions, passwords, etc.) and load them from anywhere. With this project, Mozilla is trying to be an online services provider, which is an important step. But can Mozilla labs get over the privacy issues?"

Cassanova writes "Weave is the newest Mozilla Labs project. It allows the user to save browser settings on Mozilla servers (Favorites, sessions, passwords, etc.) and load them from anywhere. With this project, Mozilla is trying to be an online services provider, which is an important step. But can Mozilla labs get over the privacy issues?"

bensafrickingenius writes "CNET's Crave site has an interesting article on Amazon's Kindle eBook reader, and the extensive reverse-engineering that fans of the device have accomplished. The site specifically points out the work of Igor Skochinsky at the Reversing Everything website. His work on the Kindle's Root Shell has revealed some fascinating goodies: 'Among the ones uncovered and described on his blog are a basic photo viewer, a minesweeper game, and most interesting, location technology that uses the Kindle's CDMA networking to pinpoint its position. There also are some basic location-based services that call up a Google Maps view to show where you are and nearby gas stations and restaurants.'"

bensafrickingenius writes "CNET's Crave site has an interesting article on Amazon's Kindle eBook reader, and the extensive reverse-engineering that fans of the device have accomplished. The site specifically points out the work of Igor Skochinsky at the Reversing Everything website. His work on the Kindle's Root Shell has revealed some fascinating goodies: 'Among the ones uncovered and described on his blog are a basic photo viewer, a minesweeper game, and most interesting, location technology that uses the Kindle's CDMA networking to pinpoint its position. There also are some basic location-based services that call up a Google Maps view to show where you are and nearby gas stations and restaurants.'"

NewYorkCountryLawyer writes "The Motley Fool investment Web site warns investors to beware of 'Sony, BMG, Warner Music Group, Vivendi Universal, and EMI.' In an article entitled 'We're All Thieves to the RIAA,' a Motley Fool columnist, referring to the RIAA's pronouncement in early December in Atlantic v. Howell, that the copies which Mr. Howell had ripped from his CDs to MP3s in a shared files folder on his computer were 'unauthorized,' writer Alyce Lomax said 'a good sign of a dying industry that investors might want to avoid is when it would rather litigate than innovate, signaling a potential destroyer of value.'"

Glyn Moody writes "Google always plays down suggestions that there's any looming clash of the titans between itself and Microsoft. Meanwhile, the search giant is pushing open source in every way it can. They're contributing directly by contributing code to projects and employing top hackers like Andrew Morton, Jeremy Allison and Guido van Rossum, and indirectly through the $60 million fees it pays Mozilla, its Summer of Code scheme and various open source summits held at its offices. Google+OSS: could this be the killer combination that finally breaks Microsoft?"

pdclarry writes "Users of the iPhone have noticed that it is showing December 31, 2007, even where it is already the new year. There have been a number of reports confirming the problem: Bug in Clock, Problem with New Year: My Clock — shows wrong year, Worldclock went wrong for "tomorrow" items."

theodp writes "Ready for one-automobile-per-child (OAPC)? India's giant Tata Group is on the verge of launching the world's cheapest car. The People's Car, slated to be unveiled January 10th at a New Delhi auto show, will carry a sticker price of 100,000 rupees ($2,500), which some analysts say could revolutionize automobile costs worldwide. The Tata is a pet project of Cornell-trained architect Ratan Tata, who helped design it. The vehicle is aimed at improving driving safety by getting India's masses off their motorbikes and into cars."

mynameismonkey writes "openEHR guru Tim Cook, writing in a guest blog at A Scanner Brightly, discusses why Electronic Health Record developers should use open standards. Why are so few doctors using EHR systems? And, as more and more hospital EHR systems come online across the country, what do we have to fear from proprietary databases? It's one thing to find out your social security number was stolen. Now add your mental health and STD results to those records."