New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the number of moderators for an instance to the About page for that instance #8557

Open
codesections opened this Issue Sep 1, 2018 · 5 comments

Comments

Projects
None yet
6 participants
@codesections
Copy link

codesections commented Sep 1, 2018

Instances vary tremendously in the number of users per moderator they have—some have ~50,000 users for every moderator; others have ~250 users per moderator. Individuals who are particularly subject to harassment may wish to join instances that have a high number of moderators because those moderators would be better able to protect vulnerable members.

However, the total number of moderators is not made public in any way. I suggest adding this information to the About page for the instance so that people who are vulnerable to harassment can view this information before deciding on an instance to join.

I believe that this change should be (relatively) easy to implement because Mastodon already shows that a user is a moderator by displaying a badge on the user's profile page. So this info is already present, it would just need to be incorporated into the About page.

[EDIT: A post with more details about the problem this solves is at https://www.codesections.com/blog/mastodon-mobs-and-mastodon-mobs/]


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
@nolanlawson

This comment has been minimized.

Copy link
Collaborator

nolanlawson commented Sep 1, 2018

I like this line of thinking. Since you point out that follower counts also matter, and since active users are arguably more important than registered users, maybe (active users * followers / moderators) would be a good number to show publicly? Or alternatively just average weekly active users / moderators.

@codesections

This comment has been minimized.

Copy link

codesections commented Sep 2, 2018

I would like either of the numbers you suggest—I agree that they are more precise than just the number of moderators.

I suggested the number of moderators in the spirit of minimalism. It seemed like the smallest possible change that would still mostly achieve the goal of giving potential new users insight into how much moderation support they can expect in an instance. But I'd definitely be open to a (slightly) larger change that gives more details.

@trwnh

This comment has been minimized.

Copy link
Contributor

trwnh commented Sep 2, 2018

I think the number of mods is maybe more useful than some other arbitrary number based on that number. "Home to x users who authored y statuses, moderated by z staff" at least sort of flows.

@lrmikestone

This comment has been minimized.

Copy link

lrmikestone commented Sep 2, 2018

I like both ideas. Do I have to decide? Why not do both. On the standard "About" page, where most users who have normal follower counts and don't really care too much about the details, update the text to show "Home to x users who authored y statuses, moderated by z staff". After that, make the "Administered by:" section more visible, maybe by including it in the same box as the above text. The it doesn't get lost in the rest of the page, and people can easily find the "Learn More" section of the About page. On the "More" page, include all the more specific stats, like what nolanlawson proposed. I think the number of users, active users, moderators, moderators per post, moderators per user, etc, would all be valuable information to include on theses pages and have visible to the public.

@Cassolotl

This comment has been minimized.

Copy link

Cassolotl commented Sep 2, 2018

"There are x active moderators on this instance, which is y active users per moderator." Maybe?

@Gargron Gargron added the suggestion label Oct 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment