25 lines
1 KiB
Markdown
25 lines
1 KiB
Markdown
# Differences in Mastodon API responses from vanilla Mastodon
|
|
|
|
A Pleroma instance can be identified by "<Mastodon version> (compatible; Pleroma <version>)" present in `version` field in response from `/api/v1/instance`
|
|
|
|
## Flake IDs
|
|
|
|
Pleroma uses 128-bit ids as opposed to Mastodon's 64 bits. However just like Mastodon's ids they are sortable strings
|
|
|
|
## Attachment cap
|
|
|
|
Some apps operate under the assumption that no more than 4 attachments can be returned or uploaded. Pleroma however does not enforce any limits on attachment count neither when returning the status object nor when posting.
|
|
|
|
## Timelines
|
|
|
|
Adding the parameter `with_muted=true` to the timeline queries will also return activities by muted (not by blocked!) users.
|
|
|
|
## Statuses
|
|
|
|
Has these additional fields under the `pleroma` object:
|
|
|
|
- `local`: true if the post was made on the local instance.
|
|
|
|
## Accounts
|
|
|
|
- `/api/v1/accounts/:id`: The `id` parameter can also be the `nickname` of the user. This only works in this endpoint, not the deeper nested ones for following etc.
|