How to make a damogzito

Ingredients: 5 parts pride 5 parts ambition 1 part instinct

Method: Blend at a low speed for 30 seconds. Top it off with a sprinkle of sadness and enjoy!

Wikitorial triumphant Last summer, the Los Angeles Times tried an extremely interesting experiment in creating a wikitorial, or wiki-based editorial. The experiment was a notorious disaster: due to excessive abuse and fighting, the Times cancelled the experiment before publishing the results. The entire experience stained wiki's reputation for an entire year. Fast forward to 2006: oh, how times have changed. Ryan Singel of W I R E D magazine put up a 1000-word article about wikis on a wiki at SocialText. He invited the general public to edit the article. The result, which is a reasonably cohesive article on wikis, was published in wired under the title Veni, Vidi, Wiki. It's not the best article in the entire world on wiki, but it's not half bad. Some people have been down on the project -- mostly wiki businesses who felt they didn't get prominent enough coverage -- but I think that the bar was set so low by the LA Times that it's hard not to call getting to publication a success. Looking back, what were the possible factors that made the WIRED article work when the LA Times one didn't?

• Point of view. The LA Times article was an editorial, while the WIRED article was ostensibly a news story. Editorials are intrinsically opinion-oriented. Wiki can work for expressing personal opinions, but it's not easy, and the result usually isn't a very good read. It's much better as a means for expressing agreed-upon consensus information.
• Topic. The LA Times decided to use the extremely divisive issue of the war in Iraq as the subject of its editorial. How they expected to have a collaborative editing success with this topic is hard to understand. By concentrating on the wiki method itself, on the other hand, the WIRED article covered a much cooler topic that lent itself better to dispassionate discussion and consensus.
• Shared goals. The Times tried to reach out to a mass-market audience that was extremely passionate and divided on the topic at hand. The discussion of the Iraq war had already largely degenerated to name-calling and demonization at that point; the people who were participating had more to gain from keeping the other side from getting a say than from getting their own opinion across. For the WIRED article, the audience was experienced wiki community members -- people who know and understand the technology and culture. They had a shared goal with WIRED and with each other -- to spread the word about wiki in a way that's easy to understand. Although Angela Beesley's point and Mike Cannon-Brookes's article correctly note that the increasing commercial interest in wikis did bring some baggage along, I think there was some common ground that participants could reach.
• Organizational commitment. This, I think, was the key success factor. The LA Times posted their wikitorial as an experiment -- they dipped their toe in the water and pulled back as soon as the going got tough. As far as I know, they had no community management or leadership, and no seasoned wiki community members participating. On the other hand, Ryan Singel's article was hosted on SocialText, and SocialText has made a good business out of teaching companies and organizations the Wiki Way. They've got some of the best wiki minds around on their payroll, and it shows in their ability to manage a wiki project.

Although I think that these experiments are interesting, I don't think they make a very good measurement of whether wiki can work. Obviously, we have thousands of examples that wiki works (see WikiIndex if you need more convincing). I think that people's engagement with a wiki is proportional to their belief in the importance of their own work. If wikis are relegated to a tiny part of a Web site or publication, participants pick up on this de-emphasis and don't put much effort into the project; it's a self-fulfilling prophecy. I think that to be healthy, a wiki needs to be a major part of its parent project, if not the whole thing. That's why, I guess, WikiNews is going to continue to be more relevant and important than one-off wiki article stunts. tags: wiki wikitorial W I R E D latimes ryan singel socialtext

Hyperscope I'm psyched to see that Hyperscope has achieved its 1.0 milestone. Hyperscope is the extension of wp:Doug Engelbart's ideas about hypertext and human intelligence augmentation into the technologies of today's World Wide Web. Eugene Eric Kim has been working hard on the project and gave a great demo of the tool at Wikisym in August. Congratulations to EEK and the entire Hyperscope team! tags: hyperscope hypertext doug engelbart eek

Reporting-MTA: dns; comcast.net
Arrival-Date: 8 Sep 2006 1:46:30 +0000

Final-Recipient: rfc822;
Action: failed
Status: 5.1.0 MAIL FROM: 550 REPLY:
550-"rejected_because_your_SMTP_server,_204.127.225.94,_is_in_the_Spamcop_RBL.
Diagnostic-Code: smtp; Permanent Failure: Other address status
Last-Attempt-Date: Fri, 8 Sep 2006 01:46:36 -0000


• Click Help->Software Updates->Find and install...
• Click Search for new features to install, then New remote site
• Enter "http://www.tresys.com/files/eclipse-update/" as URL, click Finish.
• After that, select the new entry, and install SLIDE (will restart Eclipse).

if has("autocmd")
  filetype plugin on
  augroup te
    autocmd BufRead,BufNewFile          *.te set filetype=te
  augroup END
endif

Read text from the standard input and count the number of times each word occurs. Convert letters to lower case. Order the words according to frequency, words with the same frequency should be ordered in ascending lexicographic order according to character code. Print out the top N words, where N is a decimal number given on the command line. Each output line must contain the count, a space, and the word (in lower case), and end in an ASCII LINE FEED character. Output must contain exactly N such output lines and no other output lines.

A word contains only ASCII letters A through Z and a through z (convert upper case to lower case) and ASCII digits 0 through 9 and is not empty. All other characters separate words and are ignored except to notice word boundaries. Word boundaries only occur at the beginning and end of the file and at non-word characters. You may not assume a maximum length for the word, line, or input file.

import System.Environment
import Data.List
import Data.Char
custwords = filter (/= "") . lines . map (conv . toLower)
    where iswordchar x = isAlphaNum x && isAscii x
          conv x = if iswordchar x then x else '\n'
wordfreq = map (\x -> (head x, length x)) . group . sort
freqsort (w1, c1) (w2, c2) = if c1 == c2
                                 then compare w1 w2
                                 else compare c2 c1
showit (word, count) = show count ++ " " ++ word
main = do args - getArgs
          interact $ unlines . map showit . take (read . head $ args) .
                     sortBy freqsort . wordfreq . custwords