fix #1596: Add content-type field to pleroma and gotosocial backends #2293
+14
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
h3poteto
reviewed
Nov 6, 2025
| scheduled_at?: string | ||
| language?: string | ||
| quote_id?: string | ||
| content_type?: string |
Owner
There was a problem hiding this comment.
Currently, megalodon interface doesn't have this parameter, how to use this?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! I'm adding this feature specifically to use with Akkoma, but I looked through each api. only akkoma is tested, and we don't do any amount of static checking on the input (pleroma derivatives communicate what valid content-types there are through nodeinfo, so the valid set of inputs is dynamic)
pleroma docs:
https://docs-develop.pleroma.social/backend/development/API/differences_in_mastoapi_responses/#post-apiv1statuses
akkoma docs:
https://docs.akkoma.dev/stable/development/API/differences_in_mastoapi_responses/#post-apiv1statuses
gotosocial docs:
https://docs.gotosocial.org/en/latest/api/swagger
scroll to
/api/v1/statuses
vanilla masto and friendica don't support this, firefish appears to be discontinued, and I can't find documentation for pixelfed?