Re: [twitter-dev] Re: Twitter Search cache or delayed data?
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 ashworth102...@gmail.com wrote: 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? The tutorial I found is here: http://hasin.wordpress.com/2009/06/20/collecting-data-from-streaming-api-in-twitter/ Thanks. Hopefully I'm getting closer to a better data collector :) -- ---Mark http://twitter.com/mccv
[twitter-dev] Re: Twitter Search cache or delayed data?
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=%23befantastic04 Thanks for your help. At least I have something to tell my client now.
[twitter-dev] Re: Twitter Search cache or delayed data?
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? The tutorial I found is here: http://hasin.wordpress.com/2009/06/20/collecting-data-from-streaming-api-in-twitter/ Thanks. Hopefully I'm getting closer to a better data collector :)
