track broken?
0 views
Skip to first unread message
Reinier Zwitserloot
May 10, 2008, 9:54:05 AM5/10/08
to Twitter Development Talk
I tried to 'track tipit' and I even get confirmation that I am now
tracking 'tipit', but this is not actually the case. If I send a tweet
'tipit tweet test' from a non-friend, I don't see on the web, I don't
see it on my device. Is 5 letters too short? Does it only work for
#tag?
tracking 'tipit', but this is not actually the case. If I send a tweet
'tipit tweet test' from a non-friend, I don't see on the web, I don't
see it on my device. Is 5 letters too short? Does it only work for
#tag?
Steve Brunton
May 10, 2008, 10:43:39 AM5/10/08
to twitter-deve...@googlegroups.com
cnntrack is tracking 'cnn' and it gets all kinds of Tweets that
contain just those three letters so I don't think that five letters is
to short. I just checked the web side of things for that account and
there isn't anything there, so tracks won't show up on the web side of
things. I'm getting all the track messages through XMPP/IM. I'm not in
the mood to buy an iPhone for a bot (and they won't let me expense it
either) to have it delivered to SMS too. Could your phone provider be
dropping the messages if there is a large flow of them coming through?
-steve
Reinier Zwitserloot
May 10, 2008, 12:42:53 PM5/10/08
to Twitter Development Talk
I apologize, I should have been more obvious about it: It's not coming
through via XMPP.
On May 10, 4:43 pm, "Steve Brunton" <sbrun...@gmail.com> wrote:
through via XMPP.
On May 10, 4:43 pm, "Steve Brunton" <sbrun...@gmail.com> wrote:
Jesse Stay
May 10, 2008, 12:44:55 PM5/10/08
to twitter-deve...@googlegroups.com
Speaking of which, is the Twitter dev team working to implement an API for these track messages? I'd like to be able to see all the items I'm tracking, add, remove, etc.
Jesse
Jesse
Reinier Zwitserloot
May 10, 2008, 12:49:02 PM5/10/08
to Twitter Development Talk
D'oh - my mistake. It only tracks tweets with the keyword in it sent
from accounts with a profile image. I was tweeting from a test account
which didn't have one until I thought of that.
Now my only question is how to turn the extremely scarce info sent in
the XML packet over XMPP when receiving a direct message into
something that's more useful for an API programmer.
from accounts with a profile image. I was tweeting from a test account
which didn't have one until I thought of that.
Now my only question is how to turn the extremely scarce info sent in
the XML packet over XMPP when receiving a direct message into
something that's more useful for an API programmer.
RoelandP
May 21, 2008, 2:33:13 PM5/21/08
to Twitter Development Talk
Hi Reinier,
Are you referring to the tracked direct messages, which are formatted
like this: '(username):message' ?
if you want to collect additional data about the tracked messages you
still need to check the specific '(username)'-info by means of using
the regular Twitter-API.
in other words:
The XMPP is providing you the additional functionality to track
keywords or even receive the complete public timeline, but the API is
still in place whenever you need to get additional contextual user-
information.
gr. Roelandp
On 10 mei, 18:49, Reinier Zwitserloot <reini...@gmail.com> wrote:
> D'oh - my mistake. It only tracks tweets with the keyword in it sent
> from accounts with a profile image. I was tweeting from a test account
> which didn't have one until I thought of that.
>
> Now my only question is how to turn the extremely scarce info sent in
> the XML packet over XMPP when receiving a direct message into
> something that's more useful for an API programmer.
>
> On May 10, 4:43 pm, "Steve Brunton" <sbrun...@gmail.com> wrote:
>
> > On Sat, May 10, 2008 at 9:54 AM, Reinier Zwitserloot <reini...@gmail.com> wrote:
>
> > > I tried to 'tracktipit' and I even get confirmation that I am now
Are you referring to the tracked direct messages, which are formatted
like this: '(username):message' ?
if you want to collect additional data about the tracked messages you
still need to check the specific '(username)'-info by means of using
the regular Twitter-API.
in other words:
The XMPP is providing you the additional functionality to track
keywords or even receive the complete public timeline, but the API is
still in place whenever you need to get additional contextual user-
information.
gr. Roelandp
On 10 mei, 18:49, Reinier Zwitserloot <reini...@gmail.com> wrote:
> D'oh - my mistake. It only tracks tweets with the keyword in it sent
> from accounts with a profile image. I was tweeting from a test account
> which didn't have one until I thought of that.
>
> Now my only question is how to turn the extremely scarce info sent in
> the XML packet over XMPP when receiving a direct message into
> something that's more useful for an API programmer.
>
> On May 10, 4:43 pm, "Steve Brunton" <sbrun...@gmail.com> wrote:
>
> > On Sat, May 10, 2008 at 9:54 AM, Reinier Zwitserloot <reini...@gmail.com> wrote:
>
> > > tracking 'tipit', but this is not actually the case. If I send a tweet
> > > 'tipit tweet test' from a non-friend, I don't see on the web, I don't
> > > see it on my device. Is 5 letters too short? Does it only work for
> > > #tag?
>
> > cnntrack is tracking 'cnn' and it gets all kinds of Tweets that
> > contain just those three letters so I don't think that five letters is
> > to short. I just checked the web side of things for that account and
> > there isn't anything there, so tracks won't show up on the web side of
> > things. I'm getting all thetrackmessages through XMPP/IM. I'm not in
> > > 'tipit tweet test' from a non-friend, I don't see on the web, I don't
> > > see it on my device. Is 5 letters too short? Does it only work for
> > > #tag?
>
> > cnntrack is tracking 'cnn' and it gets all kinds of Tweets that
> > contain just those three letters so I don't think that five letters is
> > to short. I just checked the web side of things for that account and
> > there isn't anything there, so tracks won't show up on the web side of
Reinier Zwitserloot
May 21, 2008, 3:40:29 PM5/21/08
to Twitter Development Talk
Roeland: Actually, all the context I need is sent along in the <atom>
extension in all status updates coming through from all sources (stuff
from random joes with a word in it I'm tracking, stuff from people I
follow, stuff with @myAccount in it), EXCEPT direct messages.
As far as I can tell this is a 'feature' bug - there's absolutely no
reason for the direct message notification to be the only one that
does NOT include an atom excerpt with information that bots need, such
as the twitter id. Right now the only actual use that XMPP gives me is
that I can call the API in response to receiving a direct message over
XMPP. Slightly improves my app's response times but that can't have
been the idea. (because other than knowing there's a direct message,
and the body content, the XMPP notification is useless; nicknames on
twitter can change and thus I don't know who sent it).
I would be much obliged if a blob of atom would be sent in direct
message jabber messages, same as all the other things you get via
jabber.
extension in all status updates coming through from all sources (stuff
from random joes with a word in it I'm tracking, stuff from people I
follow, stuff with @myAccount in it), EXCEPT direct messages.
As far as I can tell this is a 'feature' bug - there's absolutely no
reason for the direct message notification to be the only one that
does NOT include an atom excerpt with information that bots need, such
as the twitter id. Right now the only actual use that XMPP gives me is
that I can call the API in response to receiving a direct message over
XMPP. Slightly improves my app's response times but that can't have
been the idea. (because other than knowing there's a direct message,
and the body content, the XMPP notification is useless; nicknames on
twitter can change and thus I don't know who sent it).
I would be much obliged if a blob of atom would be sent in direct
message jabber messages, same as all the other things you get via
jabber.
Reply all
Reply to author
Forward
0 new messages