duplicates. Web UI regenerates UUID for that header every time the compose
form is changed or successfully submitted

Also, fix Farsi i18n overwriting the English one

* Added API backend for notification dismissal

* Added render statement

* Changed statement

* Add exclude_types param to /api/v1/notifications

* Exclude notification types in web UI through exclude_types in the API

* Allow users to update their Account in the API

It would be nice for API clients to be able to allow users to update
their accounts without having to wrap Mastodon in a web view. This patch
adds an API endpoint to let users submit a PATCH for their account.

Signed-off-by: David Celis <me@davidcel.is>

* Add /api/v1/accounts/update_credentials to the API docs

Signed-off-by: David Celis <me@davidcel.is>

* Make /api/v1/timelines/public and /api/v1/timelines/tag/:id public
Fix #1156 - respect query params when generating pagination links in API

* Apply pagination fix to more APIs

Returns accounts, statuses, hashtags arrays

Redirect /:username to /users/:username
Redirect /:username/:id to /users/:username/updates/:id
Updated API documentation and sponsors

make status pagination headers generation more lax about next page
existing

Using catch statement in api_controller.rb to catch NotPermitted
Exception, and render error message

Moved validation to services/post_status_service.rb

Modified uploadCompose action to send media ids of attached
media when sending a request. Modified create method in MediaController
to check if when posting a video, there are no other media attached
to the status by looking at the media ids sent from the uploadCompose
action.

Make replies default to privacy settings of the status being replied to

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

redis-backed "mentions" timeline as redundant (given notifications)

Federate spoiler_text using warning attribute on <content /> instead of a <category term="spoiler" />
Clean up schema file from accidental development migrations

in the background instead. Should fix delay where blocked person
can interact with blocker for a short time before background job
gets processed

background as well since it's a computationally expensive

now return empty hash instead of throwing a 404 error. When following,
merge into timeline will filter statuses

Better initial state for unlisted/nsfw toggles