The status is not showing anymore after clicking on it

This makes so clicking the link to the github opens in a new tab or windows.

I just keep getting frustrated clicking the link to github and then losing my place in my home timeline >_> that's all

Fix issue with detailed status view not supporting unreblogging/unfavouriting

Fix #635 - Include the initially-reported status in report UI even if it's not
among the user's most recent statuses

I haven't had a chance to test this, because I don't currently have a fully functioning computer I can set up a dev-environment on, but this *should* make it so when a user toggles a post to be private, a disclaimer appears clarifying what "private" really means.

to only those from local users; Add link to "extended information" to
getting started in the UI; Add defaults for posting privacy; Change
how publish button looks depending on posting privacy chosen

Try to fix Travis CI setup

warning mentions preview into area where actual content would be

overshadow requirement for remote-lookup

work flawlessly was a nightmare). WARNING: This commit makes the web UI connect to the streaming API instead
of ActionCable like before. This means that if you are upgrading, you should set that up beforehand.

sounds complex, but really it just reorganizes the posting options and
adds a seperator line

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

nested inside a common parent (<Account>), instead they all embed <HeaderContainer />

the public timeline has been using

Currently we have the problem where the follow request button is missing
from the Follow request tab. This means that when you visit that tab you
either have to press the back button in the browser or re-enter the home
page, which breaks the app flow.

This will resolve that issue by adding a new back button to that tab,
in the same way that the public timeline, and favourites have.

for extremely wide monitors

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

Also, since the root component connects to the stream that updates home/notification columns,
there is pretty much no case for refreshing those columns beyond initial load. So, move the
loading of those columns into the root component, to prevent unneccessary reloads when switching tabs
on mobile or resizing desktop window between mobile/desktop layouts