Re: Will this break your app? Chime in!

2008-12-16 Thread Kazuho Okui

Thanks :)

Also, please consider to fix issue #157. If you do, I can use show
method only to get friends existence then I can reduce 1 API call.

http://code.google.com/p/twitter-api/issues/detail?id=157

Thanks,
Kazuho

On Tue, Dec 16, 2008 at 5:09 PM, Alex Payne a...@twitter.com wrote:

 Example response:

 true

 That's it :)  Just a bare boolean literal.

 On Tue, Dec 16, 2008 at 17:06, Kazuho Okui kaz...@gmail.com wrote:

 This will break my app. 1 week to 10 days to get an approval from Apple.

 Also, please give us a example of new response.

 On Tue, Dec 16, 2008 at 4:53 PM, Cameron Kaiser spec...@floodgap.com wrote:

 As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd
 like to return a proper boolean in the JSON response for
 /friendships/exists.  Will this break your app?  If so, how much time
 to do you need to ship a fix?

 TTYtter uses its own internal JSON parser and in fact special cases trivial
 Booleans and stringified Booleans:

if ($data =~ /^[']?(true|false)[']?$/);

 So it will accept any of true, true, false, false, etc. If you decided
 to wrap it in something, though, I'd need to account for that. As described
 in the issue, it should be okay.

 --
  personal: 
 http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
 -- He whose face gives no light, shall never become a star. -- William 
 Blake --





 --
 Alex Payne - API Lead, Twitter, Inc.
 http://twitter.com/al3x



Re: Change: Search API Rate Limiting

2008-12-08 Thread Kazuho Okui

I think using 400 is much easy to handle the responses than using 401.
Because I can use same http client code and same error handling code
for both search API and REST API. In my case, I wrote a error handler
which alerts a dialog whenever it gets a 401 because search API
wouldn't return 401.

On Mon, Dec 8, 2008 at 9:56 AM, Abraham Williams [EMAIL PROTECTED] wrote:
 You could compromise and do a 400.5 O_o

 On Mon, Dec 8, 2008 at 11:51, Matt Sanford [EMAIL PROTECTED] wrote:

 Of course right after sending a lengthy public email I see something that
 could let us keep 503 and fix the proxy errors. I'm working with operations
 on that, and if it does not pan out I'll confer with Alex on 400 versus 401.
 Stay tuned.
 — Matt
 On Dec 8, 2008, at 09:46 AM, Alex Payne wrote:

 We use 400 for rate limiting on the REST API.  Matt and I are
 discussing whether or not this might be the correct response.
 Thoughts?

 On Mon, Dec 8, 2008 at 09:17, Cameron Kaiser [EMAIL PROTECTED] wrote:

The error code for search rate limiting will be changing from HTTP

 503 to HTTP 401 in the very near future (today or tomorrow). For

 details, continue reading.

 Are you sure you want to use 401 for this? 401 would indicate
 authorization

 required. If you're asking for credentials, that would make sense, but if

 you're not, I would think the 503 is still the proper response
 irrespective

 of broken proxies. I don't see other codes that have that one's temporal

 semantics.

 --

  personal:
 http://www.cameronkaiser.com/ --

 Cameron Kaiser * Floodgap Systems * www.floodgap.com *
 [EMAIL PROTECTED]

 -- If you have integrity, nothing else matters. -- Alan Simpson
 ---




 --
 Alex Payne - API Lead, Twitter, Inc.
 http://twitter.com/al3x




 --
 | Abraham Williams | Web Developer | http://abrah.am
 | Brazen Careerist | Pro Hacker | http://www.brazencareerist.com
 | PoseurTech LLC | Mashup Ambassador | http://poseurte.ch
 | Web608 | Community Evangelist | http://web608.org
 | This email is: [] blogable [x] ask first [] private



Re: favorited value is null in JSON

2008-12-07 Thread Kazuho Okui

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



favorited value is null in JSON

2008-12-03 Thread Kazuho Okui

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