This is the multi-page printable view of this section. Click here to print.
Here you will find everything you need to know about what to do if you’ve been moderated, including:
Here you will find everything you need to know about what to do if you’ve been moderated, including:
We acknowledge that being moderated can be stressful. We do our best to intervene only when necessary and in the interest of preserving Hachyderm as a safe space. We acknowledge that we are human and that we can make errors. We ask for your patience and understanding that when we approach a situation, we are doing so as strangers moderating strangers.
For more information about what goes into how we interpret and enforce our rules, please take a look at our Moderator Covenant and Rule Explainer. Some of the language used below will come from the Moderator Covenant in particular.
Although there are a few actions we can take as moderators, the most common are:
Two additional, less commonly used, actions are:
The warning feature is a tool in the Mastodon admin tools that allows us to send a message directly to you.
When you receive a warning, that means that the moderation team has decided:
Essentially, warnings are the feature that allow us to respond to a report with a gentle nudge in the right direction. Warnings do not change your login, use, or ability to federate as a Hachyderm user.
It is important to understand that, unlike some other systems, a “warning” is not something that is tracked for later punishment. This means that you are not accruing “strikes”, or similar, with every warning you receive. That said, please do keep in mind that we choose our actions to prevent recurrence of the same actions that have caused the community harm. So while there is not a strike system, this is not leeway to continue to do what you were reported for without change.
When the moderation team sends a warning, we always send a message with what we need from you. This may be a reminder to leave interactions that are not going how you hope or intend, or it may be a reminder to disengage if you’ve been asked to leave a conversation for whatever reason.
These are both actions that prevent you from using your Hachyderm account normally.
In all except the most egregious situations, whether a moderator suspends or freezes an account is based on what we are seeing in the reported interaction. Specifically:
If your account was frozen, you should always file an appeal. If your account was suspended, the situation of the suspension will determine if an appeal is possible. (Skip to The Appeals Process)
We want to call out that there are times that we temporarily suspend an account even if the rule broken is not severe. This would only happen when there is an impact to the server or community that would warrant and benefit from an immediate, visible, action and forced cool-down period.
Being limited means that you are hidden on our instance. Your posts are all still visible to your followers and can still be discovered when directly searched for. Your posts will not otherwise show up in the Local feed. You will be able to federate with other instances normally.
Delete Post is what it sounds like - we can delete the reported posts and associated media (if that media is uploaded to Hachyderm).
We do not typically Limit accounts or Delete Posts. We have a couple of reasons for this:
This means that, in general, we will use one of the other actions and communicate what we’d need from you in an appeal process to reinstate normal functioning of your account.
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.
We do not moderate in public. This is a safety decision.
When someone is moderated on Hachyderm, we can confirm that a moderation action was taken and what type of action it was (warn, freeze, suspend, etc.). What we will not do is disclose the reasons behind that action if doing so could compromise the safety of another person. Moderation situations frequently involve more than one party, and the details of why someone was moderated can make it possible to identify, locate, or target someone else in the situation. For example, if a man harasses a woman and we publicly reference the specifics of that situation, the woman is placed at risk of further harassment, whether she was the one who reported it or not.
We will disclose the details of a moderation action to the moderated person themselves, through direct communication (email or appeal). We will share the details of a moderation action with third parties only when we have the informed consent of all parties involved, not only the person who was moderated.
It is also important to understand the notification limitations of the platform. Mastodon can only notify local Hachyderm users when a moderation action has been taken on their specific account. Users who filed a report do not receive in-platform notifications about the outcome, regardless of whether the report was about a local or remote user. Remote users are also not notified through the platform when an action is taken that affects them.
In those cases, we may reach out to the remote user directly if there is a public contact method available and if doing so does not put another party at risk. We may also contact their instance’s moderation team. Both of these are manual processes that happen outside the platform itself.
You may respond to any moderator action with an appeal. In all cases except for 1 ) severe rule violations or 2 ) creating a banned account type it is in your interest to file an appeal to start or continue a conversation about what you reported for.
The only two situations when filing an appeal will not be helpful. If the harm done to the community is repetitive (before it was caught) and the impact and risk to the community is high, there is no benefit to you filing an appeal. This includes, but is not limited to, being in favor of systems of oppression, posting illegal content, harassment, etc.
The other situation is if the account is a type that we ban on our server and it was correctly flagged (please file an appeal if not). Common types of banned accounts are those that don’t abide by our NSFW Policy and Monetary Policy.
For clarity: if your account was suspended (or frozen) due to being either 1 ) an unrecognized special account type or 2 ) not following the rules for your account type (bots, companies, etc.) then you should file an appeal.
If the reason that your account was flagged for a rules violation was incorrect, you should file an appeal. We again ask for patience and understanding as we work with you to correct our mistake in that case.
Some cases for something like this:
There are other cases where we use freeze and suspend as tools to help de-escalate or otherwise resolve a situation in progress, but the freeze or suspension does not need to be permanent. Example situations for this:
Where possible and applicable, we try to include whatever needs to happen to unfreeze or unsuspend an account. Commonly, with frozen accounts, we may need you to agree to delete posts or similar to re-instate your account.
Whenever you file an appeal you should always email us due to limitations in the appeals process. (See next section.)
Whenever you want to file an appeal you should both file the appeal and email us at admin@hachyderm.io.
The reason for this is that the Appeal feature in the admin interface does not allow us to continue a conversation with you. When we receive an appeal we can only Approve or Reject. We cannot send an outbound communication when we do either action and cannot send a communication to help us decide what action to take.
In order for us to know if your account was flagged incorrectly and why, or for us to be able to reinstate your account if it was frozen or suspended pending action we requested of you, we will need you to email us at admin@hachyderm.io. Please also include a summary of the situation in the appeal itself, as that will remain tied with the appeal in admin UI, which will set the initial context and set the expectation that there are emails corresponding to the appeal.
All moderation decisions are made with the understanding that something has happened that required intervention. Resolving that intervention through an appeal is, in most cases, straightforward.
If we made an error, your appeal can be as simple as letting us know. Point us to the interaction we may have misread, or share any context we may not have had at the time of the decision. We review that information and correct course where appropriate.
If the moderation action was in response to something that did happen, the path back is also straightforward. For Hachyderm users, this commonly follows our freeze pattern: we provide a short article or similar resource (typically under five minutes of reading) related to the situation, even if it does not describe the exact circumstances. The appeal in that case is as simple as reading what we sent, confirming that you have read and understood it, and letting us know. We do not ask for lengthy actions as part of the path back to community.
If you are a remote user and are unsure whether you have been moderated or what steps to take, emailing us to ask is enough to start the conversation. We will let you know what, if anything, is needed.
The appeals process is designed to be accessible and low-friction. You do not need to build a case or recruit support. You just need to reach out.
We encourage anyone who wishes to appeal a moderation decision to do so as soon as they are able.
Moderation decisions are made based on the full context available at the time, including posts, threads, and interactions across accounts. Over time, that context can change. Posts may be deleted. Accounts may migrate or be removed. Threads may become incomplete as other participants change or remove their own contributions. The further from the original decision an appeal is filed, the less complete the available record may be.
We may not be able to meaningfully revisit a decision when the evidence that informed it is no longer available for review. This is not a penalty for delay. It is a practical reality: we cannot responsibly re-evaluate a situation on an incomplete evidence base, and we will not guess at context we can no longer verify.
If you have been moderated and are considering an appeal, the best thing you can do is reach out to us at admin@hachyderm.io while the full context of the situation is still available.
If you interact with Hachyderm from another Fediverse instance, the Mastodon appeal interface is not available to you. To appeal a moderation action that affects your ability to federate with us, email us at admin@hachyderm.io. As noted above, the platform cannot notify remote users when an action is taken, so if you believe you have been affected and have not heard from us, please reach out.
You are also welcome to ask your instance’s moderation team to contact us on your behalf. We routinely work with other instance moderators and are happy to have them act as an intermediary.
When you (or your moderators) email us, please include:
We review remote appeals with the same care and standards that we apply to appeals from our own users.
If someone you follow or care about has been moderated, your instinct to help is understandable. We ask that you pause before acting on that instinct, because not all help is helpful and some interventions can make a situation worse for the person you are trying to support.
Before you reach out to us or take action on someone else’s behalf, please consider the following:
Does the person actually want intervention?
Sometimes people talk about being moderated because they need to vent or process. Venting is not always a call to action. It is sometimes a call for people to hold space. If someone has been moderated, whether they have chosen to appeal or not, they may neither need nor want you to do anything other than be present. So just be present.
Similarly, if the person has explicitly said they do not want to engage with the moderation team, respect that decision. Reaching out to us on their behalf, against their stated wishes, is not advocacy. It is overriding their autonomy in a situation where they have already made a choice about how they want to handle it.
If the person does want help, what kind of help do they want?
The most helpful thing you can do is ask them what kind of help they actually want or need. Do they need help drafting communication? Do they want someone to review their appeal before they send it? Would it help for you to read through the correspondence so far to offer more holistic feedback? Do they need something else entirely? The most useful thing you can do is ask, and then do the thing they asked for.
Is the person someone who might need proactive support?
If the person is a member of a marginalized community, new to the industry, or otherwise in a situation where they may not feel empowered to advocate for themselves, your proactive support may genuinely be welcome. Use your judgment, but lead with a question rather than an assumption about what they need.
What we will and will not do when you contact us on someone else’s behalf
We will confirm whether or not a moderation action was taken and what type of action it was. We will not share the details of the situation with you unless we have the consent of all parties involved, not only the person who was moderated. This is the same standard we would apply to protect you if you were the other party in a moderation situation.
If you believe we have made an error, the most effective thing you can do is help the moderated person file their own appeal and email us at admin@hachyderm.io. If the moderated person is on another instance, their moderator or moderation team is also welcome to reach out to us on their behalf. Moderator-to-moderator communication is a normal and expected part of how the Fediverse works. We take every appeal seriously.
Do you want to understand the full situation?
The moderated person has the most complete picture of their own situation. They have access to any correspondence they have sent to us or received from us, and they can share that with you at their discretion. If the confirmation we are able to provide (whether an action was taken and what type) is not sufficient for you, the person you care about is the best source of additional context.
A note on public advocacy
Public pressure campaigns do not change the outcome of a moderation decision. The only way to change a moderation outcome is for the moderated person to file an appeal. Others cannot change the decision on their behalf, regardless of the method.
What public campaigns do affect is the safety of other people involved in the situation. Moderation situations frequently involve more than one person, and public attention can expose people who did not ask for that exposure, including the moderated person themselves. If you want to help, help the person that wishes to appeal to email us - and only to the degree they wish.
Blocklists are one way that a Mastodon instance can handle unwanted content on the instance level. When a Mastodon domain is on the Blocklist, this means that the server administrators have limited or completely suspended activity with the server at that domain. The specific actions are:
Mastodon has these features in their documentation.
Users can also take individual action to prevent themselves from seeing unwanted content by blocking or limiting other accounts on the user level. This is recommended for cases where the content is perhaps unwanted by an individual user, but that content does not violate the home server’s ethos.
Mastodon has additional documentation about actions that individual users can take on their Dealing With Unwanted Content documentation page.
At Hachyderm, we do our best to balance what actions should be taken at the instance level and what should be handled at the user level - both when it comes to our own users and when we receive reports of users on other instances or the instances themselves. The vast majority of the moderator action we have taken on servers on our Blocklist is to either silence/limit or suspend/block. The domains that are included on this list are:
Although suspension is the most well-known and discussed moderation action, domains may be limited as well. For example, we might limit a server that has several bots that are taking over the Federated timeline but not suspend so users can continue to follow individual accounts.
There are a few top level concerns that go into determining adding servers to the Blocklist:
It is our opinion that it is in our users’ best interest to federate with as much of the Fediverse as possible so that we can all share our joys, sorrows, growth, learning, etc. with each other.
Our goal with the maintenance of the Blocklist is to ensure that all of our users are safe on Hachyderm. That means when we move forward with taking moderation action on a server, that we will take the best course of action to ensure that safety. We will prioritize the safety of our marginalized users over the broader experience of a completely open and unmoderated (at the server level) Fediverse.
When we take moderation action against a server, we consider:
Some servers have reasons attached to their moderation action and others do not. In addition, we may or may not announce when we limit/silence or block/suspend individual instances. Why is this?
When we choose what level of notification to send, and how transparent to be, with moderation actions we consider:
For example, if we were to take moderation action against any of the large, popular Mastodon instances we would err on the side of transparency as this would be a significant and user impacting event.
Whenever we take action on a server that has malicious activity, and this can be in the form of attacks on our server or in the form of social attacks like stalking and harassment, we err on the side of safety. This means what level of information we provide and how loudly (notifications, etc.) we provide it will be based on what is safest for all of our users.
The vast, vast majority of instances fall between these two extremes and thus the resulting decisions do not fall perfectly in the “fully transparent” or “completely silent” buckets. This means:
We are all human and are prone to mistakes. If there is a domain that is moderated on our Blocklist that seems to be in error, please open a GitHub Issue in our Community repo to request that we take another look at the domain. Please include as much relevant context as you can to help us make our decision. Note that depending on the circumstances, and as outlined above, we may not be able to be fully transparent with our decision - but we commit to erring on the side of transparency with these reports as often as possible. For more information about how to file a report in our community repo, please take a look at our Reporting Documentation.
If there is a server that is not currently moderated, i.e. either limited/silenced or banned/suspended, then please file a report via the Hachyderm (Mastodon) UI or GitHub Issue in our Community repo for us to take a look at that domain or domains. As before, please include as much context as possible. If there is a concern around the domain(s) you would like to report that would be risky to report in our GitHub Issue tracker, please email us at admin@hachyderm.io. For more information about filing reports and how to choose between the Mastodon UI and the GitHub Issue tracker, please look at our Reporting Documentation.
There are far, far more Hachydermians than moderators. We do not follow tags, posts, etc. to make changes to our Blocklist - we only use the sources outlined above.
This is the set of principles that Hachyderm moderators agree to inform their decisions and judgment calls when creating and maintaining Hachyderm as a safe space and enforcing server rules. This is because first and foremost:
Hachyderm moderators acknowledge the importance of server rules / Codes of Conduct that are complete and clear. Hachyderm moderators also acknowledge that the entirety of human behavior cannot be captured by an itemized list, no matter how many subsections it has, and therefore use the following principles to ensure that we are always able to take action even in situations where a reported infraction “falls between the cracks”.
There are three ways to correspond with the Hachyderm Moderation team:
In general, the Mastodon UI (i.e. the “report” feature on Hachyderm.io) is used for reporting specific posts, users, and domains. The GitHub Community Issue tracker is for other types of reports as well as raising other questions and conversations with the Hachyderm Moderation Team. Optionally, users may also send us information via email if neither Mastodon reports nor the GitHub Community Issues are appropriate for the conversation.
Our server rules still apply when filing a report or otherwise communicating with the moderation and infrastructure teams.
The moderation team should, in general, only be contacted via email to:
In short: please prioritize using the Mastodon UI and/or GitHub issues as often as possible. That said, if you would need to reach out to the admin team for any of the above situations or another grey area, please use admin@hachyderm.io.
The Mastodon UI, i.e. what you see when you’re using Hachyderm.io or your home Mastodon instance of choice, should generally be used for reporting issues that can be reported via reporting individual posts. This typically is used for:
For information about the report feature, and what we see when you send us a report, please look at our Report Feature doc page.
What to know about the Additional Comments:
The most important limitation you should know 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:
Please note: if we receive an empty report and cannot see a clear cause, we will close the report without moderator action.
When we receive a report, we cannot follow up with the reporting user to ask for additional information using the admin tools.
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. So please do make sure to include posts as needed, comments and context, and email us at admin@hachyderm.io as needed.
The Community’s GitHub Issues, a.k.a. Issue Tracker, is for communicating with the moderation and infrastructure teams, as needed. To create an issue:
The Community Issues can still be used to report domains, as you would do in the UI. It can also be used to request emoji, report a service outage (you can also use omg.hachyderm.io for this), request updates / changes to the docs, and so on. There are issue templates for the most common issues that prompt users for the information we need to respond to requests efficiently. Depending on the nature of the request / discussion, a member of the infrasture team and/or the moderation team will respond.
In accordance with the Moderator Covenant:
Hachyderm moderators acknowledge the importance of server rules / Codes of Conduct that are complete and clear. Hachyderm moderators also acknowledge that the entirety of human behavior cannot be captured by an itemized list, no matter how many subsections it has, and therefore use [a set of] principles to ensure that we are always able to take action even in situations where a reported infraction “falls between the cracks”.
This means that we will always do our best to take action on reports, but we also acknowledge that there are situations where the rules may not be clear or may not apply. In these cases, we will do our best to take action that is in the spirit of the rules and the spirit of the Hachyderm community. In addtion, we will work to expand and clarify the rules as the community grows and the need change.
If you would like to request an exception to the rules, please email us at admin@hachyderm.io with the following information:
There are two routes for changing rules: