Requirements

• Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
• 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?

Lemmy's moderation abilities are based on a top down hierarchy: a list of admins, then mods. No one can do mod-related actions on someone higher than them in the hierarchy.

Unfortunately for UIs, this means that every place where moderation is possible, must pass:

• A list of admins
• A list of community mods
• Your person_id
• The content creator's person_id

This is cumbersome and potentially a performance hit, since some threads have thousands of comments, and these lists and logic must be performed repeatedly in the front ends.

IE the logic of whether you can_mod something, is duplicated across front and back ends.

Describe the solution you'd like.

1. Add a can_mod field to every moddable item: PostView, CommentView, and a few others.

This should be possible with postgres.

One other complication: occasionally you can_mod your own content, but that should already be taken care of by creator == myId and creator_is_mod in the front ends.

Describe alternatives you've considered.

N/A

Additional context

See LemmyNet/jerboa#1323 (comment)