Missing items/endpoints from api

[jwr1]

Here's a non exhaustive list of missing items/endpoints from the API that would be quite useful.

I'll add to this list once I run into more walls.

Also, whenever I say Content, I mean: thread/microblog/post/comment.

Missing Properties

• Tell if a user is an instance admin or global mod (should be a property in User objects): Add isAdmin and isGlobalModerator fields to user api response #1044
• Tell if the author of Content is a mod of the magazine it was put in.
• Tell if the signed in user has moderation capabilities over Content: Add field to all content response DTOs: canAuthUserModerate #1043
• For single comment requests (/api/comments/{comment_id} & /api/post-comments/{comment_id}), add a property containing the original post so it can be previewed above the comment itself.
• Get the reputation a user has (would be a property in UserResponseDto).

Missing Endpoints

• List the activities of Content (meaning who upvoted and boosted)
• Filter magazines by abandoned (this could just be another filter on the already existing /api/magazines endpoint).
• Request to become mod of a magazine
• Request to become owner of abandoned magazine
• View, accept, and deny magazine mod requests
• List the magazines a user is a mod of
• Tell what Content a user has boosted
• A combined overview of a person's Content, just like how Mbin profile pages combine their threads, microblogs, and comments together in one tab.

Current issues

• The PUT /api/moderate/magazine/{magazine_id} route (edit magazine) does not let you provide an empty description.

If you need help deciding exactly how to implement some of these, I'd be willing to give examples (also taking inspiration from Lemmy).

[BentiGorlich]

Could you split the list in

1. missing items
2. missing endpoints

Because I don't really know for which of these a dedicated endpoint might make sense