I ran into this with Firebug 1.5 and Firefox 3.5.7. For now I'm reverting to Firebug 1.4.5, since that seems to be less problematic.

'Electronic commerce, we eventually figured out, does not take the form of “shopping malls” you “walk” through. “Magazines” and “catalogues” do not have discrete pages you flip (complete with sound effects) and dog-ear. “Web sites” do not look like magazine layouts, complete with multicolumn text and callouts.' An interesting post on moving things to the web.

I seem to be on a bit of a JSON crusade at the moment; hopefully I'll be able to get a few other people to sign up along with me.

My patch to XML::Feed's Atom accessors.

I need to apply this patch to my local XML::Feed, after I've done a similar patch/test job on the changes I made to get a valid Atom feed out of the module.

Google's blog import format uses Atom/XML, like the Alastair Rankine proposal.

Using Atom as a format for blog exports. Lots of comments. Draft last updated late last year.

Call me lazy, but I like JSON and YAML because they're an eval away from being useful data structures. XML, by contrast, always seems to be painful.

His simple example is like the one I knocked up for Vox; the one that didn't work.

Looks like Python for the S60 phones has, er, XML issues. Also, Growl tiein. Might be nicer. +1 on the call for a buddy icon API. (hmm, does Flickr let you get them?)

Using XML/RDF to combine Drowned In Sound and Openguides data. I think.

Why Mozilla don't think you should send XHTML

could be useful

Apparently the format is a bit wacky; looks a lot like an RDBMS dump. Ho hum.