ope this helps out anyone else using python.
On Jun 7, 9:26 am, Ray Slakinski wrote:
> I should add the account I'm using to follow my account and my co-
> workers is not the same one as either of these 2. Its completely
> separate.
>
> On Jun 6, 12:46 pm, Matt Harris wrote:
I should add the account I'm using to follow my account and my co-
workers is not the same one as either of these 2. Its completely
separate.
On Jun 6, 12:46 pm, Matt Harris wrote:
> Hi Ray,
>
> There isn't a buffer that has to be filled before the Streaming API delivers
&g
h. My nor my co-workers streams are private.
Ray Slakinski
On Jun 6, 12:46 pm, Matt Harris wrote:
> Hi Ray,
>
> There isn't a buffer that has to be filled before the Streaming API delivers
> tweets. Only public tweets created after you open a connection will be
> delivere
I I start following just 1 or 2 people using the streaming API I do
not get any of their tweets. Is there a buffer that needs to be filled
before I get these?
Ray Slakinski
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com
Trying this second method and it seems if there are just a few follow
ids I dont get the tweets for those users, I'm curious to know if
there is some sort of buffer. It would also seem to appear that I
loose connection if its idle too long.
Any ideas/thoughts are welcome
Ray Slakinski
On
loose tweets during the time it takes to reconnect, especially
if its frequent enough.
So does the API handle this scenario and I'm just missing something?
or any tips/tricks that might make the transition smoother as users
get added/removed?
Ray Slakinski
--
Twitter developer documentation and
Awesome, thanks EH.
On Nov 29, 2010, at 1:38 AM, Edward Hotchkiss wrote:
id_str iteration.
On Nov 27, 2010, at 9:43 AM, TweetzMatter wrote:
Anyones valid answer is appreciated:
How is it that moments after opening a twitter account, 2 or 3
'spam' followers have already found it?
Drives m
I would think that this would make no difference for since_id. The
purpose of since_id is for us to the API "give me the data I need
that's happened since this id". Don't assume it's implemented as
"select * from tweets were id > since_id". :)
On Mar 26, 4:01 pm, Michael Bleigh wrote:
> To those
affect multiple, successful,
authorized logins? I'm hopeful that "this approach" means that our
apps will not be affected yet again by changing to a new auth
approach.
I appreciate you all keeping this thread informed.
Ray
On Jul 27, 11:23 am, Doug Williams wrote:
> Thanks to everyone w
I'm with Jesse on this one
On Apr 16, 10:03 pm, Jesse Stay wrote:
> stevenic, after so many followers, that one DM cascades into hundreds. I
> don't want my DM box filled with people wanting to sell me stuff. I want
> the choice to control that - I don't want the marketers controlling that.
>
;);
curl_setopt ($curl_handle, CURLOPT_USERPWD, "$username:$password");
$buffer = curl_exec ($curl_handle);
curl_close ($curl_handle);
**
Regards,
Subhankar Ray
http://AAfter.Com
11 matches
Mail list logo
