Is Google's Knol already becoming a den of spam?
Heard about Knol yet? It's Google's Xth new service, and it's a place where you can put up "an authoritative article about a specific topic". That's a knol too. Article=knol.
My first encounter with Knol was at Pointless Games, an entry by my friend Bernie DeKoven, a funsmith of the first water balloon. A knol, Knol tells us, is "a unit of knowledge". I used to think a thought was one one of those, and I maybe even wrote that once somewhere; but when I search Google now for results that include my surname and exclude knol and google (specifically, searls "unit of knowledge " -google -knol) I find nothing but articles by Searle, who apparently did say that. (Hard to tell. All the results are for abstracts of academic articles buried behind usewalls of various kinds. Meanwhile it annoys me that Google includes misspellings in its "advanced" search.)
Naturally, Knol is being covered as a "rival" to Wikipedia. That's exactly what CNet/ZDNet calls it. Social Computing Magazine calls it "The Wikipedia with a business model". TechLounge calls it "Google's Wikipedia".
(I mention those ahead of the current top result in a search of Google News for knol, because that brings up eWeek's Google's Wikipedia Answer: A Second Shooter on the Google Knol-Wikipedia Battle. There I was greeted by a giant Dell ad that tells you to click here or wait 12 seconds, which it counts down in rolling red lettering, like the clock on a bomb about to go off, absolutely distracting from the ad itself. That's a "feature" that makes one annoyed at both Dell and eWeek simultaneously. Nice work, guys.)
Naturally, Wikipedia has much more to say about Knol than does Google. It begins,
Knol is a Google project which aims to include user-written articles on topics ranging from "scientific concepts, to medical information, from geographical and historical, to entertainment, from product information, to how-to-fix-it instructions." The brainchild of Udi Manber of Google, it was announced on December 13, 2007 and was opened in beta to the public on July 23, 2008 with a few hundred articles mostly in the health and medical field.
Knol pages are "meant to be the first thing someone who searches for this topic for the first time will want to read", according to Manber. The term knol, which Google defines as a "unit of knowledge", refers to both the project and an article in the project. Several experts see Knol as Google's attempt to compete with Wikipedia, while others point out the differences between the projects. (revision link)
To put it briefly, they are not the same. They don't compete.
But that doesn't mean Knol isn't competitive with other sites and services. I think Jason Calacanis nails it pretty well when he asks, Is Google A Content Company? Of Course It Is. So What Should Publishers Do? If you're a writer or publisher, (like,um, we are), Jason's piece is relevant reading. It's a bit on the alarmist side, but Jason cops to that, wondering out loud whether complainers are "crybabies or canaries in the coal mine".
Either way, we need to face the fact that Google has become a platform. Or, as Dave Winer put it the other day, a coral reef. These things grow over a long period of time, and support many life forms. The tougher trick is to be generative. A generative platform is not about lock in. Rather, it's about opening things up, and being supportive of more than those things that depend on you directly. In The Future of the Internet — and How to Stop it., Jonathan Zittrain illustrates the PC's generativity as the flexible waist in an hourglass, rather than the bottom of a stack:
Nice that he includes Linux in there. We should add that Linux cares less about what it runs on, or what runs on it, than either of the other two OS platforms. Which brings us to Jonathan's illustration of the generative role played by the Internet itself:
Google is at the top level of that diagram. More significantly, it has a business interest in the success of its dependents (as do Microsoft and Apple in PC diagram). Wikipedia doesn't have that. Big difference.
At this point I see no threat by Knol to publications like ours or Jason's. I do see a possible threat to academic journals. As I discovered in my search above, most academic journals lock up their archives. Knol's methods and ambitions line up very nicely with those of academics who don't like to see their writing locked away — and who would like the bylined credit they don't get in Wikipedia.
But so far it looks to me like the biggest problems Knol creates are for Google itself. That's because Knol provides one more way to game Google's advertising monoculture. A few minutes ago I looked up "anemia" on Knol, with no results. Then I looked up "hair" and got eleven results. The top result is for this article on hair loss, by Rob E. Angelino, Founder Hairlab center for hair restoration. Or so it says at the top. At the bottom it says "Copyright © 2005-2007 United Global Media Group, Inc. All rights reserved". Not sure how that squares with Knol's defaulted Creative Commons Attribution 3.0 License, but it's significant that Mr. Angelino also has collaboration closed on the document. You can do that with Knol. It also says here that Mr. Angelino is "Founder and CEO of United Global Media Group Inc." and "currently the CEO of The Beauty TV Network". Mr. Angelino has a total of six knols, including one each for the Beauty Channel, BeautyTV and The Beauty Network. The search also brings up this knol by Julia Elorriaga of LastSkinCare.com, and hair bleaching tips by Sara, who has several other knols but no bio. At the bottom it says "Contributed to Mahalo.com by Greg S".
With the possible exeption of Sars's post, all that stuff is commercial gaming. "Units of knowledge" these aren't.
Knol will succeed if serious contributors outnumber the gamers. I don't hold much hope for that, even though I remain charmed that Bernie DeKoven's knol about Pointless Games was what launched me into this long post.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide