Convert all GitHub links to use HTTPS

README.md

@@ -21,7 +21,7 @@ Join the mailing list!
 
 Does your project or organization use this gem?
 -----------------------------------------------
-Add it to the [apps](http://github.com/jnunemaker/twitter/wiki/apps) wiki!
+Add it to the [apps](https://github.com/jnunemaker/twitter/wiki/apps) wiki!
 
 Continuous Integration
 ----------------------
@@ -56,12 +56,12 @@ user's ID or screen name.
 What's new in 1.0?
 ------------------
 This gem has been completely rewritten for version 1.0 thanks to [contributions from numerous
-people](http://github.com/jnunemaker/twitter/blob/master/HISTORY.md). This rewrite breaks
+people](https://github.com/jnunemaker/twitter/blob/master/HISTORY.md). This rewrite breaks
 compatibility with version 0.9.12 and earlier versions of the gem. Most notably, the
 <tt>Twitter::Base</tt>, <tt>Twitter:Geo</tt>, <tt>Twitter::LocalTrends</tt>, and
-<tt>Twitter::Trends</tt> classes [have all been merged](http://github.com/jnunemaker/twitter/commit/eb53872249634ee1f0179982b091a1a0fd9c0973) into
+<tt>Twitter::Trends</tt> classes [have all been merged](https://github.com/jnunemaker/twitter/commit/eb53872249634ee1f0179982b091a1a0fd9c0973) into
 the <tt>Twitter::Client</tt> class. Whenever possible, we [display deprecation warnings and forward method
-calls to the <tt>Twitter::Client</tt> class](http://github.com/jnunemaker/twitter/commit/192e5884f367750dbdca8471aa12385ed5b057ca).
+calls to the <tt>Twitter::Client</tt> class](https://github.com/jnunemaker/twitter/commit/192e5884f367750dbdca8471aa12385ed5b057ca).
 In a handful of cases, method names were changed to resolve namespace conflicts.
 
 **Pre-1.0**
@@ -144,12 +144,12 @@ error returned by the Twitter Search API.
   </tbody>
 </table>
 
-Additionally, the <tt>Twitter::OAuth</tt> class [has been removed](http://github.com/jnunemaker/twitter/commit/d33b119cdfdaefb10db99e56d28dd69625816edf).
+Additionally, the <tt>Twitter::OAuth</tt> class [has been removed](https://github.com/jnunemaker/twitter/commit/d33b119cdfdaefb10db99e56d28dd69625816edf).
 This class was just a wrapper to get access tokens via the [oauth
-gem](http://github.com/oauth/oauth-ruby). Given that there are a variety of gems that do the same
-thing ([twitter-auth](http://github.com/mbleigh/twitter-auth),
-[omniauth](http://github.com/intridea/omniauth), and
-[devise](http://github.com/plataformatec/devise), to name a few) we decided to decouple
+gem](https://github.com/oauth/oauth-ruby). Given that there are a variety of gems that do the same
+thing ([twitter-auth](https://github.com/mbleigh/twitter-auth),
+[omniauth](https://github.com/intridea/omniauth), and
+[devise](https://github.com/plataformatec/devise), to name a few) we decided to decouple
 this functionality so you can use whichever authentication library you prefer, or none at all. If
 you would like to see how to use the [omniauth
 gem](https://github.com/intridea/omniauth) for authentication, Erik
@@ -168,18 +168,18 @@ Here are a few more reasons to upgrade to 1.0:
 * Support for HTTP proxies: Access Twitter from China, Iran, or inside your office firewall
 * Support for multiple HTTP adapters: NetHttp (default), Typhoeus, Patron, or ActionDispatch
 * Support for multiple Twitter response formats: JSON (default) or XML
-* More flexible: Parse JSON or XML with the engine of your choosing via [MultiJSON](http://github.com/intridea/multi_json) and [MultiXML](http://github.com/sferik/multi_xml)
+* More flexible: Parse JSON or XML with the engine of your choosing via [MultiJSON](https://github.com/intridea/multi_json) and [MultiXML](https://github.com/sferik/multi_xml)
 * More RESTful: Uses HTTP DELETE (instead of POST) when requesting destructive resources
 * More methods: Request any documented resource in the Twitter API, including all [#newtwitter resources](http://groups.google.com/group/twitter-development-talk/browse_thread/thread/cdc34ae78a2350b8)
-* SSL: On by default for increased [speed](http://gist.github.com/652330) and security
+* SSL: On by default for increased [speed](https://gist.github.com/652330) and security
 * Improved error handling: More easily rescue from rate-limit errors or fail whales
 
 Help! I'm getting: "Did not recognize your engine specification. Please specify either a symbol or a class. (RuntimeError)"
 ---------------------------------------------------------------------------------------------------------------------------
 
 If you're using the JSON request format (i.e., the default), you'll need to
-explicitly require a JSON library. We recommend [yajl-ruby](http://github.com/brianmario/yajl-ruby).
-If you're using the XML request format, we recommend requiring [libxml-ruby](http://github.com/dvdplm/libxml-ruby) or
+explicitly require a JSON library. We recommend [yajl-ruby](https://github.com/brianmario/yajl-ruby).
+If you're using the XML request format, we recommend requiring [libxml-ruby](https://github.com/dvdplm/libxml-ruby) or
 [nokogiri](http://nokogiri.org/) for dramatically improved performance over REXML.
 
 Usage Examples
@@ -250,7 +250,7 @@ Here are some ways *you* can contribute:
 * by writing specifications
 * by writing code (**no patch is too small**: fix typos, add comments, clean up inconsistent whitespace)
 * by refactoring code
-* by closing [issues](http://github.com/jnunemaker/twitter/issues)
+* by closing [issues](https://github.com/jnunemaker/twitter/issues)
 * by reviewing patches
 * [financially](http://pledgie.com/campaigns/1193)
 
@@ -259,10 +259,10 @@ file and will receive the respect and gratitude of the community.
 
 Submitting an Issue
 -------------------
-We use the [GitHub issue tracker](http://github.com/jnunemaker/twitter/issues) to track bugs and
+We use the [GitHub issue tracker](https://github.com/jnunemaker/twitter/issues) to track bugs and
 features. Before submitting a bug report or feature request, check to make sure it hasn't already
 been submitted. You can indicate support for an existing issuse by voting it up. When submitting a
-bug report, please include a [Gist](http://gist.github.com/) that includes a stack trace and any
+bug report, please include a [Gist](https://gist.github.com/) 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.