This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Mastodon Report Feature

How to use the Mastodon report feature.

    This section documents features and processes maintained by Mastodon. For issues related to these features and/or processes, please reach out to the Mastodon team directly on the Mastodon project’s GitHub.

    For issues with this doc page itself, please reach out to us on Hachyderm’s Community Issue tracker.

    Overvew

    About the Report Feature

    Mastodon’s report feature is a way for Mastodon users to send reports to a Mastodon instance’s admins or moderators. If you are reporting a user to your own instance’s moderators, then only they will see the report. If you are reporting a user on a remote server, then your home instance’s admins still see the report. In the case of a remote user, you can also choose whether or not to forward the report to that instance’s admins. The nuance here is capturing whether you are reporting a user to their own home instance for their admins to take action, to your own instance admins for them to take action, or both.

    On Hachyderm, we specifically request Hachydermians to use the report feature for the following scenarios:

    • Reporting individual posts but not the user overall
    • Reporting a user via their posts
    • Reporting a domain via the posts of a user on that domain

    When submitting a report, it is important to include all relevant information. This includes supporting information, even if it seems obvious, any relevant posts as needed, as well as comments supplied by you.

    Please note: if we receive an empty report and cannot see a clear cause, we will close the report without moderator action.

    For more information about this, please see our doc on Reporting Issues and Communicating with Moderators.

    How to create a report

    1. Click on the meatballs(⋯) menu below the post and select “report”
      Example post with the text This is a blob fox appreciation post and three blob fox emoji. The UI menu is expanded to show copy link to post, embed, mention the user, mute the user, block the user, or report the user. The following steps are for reporting the user.
    2. Select why you’re reporting.
      Dialog box with four options to select for reporting a user. The options are I don't like it, It's spam, It violates server rules, and It's something else. In the example, It violates server rules is selected.
    3. If you selected Server Rules for the reason, as we did in this example, then you’ll be asked to select which and can select more than one:
      Additonal dialog box to allow user to select which rules are violated. All the server rules, including Don't be a dick, No hacking, No violence, etc. are shown. You can select one or more server rules as being violated. Here only Don't be a dick is selected.
    4. Please select any and all additional posts to include in the report
      Dialog that allows you to select other user posts that may be related to the report. The posts shown are not all in one thread, but all of the user's recent posts. In this case, an additional two posts about a form announcement and a response window are shown. Only the Blob Fox Appreciation post is selected.
    5. Please include all relevant context to help us process the report:
      Additional Comments dialog box, with a limit of 1000 characters, to allow users to supply additional information with their report.
    6. You can optionally choose to unfollow, mute, or block the user before you click “Done”.
      You can optionally unfollow, mute, or block the user you are reporting before selecting Done. You do not need to do any of these actions for the report to be submitted.

    The Additional Comments step is very important. To help us process reports efficiently there should always be additional context in the Additional Comments field - the more the better. This should be done even if the report seems self-explanatory. In the case of reports of posts, users, and domains that are in languages other than English, we will need an English translation supplied.

    The most important limitation you should know at this stage is that the Additional Comments field has a character limit of 1000 characters (as of this writing). If you need to supply more context, or the translation takes more than 1000 characters, please:

    • File the report with what you can
    • Make sure to leave enough space to tell us there is a supplementary email
    • Email us at admin@hachyderm.io

    What a Filed Report Looks Like

    For an example, I had Björn’s user create a report against my Blob Fox Appreciation Post that I used for the screenshots above. When a member of the moderation team reviews the report, it looks like this:

    Zoomed out view of what the report looks like for a Mastodon admin. The text is too small to read, but the sections show the user stats at top, report reason in the middle, any comments provided by the user filing the report, and then a section for moderator actions. These are described in detail below.

    Since that is a very zoomed out view, let’s look at each of the sections. At the top is the same user information you’d see if you navigated to the top of a user’s profile page:

    This is the top of the same report. The user is user quintessence with 1.01K posts, 3.61K followers, and 115 following. The first line of her bio is visible, as is her header and avatar. The report date and time as well as the reporting user, Björn, are visible. The Category of the report is shown as violates server rules - Don't be a dick.

    This section also shows the moderator team why the report was filed, in this case the “Don’t Be A Dick” rule is selected.

    Underneath that is the comment that the user supplied when they filed the report as well as all the posts they selected to include with it. If the user is a Hachydermian, the user name is supplied as you can see here. If the user is off our server, only the source server is supplied.

    This section shows the additional information provided by the user. In this case, only the text This is what was in the additional comments field for the reporting user comment as well as the post that was included in the report.

    At the bottom is the section where moderators can leave comments and choose what action to take:

    Moderator actions are shown here as Mark As Resolved - no action, Delete posts, Limit user, Suspend User, and Custom. There is also an additional field for moderator comments.

    Moderators can choose to close the issue with only an explaining comment, or to take one of the shown actions and close the issue. For visibility, the moderation actions are:

    1. Mark as Resolved (No moderator action)
    2. Delete posts (Moderator resolves by deleting the offending post(s))
    3. Limit (Formerly known as “silence”. The user can still participate but they will not show in Local or Federated feeds.)
    4. Freeze (User can log into their account but cannot interact.)
    5. Warn (Moderators send a note through the interface to the reported user. Note this option is not visible on the screenshot.)
    6. Suspend (Also known as “ban”. If the user is a Hachydermian then their account is removed from our server. If they are on a different server that user is banned from interacting with our server.)

    Of the above actions, the only moderation actions that are visible are if a moderator deletes a post or suspends an account. When an issue is closed without action or when a user is warned, frozen, or limited, the action is not visible to the reporting user or other users. This means that we / your instance moderators may have taken action as the result of your report, but that action is not publicly visible.

    Please look at our Actions and Appeals doc for more information about how we use the moderation tools to moderate Hachyderm.

    Who can see moderation reports

    If you are reporting a user on the same instance as you are (local user):

    • The instance moderators can see your report

    If you are reporting a user not on the same instance as you are (remote user):

    • Your instance moderators can see your report
    • Remote instance moderators / the moderators for the reported user’s instance can only see the report if you forward the report.

    Regular users do not have access to moderation reports.

    Limitations of the Mastodon Admin Interface

    When we receive a report in the admin tools, there are two main drawbacks:

    • We cannot follow up with the reporting user to ask for additional information
    • We cannot follow up with the reported user, even if they file an appeal

    How this impacts you:

    • If you are reporting an issue and do not include enough information and/or a way for us to get in touch with you to clarify, we might not be able to take the appropriate action.
    • If you are appealing a moderation decision and do not include enough information for us to make a decision and a way to contact you, we might not have enough information to reverse the decision and no way to request more information from you.

    One Last Reminder

    If we receive an empty report and cannot see a clear cause, we will close the report without moderator action.