See how rssCloud works—Update: support for threaded microblogging discussion?

I’ll have to take a closer look at the elements. I just cloned a widget with a regular feed (thus the distinctive Green Cross colors). Looks like if the tweet contains a link, the tweet’s widget link goes there; it goes to the widget itself if no link (because I have a target="_top" attribute in it). Hmm. Tomorrow.

Update 9/7: No rush to study the elements. I bulldozed into this Friday night before taking the trouble to really grok the spec. Once rssCloud became an even bigger deal today with the announcement that WordPress would support it, I took more time with it and realized that my widget is missing fully half of the equation. While the feed updates in a minute, Magpie, the parser I use in Expression Engine, doesn’t yet know it’s supposed to look for this new element at the top of the feed:
<cloud domain="rpc.rsscloud.org" port="5337" path="/rsscloud/pleaseNotify" registerProcedure="” protocol="http-post" />
So… it’s the output that still takes more than a minute. I think!

Here’s something I’m curious about: nested rssCloud:items in a new namespace. Dave hasn’t talked about it much yet, and even says here that he might not do anything with it. But check this out:

It makes me think that, when used as an alternate Twitterverse, rssCloud could support threaded microblogging discussion, which would be a big advance.