forgejo/discussions
49
43

Regarding moderation transparency #113

Closed
opened 2024年02月05日 10:00:23 +01:00 by oatbiscuits · 7 comments

I have read the moderation process document.

Given that a decent chunk of content has been recently removed, can there be a public moderation log (it could be delayed to avoid knee-jerk reactions) to document the content that was removed?

I have read the [moderation process document](https://codeberg.org/forgejo/governance/src/branch/main/MODERATION-PROCESS.md). Given that a decent chunk of content has been recently removed, can there be a public moderation log (it could be delayed to avoid knee-jerk reactions) to document the content that was removed?

I do not think this is a good idea. The goal of moderation is to remove the noise, the content that goes against the code of conduct, or is otherwise problematic. Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too.

I do not think this is a good idea. The goal of moderation is to remove the noise, the content that goes against the code of conduct, or is otherwise problematic. Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too.

As a prime example, ban evading and derailing topics is not something that should be given a platform in a public log.

As a prime example, ban evading and derailing topics is not something that should be given a platform in a public log.

Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too.

Putting a delay (30 days, for example) on it, possibly removing the identifying bits, and posting it as a markdown or log file (no comment section) might address these concerns.

I understand the trade-off and the effort involved, but I believe some form of a compromise to bring a level of transparency into moderation actions is worth it.

I also do understand that ultimately Forgejo members decide on such matters, but I thought it is important to bring up nonetheless.

> Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too. Putting a delay (30 days, for example) on it, possibly removing the identifying bits, and posting it as a markdown or log file (no comment section) might address these concerns. I understand the trade-off and the effort involved, but I believe some form of a compromise to bring a level of transparency into moderation actions is worth it. I also do understand that ultimately Forgejo members decide on such matters, but I thought it is important to bring up nonetheless.

@oatbiscuits you can write moderation@forgejo.org to get the moderation report.

In this case it is not the content of the messages that is problematic, but the fact that the poster has been explicitly banned (so any message the poster may write will be moderated during the ban period - independent of the content).

If you want a log of the messages, you should activate email notifications (and add a sorting rule in your inbox to prevent becoming overwhelmed :).

@oatbiscuits you can write moderation@forgejo.org to get the moderation report. In this case it is not the content of the messages that is problematic, but the fact that the poster has been explicitly banned (so any message the poster may write will be moderated during the ban period - independent of the content). If you want a log of the messages, you should activate email notifications (and add a sorting rule in your inbox to prevent becoming overwhelmed :).

Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too.

Putting a delay (30 days, for example) on it, possibly removing the identifying bits, and posting it as a markdown or log file (no comment section) might address these concerns.

Removing the identifying bits is hard, and error prone. When it comes to moderation, I believe the straightforward approach is to err on the side of safety, and remove everything. That's a trade off, yes. Some useful bits may be lost, indeed. But the cost of failing to remove identifying bits properly is, I think, greater than any value we may possibly gain from a public log.

There's an internal, non-public moderation log. Not being a moderator, I have no clue what's in there, but based on the moderation process, it should contain all the information necessary for a review, should the action be appealed. I suspect it might contain enough information to restore a removed message too, would the appeal be granted. I think that's fine, and this information does not need to be public.

I understand the trade-off and the effort involved, but I believe some form of a compromise to bring a level of transparency into moderation actions is worth it.

I think the current practice of forgejo-moderation posting a message at the place of removal is adequate and sufficiently transparent, and protects all parties: it does not reveal who did the moderation, and it does not reveal the target either. Once the message is removed, identifying the target without seeing the original first is going to be difficult, as it should be.

> > Reintroducing those, even partially, in a public place defeats the purpose of moderation, does it not? It gives a platform for spammers, too. > > Putting a delay (30 days, for example) on it, possibly removing the identifying bits, and posting it as a markdown or log file (no comment section) might address these concerns. Removing the identifying bits is hard, and error prone. When it comes to moderation, I believe the straightforward approach is to err on the side of safety, and remove everything. That's a trade off, yes. Some useful bits may be lost, indeed. But the cost of failing to remove identifying bits properly is, I think, greater than any value we may possibly gain from a public log. There's an internal, non-public moderation log. Not being a moderator, I have no clue what's in there, but based on the moderation process, it should contain all the information necessary for a review, should the action be appealed. I suspect it might contain enough information to restore a removed message too, would the appeal be granted. I think that's fine, and this information does not need to be public. > I understand the trade-off and the effort involved, but I believe some form of a compromise to bring a level of transparency into moderation actions is worth it. I think the current practice of `forgejo-moderation` posting a message at the place of removal is adequate and sufficiently transparent, and protects all parties: it does not reveal who did the moderation, and it does not reveal the target either. Once the message is removed, identifying the target without seeing the original first is going to be difficult, as it should be.

A message from an account created to circumvent a ban from Forgejo spaces was deleted, send a mail to moderation@forgejo.org for more information.

A message from an account created to circumvent a ban from Forgejo spaces was deleted, send a mail to moderation@forgejo.org for more information.

@oatbiscuits all moderated content is archived and available on request to moderation@forgejo.org. It will just not be made public.

@oatbiscuits all moderated content is archived and available on request to moderation@forgejo.org. It will just not be made public.
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#113
Reference in a new issue
forgejo/discussions
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?