* include migration steps to stop the redis-server service on your new machine before copying the redis dump file
* use single command for redis-cli SAVE instead of opening then exiting the interactive client
* Move pagination config to own section (deprecation warning)
* Update hugo to version 0.140.0
* Update actions/checkout to v4
* Update actions/configure-pages to v5
* Update actions/upload-pages-artifact to v3
* Update actions/deploy-pages to v4
* Update hugo to version 0.140.2
* Revert "Remove accidentally included `application_id` params attribute from `ScheduledStatus` (#1572)"
This reverts commit 1204ebeab8.
* Add note about the utter contempt we hold for this useless value
* Update ScheduledStatus.md
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
* Update ScheduledStatus.md
Co-authored-by: David Roetzel <david@roetzel.de>
---------
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
Co-authored-by: David Roetzel <david@roetzel.de>
Adds a callout box mentioning that CORS headers must be set if WebFinger requests are being redirected to support a customised WEB_DOMAIN value.
This requirement is not called out in the text (only the nginx config example next to it), and is non-obvious enough that, anecdotally, many servers do not implement it properly.
See: https://github.com/mastodon/mastodon/issues/26995
Add a new document that precisely describes the string representation of
datetime and date types.
The previous description of them as "ISO 8601 Datetime" was very
imprecise, as ISO 8601 describes many different ways of representing a
datetime and date.
Specify the datetime format precisely as the ISO 8601 profile described
in RFC 3339, and the date format precisely as the "Complete date" format
from the W3C note on date and time formats.
Adjust all the references to ISO 8601 datetimes or dates to link back
to the definition.
Fixes#1420
* Improve deprecation messaging for Application#vapid_key
* Format JSON examples in Instance methods
* Remove vapid_key from Apps API examples, since this property is deprecated on Application entity
* Add documentation for new OAuth 2.0 features added in 4.3.0
* Improve documentation for oauth-scopes
* Update content/en/api/oauth-scopes.md
Co-authored-by: Matt Jankowski <matt@jankowski.online>
* Update content/en/api/oauth-scopes.md
Co-authored-by: Matt Jankowski <matt@jankowski.online>
* Update content/en/api/oauth-scopes.md
Co-authored-by: Matt Jankowski <matt@jankowski.online>
* Update content/en/api/oauth-scopes.md
Co-authored-by: Matt Jankowski <matt@jankowski.online>
* Add deprecated and removed shortcode labels
* Use deprecated and removed shortcodes
* Improve OAuth documentation
* More OAuth documentation improvements
* Correct streaming API documentation after 4.2.0 changes
* Add note about improved Push Subscription API validation in 4.3.0
* Fix inconsistent OAuth label formatting
* Add note that there is a relationship between Accounts and the Application used to create them
* Add note that application registration endpoint also supports JSON bodies
* Be consistent in the formatting of placeholder values for Bearer tokens
* code review changes
* Slight changes in wording
* Add documentation for PKCE
* Removal of crypto oauth scope
* Cross-link authorization's scope with the OAuth Scopes documentation
* Update content/en/methods/oauth.md
* Update content/en/api/oauth-scopes.md
---------
Co-authored-by: Matt Jankowski <matt@jankowski.online>
Co-authored-by: David Roetzel <david@roetzel.de>
* Update installation instructions...
...for Mastodon 4.3 on Ubuntu 24.04 and Debian 12.
* Reorder sections
To get rid of specifying a ruby version. Also simplifies the
steps even further.
* Allow other users to traverse mastodon home
instead of using group permissions. We heard a lot of
different opinions on this and it is clearly not a
solution for everyone, but in contrast to the group
permissions:
* `www-data` will not get write access to mastodon files
* this works identical on Debian and Ubuntu
* Clarify `group_key` for ungrouped notifications
* Clarify that `grouped_types` affects `group_key` but not streaming API
* Update content/en/methods/grouped_notifications.md
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
---------
Co-authored-by: David Roetzel <david@roetzel.de>
Add tip to allocate more memory if Elasticsearch crashes to elasticsearch.md
When creating Elasticsearch indicies, the process could crash if there is not enough memory allocated to the JVM runtime.
This commit adds a hint for administrators to try to allocate more memory to Elasticsearch if they're experiencing out-of-memory issues.
* Add rough documentation for `/api/v2_alpha/notifications`
* Update notifications_alpha.md
* Add very rough documentation about notification groups entities
* Add documentation for `NotificationGroup` entity
* Document pagination-only `NotificationGroup` attributes
* Fix documentation issue with `/api/v2_alpha/notifications/:group_key` and add example output
* Add blurb about the goal of grouped notifications
* Update notifications_alpha.md
* Specify that the 80 limit is for notification groups, not notifications
* Add documentation for `group_key` to `Notification` entity
* Make `max_id`, `since_id` and `min_id` more explicit
S.H.