Re: [twitter-dev] Re: Twitter Search cache or delayed data?

2009-12-18 Thread Mark McBride
I'm not at all familiar with PHP code, but my guess is that the fopen call failed. That could be due to invalid credentials passed in (did you edit username:password?), internet flakiness, etc. Can you make that call with curl from the command line? On Thu, Dec 17, 2009 at 2:15 PM, Will Ashworth

[twitter-dev] Re: Twitter Search cache or delayed data?

2009-12-17 Thread Will Ashworth
I'm checking out a tutorial I found for the stream API (having not worked with JSON much) and am getting an error. fgets(): supplied argument is not a valid stream resource This is happening when I run it locally under WAMP as a test and also on a live production server (Media Temple). Any ideas?

Re: [twitter-dev] Re: Twitter Search cache or delayed data?

2009-12-17 Thread John Kalucki
The Streaming API has been very reliable. You absolutely build a hashtag counter on the Streaming API and not on the Search API. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Thu, Dec 17, 2009 at 9:44 AM, Will Ashworth wrote: > I've checked into the streaming API and it's

[twitter-dev] Re: Twitter Search cache or delayed data?

2009-12-17 Thread Will Ashworth
I've checked into the streaming API and it's in alpha testing. As this is a live website, we can't necessarily rely on that. The whole idea was for a tweet to count as a "vote" for a submission on our website based on each submission having its own hashtag. If this won't work, then I'm not sure wh

[twitter-dev] Re: Twitter Search cache or delayed data?

2009-12-17 Thread Will Ashworth
Okay. Do we at least know how delayed? I posted a test tweet as we launched the website yesterday with my publicly accessible Twitter account and that was at 3:40 PM PST yesterday. It's been almost 24 hours and I still don't see it come up in search. http://search.twitter.com/search?q=%23befantast