"whole known network" which is what public timeline used to be

Only domain blocks with suspend severity will block PuSH subscriptions
Silenced accounts should not appear in conversations unless followed

So that if we get an error, then we will
only delete status if it is an 404 error

Using catch statement in api_controller.rb to catch NotPermitted
Exception, and render error message

of mix of video and images in status, just wasn't rendering
the show action. I moved the validation before the status creation

Moved validation to services/post_status_service.rb

Modified uploadCompose action to send media ids of attached
media when sending a request. Modified create method in MediaController
to check if when posting a video, there are no other media attached
to the status by looking at the media ids sent from the uploadCompose
action.

No need to flash error message when status is not found.
The column will display the message "status not found"

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

Make replies default to privacy settings of the status being replied to

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

in case of debugging incoming salmons. Add <thr:in-reply-to /> to favourite
salmons because it seems to be required by GS.

StreamEntry model. Simply render Salmon slaps as they are needed

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.

Add variable for text of privacy disclaimer

Allow PuSH to distribute private toots with that condition

if account lock info was up to date, otherwise re-do the FollowService
with now updated information