Whenever more than one user or id is passed to any of these methods, HTTP
requests are made in parallel using multiple threads, resulting in dramatically
better performance than calling these methods multiple times in serial.

The Twitter::Client#direct_messages method has been renamed to
Twitter::Client#direct_messages_received.

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

The Twitter::Client#profile_image method has been removed. Use
Twitter::User#profile_image_url (or Twitter::User#profile_image_url_https)
instead.

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 does
require 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.

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").map(&:full_text)

Version 3

Twitter::Client.search("query").results.map(&:full_text)

Configuration

The Faraday middleware stack is now fully configurable and is exposed as a
Faraday::Builder. You can modify the default middleware in-place:

Identity Map

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

Errors

Any Faraday client errors are captured and re-raised as a
Twitter::Error::ClientError, so there's no longer a need to separately rescue
Faraday::Error::ClientError.

All Twitter::Error.ratelimit methods (including Twitter::Error.retry_at)
have been replaced by the Twitter::RateLimit singleton class. After making
any request, you can check the Twitter::RateLimit object for your current
rate limit status.

Additional notes

This will be the last major version of this library to support Ruby 1.8.
Requiring Ruby 1.9 will allow us to remove varioushacks put in place to maintain Ruby 1.8 compatibility.
The first stable version of Ruby 1.9 was released on August 19, 2010.
If you haven't found the opportunity to upgrade your Ruby interpreter since
then, let this be your nudge. Once version 4 of this library is released, all
previous versions will cease to be supported, even if critical security
vulnerabilities are discovered.

Here are some fun facts about the 3.0 release:

The entire library is implemented in just 2,201 lines of code

With over 5,000 lines of specs, the spec-to-code ratio is well over 2:1

The spec suite contains 631 examples and runs in under 2 seconds on a MacBook

This project has 100% C0 code coverage (the tests execute every line of
source code at least once)

At the time of release, this library is comprehensive: you can request all
documented Twitter REST API resources that respond with JSON (over 100)

This is the first multithreaded release (requests are made in parallel)

This gem works on every major Ruby implementation, including JRuby and
Rubinius

The first version was released on November 26, 2006 (over 5 years ago)

This gem has just three dependencies: faraday, multi_json, and
simple_oauth

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.