XMPP 'api' lacks practical data for Direct Messages.
0 views
Skip to first unread message
Reinier Zwitserloot
May 11, 2008, 5:00:38 AM5/11/08
to Twitter Development Talk
Strangely enough, when you receive a message through the standard XMPP
device interface (is that an official API, even?), there's a strange
discrepancy: status updates from friends, replies, or tweets from
'world' with a tracked word in them all ship with an extension with
the ATOM data. Nobody that just uses an IM client ever sees these but
us API programmers get most of the data you can get using the HTTP API
out of it.
But for direct messages, you don't get anything. You don't even get
the ID of the message. Just the text. Nothing more.
Is there any way Alex and crew can add the atom XML as extension to
the Direct Message notification like its done for the other
notifications? That would be peachy.
device interface (is that an official API, even?), there's a strange
discrepancy: status updates from friends, replies, or tweets from
'world' with a tracked word in them all ship with an extension with
the ATOM data. Nobody that just uses an IM client ever sees these but
us API programmers get most of the data you can get using the HTTP API
out of it.
But for direct messages, you don't get anything. You don't even get
the ID of the message. Just the text. Nothing more.
Is there any way Alex and crew can add the atom XML as extension to
the Direct Message notification like its done for the other
notifications? That would be peachy.
Alex Payne
May 11, 2008, 12:13:12 PM5/11/08
to twitter-deve...@googlegroups.com
Yes, that's the plan.
--
Alex Payne
http://twitter.com/al3x
Reply all
Reply to author
Forward
0 new messages