mircoblogging is nice for some things and implementations
already make use of XMPP for it. However it seems to be more a hype
and it's in constant development and features and such change,
custom im bots can cover these changes easily, an open protocol
can't. last but not least i don't see how he user experience will
be better using this protocol instead of the current use of simple
s
I think microblogging over XMPP is the future as it now becomes
obvious that using HTTP for this is not a good idea - look at
Twitter, it is the symbol of technical problems. Of course there
are probably other bottlenecks, but still.
I think the main advantage for users is that clients may have
dedicated ui support, so that you don't get lost when the thread
context changes, as it happens sometimes here
I think there's some mileage in a bot with certain known base
functionality covered, so "microblogging-aware" clients might take
advantage of it. Depends if we could get buy-in from
Jaiku/Twitter/etc or not.
Building IM bots is not easy. Parsing plain text for possible
commands is not really great to do. Ad-hoc commands could solve
that partially, and something like this for publishing would
actually be pretty flexible, unlike what @tobiasfar seems to think. I did
have a bunch of comments
on the protoxep, though :-)
14 comments so far
This proto-XEP looks nice, specially regarding threading.
1 week, 1 day ago by kael.
mircoblogging is nice for some things and implementations already make use of XMPP for it. However it seems to be more a hype and it's in constant development and features and such change, custom im bots can cover these changes easily, an open protocol can't. last but not least i don't see how he user experience will be better using this protocol instead of the current use of simple s
1 week, 1 day ago by tobiasfar.
it would be very good, imho.
1 week, 1 day ago by huni.
yes, perhaps a bot interface is the way to go -- most people seem comfortable with that, after all :)
1 week, 1 day ago by stpeter.
a bot with an ad-hoc command interface
1 week, 1 day ago by nyconyco.
I think microblogging over XMPP is the future as it now becomes obvious that using HTTP for this is not a good idea - look at Twitter, it is the symbol of technical problems. Of course there are probably other bottlenecks, but still.
1 week, 1 day ago by vardo.
I think the main advantage for users is that clients may have dedicated ui support, so that you don't get lost when the thread context changes, as it happens sometimes here
1 week, 1 day ago by sciasbat.
yes that can be very confusing :)
1 week, 1 day ago by stpeter.
I think there's some mileage in a bot with certain known base functionality covered, so "microblogging-aware" clients might take advantage of it. Depends if we could get buy-in from Jaiku/Twitter/etc or not.
1 week, 1 day ago by dwd.
true, I'll have to ping my various contacts about that...
1 week, 1 day ago by stpeter.
Of course Miccroblog on XMPP is a good idea !!!
1 week, 1 day ago by biojab.
so we hope :)
1 week, 1 day ago by stpeter.
But your protoXEP looks good as a decentralized way of doing things, which makes a lot of sense. (finally!)
1 week, 1 day ago by dwd.
Building IM bots is not easy. Parsing plain text for possible commands is not really great to do. Ad-hoc commands could solve that partially, and something like this for publishing would actually be pretty flexible, unlike what @tobiasfar seems to think. I did have a bunch of comments on the protoxep, though :-)
1 week, 1 day ago by ralphm.