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

add permissive CORS to API controllers

to the API

Also fix reloading of timelines after merge-type events

to sign in page after sign up instead of root path which redirects to /about

all required resource links (profile page, salmon, atom feed, magic key)

production as it's very verbose and not very useful