[twitter-dev] Re: Streaming API running dry again?

Yes, we just experienced the same issue today... twice too... @sphilipakis http://www.twazzup.com On Apr 1, 3:46 pm, Chad Etzel wrote: > Hi all, > > I am using the filter stream, and twice in the last 24 hour period the > stream has run dry... the connection remains open but no tweets > arrive.

[twitter-dev] Re: Getting friends as usernames instead of user ids

you can also use the statuses/friends method : http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0friends Merry Christmas ! Stephane @sphilipakis On Dec 25, 3:19 am, Raffi Krikorian wrote: > unfortunately, yes. > > > > On Thu, Dec 24, 2009 at 12:12 PM, Michael

[twitter-dev] internal server error 500 on home_timeline

Hi Twitter team I'm getting internal server errors 500 on home_timeline calls for my user (sphilipakis) It seems It's the only account with wich we have issues right now. Anyone can help ? Stephane Philipakis @sphilipakis

[twitter-dev] Re: the new retweet feature might break my app

ere the new RT API leads to :) So probably we will keep on seeing classic RTs in the feed, I'll probably keep on RTing full text as I often need to say more / something else than "I Like it" to my (small) audience. As a developer, I'll try my best to be able to support both as l

[twitter-dev] Re: List API : statuses timeline and count parameter

, Nov 3, 2009 at 5:01 PM, Marcel Molina wrote: > > You can use all the same parameters as are available in the other > > status timeline resources (e.g. max_id, count, since_id, etc). > > > On Tue, Nov 3, 2009 at 4:07 PM, stephane > > wrote: > > >> Hi guys ! >

[twitter-dev] Re: friends_timeline & home_timeline broken

Echo, you are not alone Stephane @sphilipakis http://www.twazzup.com On Oct 8, 5:39 pm, Cameron Kaiser wrote: > > Errm it looks like the friends_timeline and home_timeline are broken, > > search seems to confirm this too. > > > Basically I and many others have had no T

[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up

gt; when I sign-in on twitter, instead of being forwarded to my home_timeline, I'm brought to the Oauth accept page for the 3rd party app "myoauthapp". I think this (buggy) behavior has already been reported on this group several weeks ago Stephane @sphilipakis http://twazzup.com

[twitter-dev] Re: Is twitter down ???

Oauth seems down ... stephane @sphilipakis http://www.twazzup.com On Aug 25, 9:22 pm, Andrew Badera wrote: > status.twitter.com is rarely up to date or detailed. > > I've seen issues on the web the past 20 minutes or so. loading now though. > > On Wed, Aug 26, 2009 at 12:

[twitter-dev] Re: Early developer preview: Retweeting API

Mark has a point there, Twazzup makes use of RTs from the search results to compute some relevancy/popularity scores. If we consider that those RTs are simple "forwards" or "likes", search result could simply provide each tweets with its number of RTs (total number and/or unique RT'ing user numbe

[twitter-dev] Re: API Calls During DoS Attack

Same thing here on google appengine side for www.twazzup.com Stephane @sphilipakis www.twazzup.com On Aug 6, 2:30 pm, Hayes Davis wrote: >  I'm also seeing this same behavior for my whitelisted production IPs for > CheapTweet.com and TweetReach.com. (Those were whiteliste

[twitter-dev] OAuth and twitter.com home authentication strange behavior

n mixing with another OAuth flow) something we, 3rd party app developers, can or should take care of ? Cheers, Stephane www.twazzup.com

[twitter-dev] Re: Search returning slightly different text than actual tweet

So now all links with query that are not tinyfied are broken in search results (web and API)... any ETA for a bugfix ? Cheers, Stephane www.twazzup.com On Aug 4, 10:20 pm, Chad Etzel wrote: > There is a current issue where the Search API is omitting question > marks from search results.

[twitter-dev] Re: created_at format change

It seems all the server don't return the same date format ... probably because of the cached results... What is the recommended action ? is this new format going to be the good one from now on? Should we fix it ? Stephane On Jun 23, 6:02 pm, Christopher Finke wrote: > Around 7:45pm

[twitter-dev] Re: Streaming API: Spritzer-stream coverage

904 I did not push the analysis further though On May 26, 3:24 am, Sven Svensson wrote: > Hi Stephane, > > I used the following calculation to obtain a four percent estimate for > the spritzer stream: >   tweets_seen_in_stream / (max_tweet_id_seen_in_stream - > min_tweet_id_seen_in

[twitter-dev] Re: Streaming API: Spritzer-stream coverage

looking at the tweet ids it looks like the spitzer stream delivers 5 tweets every hundreds this would make it a 5% of the firehose am i correct? Stephane http://www.twazzup.com On May 25, 12:17 am, elversatile wrote: > How are spritzer statuses sampled? Are they picked uniformly at >

[twitter-dev] twitter search API calls are requesting basic Auth sometime

Hi, from time to time today, calls to the search json API return an auth request "Access - Employees only" Is it a behavior of the API service when overloaded ? Is it a temporary ? is there a way to circumvent this ? Best, Stephane Philipakis @sphilipakis