Push Changes - Aug 25 2009

r181638 | nbiswas | 2009-08-18 13:36:08 -0700 (Tue, 18 Aug 2009) | 17 lines

developers will be unable to set application names which contain profanity via the api. before they were only restricted when editing in the Developer application, but not via the admin API (admin.setAppProperties).

r181705 | nbiswas | 2009-08-18 15:42:39 -0700 (Tue, 18 Aug 2009) | 22 lines

users.isVerified will now return correctly (1 or 0, true or false) instead of empty strings, as it used to in XML and PHP response formats
bug 5129: Users.isVerified is returning empty string for PHP client. Used to return 1 or 0.

r182079 | rhe | 2009-08-19 16:38:16 -0700 (Wed, 19 Aug 2009) | 23 lines

stream.get and stream (FQL) queries should return the number requested more often. Previously, if you asked for 10 posts, you could get anywhere from 0 to 10 posts. Now we'll make a better effort to get you 10 posts.
bug 5904: FQL query not returning result count asked.

r182666 | jleszcze | 2009-08-21 21:55:58 -0700 (Fri, 21 Aug 2009) | 48 lines

API results will now be available in localized formatting, when such formats exist. Namely, all requests made through restserver.php will obey the following:

If the current user is in a non-US English locale, then the results of the API queries will return the user's locale only if your application has been listed as "published" from the Translations Admin Panel, or if they are allowed to see translations in progress for your application (see Translating Platform Applications for details). Otherwise, it will be returned with US English formatting.
If the user is in the US English locale, results will be returned as expected.
Both 1+2 can be optionally overridden, by adding a &locale parameter to either the GET or POST params for a restserver.php request. For a list of valid locales, please check Facebook Locales.

r182833 | rhe | 2009-08-24 14:41:58 -0700 (Mon, 24 Aug 2009) | 24 lines