The `Status` class has a default order on it, so when this query gets built and
gets all the way to `find_in_batches` there is an order already there.

When `find_in_batches` is run it discards any existing order on the query, and
emits a warning to the logs if there is one there.

This change removes the order prior calling `find_in_batches`, which will stop
the logged warning from occurring as well.

make regeneration worker unique, (only schedule/execute once at a time)

do not re-create a dynamic class on each feed push call, make sure redis-rb uses hiredis

adjusted to allow choosing it, yet

reinsert it when someone boosts it

status is not in the system at time of distribution; fix #607 - reset privacy
settings to defaults when cancelling replies

redis-backed "mentions" timeline as redundant (given notifications)

background as well since it's a computationally expensive

now return empty hash instead of throwing a 404 error. When following,
merge into timeline will filter statuses

resolving the confusion from self-chain replies ultimately linking to a
non-self status. Adjust filters

Reflect "requested" relationship in API and UI
Reflect inability of private posts to be reblogged in the UI
Disable Webfinger for locked accounts

who don't follow them

to be more readable, add extra logging to process feed service

timeline reload in UI, other small fixes

as well as formatting of content

in the pool, adding a throttle of 60rpm per IP, adding mini profiler, adding
admin status to users

and atom feed generation to some extent, as well as the way mentions are
stored