[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 jazzyc...@gmail.com 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. If I manually kill the connection and reconnect everything works properly again (so I don't think my account somehow got banned). I know this issue popped up and was squashed not too long ago, but is anyone else experiencing this again recently? -Chad
[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 ra...@twitter.com wrote: unfortunately, yes. On Thu, Dec 24, 2009 at 12:12 PM, Michael mbw...@gmail.com wrote: Ok, thanks! So, in the meantime you would say that the only way to do this is run through all the ids, callhttp://twitter.com/users/show.xmlon each id, and parse out the ursername from the xml returned? On Dec 24, 2:52 pm, Raffi Krikorian ra...@twitter.com wrote: we are working on releasing a bulk lookup API (i don't have a release date on it yet), and you will be able to use that for this purpose. On Thu, Dec 24, 2009 at 10:31 AM, Michael mbw...@gmail.com wrote: I am using thehttp://twitter.com/friends/ids.xml?screen_name=$username method to get a list of friends for a user. However, the friends come back as ids. Is there anyway I can convert these ids to their usernames? -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[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
Thing is the new RT api simply does not express the same thing the classic RT @xxx is : It's a subset of a big set of meanings : [ Like , Forward , Comment, Thanks, Emphasis, Reply ] (and I'm sure there are a lot more uses) The rich semantic of classic RTs make them sometime difficult to analyze through simple algorithms but is a no-brainer for a human. Twitter (or Ev) thinks that they needed to disambiguate the RT concept. I'm really not sure about that on the user perspective ... though I see the advantages for the platform. They probably decided to chose the most frequent use (ie : Like). It's a really complex issue, I would not have addressed this way personally (we went through the exact same brainstormings when working on Yokway) but I'm curious to see where 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 long as possible. Stephane http://www.twazzup.com On Nov 13, 2:54 pm, Cameron Kaiser spec...@floodgap.com wrote: Speaking for TTYtter only, while I'll support receiving retweets, I am unhappy with the API as it currently exists and retweets received will be canonized into the older format (and retweets sent will be done programmatically in the older fashion instead of through the retweet methods). I suspect there are other app authors who will also do something similar. I haven't looked closely at the RT API (it's not currently relevant to FishTwits, so I figure I'll let it stabilize before concerning myself with it), but would you mind sharing your issues with it, either here or off-list if you think that would be more appropriate? It isn't the API methods per se, it's the fact that (as others have pointed out) there is no way to edit or mark up a tweet using the Retweet system as it is currently designed. This is important to me personally, and certainly to anyone posting with #saveretweets. Also, as implied by the fact that I won't be supporting it in its current form, it's easy enough to continue to post in the old manner (or come up with a new one), which dilutes its alleged advantages in trackability and ignorability, and I've always considered it more important to know who is doing the retweet than who is being retweeted, because who the filter is tells me as much if not more than what is being filtered through them. These are just complaints about the design of the system, although in fairness to Ev, he has acknowledged some of the deficiencies and has implied they will be fixed in later versions (cf. http://evhead.com/2009/11/why-retweet-works-way-it-does.html ). But I won't be supporting posting through it in its current form. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- BOND THEME NOW PLAYING: Thunderball --
[twitter-dev] Re: List API : statuses timeline and count parameter
cool :) thx a lot ! On Nov 4, 2:34 am, Marcel Molina mar...@twitter.com wrote: Oh. I've realized that all the options *except* for count are supported. Fixing that now. Should be deployed to production in the next day or so. Thanks for reporting this. On Tue, Nov 3, 2009 at 5:01 PM, Marcel Molina mar...@twitter.com 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 stephane.philipa...@gmail.com wrote: Hi guys ! Is there a way (or planned method) to get more than 20 statuses per list timeline API call ? apparently there is no equivalent to the count parameter. Best, Stephane Philipakis @sphilipakis www.twazzup.com -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[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 spec...@floodgap.com 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 Tweets appear here for over an hour, yet I know 100% that there are users on my feed that have tweeted. Echoing this. I'm seeing this also. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- I think you underestimate the sneakiness.
[twitter-dev] Re: Ignoring OAuth application authorization page once causes following pages not be able to load up
The problem I usually (systematically in fact) encounter is that if 1 / I start a oauth process (go to the oauth login page on twitter) from a 3rd party app (say myoauthapp) 2 / I don't click neither accept nor deny and just close the window (or tab), - 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 On Oct 7, 9:59 pm, Michael Steuer mste...@gmail.com wrote: I¹m not angry. This is however a mailing list about Twitter development, and Panu is posing what seems like a legitimate question relating to Twitter development. Sending SPAM as original messages as one thing and would be ignored by everyone, sending spam in response to legitimate questions/threads is another, and probably especially frustrating for the person trying to get an answer to a question, in this case Panu. Anyway, just my 2 cents. Panu I tried to reproduce that issue on my machine, but wasn¹t able too. Perhaps someone else can weigh in with a response that¹s not about disk defragmentation ;) On 10/7/09 12:39 PM, JDG ghil...@gmail.com wrote: it didn't waste a ms of my time. it only wasted your time by responding. why do people get so angry about things they see on the internet? it's the easiest thing on the planet to ignore. On Wed, Oct 7, 2009 at 13:17, Michael Steuer mste...@gmail.com wrote: Is this a joke? Why waste 100s of people¹s time?! On 10/7/09 10:10 AM, thomas cavanaugh tomros0...@gmail.com http://tomros0...@gmail.com wrote: windows 98 and above 1 reboot 2 opencomputer go to storage drives click on properities., click on defrag or clear button defrag or clear NONESSENTIALS FROM THAT DRIVE.,reboot again if this doesnt solve the problem consult microsoft especially if it is windows vista operating system .there is an internal conflict between downloaded soft ware on your unit probably conflicting security programs.,, be patient let me know how you make out t. On Wed, Oct 7, 2009 at 12:38 PM, Panu Tangchalermkul pan...@gmail.com http://pan...@gmail.com wrote: I have tested this on 2 Twitter OAuth demo site, http://twitteroauth.appspot.com/ http://fourmargins.com/labs/twitter_oauth/ by using Firefox 3.5 and Internet Explorer 8 on Windows Vista 32bit Every time after I ignore (close without any action on the page) Twitter OAuth application authorization page (the page that has Allow and Deny button), I cannot load any page that using Twitter OAuth API including Twitter own login system. To describe in step-by-step, I open one of the above OAuth demo website, click on the link that will give the application an access to my twitter account, a browser redirect me to twitter page that require me to choose Allow or Deny, I choose to ignore it and close that page. Then I regret my action and try to open it again, I have encountered The connection was reset on Firefox 3.5 and Internet Explorer cannot display the webpage on IE, after I have clicked the same link. I don't know why but it seems deleting all cookies is an only resolution. This is reproducible every times on my machine. OAuth BUG?
[twitter-dev] Re: Is twitter down ???
Oauth seems down ... stephane @sphilipakis http://www.twazzup.com On Aug 25, 9:22 pm, Andrew Badera and...@badera.us 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:17 AM, Vigneshvignesh.isqu...@gmail.com wrote: All my api calls are getting a download error and the twitter website itself is not opening, http://status.twitter.comhas no updates about this What is happening?
[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 number ?) and one could argue that there is no real need for RT's as entries in the search results. Another nice effect to this : increasing the twitter search memory by reducing the amount of tweets to keep in the index. This is overall a good step, I'd just like to know how disruptive it's going to be for apps that use twitter search API ... @sphilipakis www.twazzup.com On Aug 14, 12:59 pm, Mark Nutter marknut...@gmail.com wrote: So when someone uses this retweet feature, does it actually create a status update in the twitter system? In other words, if I retweet your post, and I use the search api and look for tweets posted by me, will that retweet show up as a search result? Is this new retweet feature going to kill a good portion of the tweets that you might find using the search API? I would have to imagine sites like tweetmeme would be interested to know this. Providing an array of the people who have retweeted a particular link would be a very handy API call to have (without requiring user authentication). Do you plan on including that feature if actual posts aren't being created? On Aug 13, 3:52 pm, Marcel Molina mar...@twitter.com wrote: Retweeting has become one of the cultural conventions of the Twitter experience. It's yet another example of Twitter's users discovering innovative ways to use the service. We dig it. So soon it's going to become a natively supported feature on twitter.com. It's looking like we're only weeks away from being ready to launch it on our end. We wanted to show the community of platform developers the API we've cooked up for retweeting so those who want to support it in their applications would have enough time to have it ready by launch day. We were planning on exposing a way for developers to create a retweet, recognize retweets in your timeline and display them distinctively amongst other tweets. We've also got APIs for several retweet timelines: retweets you've created, retweets the users you're following have created, and your tweets that have been retweeted by others. - Creating Retweets The API documentation for creating retweets can be found here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retweet Reminder: Making requests to /statuses/retweet won't work yet as the feature has not launched. - Consuming Retweets in the Timeline 1) Retweets in the new home timeline We don't want to break existing apps that don't add retweeting support or create a confusing experience for that app's users. So the /statuses/friends_timeline API resource will remain unchanged--i.e. retweets will *not* appear in it. For those who *do* want to support retweets, we are adding a new (more aptly named) /statuses/home_timeline resource. This *will* include retweets. The /statuses/friends_timeline API resource will continue to be supported in version 1 of the API. In version 2 it will go away and be fully replaced by /statuses/home_timeline. The API documentation for the home timeline, which includes retweets, can be found here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-home_t... Take a look at the example payload in the documentation. The original tweet that was retweeted Thanks appears in the timeline. Notice the embedded retweet_details element. It contains the user who created the retweet as well as the date and time the retweet occurred. 2) Retweeted by me timelinehttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retwee... 3) Retweeted to me timelinehttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retwee... 4) My tweets, retweetedhttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retwee... Reminder: Making requests to any of these timelines won't work yet as the feature has not launched. UI considerations: -- Here are some early draft design mockups of how retweets might appear on the Twitter website (don't be surprised if it doesn't look exactly like this). They are presented just as an example of how retweets can be differentiated visually. http://s.twimg.com/retweet-dev-mocks-7-aug-09.png Things to note: 1) It was important for us that retweets are easily differentiated visually from regular tweets. If someone you follow retweets a tweet, the original tweet will appear in your timeline whether you follow the author of the original tweet or not, just as it currently does when users use the RT convention. Seeing a tweet in your timeline from someone you don't follow without being told it was shared from someone you *do* follow could be confusing.
[twitter-dev] OAuth and twitter.com home authentication strange behavior
It's probably linked to the current DDOS but the authentication flow shows some strange behavior : 1 - I try to initiate an OAuth authentication from www.twazzup.com - twazzup server gets a timeout trying to connect to twitter for oauth token (ApplicationError 5 on appengine) 3 - I go to twitter.com click sign-in - strangely twitter redirects me to the oauth authorization form (do you want to allow twazzup blabla ...) So I have to questions there : A / did you block incoming OAuth reqs from appengine ? B/ is the strange behavior (twitter home authentication 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: 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 ha...@appozite.com wrote: I'm also seeing this same behavior for my whitelisted production IPs for CheapTweet.com and TweetReach.com. (Those were whitelisted under the @CheapTweet and @appozite accounts, respectively.) It works in development, but no requests are getting through to twitter.com on our production servers. I know you all have a lot on your plate right now but let us know what we can do to get un-blocked. Hayes -- Hayes Davis Founder, Appozitehttp://cheaptweet.comhttp://tweetreach.com On Thu, Aug 6, 2009 at 3:56 PM, Mario Menti mme...@gmail.com wrote: Thanks Alex - just to confirm, no requests from twitterfeed have been getting though ever since the DOS attack. It does appear to be IP based, as requests from non-production machines (ironically the non-whitelisted IPs) get through, but all production IPs appear to be blocked. On Thu, Aug 6, 2009 at 9:40 PM, Alex Payne a...@twitter.com wrote: We're talking to our operations team about it, who in turn is talking to our hosting provider. It seems that some aggressive IP filtering may have been catching some web-based third-party Twitter applications, as well as data centers used by mobile providers. On Thu, Aug 6, 2009 at 12:52, Jonathantwitcaps.develo...@gmail.com wrote: I would also appreciate an answer to this question. My calls to the Search API are failing because of circular redirection, and curlhttp://twitter.com returns nothing at all from my production server, which seems like a sign that its IP has been blocked. My app works fine from my dev box. -jonathan On Aug 6, 1:35 pm, Dewald Pretorius dpr...@gmail.com wrote: Chad, I know it's a little late in asking, but should we switch off cron jobs that make a lot of API calls while this DoS is going on, or while you are recovering from it? I don't want my IP addresses to be blocked because they are making a lot of calls! I've seen in the past that Ops lay down carpet bombing with cluster munitions when under attack. Will it help you to recover if we switched off the cron jobs? Right now most of my connections are just being refused. Do you guys at least check against the list of white listed IP addresses before you block an IP address in times like these? Will there be innocent bystanders caught in the cross-fire again? This is the kind of info that we developers need... Dewald -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x
[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 c...@twitter.com wrote: There is a current issue where the Search API is omitting question marks from search results. We're looking into it. -Chad On Wed, Aug 5, 2009 at 1:17 AM, TCIticoconid...@gmail.com wrote: Hello, Today I started noticing a diference in tweets returned by search vs their original versions. The difference is noticeable to me because I combine both sources and I suddenly got a lot of duplicated entries that were really slightly different. This started happenning today as far as i can tell. Example: Query:http://search.twitter.com/search?q=millonesrpp=100geocode=9.748917,-83.753428%2C501mimax_id=3137352775 First tweet there says se llevará los 25 millones #qqsm in search, but real tweet says se llevará los 25 millones? #qqsm - notice the extra question mark after millones Help.
[twitter-dev] Re: Streaming API: Spritzer-stream coverage
Hi Sven, well I merely assumed that the easiest way for twitter to send a subset of tweets on spitzer was to send them based on their ids (autoincrement integer)... watching at the stream, I noticed that all the ids where ending with 000,001,002,003,004, 100,102, ... 900,901,... 904 I did not push the analysis further though On May 26, 3:24 am, Sven Svensson twitterf...@gmail.com 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_stream) Did you use the same methodology? The four percent is probably a bit too low as I assume private tweets get tweet_id:s too, which makes the denominator a bit too large due to private tweets being included. On Mon, May 25, 2009 at 11:39 PM, stephane stephane.philipa...@gmail.com wrote: 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
[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 elversat...@gmail.com wrote: How are spritzer statuses sampled? Are they picked uniformly at random? Or is there some logic behind it? Also, what makes it statistically insignificant? Is it its percentage in relation to the entire stream or the way it is sampled? Thanks, -Eldar On May 24, 8:23 pm, John Kalucki jkalu...@gmail.com wrote: Sven, Excluding connection ramp-up and ramp-down skew, each spritzer feed delivers the same statuses as all other spritzer feeds. Likewise, each gardenhose feed delivers the same statuses as all other gardenhose feeds. Also, spritzer feeds are a strict subset of gardenhose feeds. There's no point in consuming multiple sampled feeds (spritzer/ spritzer, gardenhose/spritzer, gardenhose/gardenhose), as you'll just receive duplicate data. Multiple sessions on sampled feeds just waste scarce resources and you also may find your access automatically limited for a period of time. Reduce, reuse, recycle! -John Kalucki Services, Twitter Inc. On May 24, 10:51 am, Sven Svensson twitterf...@gmail.com wrote: Thanks for an excellent API. I have two questions in relation to the streaming API: * Assume that two users are both reading the spritzer stream at the same time - will they get the same spritzer streams covering the same subset of all tweets, or will they get two separate spritzer streams covering different tweets? * Roughly what percentage of all tweets are distributed in the spritzer stream? Is it in the region of four percent of all tweets (my guesstimate)? Thanks!
