SSE and Blogs:

I subscribe to your feed through bloglines. This post, like all others, are delivered to my bloglines inbox where I access and read. When a particular post arrises that I’d like to comment on, I click the comment button, am redirected to your site where I’m able to post a comment.

Enter SSE. If you (or your blog software) were to implement SSE and Bloglines was to support it, it’d be possible for me to post my comment directly from the blogline reader. True, this is possible through APIs; but APIs are propriatary. An API written for TypePad is not the same as an API written for WordPress, currently it’s up to the RSS agregator software to support what APIs it desires. With SSE, an aggregator only has to support one specification.

SSE and Calender Apps:

My Wife uses Lotus. I use Outlook, Blackberry, and sometimes Upcoming. There’s never a single moment where all our calenders are sync’ed. To transfer an appointment from me to her I have to physically email her the information and she enteres it into her calender. It’s a hastle.

With SSE, I would set-up a group (say family appointments) and when both of us are subscribed to this group, any appointment she classifies as family will show on my various calenders and vice versa. Also, any changes either of us make to an appointment will automagically be reflected in the others calender.

SSE and Social Apps:

Take groups. I a jeep collector. There’s many groups dedicated to jeeps out there (yahoo, livejournal, google, ifsja, etc.). To stay up on jeeps would be a fulltime job. Say that I could find my favorite “jeep stay-up” software. With SSE (being that it’s supported on all platforms) I could read, post, and comment all from my favorite medium.

All these things are current possible with a lot of toil and coding, but the prospect of a simple standard of two-way data transfer; the possibilities are vast. Think. These are simple possibilites, when a mind far richer than mine captures the concept; some pretty sweet apps may come from this.