The modal-handling code gives back focus to the element focused when the
modal opened. However, in the case of reply confirmation, it would do so
*after* the composer code itself requested focus.

Port bfec030a4e to glitch-soc

Port 4fdefffb99 to glitch-soc

Port 4c03e05a4e to glitch-soc

This introduces new requirements in the API:

  `/api/v1/timelines/tag/:tag` now accepts new params: `any`, `all` and `none`
  It now returns status matching tag :tag or any of the :any, provided that
  they also include all tags in `all` and none of `none`.

Port relevant parts of 9d4541c612 to glitch-soc

WARNING: This may break some custom skins!

  `.drawer > .contents` has been moved to
  `.drawer > .drawer__pager > .drawer__iner`, and the waves have been moved
  from `.drawer > .contents` to `.drawer__inner__mastodon`!

Port 5bf100f87b to glitch-soc

This is only available if the instance-wide setting isn't set and allows
people to hide their own followers count. This does not hide others' to
them.

Fixes #6060

Merge upstream changes

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

Merge upstream changes

Port 12ab15e584 to glitch-soc

Port 13dce12665 to glitch-soc

Port SCSS changes from 087e118971 to glitch flavour

Conflicts:
- app/controllers/admin/base_controller.rb
  Some refactoring made upstream, no real conflict.
- app/javascript/mastodon/features/compose/components/compose_form.js
  Updated using upstream's code but using maxChars instead of the
  hardcoded length of 500 characters per toot.
- app/javascript/styles/mastodon/components.scss
  Upstream redesigned the onboarding modal. Not sure why we had a
  conflict there.

Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.8.5 to 1.9.1.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.8.5...v1.9.1)

Signed-off-by: dependabot[bot] <support@dependabot.com>

This allowed you to brick your system when running that command, because the accounts would continue to advertise the old public key, but sign things with the new one

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.