* Add documentation for `delete_media` parameter to `DELETE /api/v1/statuses/:id`
* Add documentation for `DELETE /api/v1/media/:id`
* It's actually version 4
* It's actually version 4
* Revert "Remove accidentally included `application_id` params attribute from `ScheduledStatus` (#1572)"
This reverts commit 1204ebeab8f7934eb572f3b54073f54b696482e6.
* 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>
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>
* 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 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
* Add documentation for GET /api/v1/notifications/policy
* Add documentation for `PATCH /api/v1/notifications/policy`
* Add documentation for `GET /api/v1/notifications/requests`
* Add documentation for `GET /api/v1/notifications/requests/:id`
* Add documentation for accepting and rejecting requests
* Remove redundant HTTP request examples
* Add documentation for the `NotificationPolicy` entity
* Add documentation for the `NotificationRequest` entity
* Update admin/domain_blocks to include conflict response
When creating a domain block, if there is already a domain block rule for the domain, then the existing block is returned. This documents that behavior.
I've also documented the `digest` property which was added in https://github.com/mastodon/mastodon/pull/29092
* Document digest in Admin DomainBlock Entity
