Topic of the weeki

Everybody’s talking about Wikileaks, so in general, I haven’t. People like John are doing a much better job than I ever could.

There was some discussion on a couple of the Twit.tv podcasts about the heightened emotions directed at Wikileaks itself, though, and I thought they came to some sane conclusions, which were roughly as follows:

  • The person who committed a crime was the original source, who is now being dealt with by the law
  • Wikileaks did no more than any newspaper would have done if it got its hands on the material, and is no more or less culpable than the New York Times and the Guardian and others who have been republishing it.
  • Wikileaks just did it more efficiently and for different, and some would argue, more honourable, motivations than a newspaper’s. [This is the real novelty. People know how to interpret newspapers’ actions.]
  • Those hackers attempting to target organisations that failed to support Wikileaks are guilty of suppressing the kind of freedoms of speech and action for which Wikileaks stands.
  • The big danger is that any measures brought in to ‘deal with’ Wikileaks could be used against the New York Times and the Guardian in the future.

That seemed to me a pretty good executive summary, but what a lot of fun debate is going on about these, and all the ramifications, especially as initial outrages give way to more careful considerations.

They’re all missing the real question, of course: who will play Assange when the movies start to come out?

Enjoyed this post? Why not sign up to receive Status-Q in your inbox?

1 Comment

[…] it’s almost a year since the big WikiLeaks furore. Tempus does indeed fugit. At the time I wrote briefly about the similarities between WikiLeaks and print […]

Got Something To Say:

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

*

© Copyright Quentin Stafford-Fraser