TwitterTrend User Indexing Started!
Since we cannot index old data via the public timeline or the data mining feed, we opened up a way for users to submit their timeline for indexing! This is plagued by the Username/Password situation, but as soon as OAuth is released or anything else, I will fully support it! :) Also, I have had two Twitter API requests, http://code.google.com/p/twitter-api/issues/detail?id=180 and http://code.google.com/p/twitter-api/issues/detail?id=183 The first one is regarding the missing link to the source, in the Data mining and public timeline APIs. The links seem to work fine in the user timeline. The second one is a request for 3 new fields to be added to the Firehose/timelines, I would like them because, currently I have to request Twitter again for user information like timezone, etc. that should be included in timeline's user field. I don't understand why followers_count was included but not updates_count or following_count? If you agree/like either of the requests, please star them so they get noticed :) Thanks, James Hartig
Re: Firehose API's total load rate?
Alex, Then I'm glad I've tested to 5,000 msgs per sec
Re: Search API Rate Limiting
No, you can't do an ajax authenticated GET or POST to a 3rd-party site. I am dynamically loading the json in the clients' browser. I would rather know the rate limits so I can abide by them. -Chad On Sun, Dec 7, 2008 at 10:42 AM, fastest963 [EMAIL PROTECTED] wrote: Since your doing this via AJAX and such, this may not be a good idea, but you could try passing a login to Twitter and having that login whitelisted?
Re: What fields can I pull from public timeline atom feeds or the upcoming firehose?
Thanks for the clarification, the firehose will still probably be the best solution for us, it's just good to know we'll need to do some filtering of it on our end. On Dec 6, 2:51 pm, Alex Payne [EMAIL PROTECTED] wrote: No, the firehose is distinct from Twitter Search. It's simply for delivering the entire stream of public updates. We may add filters and such in the future, but for now, we're just focusing on this one need that our partners have. On Sat, Dec 6, 2008 at 11:42, drupalot [EMAIL PROTECTED] wrote: Sounds good. Thanks Alex. Btw, will the firehose have the same capacity to filter before pulling (or received the push) as regular feeds do (via advanced search or elements in the feed URL directly)? On Dec 6, 2:37 am, Alex Payne [EMAIL PROTECTED] wrote: The firehose will provide all the fields returned in the REST API. Our Atom feed is limited to those attributes that fit an Atom entry; use XML or JSON for all attributes. On Fri, Dec 5, 2008 at 12:37, drupalot [EMAIL PROTECTED] wrote: Looks like I can pull username, tweet (text and URL) and timestamp from the public timeline (or advanced search slice of the public timeline) atom feed. Can I also pull image, reply-to URL, and location? If not, will the upcoming firehose provide these additional fields by any chance, or is there another aspect of the search API I could utilize for this? Thanks for any help on this front. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: favorited value is null in JSON
I have received the null value of favorited statuses more frequently today. Thousands of my app users have been struggling for these days. (I guess several other iPhone clients also crash when they receive the null values.) I submitted the new version of my app to AppStore 4 days ago but I guess it will take for another few days to get an approval. If you could address the things on the server side, it would help my users very much. Regards, Kazuho On Thu, Dec 4, 2008 at 10:32 PM, Alex Payne [EMAIL PROTECTED] wrote: Thanks much! On Thu, Dec 4, 2008 at 22:12, Kazuho Okui [EMAIL PROTECTED] wrote: I attached another example which is a result of curl. it contains a request/response headers and a JSON content. I hope this will help to find the issue. Thanks, Kazuho On Thu, Dec 4, 2008 at 1:21 PM, Kazuho Okui [EMAIL PROTECTED] wrote: Hello Alex, I attached JSON objects which my app users gave me. Thus, I don't have any request header, but the request is http://twitter.com/statuses/friends_timeline.json; with auth header. The JSON objects contains favorited:null instead of favorited:true or false randomly. Thanks, Kazuho -- Forwarded message -- From: Alex Payne [EMAIL PROTECTED] Date: Thu, Dec 4, 2008 at 12:11 PM Subject: Re: favorited value is null in JSON To: twitter-development-talk@googlegroups.com If you could please provide example request/response output that would help us track this down. Apologies for the inconsistency. On Wed, Dec 3, 2008 at 17:28, Kazuho Okui [EMAIL PROTECTED] wrote: Today, I suddenly received a JSON value which favorited value is null instead of bool. http://code.google.com/p/twitter-api/issues/detail?id=179 This crushes my Twitter client because it assumed that the value is boolean. The application is written in Objective-C, so the value type is very important for my client. The favorited value was null or true until October, then true or false until today. Could you please define exactly the type of favorite value?? Also, could you use boolean to all favorited status? Thanks, Kazuho -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: favorited value is null in JSON
Indeed, I basically can't use TwitterFon until this gets sorted out. (I'm aware of the workaround script online, but don't want to de-fav items in my timeline). -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Sun, Dec 7, 2008 at 10:50 PM, Kazuho Okui [EMAIL PROTECTED] wrote: I have received the null value of favorited statuses more frequently today. Thousands of my app users have been struggling for these days. (I guess several other iPhone clients also crash when they receive the null values.) I submitted the new version of my app to AppStore 4 days ago but I guess it will take for another few days to get an approval. If you could address the things on the server side, it would help my users very much. Regards, Kazuho On Thu, Dec 4, 2008 at 10:32 PM, Alex Payne [EMAIL PROTECTED] wrote: Thanks much! On Thu, Dec 4, 2008 at 22:12, Kazuho Okui [EMAIL PROTECTED] wrote: I attached another example which is a result of curl. it contains a request/response headers and a JSON content. I hope this will help to find the issue. Thanks, Kazuho On Thu, Dec 4, 2008 at 1:21 PM, Kazuho Okui [EMAIL PROTECTED] wrote: Hello Alex, I attached JSON objects which my app users gave me. Thus, I don't have any request header, but the request is http://twitter.com/statuses/friends_timeline.json; with auth header. The JSON objects contains favorited:null instead of favorited:true or false randomly. Thanks, Kazuho -- Forwarded message -- From: Alex Payne [EMAIL PROTECTED] Date: Thu, Dec 4, 2008 at 12:11 PM Subject: Re: favorited value is null in JSON To: twitter-development-talk@googlegroups.com If you could please provide example request/response output that would help us track this down. Apologies for the inconsistency. On Wed, Dec 3, 2008 at 17:28, Kazuho Okui [EMAIL PROTECTED] wrote: Today, I suddenly received a JSON value which favorited value is null instead of bool. http://code.google.com/p/twitter-api/issues/detail?id=179 This crushes my Twitter client because it assumed that the value is boolean. The application is written in Objective-C, so the value type is very important for my client. The favorited value was null or true until October, then true or false until today. Could you please define exactly the type of favorite value?? Also, could you use boolean to all favorited status? Thanks, Kazuho -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
