Wow no reason to be so angry -- it's just some pings going back and forth. There's no need to make it personal. Besides, I've had way worse ideas.
We've always planned to have a variety of update notifications available -- the first we did was Jabber/XMPP, now RSS Cloud, after this we'll do some others. I mentioned this in my post on the subject, which you can check out here:
We've supported other things before, like Atom Publishing, that to this day get almost no use (literally less than but we support them anyway because it can't hurt and might help. In general I would consider myself API- and format-agnostic.
The vitriol on my part was due to the Winerian aspect -- the man has a long history of fucking up everything he touches technically, and vindictively fucking over anyone less than sycophantic. Run away.
APP doesn't see much use in Wordpress because nobody uses desktop blogging clients anymore. However, it is widely implemented on both sides (even Microsoft!), something that will never be true for <cloud>.
'RSSCloud' is inelegant, idiotically-designed (he thinks traditional SOAP posted to a resourcey URL is REST!), doesn't help centralized aggregators scale, doesn't work with NATed clients, and worst of all it was specced/never-implemented/forgotten by Dave Winer 8 years ago. At least you were smart enough not to use rpc.rsscloud.org -- Winer can't be trusted to host anything for anyone (eg: weblogs.com).
Google, Bloglines, Facebook, Twitter, et. al. will never implement it. The only people <cloud> could possibly help would be the few running their own server-side aggregators. Implementing PubSubHubBub would actually help people -- doing this just feeds Winer's ego (and thus pumps up the drama).
Why the hell were you still serving duplicate RSS2 at all anyway? The only extant feedreaders that don't grok Atom were written by Winer (and he's the only user left!).
Last month we got 688,000 new blog posts via XML-RPC, so desktop clients are still meaningful. (XML-RPC API is also used by other folks like Flickr.) APP may be better, I don't have a strong opinion, but it's hardly used and in fact we had trouble finding clients to test with when writing support for it. Regardless, we try to have the best support for APP possible.
Same thing with feeds -- we offer every feed in a choice of 4 formats (two Atoms, two RSSes). It's the same content and there's no overhead to us (it's just a template file) so why not let people choose what they like best.
We've always planned to have a variety of update notifications available -- the first we did was Jabber/XMPP, now RSS Cloud, after this we'll do some others. I mentioned this in my post on the subject, which you can check out here:
http://en.blog.wordpress.com/2009/09/07/rss-in-the-clouds/
We've supported other things before, like Atom Publishing, that to this day get almost no use (literally less than but we support them anyway because it can't hurt and might help. In general I would consider myself API- and format-agnostic.