Follow @gem on Twitter

Mailing List

Apps Wiki

Does your project or organization use this gem? Add it to the apps
wiki!

What's new in version 3?

The Active Support dependency has been removed!

The Twitter::Client#follow and Twitter::Client#unfollow methods now accept
multiple users as arguments and return an array instead of a Twitter::User.
Additionally, the Twitter::Client#follow method now checks to make sure the
user isn't already being followed. If you don't wish to perform that check
(which requires an extra HTTP request), you can use the new
Twitter::Client#follow! method instead. Note: This may re-send an email
notification to the user, even if they are already being followed.

This version introduces an identity map, which ensures that the same objects
only get initialized once:

(In all previous versions of this gem, this statement would have returned
false.)

The Twitter::Client#search now returns a Twitter::SearchResult object,
which contains metadata and a results array. In the previous major version,
this method returned an array of Twitter::Status objects, which is now
accessible by sending the results message to a Twitter::SearchResults
object.

# Version 2
Twitter::Client.search("query").each do |status|
puts status.full_text
end
# Version 3
Twitter::Client.search("query").results.each do |status|
puts status.full_text
end

The Twitter::Status#expanded_urls method has been removed. Use
Twitter::Status#urls instead.

Submitting an Issue

We use the GitHub issue tracker to track bugs and features. Before
submitting a bug report or feature request, check to make sure it hasn't
already been submitted. When submitting a bug report, please include a Gist
that includes a stack trace and any details that may be necessary to reproduce
the bug, including your gem version, Ruby version, and operating system.
Ideally, a bug report should include a pull request with failing specs.

Supported Ruby Versions

If something doesn't work on one of these interpreters, it should be considered
a bug.

This library may inadvertently work (or seem to work) on other Ruby
implementations, however support will only be provided for the versions listed
above.

If you would like this library to support another Ruby version, you may
volunteer to be a maintainer. Being a maintainer entails making sure all tests
run and pass on that implementation. When something breaks on your
implementation, you will be personally responsible for providing patches in a
timely fashion. If critical issues for a particular implementation exist at the
time of a major release, support for that Ruby version may be dropped.