Federate spoiler_text using warning attribute on <content /> instead of a <category term="spoiler" />
Clean up schema file from accidental development migrations

in the background instead. Should fix delay where blocked person
can interact with blocker for a short time before background job
gets processed

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

Better initial state for unlisted/nsfw toggles

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

Filters out hidden stream entries from Atom feed
Blocks now generate hidden stream entries, can be used to federate blocks
Private statuses cannot be reblogged (generates generic 422 error for now)
POST /api/v1/statuses now takes visibility=(public|unlisted|private) param instead of unlisted boolean
Statuses JSON now contains visibility=(public|unlisted|private) field

from accounts/tags because it's a terribly inefficient way to paginate
large sets of data

Fix #233, fix #268

before loading new one, cache notifications API, fix missing follow button
on public profiles

account results

resources that require a user context vs those that don't (such as public timeline)

/api/v1/statuses/public   -> /api/v1/timelines/public
/api/v1/statuses/home     -> /api/v1/timelines/home
/api/v1/statuses/mentions -> /api/v1/timelines/mentions
/api/v1/statuses/tag/:tag -> /api/v1/timelines/tag/:tag

created via remote look-up when domains differ but point to the same resource