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

office.trom.tf/pad/#/2/pad/edi…

Cc: @Friendica Support @Friendica Developers @Friendica Admins

#Friendica @Friendica Developers @Friendica Admins @Friendica Support @Michael Vogel @Tio

reshared this

in reply to Hypolite Petovan

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

reshared this

in reply to Marco R.

Hypolite Petovan
Hypolite Petovan
• •
@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.
@Marco R.

reshared this

in reply to Hypolite Petovan

F00FC7C8 likes to infodump
F00FC7C8 likes to infodump
• •
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

Schmaker
Schmaker
•

I'm not sure if it's related to this document (as it seems to me like it is focused on reporting only, not the moderation itself), but somehow i find it important to mention - what will be actual moderation options (and what activitypub and related implementations allows to do).

Just an ideas to consider, you may also don't care at all, feel free to ignore 😀

At this moment we can:
Block user on my instance
It's not clear to me if it just hides user on my instance, or also block for users followers on my instance. Does he keeps read-only access?
Block remote user for everyone on my instance
Delete user on my instance
Obvious

What i think we also should be able to do:
Block user for everyone but his followers on my instance
No more showing in global/local timelines and public comments
Hide user's profile
Mark user as moderated and let visitor show his profile with warning from moderator (similar what Mastodon does)
Warn user
No moderation action, just giant "you have been warned by moderator, if you continue violating instance rules, then your account can face consequences"
Block user's federation to other servers
Sometimes you may want user's content and comments only on your server (or block it for selected server) as they can be controversial for others
Let user comment only his posts
This may be specifically effective against trolling imho
Mark post/comment moderated
Hide post/comment behind warning message

reshared this

in reply to Schmaker

Hypolite Petovan
Hypolite Petovan
• •

@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).

@Schmaker

reshared this

in reply to Hypolite Petovan

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

reshared this

in reply to Hypolite Petovan

utzer [Friendica]
utzer [Friendica]
• •

Filtrované slovo: nsfw

@Schmaker @Hypolite Petovan

reshared this

in reply to utzer [Friendica]

Hypolite Petovan
Hypolite Petovan
• •
@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.
@Schmaker @utzer [Friendica]

reshared this

Unknown parent

Hypolite Petovan
Hypolite Petovan
• •

@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.

@Andy H3

reshared this

Unknown parent

Marco R.
Marco R.
• •
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

Unknown parent

Hypolite Petovan
Hypolite Petovan
• •
@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.
@Andy H3

reshared this

in reply to Hypolite Petovan

Matthias Moritz
Matthias Moritz
• •
@Hypolite Petovan @Michael Vogel @Tio There should also be an option to mute/suspend/block users or instances for a limited time period!
@Hypolite Petovan @Michael Vogel @Tio
Tato položka byla upravena (2 years ago)

reshared this

in reply to Hypolite Petovan

Gidi Kroon
Gidi Kroon
• •
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

⇧