status clickable (this also fixes multiple dropdown being openable at the same
time)

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