What's the word on a rate limit increase related to the issue 474 fix?

--
Ed Finkler
http://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com


On Jun 25, 7:18 pm, Matt Sanford <m...@twitter.com> wrote:
> Two features and five fixes were deployed today, 2009-06-25:
>
>    * Feature (REST): Added screen_name and user_id attributes to  
> direct_messages/new for disambiguation
>      - Issue:http://code.google.com/p/twitter-api/issues/detail?id=550
>      - 
> Documentation:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages...
>
>    * Feature (REST): Added new friendships/show method (issue 474,  
> documentation)
>      - Issue:http://code.google.com/p/twitter-api/issues/detail?id=474
>      - 
> Documentation:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships-show
>
>    * Fixed (REST): Partially fixed issue with tiling background images  
> via the API
>      - Issue:http://code.google.com/p/twitter-api/issues/detail?id=650
>      - Note: This was part one. There is a second part to complete the  
> fix that is expected this week. The issue will be updated.
>
>    * Fixed (OAuth): Added a more helpful error message when you try to  
> use a request token in place of an access token.
>      - Error Text: "Request token must be exchanged for an access  
> token before use"
>
>    * Fixed (OAuth): Improved error handling when invalid data is  
> submitted in place of a token.
>      - The generic HTTP 500 should now be replaced with a message that  
> the token was not found
>
>    * Fixed (REST): The JSON returned in maintenance mode now correctly  
> contains null rather than NULL
>      - Issue:http://code.google.com/p/twitter-api/issues/detail?id=703
>
>    * Fixed (Mail): Improved outbound email reliability (for apps  
> parsing DM/friend emails)
>      - Improved some retry logic related to transient errors such as  
> timeouts.
>
>      As always we've updated the change log 
> athttp://apiwiki.twitter.com/REST-API-Changelog
>
> Thanks;
>   – Matt Sanford / @mzsanford
>       Twitter Dev

Reply via email to