PleromaFE moderation tools discussion

feld commented

2019-02-04 01:22:23 +00:00

Owner

Pleroma doesn't have any moderation tools in the UI yet except the "Delete" functionality as pictured below.

I propose that we replace the delete button with some kind of context menu that exposes the following:

If moderator:

Delete status
Lock/Unlock account (local users)
Activate/Deactivate account (remote users; effectively an instance-wide block)

If admin:

Grant/Revoke moderator (local users)
Grant/Revoke admin (local users)
Delete account (local users)

Does this make sense? Let me know if I confused anything

Pleroma doesn't have any moderation tools in the UI yet except the "Delete" functionality as pictured below. ![E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09](/attachments/0c9196bb-100f-475f-b849-429264bb5ac2) I propose that we replace the delete button with some kind of context menu that exposes the following: If moderator: * Delete status * Lock/Unlock account (local users) * Activate/Deactivate account (remote users; effectively an instance-wide block) If admin: * Grant/Revoke moderator (local users) * Grant/Revoke admin (local users) * Delete account (local users) Does this make sense? Let me know if I confused anything

E14AB7EF-01E6-4D3F-9EBA-89CE695F3A09.jpeg

159 KiB

ibrokemypie commented

2019-02-04 01:29:21 +00:00

Member

It'd be good to have the account related options accessible from accounts as well.
Also an option to automatically mark all media posted by a user as sensitive would be very useful

It'd be good to have the account related options accessible from accounts as well. Also an option to automatically mark all media posted by a user as sensitive would be very useful

lanodan commented

2019-02-04 01:30:46 +00:00

Owner

Would require some backend changes for the moderator part outside of deleting the status but why not.

And I think the admin part should be on the user view, along with password reset.

Would require some backend changes for the moderator part outside of deleting the status but why not. And I think the admin part should be on the user view, along with password reset.

mirsal commented

2019-02-04 01:31:44 +00:00

Member

I think it does make sense.

Also a way for non-admin/moderator users to flag posts or users would be helpful. However I suspect it will require much more work.

I think it does make sense. Also a way for non-admin/moderator users to flag posts or users would be helpful. However I suspect it will require much more work.

kaniini commented

2019-02-04 01:31:56 +00:00

Member

I am working on an MRF module that leverages the tagging system.

The tags are:

mrf_tag:media-force-nsfw: force attachments to be NSFW
mrf_tag:media-strip: strips media uploads from posts
mrf_tag:force-unlisted: public posts become unlisted
mrf_tag:disable-remote-subscription: disable following the remote user
mrf_tag:disable-any-subscription: disable following the user at all
mrf_tag:quarantine: disable outgoing federation for the user
mrf_tag:sandbox: forces posts to be followers-only

I am working on an MRF module that leverages the tagging system. The tags are: * `mrf_tag:media-force-nsfw`: force attachments to be NSFW * `mrf_tag:media-strip`: strips media uploads from posts * `mrf_tag:force-unlisted`: public posts become unlisted * `mrf_tag:disable-remote-subscription`: disable following the remote user * `mrf_tag:disable-any-subscription`: disable following the user at all * `mrf_tag:quarantine`: disable outgoing federation for the user * `mrf_tag:sandbox`: forces posts to be followers-only

kaniini commented

2019-02-04 01:33:27 +00:00

Member

@mirsal flagging reports is Pleroma MR pleroma!701.

feld commented

2019-02-04 01:44:22 +00:00

Author

Owner

Backend changes can be handled once we decide the exact scope of this issue.

Is there consensus that only delete should be in posts and the rest in a new menu on user profile? I'm OK with any approach. Duplicated UI elements is kind of confusing and silly, so let's avoid that.

Backend changes can be handled once we decide the exact scope of this issue. Is there consensus that only delete should be in posts and the rest in a new menu on user profile? I'm OK with any approach. Duplicated UI elements is kind of confusing and silly, so let's avoid that.

kaniini commented

2019-02-04 01:45:12 +00:00

Member

I think delete button should be kept and then the staff options can be a context menu next to it.

ilja commented

2019-02-04 07:03:22 +00:00

Member

Maybe instance wide stuff can be added as well?
For instance, if the "SimplePolicy" is active:

add instance to SimplePolicy.reject
add instance to SimplePolicy.media_removal
add instance to SimplePolicy.media_nsfw
add instance to SimplePolicy.federated_timeline_removal

(Unless there's a better way for that offcourse)

Basically I see three scopes here

What to do with the post
What to do with the useraccount
What to do with the instance

Maybe instance wide stuff can be added as well? For instance, if the "SimplePolicy" is active: * add instance to SimplePolicy.reject * add instance to SimplePolicy.media_removal * add instance to SimplePolicy.media_nsfw * add instance to SimplePolicy.federated_timeline_removal (Unless there's a better way for that offcourse) Basically I see three scopes here * What to do with the post * What to do with the useraccount * What to do with the instance

feld commented

2019-02-04 17:41:53 +00:00

Author

Owner

Instance-wide stuff will probably live in a dedicated admin interface. It's a lot of extra work to figure that stuff out vs just improving available moderation capabilities right now.

kaniini commented

2019-02-04 18:24:33 +00:00

Member

this issue has to do with posts and accounts, yeah.

by the way, the accounts stuff is ready for review on BE side (pleroma!768), so once that goes in, we can add the actions to FE if TagPolicy is enabled (check nodeinfo for that).

this issue has to do with posts and accounts, yeah. by the way, the accounts stuff is ready for review on BE side (pleroma!768), so once that goes in, we can add the actions to FE if `TagPolicy` is enabled (check nodeinfo for that).

kaniini commented

2019-02-05 19:42:57 +00:00

Member

@feld is anyone building a prototype for the dropdown?

feld commented

2019-02-05 21:14:10 +00:00

Author

Owner

Not at the moment. Do we want to prototype dropdowns yet or just reach a final consensus of what features we're exposing in each part of the UI? It's not clear to me yet that we have a final decision of what goes where, so if you want to make that call that's OK with me.

Sooner we have a clear scope of work the sooner I can have someone start working on it.

Not at the moment. Do we want to prototype dropdowns yet or just reach a final consensus of what features we're exposing in each part of the UI? It's not clear to me yet that we have a final decision of what goes where, so if you want to make that call that's OK with me. Sooner we have a clear scope of work the sooner I can have someone start working on it.

kaniini commented

2019-02-05 21:29:10 +00:00

Member

Lets do this:

delete button on posts stays where it is
dropdown menu on user profile cards (maybe next to 'Block' button):
- grant/revoke admin
- grant/revoke moderator
(there should be a divider and then these options)
- deactivate account
- delete account
(the next options should only show if mrf_tag is available):
- force user posts to be NSFW
- force user posts to not have media at all
- force user posts to be unlisted
- force user posts to be followers-only
- disallow following user from remote instances
- disallow following user at all
- disallow user posts from federating

Lets do this: - delete button on posts stays where it is - dropdown menu on user profile cards (maybe next to 'Block' button): - grant/revoke admin - grant/revoke moderator (there should be a divider and then these options) - deactivate account - delete account (the next options should only show if mrf_tag is available): - force user posts to be NSFW - force user posts to not have media at all - force user posts to be unlisted - force user posts to be followers-only - disallow following user from remote instances - disallow following user at all - disallow user posts from federating

feld commented

2019-02-05 21:31:16 +00:00

Author

Owner

I expect that it should query for current state and update text appropriately, right?

So:

Grant admin

after set this menu should show

Revoke admin

etc, etc

I expect that it should query for current state and update text appropriately, right? So: * Grant admin after set this menu should show * Revoke admin etc, etc

kaniini commented

2019-02-05 21:32:29 +00:00

Member

Yeah, I don't know what BE changes are needed for this off the top of my head, but at least we can prototype the UX side.

shpuld commented

2019-02-06 14:49:53 +00:00

Owner

I would also replace the delete X button with a ... menu that also contains delete there, and would be a good place to put other future per-post actions (mute thread, report, bookmark, whatever) as well as admin actions. more than 4 buttons in the bottom sounds a bit too excessive.

eugenijm referenced this issue

2026-02-06 05:29:28 +00:00

Moderation menu #310 #1865

Rows
Columns

PleromaFE moderation tools discussion #310