Added search_controller_spec, moved some tests from people_controller_spec to search_controller_spec

Fixed merged conflict in Changelog

update routes and search controller

remove useless except from search controller

Fix indentation in search_controller

From a quick look at the for us available databases this was not actually used in the wild.

* added a presenter for hovercard json
* added new backbone view for handling hovercard JS
* refactoring of PeopleController

* finished the backbone js version of hovercards
* don't try to make people_controller more restfull, out of scope
  just add a new route and use that for hovercard json
* added spec for people_controller#hovercard
* add new exception for "AccountClosed" to be able to raise from anywhere

* removed legacy code, since everything got ported to backbone
  (except the "cache" stuff, but that's not strictly necessary)

This reverts commit c52342b7.

don't render page-viewer twice; last_post should actually get the last post posted, not the first one

you can now create a comment with User#comment!(post, text)

fix #2627 (webfinger produces 500 error, and refactor a little to encapsulate into Webfinger object a bit more

ms iz rendering nothing for hcard and webfinger if account is closed, not showing aspect dropdown if the user account is closed

exclude blocked users from all streams

What i did was to redirect to the tag without dots, in this case cubbies
I didn't consider a good idea to add route support for /tags/cubbi.es
since it get messed with request formats

So. It turns out that postgresql has a less-consistent idea of what .first means in an association with no default ordering. All the places we were doing bob.aspects.first (& etc.) needed to be more specific. & o ya, POSTGRES IS GREEN.