Port 2e1b5edfea to glitch-soc

Port 4f42238c29 to glitch-soc

Port 90b64c0069 to glitch-soc

This is both for consistency with account timelines and to not mess with
the logic used to decide whether going back in the browser's history is
going to make us leave the WebUI.

Port 8182b61518 to glitch-soc

Port 4eeda67727 to glitch-soc

Port 06252ec71e to glitch-soc

Port 5ea643b279 to glitch-soc

Port 46061dc041 to glitch-soc

Port 7403e5d306 to glitch-soc

Port 12ab15e584 to glitch-soc

Port 13dce12665 to glitch-soc

Port SCSS changes from 087e118971 to glitch flavour

It should not be necessary thanks to our Content Security Policy, but best
be sure in case a server's CSP is incorrect. Also, avoids a CSP warning about
loading remote scripts.

* Make sure loading indicator has enough vertical space
* Respect reduce_motion setting for loading indicator

Port 4ede51743e to glitch-soc

Fixes #855

Port c58c00651b to glitch-soc

Port part of 7c48688d85 to glitch-soc

The `hasMore` property of timelines in redux store was set whenever an API
request returned only one page of results, *even* if the query only requested
newer statuses (using `since_id`), causing `hasMore` to be incorrectly set to
false whenever fetching new toots in a timeline, which happens each time
an account's timeline or media gallery is visited.

Display “load more” more consistently, add a loading indicator on first load.

(Even though that codepath is probably never actually used…)

Port ecd303c097 to glitch-soc

Port 73be8f38c1 to glitch-soc

Port e18390cfe6 to glitch-soc

Port dfbadd6837 to glitch-soc

Port 7706ed038f to glitch-soc

Port 023fe5181b to glitch-soc

- Move componentWillMount and componentWillReceiveProps logic to
  getDerivedStateFromProps.
- Compute CW auto-unfold status earlier

Fixes #832

Port f978afa487 to glitch-soc

Port 180ae0472a to glitch-soc