Shashi wrote:
But what I have found is that although the
XMPP stream already contains abundant data (i.e an xmpp body, an html
element and an atom entry) it is not enough for a fully-featured
client to feed on. For instance it does not contain in_reply_to data
like the api does, which will be a very good piece of information for
showing threads and conversations in the client.
I can't replicate this. I see the in_reply_to data in XMPP output, and
the code for generating an Atom Entry for XMPP and for HTTP is the same.
-Evan
--
Evan Prodromou
CEO, Control Yourself, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
