SP
unread,Sep 7, 2010, 2:00:01 AM9/7/10Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to twitter4r-users
Hi all,
I worked on the following bugfixes since the OAuth v0.5.0 release:
* Fixed consumer token override issue.
* Fixed 'key' and 'secret' only allowed to be passed in as string
keys issue (see previous three threads on v0.5.0 release).
* Added OAuth proxy support based on previous Twitter::Configuration
settings (new default and new setting parameter, see documentation).
* Fixed documentation bugs (renamed :per_page parameter option
to :count as per Twitter.com API docs)
* Fixed specific OAuth GET requests that were not passing options
appropriately to the OAuth request Ruby API, therefore some APIs were
not being sent with customized parameters.
You can download and install the latest Twitter4R v0.5.1 release from
gemcutter/rubyforge:
$ [sudo] gem install twitter4r -v 0.5.1
The first two bugs that most people had problem with on this mailing
list can be tested by running the following script with v0.5.1:
Twitter::Client.configure do |conf|
conf.oauth_consumer_token = CONSUMER_KEY
conf.oauth_consumer_secret = CONSUMER_SECRET
end
client = Twitter::Client.new(:oauth_access => { :key =>
ACCESS_KEY, :secret => ACCESS_SECRET })
client.status(:post, "Validating two bugfixes in one roundtrip test.")
If anyone has any questions about the other bugfixes let me know.
Best,
Susan