Note: invalidate_token isn't working at this time. Seems to be a Twitter issue---perhaps a doc bug. E.g., see: https://twittercommunity.com/t/revoke-an-access-token-programmatically-always-getting-a-403-forbidden/1902
- Add API method retweeters_ids - Fix update_with_media with utf8 status (RT#72814) - Expand Carp::Clan list (should resolve RT#77306) - Remove reliance on MooseX::Aliases (issue #35) - Use Class::Load to replace deprecated Class::Mop method (issue #35) - Add missing dependency: LWP::Protocol::https (issue #25) - Fix OAuth failure for UTF8 params (issue #21)
Bug reporteb by Nick Andrew (@elronxenu) 2013-02-27 via Twitter. We used to rely on HTTP::Requet::Common to encode arguments, but it relies on URI which doesn't encode the full set of values required by the OAuth spec. We now use Net::OAuth::Message to encode paramters.
HTTP::Message 6.03 throws a bunch of warnings for undefined content. No use forcing users to upgrade just for that. :-/
Ensure deprcated methods throw warnings and non-deprecated methods do not.