Skip to main content


Help wanted to design the moderation pages


Hi #Friendica people,

I've started a design document for the upcoming moderation pages that come with adding support for moderation reports by @Michael Vogel . However, I need your help. I'm notoriously bad at keeping focused on writing such a document even if I recognize its usefulness to do things once and do them right.

So please add/edit what you think is missing/incorrect in this CryptPad file hosted by the ever-gracious @Tio

https://office.trom.tf/pad/#/2/pad/edit/1ensaAqGa8BSt3yPNBftb+mr/

Cc: @Friendica Support @Friendica Developers @Friendica Admins
in reply to Hypolite Petovan

I added an open question concerning the additional report fields (category and rule id).

reshared this

in reply to Marco R.

@Marco R. Thanks for your input! Category is meaningful but we don't have a concept of bulleted point TOS in Friendica so I'm not sur we should display the latter field for everybody.

reshared this

in reply to Marco R.

If I understand you correctly Marco, you are suggesting that admins will define their own reporting categories. Is that right? It would make sense considering the nature of the Fediverse.

I currently have three broad categories in my TOS in terms of reporting content https://friendica.hubup.pro/tos (See Section 3.) They are Spam, Online Harassment, and Grossly Offensive.
in reply to Andy H3

If the report is posted via API, it should be standardized categories. This would make it easy for a GUI.
Also "illegal" as additional category seems sensible.

reshared this

in reply to Andy H3

@Andy H3 This would be ideal, but at first we'll have hard-coded categories. Spam, Illegal Content, Safety (including harassment, discrimination, death threats...) and a broad Unwanted Behavior are my candidates.

reshared this

in reply to Hypolite Petovan

I was just thinking about how annoying it is to see trolls in the feed and not be able to report them. So thanks for helping implement this and doing it so thoughtfully. As of now, I don't have any notes.

reshared this

in reply to Hypolite Petovan

reshared this

in reply to Schmaker

@Schmaker Thanks, these suggestions are valuable, this was gong to be my next design avenue after handling reports.

As a aside, “ Block user for everyone but his followers on my instance” is already available as a console command named “silence-something” (I’m on my phone, will confirm later).

reshared this

in reply to Hypolite Petovan

@Schmaker The console command is globalcommunitysilence. There's no local alternative but there probably should be.

reshared this

in reply to Hypolite Petovan

Filtered word: nsfw

reshared this

in reply to utzer [Friendica]

@utzer ~Friendica~ @Schmaker I was replying to Schmaker, thanks for the elaboration, I thought this command was only for remote contacts not to show in the global community page, I guess it is wrongly named.

reshared this

in reply to Hypolite Petovan

I added a comment regarding the optional description when reporting. I saw at the end Marco's question pointing the need for categories.

reshared this

in reply to Andy H3

@Andy H3 Thanks! In my experience, making a free form text box required will not make people who did not intend on adding meaningful information suddenly do so.

I know it’s true at least for the “Signup reasons” field Mastodon provides for registration by approval.

reshared this

in reply to Hypolite Petovan

@Hypolite Petovan @Michael Vogel @Tio There should also be an option to mute/suspend/block users for a limited time period!

reshared this

in reply to Hypolite Petovan

I don't know whether text gets annotated with who added it, but I added the items about adding extra context to a report, bulk/group handling of reports and related history of an account, so if there are any questions there about what I mean, feel free to ask, change, remove, etc.

reshared this