Mastodon API compatibility changes for stable FE

This is a list of things missing from MastoAPI that's present in QvitterAPI and PleromaFE uses.

This list probably incomplete and will be updated when we find bugs.

Breaky stuff

Misc

• only includes activities and no favs etc, this is needed to update fav/rt counters and other things. See also #406 (closed)

Post

• masto only gives HTML representation of post, no plaintext version. This would probably break notifications, and makes word-muting slightly less predictable and optimal
• missing is_local makes all posts marked as external even if they are local. this shows "open on original instance" link on all posts.
• statusnet_conversaion_id (now pleroma.conversation_id)

User

• background_image there's an issue about making use of it
• name only gives html name, this, same as post's text would mess up notifications
• /api/v1/accounts/:id/followers and /api/v1/accounts/:id/following do not actually support limit, max_id, since_id params this basically causes a regression of known bug pleroma-fe#285 (closed) making viewing profile of someone's with large list of followers a bit unbearable.

Notifications

• is_seen is missing, there's also some some discrepancy in how status is attached to it but it requires further investigation

User Setting

• /api/v1/accounts/update_credentials does not support [show_role no_rich_text default_scope hide_follows hide_followers params]

Not that big of a deal

• token (used for Pleroma chat)
• no_rich_text default_scope hide_follows hide_followers (and others similar), these are used to read user-profile-settings. Probably needs its own separate API and should be worked around in FE until we get dedicated APIs for it.

Worked-around by FE

Post

• in_reply_to_screen_name worked around in FE but still it's some unnecessary complexity in FE
  Worked around in FE, but still kinda buggy

User

• lack of follows_you on user data will cause "Follows you" to be inconsistent. In MastoAPI you need to query a separate endpoint go get the info.
  It has been discussed in IRC, but it's probably better to keep FE more stable while we switch it to MastoAPI, so it could be added temporarily until we add needed API handling into FE.
• statusnet_blocking this determines "blocked"/"block" button on usercard, probably related to one before it.
• muted same as above, but regarding muted user
• rights used to determine if user is an admin and can delete posts of others but as far as I can see this doesn't work
  Still not working, added support for relationship API in pleroma-fe!655 (merged)
• is_local worked around by detecting an @ in screen_name

Attachments

• mimetype MastoAPI only gives type, it sorta works with only half of it but more info would be better.