sferik/twitter — pull request #330 by thomasklemm (2012-11-29 16:40:17+00:00)
Title: Allow users lookup to optionally be handled via a GET request

Hey Erik, hey everyone who reads this PR :-D,

thanks for making and maintaining this great gem!

I'm in the process of making an app that allows users to uncover who started or stopped following them.

All requests im currently using except the users/lookup use GET requests, which only require 'Read' permission for the application.

Not wanting my users to grant me write access when I actually do not want to post any information, this PR implements the option to optionally make a GET request for the users/lookup resource, which is in fact the only one I found where this option makes some difference.

Since Twitter encourages making POST requests to this [users/lookup resource](https://dev.twitter.com/docs/api/1.1/get/users/lookup) in case of requesting up to 100 screen_names or user_ids, the POST request should remain the standard.

```ruby
Twitter.users('sferik', 'thomasjklemm') # => POST request
Twitter.users('sferik', 'thomasjklemm', method: :get) # => GET request
```

More on [Twitter's application permission model](https://dev.twitter.com/docs/application-permission-model).

Please feel free to suggest changes in the implementation, I'll try to respond quickly.

Best regards,
Thomas