By default, Movable Type RSS entries only include the first twenty words of an article. This seems wrong - if the principal way in which content is to be read is through an RSS aggregator, much of the interesting comment will be missed.

It's easily fixed - change the RSS 0.92 and 1.0 templates to use MTItemBody rather than MTEntryExcerpt.

To see what you are missing, compare the RSS datafor Daring Fireball with the siteitself.

I've been experimenting with a small script to take a bunch of RSS/RDF feeds and inject them into newgroups. Perl is a convenient language - libraries for RSS parsing, an NNTP client, etc. all exist and can be downloaded from CPAN. But Perl is full of so much syntactic goop. Sometimes that gives you power, as you can attack problems for a variety of different angles. Then, some things seem clumsy. For example:

$from = $result{'managingEditor'};
if ($from eq "") {
    $from = $result{'webMaster'};
} if ($from eq "") {
    $from = "invalid\@invalid.invalid";
}

From Alec Muffett:

Neil Cowie, senior virus researcher at the McAfee lab, said it was now seeing between 150 and 200 new viruses per month. In total there are more than 30,000 documented viruses.

Those numbers don't seem credible. 150 new virus in a month means that we average about 5 each day. Funny that Neil Cowie works for a company that sells virus software...

Having baroque connectivity some of the time is a real strain.

At workaccess to the outside world is via one of two mechanisms:

A pertinent example of this is the difficulties in trying to get Radio upstreaming to work in this environment. Using the Radio Userland servers (accessed using SOAP over HTTP it would appear) works well. Any attempt to publish using ftp to machines at homeseems doomed.

The fact that there are (at least) two other network configurations to consider ("DSL at home" and "DSL at home with Cisco VPN") suggests that I'll be sticking with with Radio Userland servers for a while :-(

The wireless network for the office is up and running now. Initially, the Regus supplied network port had almost all traffic restricted (only possible use was web browsing, and that through a "transparent" proxy). They were actually quite good at sorting it out over the phone, and within an hour we had all of the restrictions removed.

Performance is quite good - with our Cisco VPN running between my laptop, over wireless, through firewall, through Regus network to BT, over the internet to the VPN server, etc. the RTT is around 25ms. Perfectly usable.

Proposed instructions are written, just being reviewed by Richard, Paul, Guy and Alec Muffett.

Here are the functions to mangle the new xml.el output back to a format that xml-rpc.el is more content to understand:

(defun xml-rpc-clean-string (s)
  (let ((new-string (replace-regexp-in-string "^[ t\n]+" "" s)))
    (if (string-equal "" new-string)
	nil new-string)))

(defun xml-rpc-clean (l)
  (cond ((listp l)
	 (let ((remain l)
	       elem (result nil))
	   (while l (let (tmp)
		      (setq elem (car l)
			    l (cdr l))
		      (cond ((stringp elem)
			     (if (setq tmp (xml-rpc-clean-string elem))
				 (append (list 'result)
					 (list tmp))))
			    ((listp elem)
			     (append (list result)
				     (list (xml-rpc-clean elem))))
			    (t (append (list result)
				       (list elem))))))
	   result))
	((stringp l)
	 ;; will returning nil be acceptable ? (xml-rpc-clean-string elem))
	 (t l)))

When combined with:

It seems that the version of url.el that I was using was too old for blogger.el (well, xml-rpc.el). Getting the version from CVS fixed that.

Unfortunately it seems that this isn't enough. To have a good version of Emacs for MacOS X, I'm running the CVS version of Emacs. There are some changes which have been made to xml.el such that it no longer ignores whitespace in XML text which it is given. The whitespace turns up as strings in the resulting emacs lisp lists. This confuses xml-rpc.el a great deal, causing failure.

Mail sent to Mark Hershberger(the author of xml-rpc.el version of blogger.el). Perhaps Daniel Lundinwould be a better bet.

Strangely, I was browsing Advogato's recent diaries, and I came across someone elsehaving problems, though they don't say which version of Emacs is involved.

Trying to get the emacs blogger.elposting to my local Radio server is driving me nuts. Wandering through the xml-rpc.el data structures in the lisp debugger is unpleasant !

Oh well. We didn't deserve to win the game on the day.