At this point, all I'm looking for is a way to upgrade this piece of
PHP code to take into account the new authentication model:
$ch = curl_init('http://twitter.com/statuses/update.xml');
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 10);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS,
'status='.urlencode(trim($message)));
curl_setopt($ch, CURLOPT_USERPWD, $settings['twitter-username'].':'.
$settings['twitter-password']);
$response = curl_exec($ch);
$resp = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
On Apr 24, 6:40 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> hi all.
>
> you're going to be hearing a lot from me over the next 9 weeks. our plan is
> to turn off basic authorization on the API by june 30, 2010 -- developers
> will have to switch over to OAuth by that time. between now and then, there
> will be a *lot* of information coming along with tips on how to use OAuth
> Echo, xAuth, etc. we really want to make this transition as easy as we can
> for everybody.
>
> as always, please feel free to reach out to this group, or to @twitterapi
> directly. if you need help remembering the date -http://bit.ly/twcountdown
> .
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi
>
> --
> Subscription
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
