On Oct 4, 2007, at 12:21 PM, Peter Saint-Andre wrote:
I was just thinking about suggesting this to you in the comments
on your
XMPP post. Subscribing to a feed via instant messaging has long
been on
my todo list of cool features that nobody but me would care about.
It'll
probably be years before I have an implementation though (precisely
because nobody but me would care). When I do, I'll be sure to get
back
to you.
In fact the IM integration features of microblogging services like
Twitter and Jaiku seem to be very popular. Whether IM integration (or,
to be more precise, real-time notification) makes sense in more
traditional blogging scenarios remains to be seen. I happen to use
my IM
client as a feed reader using the Mimir service, but I'm probably
in the
minority...
As you know well Peter ;) the client that gets Jabber notifications
of feed changes doesn't need to be an IM client. The BIFF BoF last
IETF was about getting email clients that wanted realtime
notifications of mail store events to implement jabber or SIP in
order to get those -- rather than try to turn some request-oriented
protocol into a notification protocol. I don't know where this will
end up, but I certainly wanted to encourage people to consider using
two protocols between client and server -- a request-oriented one for
heavy data retrieval, searching and the like, and a notification-
oriented one for change events. Some clients and helper applications
will only need to implement one of the two, while a rich powerful
client would probably in the long run implement both.
FWIW, the BIFF BoF seemed to generate interest in discussing use
cases and narrowing scope, but since then nothing has really happened
due to lack of activity, and there won't be a follow-on meeting, BoF
or WG, in Vancouver.
Lisa
