SSE, Use Cases, and Narcissism

Okay, I’ve been reading Ray Ozzie’s comments on the creation of Simple Shared Extensions (SSE) — an RSS (and OPML) extension to allow two-way communications over RSS — as well as the FAQ and the spec. It’s all interesting and ovedue stuff, and while a more verbose standard than I would like (why is there no apparently limit on the sx:history element? that thing will get massive in a hurry), SSE is still simple enough to merit a closer look. — and as Mike points out, it will spark companies.

Anyway, I’m a narcissist, so I’m more interested in personal use-cases. I currently use Foldershare to keep the watch lists intact across my various Feeddemon instances. While Feeddemon is integrated into Newsgator for subscriptions, it doesn’t synch watch lists, which, at least in the way I use Feeddemon, are more important than the subscriptions themselves. Foldershare works for this purpose, but this is like killing mosquitoes with bazookas: Far more firepower is being deployed than the task at hand requires. It is easy to imagine how SSE could be used to accomplish the same thing in a much more lightweight, distributed fashion.


  1. George Moromisato says:

    You are so right: SSE would be good for synchronizing watch lists. In fact, that’s one of the reasons Dave Winer is interested in it–to synchronize OPML blogrolls.
    As for the limit on update elements, that’s under the control of the publisher. I.e., according to the spec, the publisher can put its own limit on it (trucate history)–and the spec talks about how to deal with trucated history. The bottom line is that you lose some conflict-detection ability, but you get to save disk-space.