You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the account object has header_bg instead of header and header_static, is missing emojis and fields, has extra properties like pronouns and location, etc. Same with media_attachments: the object has extra properties not in other Mastodon API responses. I think the response from the delete handler isn't getting the same output transformations applied as other Mastodon API handlers.
The impact is that clients which use the result of a delete call may experience decoding errors.
Additionally, there's no text field on the deleted status as in the Mastodon API, which means that Mastodon API clients can't use this response to do a delete-and-redraft operation, since they don't have the original plain text source of a status.
The text was updated successfully, but these errors were encountered:
An example of the response to fetching an account, in the correct Mastodon format:
An example of the response to fetching a status created by the same account, also in the correct format:
An example of the response to deleting a status created by the same account:
Note that the
account
object hasheader_bg
instead ofheader
andheader_static
, is missingemojis
andfields
, has extra properties likepronouns
andlocation
, etc. Same withmedia_attachments
: the object has extra properties not in other Mastodon API responses. I think the response from the delete handler isn't getting the same output transformations applied as other Mastodon API handlers.The impact is that clients which use the result of a delete call may experience decoding errors.
Additionally, there's no
text
field on the deleted status as in the Mastodon API, which means that Mastodon API clients can't use this response to do a delete-and-redraft operation, since they don't have the original plain text source of a status.The text was updated successfully, but these errors were encountered: