X-Git-Url: http://git.squeep.com/?a=blobdiff_plain;f=docs%2FDifferences-in-MastodonAPI-Responses.md;h=7b11fe90f6d4ab843f094fde8db3349a1522a81a;hb=34fc0dca2e879bcbb73acc80fdc72678411d0ebf;hp=f6a5b6461b8d86486508774dfa02c5edd9880872;hpb=cd019a5927059bb52447add43a9b29893928c416;p=akkoma

diff --git a/docs/Differences-in-MastodonAPI-Responses.md b/docs/Differences-in-MastodonAPI-Responses.md
index f6a5b6461..7b11fe90f 100644
--- a/docs/Differences-in-MastodonAPI-Responses.md
+++ b/docs/Differences-in-MastodonAPI-Responses.md
@@ -9,3 +9,17 @@ Pleroma uses 128-bit ids as opposed to Mastodon's 64 bits. However just like Mas
 ## 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.