My early notes on Radio UserLand hacking might be useful to someone, somewhere, sometime - possibly even me.

Whoa, I just realized that Dan's OPMLRenderer plugin for WordPress is, like, all XSLT. I had trouble getting XSLT working on my server in PHP, yet his code just ran the first time. Obviously I've missed something, and luckily I have his code to school me.

Hmm, seems like the getItem() method of the Aggregator API is not quite working as I'd like. It seems to be truncating item content, as well as including a redundant link to the item itself. What I think I really want is something that sends back a copy of the full item structure in the database. I may end up adding this as a method in an add-on decafbadAggregator API, if I don't resist my temptation to build a REST-styled API.

I've installed and run the OPML Editor for the first time on Windows today. Weird! I'd wondered where that window with the built-in browser came from in screenshots. I wonder how hard / desirable that would be to get working on OS X with a Safari pane? Is anyone using that window for anything extra useful? Oh, wait, that's the MDI window within which all the outline windows live! Yikes, my brain's really soaked in Mac GUI conventions.

I've just created a new page using Dan MacTough's OPMLRenderer plugin for WordPress to publish a .plan outline managed via OPML Editor.

Wiky is a wiki-text implementation in JavaScript. What's really keen about it, though, is that it's bidirectional - that is, it can produce HTML from its own SmartAscii format, and then go back again from HTML source. Why's this important? Well, for my XOXO Outliner and subsequent half-baked start at a structured wiki, I had a notion to push some of the HTML formatting and composition responsibilities onto the client side UI, so that the server just dealt in pure XHTML. This could help with that, if/when I get back to that project.

Hmm, one semi-inconvenience with the WordPress Tool: If I save an entry, then switch back to today's outline for my OPML blog, the attributes returned by WordPress after posting the entry (blog post ID, etc) get applied to the current entry on the OPML blog. i think I understand why, but not sure how to fix yet...

The import page for Technorati Favorites mentions that it supports XOXO as a format along with OPML. Cool! I'm a known XOXO lover. So, I tried importing my OPML "amusements" reading list as an XOXO outline. I used the XSL transformation I mentioned a few weeks ago, tweaked to follow some ideas for subscription markup in XOXO. Well, it looks like it worked! So, what's the moral of the story? I can use the OPML Editor and still use XOXO, thanks to my stylish glasses. Although, it would be nice to have a profile, spec, or guideline as to what XOXO is expected by Technorati Favorites - XOXO is a pretty wide open microformat. I mainly made an educated guess, followed a wiki brainstorming example, and crossed my fingers as I hit submit.

Good morning. Coffee good, bed better, but here I am. How's about you?