updated faraday version and fixed related issues
no reason to require higher hashie
Merge pull request #24 from bakks/master

Fixed Faraday version issue
Version bump to 0.8.3
Instagram.media_search takes two arguments, not one
changes for faraday exception raising to return the body of messages brought back by the server.
added the require for multi_json just in case
changes to not use multi_json per https://github.com/Instagram/instagram-ruby-gem/pull/30/files as a more elegant solution
Merge pull request #31 from eerwitt/master

Return response body from 400 error messages.
Faraday 0.8 is compatible with current usage, so why not allowing to use it?
Ensure that urls are of class Addressable::URI, to overcome Faraday dropping it
Force inferred port, otherwise someone may think we are calling port 80
Use Faraday::Utils to parse and update the query (inspired by https://github.com/Instagram/instagram-ruby-gem/pull/35/files)
Version bump 0.8.4
Allow better, faster multi_json until the 2.0 API break
Merge pull request #27 from ckundo/bugfix

Instagram.media_search takes two arguments, not one
Merge pull request #42 from simplymeasured/fix/relax-multi_json-version-constraints

Allow better, faster multi_json until the 2.0 API break
Merge pull request #34 from rewritten/patch-1

Faraday 0.8 is compatible with current usage, so why not allowing to use it?
Merging #40
Merge branch 'joshuaknox-6f932ff'

Closes #40