RE: [twitter-dev] Announcing Twurl: OAuth-enabled curl for the Twitter API
Dean Collins
Great so you are moving before oauth 2 is finished. You guys are crazy. You’re making everyone change now and then change again in 3 months.
Cheers,
Dean
From: twitter-deve...@googlegroups.com [mailto:twitter-deve...@googlegroups.com] On Behalf Of Marcel Molina
Sent: Tuesday, April 20, 2010 3:13
PM
To: twitter-deve...@googlegroups.com;
twitter-ap...@googlegroups.com
Subject: [twitter-dev] Announcing
Twurl: OAuth-enabled curl for the Twitter API
We've announced that come June 2010, Basic Auth will no longer be supported via the Twitter API. All authenticated requests will be moving to OAuth (either version 1.0a or the emerging 2.0 spec). There are many benefits from this change. Aside from the obvious security improvements, having all requests be signed with OAuth gives us far better visibility into our traffic and allows us many more tools for controlling and limiting abuse. When we know and trust the origin of our traffic we can loosen the reigns a lot and trust by default. We've already made a move in this direction by automatically increasing rate limits for requests signed with OAuth made to the new versioned api.twitter.com host.
One of the often cited virtues of the Twitter API is its simplicity. All you have to do to poke around at the API is curl, for example, http://api.twitter.com/1/users/noradio.xml and you're off and running. When you require that OAuth be added to the mix, you risk losing the simplicity and low barrier to entry that curl affords you. We want to preserve this simplicity. So we've provided two tools to let you poke around at the API without having to fuss with all the extraneous details of OAuth. For those who want the ease of the web, we've already included an API console in our new developer portal at http://dev.twitter.com/console. And now today we're glad to make available the Twurl command line utility as open source software:
If you already have RubyGems (http://rubygems.org/), you can install it with the gem command:
sudo gem i twurl --source http://rubygems.org
If you don't have RubyGems but you have Rake (http://rake.rubyforge.org/), you can install it "from source". Check out the INSTALL file (http://github.com/marcel/twurl/blob/master/INSTALL).
Once you've got it installed, start off by checking out the README (http://github.com/marcel/twurl/blob/master/README) (you can always get the README by running 'twurl -T'):
+-------+
| Twurl |
+-------+
Twurl is like curl, but tailored specifically for the Twitter API.
It knows how to grant an access token to a client application for
a specified user and then sign all requests with that access token.
It also provides other development and debugging conveniences such
as defining aliases for common requests, as well as support for
multiple access tokens to easily switch between different client
applications and Twitter accounts.
+-----------------+
| Getting Started |
+-----------------+
The first thing you have to do is register an OAuth application
to get a consumer key and secret.
When you have your consumer key and its secret you authorize
your Twitter account to make API requests with your consumer key
and secret.
% twurl authorize --consumer-key the_key \
--consumer-secret the_secret
This will return an URL that you should open up in your browser.
Authenticate to Twitter, and then enter the returned PIN back into
the terminal. Assuming all that works well, you will beauthorized
to make requests with the API. Twurl will tell you as much.
If your consumer application has xAuth enabled, then you can use
a variant of the above
% twurl authorize -u username -p password \
--consumer-key the_key \
--consumer-secret the_secret
And, again assuming your username, password, key and secret is
correct, will authorize you in one step.
+-----------------+
| Making Requests |
+-----------------+
The simplest request just requires that you specify the path you
want to request.
% twurl /1/statuses/home_timeline.xml
Similar to curl, a GET request is performed by default.
You can implicitly perform a POST request by passing the -d option,
which specifies POST parameters.
% twurl -d 'status=Testing twurl' /1/statuses/update.xml
You can explicitly specify what request method to perform with
the -X (or --request-method) option.
% twurl -X DELETE /1/statuses/destroy/123456.xml
+------------------+
| Creating aliases |
+------------------+
% twurl alias h /1/statuses/home_timeline.xml
You can then use "h" in place of the full path.
% twurl h
Paths that require additional options such as request parameters for example can
be used with aliases the same as with full explicit paths, just as you might
expect.
% twurl alias tweet /1/statuses/update.xml
% twurl tweet -d "status=Aliases in twurl are convenient"
+-------------------------------+
| Changing your default profile |
+-------------------------------+
The first time you authorize a client application to make requests on behalf of your account, twurl stores your access token information in its .twurlrc file. Subsequent requests will use this profile as the default profile. You can use the 'accounts' subcommand to see what client applications have been authorized for what user names:
% twurl accounts
noradio
HQsAGcBm5MQT4n6j7qVJw
hhC7Koy2zRsTZvQh1hVlSA (default)
testiverse
guT9RsJbNQgVe6AwoY9BA
Notice that one of those consumer keys is marked as the default. To change the default use the 'set' subcommand, passing then either just the username, if it's unambiguous, or the username and consumer key pair if it isn't unambiguous:
% twurl set default testiverse
% twurl accounts
noradio
HQsAGcBm5MQT4n6j7qVJw
hhC7Koy2zRsTZvQh1hVlSA
testiverse
guT9RsJbNQgVe6AwoY9BA (default)
% twurl set default noradio HQsAGcBm5MQT4n6j7qVJw
% twurl accounts
noradio
HQsAGcBm5MQT4n6j7qVJw (default)
hhC7Koy2zRsTZvQh1hVlSA
testiverse
guT9RsJbNQgVe6AwoY9BA
+--------------+
| Contributors |
+--------------+
Marcel Molina <mar...@twitter.com> / @noradio
Raffi Krikorian <ra...@twitter.com> / @raffi
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
Raffi Krikorian
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
Marcel Molina
Jeffrey Greenberg
Sent from my iPhone
Thomas Woolway
Jaanus
my-mac:~ jaanus$ twurl authorize --consumer-key blabla --consumer-
secret blabla
You must authorize first
huh?
On Apr 20, 3:13 pm, Marcel Molina <mar...@twitter.com> wrote:
> We've announced that come June 2010, Basic Auth will no longer be supported
> via the Twitter API. All authenticated requests will be moving to OAuth
> (either version 1.0a or the emerging 2.0 spec). There are many benefits from
> this change. Aside from the obvious security improvements, having all
> requests be signed with OAuth gives us far better visibility into our
> traffic and allows us many more tools for controlling and limiting abuse.
> When we know and trust the origin of our traffic we can loosen the reigns a
> lot and trust by default. We've already made a move in this direction by
> automatically increasing rate limits for requests signed with OAuth made to
> the new versioned api.twitter.com host.
>
> One of the often cited virtues of the Twitter API is its simplicity. All you
> and low barrier to entry that curl affords you. We want to preserve this
> simplicity. So we've provided two tools to let you poke around at the API
> without having to fuss with all the extraneous details of OAuth. For those
> who want the ease of the web, we've already included an API console in our
> software:
>
> http://github.com/marcel/twurl
>
> If you already have RubyGems (http://rubygems.org/), you can install it with
> the gem command:
>
> Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Marcel Molina
Kartik
I installed RubyGems and did this
Then tried to use twurl but it gives a error :
twurl: command not found
Please tell me what am I missing ?
Also, how do we use twurl with PHP ? cURL can be used with the PHP
built in functions.
Kartik
> We've announced that come June 2010, Basic Auth will no longer be supported
> via the Twitter API. All authenticated requests will be moving to OAuth
> (either version 1.0a or the emerging 2.0 spec). There are many benefits from
> this change. Aside from the obvious security improvements, having all
> requests be signed with OAuth gives us far better visibility into our
> traffic and allows us many more tools for controlling and limiting abuse.
> When we know and trust the origin of our traffic we can loosen the reigns a
> lot and trust by default. We've already made a move in this direction by
> automatically increasing rate limits for requests signed with OAuth made to
> the new versioned api.twitter.com host.
>
> One of the often cited virtues of the Twitter API is its simplicity. All you
> and low barrier to entry that curl affords you. We want to preserve this
> simplicity. So we've provided two tools to let you poke around at the API
> without having to fuss with all the extraneous details of OAuth. For those
> who want the ease of the web, we've already included an API console in our
> software:
>
> http://github.com/marcel/twurl
>
> If you already have RubyGems (http://rubygems.org/), you can install it with
> the gem command:
>
Scott Schulz
> If you already have RubyGems (http://rubygems.org/), you can install it with
> the gem command:
> sudo gem i twurl --source http://rubygems.org
and am trying to use Twurl to get the necessary keys/tokens/whatever.
I've installed ruby, gems, etc, and install twurl via gem, but when I
run it, I get the following:
/usr/local/lib/ruby/gems/1.9.1/gems/twurl-0.6.1/lib/twurl/request_controller.rb:2:in
`<module:Twurl>': uninitialized constant
Twurl::AbstractCommandController (NameError)
Am I missing another gem? Other ideas?
Thank you,
SwS
Nathaniel K Smith
> I've installed ruby, gems, etc, and install twurl via gem, but when I
> run it, I get the following:
>
> Twurl::AbstractCommandController (NameError)
ruby1.9.1.
nate
Faried Nawaz
I got it to work with a minor adjustment on Ubuntu 10.04. I did
apt-get install rake rubygems libopenssl-ruby
gem install oauth
gem install rr
gem install require_all
git clone http://github.com/marcel/twurl.git
apply this diff: http://gist.github.com/400489
rake dist:gem
gem install pkg/twurl-*.gem
You're set.
kuhkatz
i followed your instructions, but when i apply the diff, i get this:
$ patch -i twurldiff
patching file Rakefile
patching file twurl.rb
Hunk #1 FAILED at 4.
1 out of 1 hunk FAILED -- saving rejects to file twurl.rb.rej
patching file rcfile_test.rb
Hunk #1 FAILED at 138.
1 out of 1 hunk FAILED -- saving rejects to file rcfile_test.rb.rej
$ rake dist:gem
(in /home/lorth/twurl)
mkdir -p pkg
WARNING: description and summary are identical
Successfully built RubyGem
Name: twurl
Version: 0.6.1
File: twurl-0.6.1.gem
mv twurl-0.6.1.gem pkg/twurl-0.6.1.gem
installing the patched twurl works, but it still gives me the same
error as before.
this is the first time i am touching ruby, so i have a kinda hard time
figuring out whats going on. seems like twurls wants to load some
dependencies when the error occured, but i dont know how to fix this.
anyone have a clue?
Faried Nawaz
> so i suppose i am doing things wrong.
> i followed your instructions, but when i apply the diff, i get this:
>
> $ patch -i twurldiff
patch -p 1 -i twurldiff
or
git apply twurldiff
Faried.
Patrick Kennedy
I tried it too, since I have Linux 10.04, and it also has a problem at
the patching part, even provided your two ways to execute the diff.
I'm also new to Ruby stuff.
$ patch -i twurldiff
patching file Rakefile
Hunk #2 FAILED at 69.
2 out of 2 hunks FAILED -- saving rejects to file Rakefile.rej
patching file lib/twurl.rb
patching file test/rcfile_test.rb
Just feedback. Patrick
Faried Nawaz
separately before posting the commands, and they both worked for me.
Note that the git command doesn't produce any output, but does patch
the files.
If it still isn't working for you, you can always manually edit the
files. It's a small change.
Faried.
Patrick Kennedy
I'm sure it mostly my new newness to Ruby; rake/make files are not my
strong area as well.
If it's fairly small changes, can you provide those changes?
Basically, why patch it - if I can just use a replacement file. But
since it's not provided yet, maybe you can demonstrate those tweaks?
Well, I'm not asking you to do something, if it's onerous to you - so,
absolutely no worries. But, then again, if it's trivial, it would be
cool to get working on the new Ubuntu. Otherwise my passion for
Twitter coding may slowly cool down - though, of course I love all
things Twitter - and I'm trying to get back into the coding of it.
~Patrick
Faried Nawaz
> I'm sure it mostly my new newness to Ruby; rake/make files are not my
> strong area as well.
repository. At the end, download the gist, and use "git apply
patchfile".
> If it's fairly small changes, can you provide those changes?
work.
Faried.
kuhkatz
gave me an error with lib/twurl.rb,
but with looking into the .rej and manually patching the file i
succeded, finally.
thanks for your help =)
Patrick Kennedy
but no worries.
kuhkatz
further details on where exacly what goes wrong.
"doesnt work" is never a good way to call for help.
Jef Poskanzer
written in a language I don't have so it's useless to me.
Before turning off basic auth twitter needs to provide their own
official implementation of a CLI OAuth getter, written in plain old C.
Faried Nawaz
> Before turning off basic auth twitter needs to provide their own
> official implementation of a CLI OAuth getter, written in plain old C.
parser?
Cameron Kaiser
Raffi to get TTYtter 1.1 in an acceptable form for public release (we are
having discussions about how to streamline the keys process in such a way
that's simpler for users, but still secure for Twitter).
That implementation is 100% pure Perl, and does not use any external
libraries. You're welcome to take a crack at it now if you like, but you
will need to generate your own app keys in its current state. E-mail me
off list if interested.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- Why do we scoff at fortune tellers, yet listen to economists? --------------
Zac Bowling
I forked a version of twurl and updated all own my scripts to recognize the rc file and Mac keychain format and use it if it's detected. It makes it far less complicated to use command line tools.
It would be nice to standardize this or something maybe.
Zac Bowling
@zbowling
Sent from my iPad