Status-Q

[Original Link] If I criticise you in my blog, you may soon be able to demand the right of reply. Perhaps. An article by Declan McCullagh is causing some concern on Slashdot, where they’re wondering what would happen if Microsoft decided to respond to every criticism!

Still, this is only in Europe and may not be enforceable even here. I wonder if adding an unmoderated ‘comments’ feature to a blog would be enough to satisfy the legislation?

[Original Link] Walt Mossberg gives a very balanced account of his experiences with a Segway. Pun intended. [Thanks to John Naughton for the link.]

[Original Link] Paul Boutin’s very readable description of how the Slammer worm worked.

[Original Link] Dan Gillmor on the inevitability of internet telephony. We use it regularly for most of our transatlantic calls….

[Original Link] At long last, Apple’s splendid iSync is starting to support a much larger range of devices.

[Original Link] …but I’ve never tried emulating one.

[Original Link] A wonderful collection of public pronouncements about Weapons of Mass Destruction in Iraq. (Thanks to Adam Curry for the link)

[Original Link] Dave Winer hits on what is, for me, a key attraction of weblogs:

“On my weblog no one can change what I wrote. In contrast, having written for professional publications, pros have to prepare for their writing being interfered with. Sometimes you submit right at the copy-edit deadline. Or you write exactly the required number of words so nothing can be cut. But in the end, the words that appear are an amalgam of what your organization thought should be said on the subject you’re addressing.”

Exactly this has happened to me, most recently writing for the Communications of the ACM and the IEE Review. The dear old CACM, for example, objected to my use of the phrase “three score years and ten”, presumably as requiring too much education on the part of its readers. Sad to see such dumbing down in what used to be an academic journal. They admitted it, too, though with the qualifier, “…we call it ‘mainstreaming'”.

The Review editors, on the other hand, introduced typos, while cutting out entire paragraphs, with the result that I appeared to be arguing the opposite point from my intended one, and doing so incompetently. This was done at the last minute, of course, after I had approved another version.

In both of these cases, it’s only really my wounded pride that bothers me, because despite their large distribution numbers, I doubt very many people actually read that sort of journal any more. I care less about the mangling of my words than that my name is still associated with them afterwards! I make lots of mistakes and stylistic errors too, of course, but at least here I can fix them before too many people notice.

[Original Link] Dave Shea’s ‘Zen Garden’ is a wonderful demonstration of the power of CSS. Recommended for anybody who designs web sites. [link from Scripting News]

I’ve just been doing a (much less ambitious) web site. Since it’s been a while since I last did any substantial HTML coding, I’ve been finding it a real joy to use CSS with the realistic expectation that almost all of the intended audience will be able to see the results as I intended.

[Original Link] David Berlind tells it like it is. Bluetooth is great when it works, but more often than not, it doesn’t. One of the follow-up comments says, “Bluetooth is destined to be the Edsel of IT…”. And another, “…at some point we have to take stock and decide whether it is worthwhile to continue investing in an architecture that has taken so long to deliver so little”. Sad, but true. It works flawlessly for me but only in one specific situation: connecting my Mac to one of the small number of Apple-approved Ericsson phones.

I’ve written about this before: I linked to an osOpinions article and also to a BusinessWeek article, among others. The BW article has now disappeared behind a pay-for-access barrier. So I’m likely to link to them in future about as often as I try linking to my Bluetooth headset.

When you update a blog, many systems have the ability to ‘ping’ another site to tell it that something has changed, typically using the weblogs.com XML-RPC interface.

I wanted to be able to receive these pings and to perform some simple operation as a result; in this case grabbing an file from the associated Movable Type blog. Here is a very simple Python CGI script which does just that, based on Jan-Klaas Kollhof’s neat little xmlrpc server module.

Update: This works with Movable Type – in your weblog config you can specify it as one of the sites to be notified by typing the CGI script’s URL into the ‘Others’ box. However, MT has a bug which gives it a tendency to misinterpret the results and think that the ping has failed when it has in fact succeeded. The call returns two values, and MT assumes that they will be in a specific order when the order is, in fact, irrelevant. To fix this, edit the lib/MT/XMLRPC.pm file and change:

  my($error, $msg) = $content =~
        m!flerror.*?<boolean>(d+).*message.*?<value>(.+?)</value>!s;

to say

    my($error) = $content =~  m!flerror.*?<boolean>(d+)</boolean>!s;
    my($msg) = $content =~  m!message.*?<value>(.+?)</value>!s;

at approx line 71.