How to Report a User: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(A bunch of changes (mainly for brevity))
Line 1: Line 1:
While browsing or editing MusicBrainz, you might find that a user is acting in ways that go against our [[meb:code-of-conduct|general Code of Conduct]] or [[Code%20of%20Conduct|MusicBrainz-specific Code of Conduct]], or that seem to be otherwise negative for the community and/or the database.
While using MusicBrainz, you might find a user acting against our [[meb:code-of-conduct|general Code of Conduct]] or [[Code%20of%20Conduct|MusicBrainz-specific Code of Conduct]], or otherwise negatively affecting our community and/or database.


== Should I report? ==
== Should I report? ==
In general, the first reaction when you find an editor who seems to be doing something wrong is to try to help them understand the problem and improve their editing. Sometimes this can work very well, and it's expected that new editors will make mistakes. Please assume good faith when at all reasonable and try to help editors before you report them! This includes cases such as editors who consistently do things wrong in a way that is time-consuming to fix, at least until it's clear that communication is not helping.
In most cases, the first step is to try to help an editor understand the problem and improve their editing. We expect new editors to make some mistakes. Please assume good faith and try to help editors before you report them! This includes cases where editors consistently do things wrong in a way that is time-consuming to fix, at least until it's clear that communication is not helping.


That said, sometimes either an editor is clearly not acting in good faith (engaging in vandalism or spam, or creating additional accounts to vote on their own edits). In other cases, trying to talk things through with an editor just isn't helpful (because they ignore edit notes or they respond badly to them), or the editor is engaging in abusive behavior towards other editors (insults, indiscriminate no-voting, etc.). In this case, you should report the user to the site administrators so that they can review the case and act as needed.
However, sometimes an editor is not acting in good faith (engaging in vandalism or spam, or creating additional accounts to vote on their own edits). Sometimes talking things through with an editor isn't helpful (because they ignore or respond negatively to edit notes). And sometimes an editor is engaging in abusive behavior (insults, indiscriminate no-voting, etc.). In these cases, you should report the user to the site administrators so that they can review the case and act as needed.


== How to report ==
== How to report ==
Line 16: Line 16:




The first field of the report lets you choose the reason why you are reporting the user. This allows you to select the most common reasons or, if nothing else fits, the more general "Editor has violated some other part of our Code of Conduct". Choosing the right reason here helps us figure out the situation faster.


The first field of the report lets you choose the reason for your report. Select the most applicable reason or, if nothing fits, the more general "Editor has violated some other part of our Code of Conduct".
The second field is even more important, and it's a free text field where you should explain the situation in more detail. You don't have to write an essay here (unless a lot of context is needed!) but do make sure to both specify what the editor is doing wrong and provide some links to help the admins quickly understand where this is happening. For example, if the editor is leaving offensive edit notes, link to the appropriate edits. If the editor is ignoring edit notes and keeps doing the same wrong thing, link to an edit where they were told that they were doing it wrong and what they should do instead, then one or more recent edits where they have clearly ignored the suggestion. If there's a lot of edits that apply, you don't need to link every single one of them, but do link enough that the situation is easy to understand. Unless the situation is blindingly obvious (such a spammer that only makes edits about their illegal medicine store), not adding details to the message field will make acting up on it a lot harder and might mean that your report is not acted on or that an admin needs to contact you for more info.


The second field is the most important. It is a free text field where you should explain the situation in more detail. You can keep it short (unless a lot of context is needed), but make sure to specify what the editor is doing wrong ''and'' provide relevant links. For example, if the editor is leaving offensive edit notes, link to those edits. If the editor is ignoring edit notes, link to an edit where someone tried to help them improve, as well as one or more recent edits where they have ignored the suggestion. You don't need to link to every relevant edit, but link enough so the situation is easy to understand. Unless the situation is blindingly obvious (usually SEO spam), not adding details might mean that your report is not acted on, or that an admin will need to contact you to follow up.
The first checkbox indicates whether you want the admins to receive your email address with the report. This allows them to let you know about their decision, if any. If you uncheck this we will assume you do not generally want to be contacted, so if your message does not contain enough info to act on the report, the admin might decide to ignore it rather than ask for more details. That said, admins do have access to your email address, and if they deem it really important, they might still contact you about the report directly even if you have unchecked this box, but that should only happen in extreme circumstances.


The first checkbox indicates whether you want the admins to receive your email address with the report. This allows them to let you know about their decision, if any. If you uncheck this we will assume you do not want to be contacted - this means that a report with insufficient information may not be acted upon. In extreme circumstances, site admin may email you about a report even if you have unchecked this box.
The second checkbox just makes it so that you get a copy of the report when it's sent. This doesn't have any effect on the report itself, and it's just useful if you want to archive a copy for yourself (since you cannot otherwise browse your sent reports).

The second checkbox lets you request a copy of the sent report. This has no effect on the report, but is useful if you want to archive a copy. You cannot browse your sent reports in MusicBrainz.


== What happens next? ==
== What happens next? ==
Once the admins have received your report, they will try to look at it as soon as possible. Keep in mind this might take a few days. After that, they will take the action they consider necessary. In mild cases this might just mean leaving an edit note or sending an email with a warning. Any offending edit notes might also be censored or removed if needed. In more serious cases, or for repeat offenders, the admin might revoke the editor's privileges to leave edit notes or to edit MusicBrainz, mark them as a spammer, or delete their account outright. As long as you have said you want to share your email address, you will usually get an answer from the admin who dealt with your report, letting you know what their decision was. Sometimes, in mild cases, an admin might not take action immediately, but ask you to report the user again after a period of time if their behavior has not changed.
Once the admins have received your report, they will look at it as soon as possible. This may take a few days. Then, they will take any action they consider necessary. In very mild cases action may not be taken immediately, and you may be asked to report the user again if their behavior does not change. In other mild cases, admin may mean leave the reported editor an edit note or sending an email with a warning. Their offending edit notes might be censored or removed. In more serious cases, or for repeat offenders, the admin might revoke the editor's ability to edit or leave edit notes, mark them as a spammer, or delete their account outright. If you have elected to share your email address, you will usually get an email from the admin who dealt with the report, letting you know of their decision.


{{HowtoBox}}
{{HowtoBox}}

Revision as of 22:45, 15 May 2023

While using MusicBrainz, you might find a user acting against our general Code of Conduct or MusicBrainz-specific Code of Conduct, or otherwise negatively affecting our community and/or database.

Should I report?

In most cases, the first step is to try to help an editor understand the problem and improve their editing. We expect new editors to make some mistakes. Please assume good faith and try to help editors before you report them! This includes cases where editors consistently do things wrong in a way that is time-consuming to fix, at least until it's clear that communication is not helping.

However, sometimes an editor is not acting in good faith (engaging in vandalism or spam, or creating additional accounts to vote on their own edits). Sometimes talking things through with an editor isn't helpful (because they ignore or respond negatively to edit notes). And sometimes an editor is engaging in abusive behavior (insults, indiscriminate no-voting, etc.). In these cases, you should report the user to the site administrators so that they can review the case and act as needed.

How to report

To report a user, click the big link at the bottom of their profile page:

reportuser1.png

Clicking this link will present you with the following form:

reportuser2.png


The first field of the report lets you choose the reason for your report. Select the most applicable reason or, if nothing fits, the more general "Editor has violated some other part of our Code of Conduct".

The second field is the most important. It is a free text field where you should explain the situation in more detail. You can keep it short (unless a lot of context is needed), but make sure to specify what the editor is doing wrong and provide relevant links. For example, if the editor is leaving offensive edit notes, link to those edits. If the editor is ignoring edit notes, link to an edit where someone tried to help them improve, as well as one or more recent edits where they have ignored the suggestion. You don't need to link to every relevant edit, but link enough so the situation is easy to understand. Unless the situation is blindingly obvious (usually SEO spam), not adding details might mean that your report is not acted on, or that an admin will need to contact you to follow up.

The first checkbox indicates whether you want the admins to receive your email address with the report. This allows them to let you know about their decision, if any. If you uncheck this we will assume you do not want to be contacted - this means that a report with insufficient information may not be acted upon. In extreme circumstances, site admin may email you about a report even if you have unchecked this box.

The second checkbox lets you request a copy of the sent report. This has no effect on the report, but is useful if you want to archive a copy. You cannot browse your sent reports in MusicBrainz.

What happens next?

Once the admins have received your report, they will look at it as soon as possible. This may take a few days. Then, they will take any action they consider necessary. In very mild cases action may not be taken immediately, and you may be asked to report the user again if their behavior does not change. In other mild cases, admin may mean leave the reported editor an edit note or sending an email with a warning. Their offending edit notes might be censored or removed. In more serious cases, or for repeat offenders, the admin might revoke the editor's ability to edit or leave edit notes, mark them as a spammer, or delete their account outright. If you have elected to share your email address, you will usually get an email from the admin who dealt with the report, letting you know of their decision.

How-To Pages
Introductory Guides
Basic How-Tos
Specific How-Tos