Welcome
Hey everyone, how's it going?
This page is the handbook for the people who moderate bolha.us. It's here to help us make decisions with more confidence and in a consistent way, so that the reported person gets the same treatment no matter who picked up the report.
It doesn't replace common sense, or talking it over in the group. When in doubt, ask.
It's a living document: the content lives in an open repository and contributions are welcome. See how to contribute.
The 30-second version
- Open the report and click Assign to me, so nobody does the same work twice.
- Read the context: the post, the whole conversation and the account's history.
- Find the rule that was broken. No rule broken, no penalty.
- Use the smallest action that solves it: a warning, then limit, then suspend.
- Serious and obvious? Act right away. Not sure? Comment on the report and wait for a second opinion.
- Write in the comment field what you did and why.
Shortcuts
| What | Where |
|---|---|
| Open reports | bolha.us/admin/reports |
| Appeals | bolha.us/admin/disputes/appeals |
| Pending sign-ups (every service) | aprova.bolha.io |
| How aprova decides | aprova.bolha.io/how-it-works |
| Federated instances | bolha.us/admin/instances |
| Limited or blocked instances | bolha.us/admin/instances?limited=1 |
| The rules, explained | regras.bolha.us |
| Code of conduct | conduta.bolha.us |
| About (official source) | bolha.us/about |
| Bolhaverse code of conduct | bolha.io/conduta |
| Service status | status.bolha.us |
Who's who
Founder
bolha.us was founded by Guto Carvalho (@gutocarvalho).
The bolhaverse is an initiative created by and inspired by BolhaTech, a project founded earlier by Guto Carvalho and Rafael Gomes.
Sages (the council)
- Ulysses Almeida (@ulyssesalmeida)
- Roberto Murta (@robertomurta)
- Thiago Jedi (@jedi)
- Rui Ogawa (@rogawa)
The Sages are the bolha's council and take part in the harder decisions, so that Guto doesn't decide the project's direction alone. For moderation, the Sages are the last word: cases the team can't settle by majority, blocking large instances, approving bots and anything with legal risk go up to the Sages.
Wizards (engineers)
They are the only people with access to the servers, services and providers of the bolha.
- Guto Carvalho (@gutocarvalho)
- Ulysses Almeida (@ulyssesalmeida)
- Roberto Murta (@robertomurta)
Guto runs things day to day. Ulysses and Murta are the backup for any problem. Call a Wizard when a case needs something the moderation panel can't do: preserving data for the courts, a mass spam attack, a technical problem with the instance.
Protectors (moderation)
The Protectors are the moderation team: the people with moderator permissions on Mastodon.
- @blau_araujo
- @bug_elseif
- @capitaobviodev
- @dellagustin
- @droposhado
- @gomex
- @hugo
- @joaquim_satolep
- @josir
- @lupatini
- @mayhm
- @OG
- @omorrigan
- @polvoada
- @requena
- @riverfount
- @rodrigofaustino
- @Roneyb
- @sam_bughunter
- @silviavont
- @somatorio
- @v_raton
- @vitordelucca
Joined the team and you're not on the list? Open a merge request or let the group know.
What can a Protector do?
In the Mastodon admin panel, moderators can:
- Approve sign-ups from new people, through aprova.bolha.io (see how);
- Review reports (see how);
- Review appeals from people who were penalized (see how);
- Limit (formerly "silence") accounts (see the actions);
- Suspend accounts (see the actions).
Changing the rules or the instance settings, and approving bots, is up to the Wizards and the Sages.
bolha.us rules
These are the rules you'll cite when you act. Each one is explained, with examples, at regras.bolha.us. The official source is always the bolha.us about page; if they change there, update them here too.
- Treat everyone with respect, kindness and courtesy.
- Do not commit or incite crimes under Brazilian and Canadian law.
- No praise of fascism, Nazism, white supremacy or totalitarian governments.
- No racism, xenophobia, colonialism, extremist nationalism or religious extremism.
- No LGBTphobia, sexism, misogyny or ableism. This is a safe space for LGBTQIA+ and neurodivergent people.
- No hate speech, threats, violence, harassment, stalking or exposing personal data (doxing).
- No disinformation, including disinformation about the electoral process and democratic institutions.
- No spam, flooding or commercial advertising on the timeline.
- No pornography. Nudity only of your own body, always marked as sensitive media, with a content warning (CW) and the #NSFW tag.
- Content that isn't safe for work always gets sensitive media, a CW and #NSFW.
- Do not share copyrighted material, whether software, music, photos, videos, documents and especially BOOKS.
- AI-generated images get the #aiart tag and the tool's tag (e.g. #midjourney), with the prompt in the description (ALT).
- Parody and fan accounts must say so in their profile. Bots only with the team's prior approval, and marked as bots.
- You must be 18 or older to have an account on bolha.us or any bolha service.
Code of conduct and other foundations
Besides the rules, weigh reports against:
- The code of conduct, which spells out what we expect from everyone: conduta.bolha.us (the one for the whole bolhaverse is at bolha.io/conduta).
- Brazilian law, especially the Marco Civil da Internet (Brazil's Internet Bill of Rights, Law 12,965/2014), and Canadian law, since the servers are in Canada.
- The terms of service and privacy policy, also on the about page.
- The Mastodon Server Covenant, which the bolha follows in full: active moderation against racism, sexism, homophobia and transphobia.
We are a moderated instance: feminist, antifascist, anti-Nazi, antiracist, anticolonialist, pro-science and pro-LGBTQIA+. When a rule isn't explicit, these values help decide.
Mastodon's tools
Actions on accounts, from lightest to heaviest:
| Action | What happens | When to use it |
|---|---|---|
| No action (resolve) | Closes the report without touching the account. | Unfounded report, or already resolved. |
| Warning | The person gets a notice with the reason and can appeal. It stays on the account's record. | A first, minor violation. |
| Mark as sensitive | The account's media are shown behind a sensitive-content warning. | People who forget CW/sensitive media (rules 9 and 10). |
| Delete posts | Removes the reported posts and notifies the person. | The post breaks a rule, but the account itself isn't a problem. |
| Limit (formerly "silence") | Posts only show to people who already follow the account; for everyone else they disappear from public timelines and search. | Flooding, spam, a provocative or aggressive post, minor repeat offenses. |
| Freeze | The person can't log in, but the profile stays up. | An account that may have been compromised, or is on hold for review. |
| Suspend | The account goes offline. For bolha accounts, the data is kept for 30 days and then deleted; within that window it can be reversed. | Serious violations, hate, accounts created to cause harm, professional spam. |
Tips:
- For accounts on other instances, limiting and suspending only apply here on the bolha. Only the moderators of the home instance can remove the account for good.
- Always fill in the reason and select the rule that was broken. The text goes to the person and shows up in any appeal.
- Leave "notify the user" on, except for obvious spam. People have the right to know why and to appeal.
How to review a report
- Assign the report to yourself (the "Assign to me" button) before you start.
- Read the context. Open the post, the whole conversation and the profile. A single post can be misleading: it may be irony, a quote or a reply to an attack.
- Check the account's history. The panel shows earlier warnings and reports. Repeat offenses count.
- Check who reported it and from where. Reports from other instances are valid too, but watch out for mass reporting used as a form of harassment.
- Identify the rule that was broken. If you can't point to a rule or a passage of the code of conduct, it's probably not a case for a penalty.
- Choose a proportionate action (see below).
- Write it down. In the report's comment, say what you did and why. That helps whoever picks up the appeal, and whoever picks up the next report about the same account.
Reporters are never identified to the reported account. Keep it that way: never say who reported.
How to decide
The general recommendation is to limit first in cases of flooding, spam, or a provocative or aggressive post. When we limit someone, only people who follow that profile directly keep seeing its posts, and the public timeline is clear of that content.
For a serious violation of the rules, the recommendation is to suspend.
A rule of thumb:
| Severity | Examples | Suggested action |
|---|---|---|
| Minor | Forgot a CW or #NSFW; AI image without the tag; a discussion that got heated; one-off advertising. | Warning, or mark as sensitive. |
| Moderate | Flooding; repeated commercial advertising; persistent rudeness; disinformation shared in good faith; a repeat of a minor case. | Delete the posts and limit. |
| Serious | Hate speech; racism; LGBTphobia; misogyny; ableism; harassment; threats; praise of fascism or Nazism; deliberate election disinformation; spam account. | Suspend. |
| Critical | Child sexual abuse; a real and imminent threat; terrorism; doxing. | Suspend right away and follow the critical cases steps. |
Principles:
- Proportionality. Use the smallest action that solves the problem.
- Consistency. Similar cases get similar actions. When in doubt, look for similar past reports.
- Our own members deserve a conversation. With people from the bolha, a well-written warning usually works better than a suspension.
- Outside accounts get less patience. If a remote account only brings trouble, limit or suspend it here without ceremony.
- Don't moderate your own cause. If you're part of the discussion, or a friend or rival of someone involved, hand the report to someone else.
Critical cases
For child sexual abuse, a real and imminent threat to life, terrorism or exposure of personal data:
- Suspend the account immediately. Don't wait for a second opinion.
- Do not download, copy or forward the media, not even to show the group. Describe it in words.
- Tell a Wizard (Guto, Ulysses or Murta) right then. They preserve the records the courts will need before they are deleted.
- Child sexual abuse is also reported to the authorities: in Brazil, through SaferNet; in Canada, through Cybertip.ca. The Wizards take care of this.
- If it's an account on another instance, besides suspending it here, let that instance's moderators know.
Court orders, legal notices and requests from authorities are not answered by the moderation team. Forward them to juridico@bolha.us and tell a Wizard.
I'm not sure, now what?
Leave a comment on the report with your suggested action and let the group know. If another moderator agrees, it can be applied. Majority wins.
If nobody responds within 24 hours, ping the group again. If the team can't reach an agreement, the case goes up to the Sages.
What if the person appeals?
Appeals arrive at bolha.us/admin/disputes/appeals.
Leave a comment on the appeal with your suggested action. If another moderator agrees, it can be applied. Majority wins.
Whenever possible, the appeal should be reviewed by someone other than the person who applied the penalty. Reviewing your own decision is hard for anyone.
Accepting an appeal isn't a defeat: mistakes happen, and fixing them quickly is what builds trust in the moderation.
Blocking instances
We should only block an entire instance for very clear reasons. Blocking an instance cuts off everyone there, including people who did nothing.
When to suspend (block) the instance:
- The instance encourages content that breaks our rules;
- The instance encourages content that breaks our code of conduct;
- The instance encourages content that breaks our terms of use;
- The instance encourages content that violates Brazilian or Canadian law.
When to limit the instance:
- The instance refuses to moderate its users when told about problems;
- The instance has a lot of spam or problem accounts, but also legitimate people.
Mastodon has these options under federated instances, on each instance's page:
| Option | Effect |
|---|---|
| Limit | The instance's posts disappear from public timelines; only people who follow accounts there see them. |
| Suspend | Cuts federation: nobody here sees anything from there, and existing connections are lost. |
| Reject media files | Doesn't download images and videos from the instance. Good against image spam. |
| Reject reports | Ignores reports coming from there. Useful against mass reporting. |
Before blocking:
- Discuss it in the group. Blocking an instance is never one person's decision. Large instances go up to the Sages.
- Gather examples (links) of the problem and put them in the block's private comment.
- Write a short public comment, because it shows up in the list of moderated servers on the about page.
- Prefer limiting when you're not sure. You can always tighten it later.
Approving sign-ups
Sign-ups across the bolha are approved in aprova.bolha.io, one panel for the requests of every service: bolha.us, jornalismo.social, bolha.forum, bolha.dev, bolha.tube, bolha.photos, bolha.review and bolha.network. Sign in with your bolha.us account.
Protectors, Sages, Wizards and the Founder review. Escalated cases go to the Sages and the Founder. The @aprova bot sends a DM with the pending requests at 9:00, 14:00 and 20:00 (you can turn it off in the panel). The rules the panel applies on its own are always current on How it works.
How to review
Open the request, read the reason, the name, the e-mail and the discussion, and pick one:
- I would approve: a vote to approve.
- I would reject: a vote to reject. A justification is required and stays within the team.
- Ask the applicant: e-mails your question (see below).
- Comment: talks to the team only, not a vote.
Each person has one vote per round, and can change it while the request is undecided.
When the panel decides on its own
The quorum is 2 matching votes, a majority of a panel of three.
| Votes in the round | What happens |
|---|---|
| 2 × 0 to approve | Approved at once, with the account of whoever cast the second vote. Only if no check failed (see below). |
| 2 × 0 to reject | Rejected at once. The person gets the standard rejection message. |
| 1 × 1, or any disagreement | Nobody decides alone: the request goes up to the Sages and the Founder, and from then on only their votes count (again 2 matching). Anyone can still comment. |
| A single vote | Waits for the second. One "I would reject" already stops the automatic approval. |
Note that there is no 2 × 1: a disagreement goes up as soon as it shows. If two approved first, the request is already approved and there is no third vote. If one approved and another rejected, it is already escalated. So if you have a real doubt, vote I would reject with the justification: that stops the approval and takes the case to those who decide.
Checks. The panel looks for signs of automated (bot) sign-ups and disposable e-mail. If one fails, two "I would approve" don't approve on their own: someone has to decide by hand, with a note saying why.
Manual decision. "Approve now" and "Reject" stay available to whoever may decide. Use them for the cases agreed here (e-mail not delivered, obvious spam), not to skip the quorum. Approving over a reject vote or a failed check requires an internal note.
The e-mails the person gets
1. Welcome, right after the request. Every account request, on any service in aprova, gets an e-mail right away (in Portuguese and English) saying the team is reviewing it and asking the person to tell us who they are, what they do and what they plan to post. We recommend answering it: it speeds up the approval. The reply goes straight to the request in aprova.bolha.io, where the team reads it and decides. The welcome is not a vote, and not answering it is no reason to reject.
2. Questions from the team. When someone uses "Ask the applicant", the question goes out by e-mail and the answer lands on the request by itself too (see the deadline below).
3. Approval. An e-mail with the sign-in link, the rules, the code of conduct and the bolha's other services. Some apps also send their own.
4. Rejection. Always the same standard message, never with the reason. The justification you wrote stays with the team. An example of what the person gets:
Subject: Seu pedido de conta em bolha.us / Your account request on bolha.us
Olá,
Obrigado pelo interesse em bolha.us. Analisamos seu pedido de conta (someone) e, no momento, não poderemos atendê-lo.
Equipe bolha.us
Hello,
Thank you for your interest in bolha.us. We reviewed your account request (someone) and, at the moment, we can't accept it.
The bolha.us team
Asking for more information: 24-hour deadline
When something is missing to decide (empty reason, looks like a company, unclear age), use Ask the applicant. The e-mail goes out on behalf of the bolha and the request shows Waiting for answer.
- The reply lands on the request by itself and starts a new round: earlier votes stop counting. Review again.
- With no answer in 24 hours, aprova rejects the request on its own, on any service, and the person gets the standard rejection e-mail. The request keeps the reason "no answer to the question within 24 hours". Someone who really wants in can sign up again.
- If the request is flagged E-mail not delivered, the address doesn't exist: a strong sign of a fake sign-up, reject without waiting.
Keep questions short and kind, one thing at a time. The person doesn't know the bolha yet.
What to look at
We should not approve:
- Company accounts;
- Accounts for selling products;
- Accounts for sites that will only post news, without interacting;
- Bots that haven't been approved by the Protectors and cleared by the Sages;
- People under 18.
We value:
- Real accounts;
- Real conversations;
- Interaction between human beings;
- Diversity of opinions and cultures;
- Sharing knowledge.
Signs of a suspicious sign-up: an empty or generic reason, a random username, a disposable e-mail address, an e-mail that wasn't delivered and several similar requests in a row. When in doubt, ask the applicant or vote "I would reject" with the justification, and bring it up in the group if needed.
What about bots?
- The bot has to be useful to the community and approved before it joins.
- It must be marked as a bot in its profile, like @descreve.
- Whenever possible, it should serve people in private.
- It should avoid flooding.
Talking to people
- Be polite and direct. Say what happened, which rule was broken and what the person can do.
- Don't argue in public. Moderation happens through the panel and private messages, not on the timeline.
- Don't expose who reported, or details of other reports.
- Speak for the team, not for yourself: "the bolha moderation team decided…".
Sample warning text:
Hi! Your post about X was reported and, after reviewing it, the moderation team found that it breaks bolha.us rule N ("…"). Because of that, the post was removed. If you disagree, you can appeal through the notification itself. Thanks for helping keep the bolha a nice place!
Privacy and confidentiality
When you moderate, you see data that isn't public: e-mail addresses, IPs, reports and reported private conversations.
- Use that data only for moderation.
- Don't take screenshots of reports, e-mails or IPs outside the moderation channels.
- What's discussed in the moderation channels stays in the moderation channels.
Taking care of moderators
Moderating is tiring and sometimes it hurts. A few agreements:
- You don't have to take every report. If a topic gets to you, pass it on.
- Take breaks. Nobody needs to be on call.
- Saw something heavy? Talk about it in the group. Nobody has to carry that alone.
- Need to step away for a while? No problem, just let us know.
Moderation channels
All Protectors are invited by e-mail to a WhatsApp group, where we discuss moderation.
There's also a Protectors channel (called Guardians) on the bolhaverse's Mattermost, Zulip and XMPP. It isn't bridged to WhatsApp yet; we're looking into how to do that.
Official bolha contacts:
| Topic | Contact |
|---|---|
| General help | help@bolha.us or help.bolha.us |
| Reports and abuse | abuse@bolha.us |
| Legal matters and court orders | juridico@bolha.us |
| Privacy and LGPD (Brazil's data protection law) | privacidade@bolha.us |
How to contribute
This handbook is written by the team. Spotted something wrong, outdated or missing?
- Edit
moderacao.en.md(English) ormoderacao.md(Portuguese, the reference version) and open a merge request; or - Open an issue; or
- Send the suggestion to the group.
Changes to how we moderate (and not just to the wording) are agreed in the group first.
Run an instance and want to use this handbook? Go ahead: the repository is MIT. Fork it and adapt the names, rules and links.
References
- Moderation on Mastodon (official documentation)
- Mastodon Server Covenant
- IFTAS, an organization that supports fediverse moderators, with guides and resources
- Marco Civil da Internet (Law 12,965/2014, in Portuguese)
- LGPD, Brazil's General Data Protection Law (Law 13,709/2018, in Portuguese)
- The rules, explained, code of conduct and bolha.us about page