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
Did you check to see if this issue already exists?
Is this only a feature request? Do not put multiple feature requests in one issue.
Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
Is your proposal related to a problem?
I'm one of the devs on Mlem, an iOS reader for Lemmy. We want to flair moderators in the main feed, but to do so with the current API would require us to make additional calls for every post to fetch community context and parse the mod list. Including this information in the original PostView response would let us reduce the load our app puts on instances.
Describe the solution you'd like.
Include a boolean creator_mod field in PostView and CommentView to indicate whether the creator is a moderator of the community the post or comment was made in.
Describe alternatives you've considered.
Making an additional call for every post to get the community information and parsing the mod status from there. We discarded this because of the load it would add to instances.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Requirements
Is your proposal related to a problem?
I'm one of the devs on Mlem, an iOS reader for Lemmy. We want to flair moderators in the main feed, but to do so with the current API would require us to make additional calls for every post to fetch community context and parse the mod list. Including this information in the original PostView response would let us reduce the load our app puts on instances.
Describe the solution you'd like.
Include a boolean
creator_mod
field inPostView
andCommentView
to indicate whether the creator is a moderator of the community the post or comment was made in.Describe alternatives you've considered.
Making an additional call for every post to get the community information and parsing the mod status from there. We discarded this because of the load it would add to instances.
Additional context
No response
The text was updated successfully, but these errors were encountered: