#467 – Making the back button a little smarter

loaded status; do not preload submitted statuses into community/public
timelines, unless those timelines have already been loaded; do not
close streaming API connections for community/public timelines, once
they have been established (most users navigate back to them eventually)

reinsert it when someone boosts it

Add social.diskseven.com

New instance

Fixes #263; makes JavaScript's character counting the same as Ruby's

Add ability to search accounts by display name

from zooming in on them

for those errors

now allows to cycle through multiple images

make status pagination headers generation more lax about next page
existing

upon un-reblogging. Check if the reblog was in the feed in the first
place. It might have been filtered on distribution.

"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