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

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

on scrollable areas

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

This makes the UI appear less laggy. After all, the status *is* created
right there and then, it's the distribution to home timelines that can take
a while

See: https://dequeuniversity.com/rules/axe/2.1/label

add permissive CORS to API controllers

See: https://dequeuniversity.com/rules/axe/2.1/html-has-lang