This is just the stuff for a half-baked, Friday evening post when my traffic begins to dive into the weekend lull.
I'm going to admit this right now: There's one big, glaring omission in my book, and it's Google. While I devote a few pages here and there to the Mountain View Monolith, I hardly give it the attention it deserves. You'd think writing a book would provide enough space to do anything. In fact, it's an exercise in reduction. I wound up taking a chunk on Google Earth out entirely, and by the time Android was launched I was already in edits. But for the record, I believe a separate Crowdsourcing book could be written using Google as one single, fat case study.
And that's good. Because a writer's blog is sort of an ongoing appendix to his book. I want to lay out the areas in which Google is crowdsourcing. Ideally, I'll revisit each of the bullet points below in more depth in the coming weeks (Ed's Note: Emphasis in previous sentence mine. Jeff is too ...mercurial, let's say, in his posting habits to make promises of future content).
• Google Earth: See Sketch-Up
• GoogleMaps: See Google MapMaker
• PageRank: I write about this in Chapter 8. It's a tad controversial to cram this most elemental part of the Web under the Crowdsourcing banner, but in the end I decided it'd be erroneous not to include it.
• Google Answers
• Google Moderator
And I'm leaving lots of stuff out. I gotta go home and bathe my kids. I'll try to come back to this post over the weekend. In the meantime, let's consider this a group working paper. I know I have Googlers out there reading this! I'm issuing an open call to add to my list.