Home | Terms of Service | Federation | Privacy Policy | Mobile / Desktop Apps | Getting Started

Remote content policy

The policies can be viewed on

Instances on this list may contact us asking for reconsideration. In some cases we may be willing and able to implement different handling of the problems in question. participates in MRF transparency. Users may verify the running configuration by viewing our NodeInfo data.

Overall, we try to avoid blocking whole instances, but we have the capability. Instead, we prefer to take less intrusive actions to solve problems. As such, this is our current policy:


Specific Instances

Instance Actions Taken


Why do you filter content from remote instances?

In order to provide a comfortable environment for our users, we filter out some content on the shared timelines. This is also known as "editorial control" and is a form of protected speech. In American jurisdictions, this form of "editorial control" is explicitly protected speech per 47 USC § 230(c).

Additionally as has been upheld by 47 USC § 230(c), the ability to publish otherwise legal content is protected speech, but only the publishing itself: as with all other forms of publishing, there is no right to an audience.

Why do you defederate instances?

In certain extreme cases, we defederate specific instances. This usually happens due to spam or some related abuse issue. Occasionally defederation occurs due to egregious incompatibility with our own policies. We used to provide reasons for each instance listed, but are no longer able to due to the list being automatically generated based on our NodeInfo data.