[twitter-dev] Re: tracking URLs using Streaming API

2009-09-08 Thread John Kalucki

You could track on http, but you'll be rate limited. You can track on
mysite and I think you'll get what you want, and a little more, but if
you track on mysite.com you probably won't get anything.

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



On Sep 8, 4:37 am, Robert Chatley  wrote:
> Hi,
>
> I want to use the Streaming API to track all the statuses that include
> URLs from a particular domain. e.g.
>
> * "I really likehttp://mysite.com";,
> * "http://mysite.com/goodstuffis great"
> etc.
>
> Given the current track api this doesn't seem to be possible? If I
> specify "http://mysite.com"; as a keyword, it doesn't match the above
> cases. Is there a way to do that? A specific keyword syntax perhaps?
> We happen to be using the Twitter4J java client, but I don't think
> this is a client issue.
>
> Using the search api, specifying "mysite.com" (but not "http://
> mysite.com")  finds the statuses we want to match, but we would rather
> use the streaming api rather than polling.
>
> thanks,
> Robert


[twitter-dev] Re: tracking URLs using Streaming API

2009-09-08 Thread Joel Strellner
In order to accomplish this, you need to follow each and every link that
gets passed on Twitter to see if it matches the domain you are looking for.

We do this on inView for our clients, and it may be what you are looking
for: http://myinview.com (Note: This is our service, there may be others
doing this, but if so, I am unaware of them)

-Joel


On Tue, Sep 8, 2009 at 4:37 AM, Robert Chatley wrote:

>
> Hi,
>
> I want to use the Streaming API to track all the statuses that include
> URLs from a particular domain. e.g.
>
> * "I really like http://mysite.com";,
> * "http://mysite.com/goodstuff is great"
> etc.
>
> Given the current track api this doesn't seem to be possible? If I
> specify "http://mysite.com"; as a keyword, it doesn't match the above
> cases. Is there a way to do that? A specific keyword syntax perhaps?
> We happen to be using the Twitter4J java client, but I don't think
> this is a client issue.
>
> Using the search api, specifying "mysite.com" (but not "http://
> mysite.com")  finds the statuses we want to match, but we would rather
> use the streaming api rather than polling.
>
> thanks,
> Robert
>