word-break:break-all is a surefire way to break things. It should be set
to normal.
This merge just set it back to what it should be.
Tested on Firefox 52.0.2 and Chrome 56.0.2924.87 with no detected
errors.

Thanks garg

Privacy descriptions were very difficult to reason. This is the minimal level of color contrast to be WCAG AA compliant.

add ability to open status by URL from search (fix #53)

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)

from zooming in on them

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

Changing the way the background image is positioned and the box is sized should fix problems with the text overlapping the image on mobile browsers and Edge.

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

for extremely wide monitors

improved how "show more" link looks

Currently, the getting started text fails WCAG standards for color contrast by a lot. Especially on the part overlapping with the elephant graphic which is nearly unreadable even for users with 20|20 vision. This change doesn't fix the elephant overlap but at least makes the text meet AAA WCAG Small Text color contrast standards, making it easier to read.