Dear Twitter API peeps,
The API doccos for "Twitter REST API Method: trends
available" (https://twitterapi.pbworks.com/Twitter%20REST%20API
%20Method:%20trends%20available) say that no authentication is
required, but I think it is:
$ curl http://api.twitter.com/1/trends/available.json
{"
If we cannot run-time configure the callback URI then we'll need
multiple application registrations for development + production?
(assuming the need for absolute URIs)
Cheers
Nic
On Apr 24, 7:38 am, Matt Sanford wrote:
> Hi there,
>
> I totally forgot about that change. Since the oauth cal
Currently the only way (I think) to register an application to use the
OAuth API is via the web form at http://twitter.com/oauth_clients/new
which requires the user to use login/password on the main site. To
automate this (e.g. move it into a command-line application like the
twitter rubygem) mean