Federate custom emojis with accounts

This prevents submission through ctrl/cmd+enter when the submit button is disabled.

Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

* run yarn manage:translations

* Update Japanese translations for domain blocks.

`navigator.share()` rejects Promise if user cancelled sharing, and it may
print it as an error on JavaScript console.

This patch ignores it and prints other errors on the console.

Fixes CW unfolding in moderation

* Support fetching objects of convertible types by URL (fixes #6924)

* Ignore invalid hashtags

Port 913a38111f to glitch-soc

* Keep list of blocked domains

Might be overkill, but I'm trying to follow the same logic as for blocked users

* Add basic domain block UI

* Add the domain blocks UI to Getting Started

* Fix undefined URL in `fetchDomainBlocks`

* Update all known users' domain_blocking relationship instead of just one's

Port f6a8d835d3 to glitch-soc

Might be overkill, but I'm trying to follow the same logic as for blocked users

related https://github.com/tootsuite/mastodon/pull/6956

* Implement ability to send direct messages from the user menu

* Implement message warning users that direct messages are visible to all mentioned users

* Update locales

Backport 3987bd18a4 to glitch-soc

Port WebUI changes from 58cede4808

Cache API is not supported on Safari 11.0 / iOS 11.

Since those caching is optional, this patch simply ignores it.

`notification.status` may not be present, e.g. follow notification.

That way, they are displayed in a list below the corresponding toot.

This is necessary to display toots with media but otherwise no contents,
as glitch-soc displays the media as a child of StatusContent, unlike
Mastodon.

add <div.zoomable-image__margin/> to keep margin of the image on zooming
move setting `scrollLeft` and `scrollTop` of container from callback of
`setState` to `componentDidUpdate`
add 'hammerjs' package for touch gesture detection
rewrite `ZoomableImage` using 'hammerjs'

max_id in the fetch request should be a status id, but media attachment id was used.

Port 77406d3a09 to glitch-soc

Port 86a9de6753 to glitch-soc

`Response.prototype.clone()` must be called before the response used.

This fixes an error from ServiceWorker and failing to load image when the
image is not cached.

This patch adds null item (i.e. gap) handling on below functions to avoid TypeError.

* `filterNotifications` called on user mute/block
* `deleteByStatus` called on status deletion

Comparison was downcasing only one side, therefore if previously
existing account had a non-lowercase spelling, it would be ignored
when checking for duplicates.

New rake task `mastodon:maintenance:find_duplicate_usernames` will
help find constraint violations that might have occured from the
presence of this bug.

Bump version to 2.3.3

to_s method of HTTP::Response keeps blocking while it receives the whole
content, no matter how it is big. This means it may waste time to receive
unacceptably large files. It may also consume memory and disk in the
process. This solves the inefficency by checking response length while
receiving.

* Refactoring scss

introduce scss variables for the media modal
fix css block structure corresponding to react components
fix flex layouts
remove background image of the loaded image on the media modal

* Fix typo

* Fix stack overflow on importFetchedAccounts

  When the account has moved property, it should process destination
  account instead of source account itself.

* Set account id instead of account object for moved property

  This restores "foo has moved to" indication on account view, and
  fixes `reblog` index on `accounts` object store.

Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

* Invites: Add '1 week' as expire option

IMO a max. of 1 day is too short. Not everyone has the time and motivation to use an invite in a 24 hour period. 1 week as a max. is I think a good compromise between convenience and security.

* Invites: Add '1 week' as expire option

IMO a max. of 1 day is too short. Not everyone has the time and motivation to use an invite in a 24 hour period. 1 week as a max. is I think a good compromise between convenience and security.

* Update en.yml