A Minute from the Moderators

Community Care in Online Spaces: When Connection Isn’t Enough (Part 3)

By Quintessence (@quintessence) | Thursday, June 25, 2026

Welcome back to Moderator Minutes. This is the third post in our series on Community Care in Online Spaces.

A note before we begin, and as with the rest of this series: these posts run a little denser than our usual Moderator Minutes, and we don’t expect anyone to absorb all of it at once. We’ll keep the recap short, because each post is meant to stand on its own, but if you’d like the fuller picture: Part 1 looked at how shifting norms create friction, and asked you to sit with a question: is it working? Part 2 looked at what drives us toward confrontation in the first place, and at the idea of care webs: the networks of mutual support that let us do collective work without each of us carrying it alone.

Both of those posts asked you to lead with connection. To avoid assuming bad faith. To choose communication over correction, and to extend considered grace to people who are, like all of us, navigating norms that keep shifting under their feet.

You may have noticed that we kept setting something aside. We said, more than once, that choosing community care does not guarantee care in return. We said there are times when connection is not the answer, and that we would come back to them. And we mentioned, briefly, that when connection fails you have other tools available and that we would talk more about those later.

This is later. This post is about what to do when connection isn’t enough.

Connection First Is Not Connection Only

We want to be clear about something up front, because it would be easy to read this post as a reversal of the previous two. It isn’t.

Everything we said about leading with grace still holds. For the vast majority of the friction we see, the person on the other side is not acting in bad faith, and connection really is the better choice. None of that changes.

It’s worth saying why we keep recommending it, because the reason is not sentimentality. Connection-first is, in part, a guard against two equally costly mistakes: the naïveté that insists no one would ever act in bad faith, and the suspicion that treats everyone as an enemy until proven otherwise. When you enter an unfamiliar interaction, you usually don’t yet know which kind you’re in. You’re building that picture in real time, from the data the interaction gives you. Leading with connection means keeping the other person’s humanity in view while that picture forms, rather than deciding it in advance. And there’s another reason, and gently that is: how you treat someone you’ve judged to be acting badly is, in the end, as much a statement about you as about them. That matters especially because the judgment that feels most certain in the moment is exactly the kind we sometimes get wrong.

But “lead with connection” was never the same as “extend infinite grace to everyone, forever, regardless of how they respond.” Those are different claims, and the difference is the whole subject of this post. You can afford to lead with generosity precisely because you are not obligated to keep extending it into a void. Boundaries are not the opposite of community care. They are part of what makes it sustainable. They are how you keep the door open without leaving yourself standing in the doorway indefinitely, absorbing whatever comes through it.

So this is not the post where we tell you to stop being generous. It’s the post about what holds that generosity up.

Boundaries: The Part You Control

A useful place to start is a distinction that quietly resolves a lot of online conflict: the difference between what you will do and what you want or need someone else to do.

The first is a boundary. The second is a request.

“I’m not going to keep discussing this tonight” is a boundary. You control it completely. “You need to stop replying to me” is a request, and whether it’s honored is no longer in your hands. Both can be reasonable. But only one of them is something you can actually enforce, and a great deal of exhaustion comes from trying to defend a line that depends on someone else’s cooperation to hold.

Boundaries phrased as things you control are ones you can keep. Muting a thread you keep getting pulled back into. Saying once, clearly, that you’re stepping away, and then actually stepping away rather than staying to monitor how it lands. Deciding in advance what you’ll do if a particular kind of message arrives, so the decision is already made when it does. None of these require the other person to agree, which is exactly why they work.

Holding a boundary is harder than setting one, especially in public, and extra especially when someone is testing it. The pull to re-engage is not a personal failing; it’s a normal response to the discomfort of leaving something unresolved and the worry that silence will be read as concession. It helps to remember two things. The first: you can’t control how your boundary is interpreted. Trying to, by staying just long enough to correct the record, is usually how it collapses. The second: you can hold the boundary whether or not it is understood. You do not have to announce it twice, defend it, or win the argument about whether you were allowed to draw it.

This is, itself, a form of the community care we’ve been describing. In Part 1 we wrote that the practice of choosing connection over punishment is part of building the community we all want to live in. Setting a clear boundary is part of that same building. It models that limits are normal, that they can be stated without hostility, and that staying in community does not require dissolving yourself into it.

When the Other Person Isn’t Trying to Hear You

Most of what we’ve written about de-escalation, here and in earlier posts, is for situations where the other person wants to understand you. In those situations, it’s often true that if you communicate clearly, you’ll be heard as you both share the goal of understanding.

Sometimes it isn’t true, though. Sometimes you communicate clearly, you make a reasonable request, and the other person still doesn’t hear you. As we noted in Part 1, when that happens, that is not on you. And sometimes the person on the other side is not trying to reach an understanding at all. They are reaching for something else. Maybe they want to change your mind as much as you want to change theirs. Maybe they are starting from a different premise, and the two of you are not actually arguing about the same thing. Maybe they just want a reaction. Whatever the reason, the part you can act on is the same: they aren’t hearing you. Sorting out exactly why rarely changes what you do next.

De-escalation looks different in that situation. It is no longer about reaching the other person, because the other person is not reachable in the way de-escalation depends on. It becomes, instead, about not handing them fuel. You lower your own stakes rather than matching theirs. You decline the thread instead of feeding it. You resist the pull to perform for whoever might be watching. The strongest move available is often simply to stop adding to it, not because you’ve conceded, but because continuing only gives the dynamic more to run on.

Part of what makes these situations so sticky is the urge to make the other person admit the thing. As a slightly more precise example: let’s say you witness someone being ableist, to you or another. You are unlikely to convince them of it in the moment, for any number of reasons. They may tell you they are not being ableist: they are only being direct, or honest, or precise. Here it helps to notice that both things can be true at once. Someone can be direct (or precise, etc.) and ableist. Someone can be giving genuine advice and be ableist in how they give it. “I’m actually doing this other thing” rarely makes the first thing stop being true, and arguing the point usually just feeds the dynamic we just described. So it’s worth asking what you actually want. Maybe part of what you want is for other people to come away with better understanding, so that they have an opportunity to grow. A fresh post in a separate thread often serves that far better than the argument in front of you: the people who want to learn can choose to enter it, and it doesn’t drag in the person who has made clear that is now how they are engaging at this time.

This is where disengagement stops being avoidance and becomes a genuine tool. Walking away from an interaction that has nowhere good to go is not losing. It is refusing to spend your energy where it cannot accomplish anything.

The Tools You Already Have

It’s worth pausing on why a post about bad faith has spent so long on boundaries and self-regulation. The reason is a framing choice: a great deal of bad-faith and inauthentic behavior can be modeled as a boundary violation. Content you don’t want shown to you. A phishing attempt you don’t want to engage with. An effort to extract protected data (e.g. personal information, payment details) that you don’t want to disclose. Attempts to slip past the filters so you see content you opted out of. In person-to-person interactions, it is often true that sometimes the other person genuinely doesn’t understand your boundary, since you are two different people. And it is also true that sometimes others put in real effort to get around boundaries. By choosing to frame these as two sides of the same coin, boundary violations, we have a dual purpose model that serves both when people don’t understand and when they definitely do. And the tools for one are the tools for the other.

While not a software feature, disengagement is a tool at your disposal. It is not the only one, and for the harder situations it is not enough on its own. This is the part Part 1 seeded that we wanted to give real space to here.

Beyond simply stepping away, most platforms give you tools to enforce boundaries directly and Mastodon is no exception: you can mute or block an individual, or block an entire server. You can filter keywords in or out. And you can do this independent of the “faith” of the engagement you are in or witnessing. You can do it for any reason at all. Maybe you dislike the way you see someone engaging with others. Maybe there are some forms of content that aren’t harmful, but that you simply don’t want in your day. These tools are yours, and using them does not require you to build a case.

When an interaction has gone past the point where connection or boundaries can resolve it (someone is harassing you, evading your boundaries, escalating instead of de-escalating, etc.), you have a path that does not require you to either keep absorbing it or handle it alone: you can report it to your moderation team.

Bringing in a moderation team is not an escalation nor a failing. It is the opposite of what was flagged in Part 1, where people are fighting it out instead of reaching for other options. Reaching out for help is a de-escalatory move. It takes a conflict that is not resolving on its own, and diverts it to try another approach or neutral eyes.

You might hold back from reporting because you don’t want to add to a team that is already carrying a lot. That hesitation is its own kind of care, and it is worth setting down gently. A report is not a weight dropped on someone else. It is the web doing what it is built for, and a pattern no one names is harder to hold than one that is reported.

This is, in the most concrete sense, the care web from Part 2 doing what it’s for. You were never meant to carry the whole interaction by yourself. A moderation team is part of the infrastructure that holds it with you. When you report, you are not offloading a problem; you are using a structure that exists so that no single person has to be the entire response to harm directed at them.

And reporting is care directed outward, too. A report is information. It helps the people whose job is to keep a space safe see patterns they would otherwise miss, and to protect others who may be experiencing the same thing and saying nothing. It provides visibility when someone is testing more boundaries than only yours. In this way, choosing to report contributes to community care.

Practical Notes for Hachydermians

Everything so far applies on any instance or platform. These last notes are specific to Hachyderm, so reporting here never becomes a barrier.

Report when behavior crosses into harassment or boundary violations, on or off Hachyderm. For anything that has a lot of complexity or deeper back-and-forth, email us. That is also how we receive security reports. For one-to-one or point-in-time things, the Mastodon’s Report feature works very well. Both reach us, so use whichever suits the moment. Please don’t worry if you have all the details, we’ll ask follow up questions if we have them. What matters is that your report comes through one of these, where we can act on it. When another instance is involved, please feel free to reach out to us if you would like us to engage with their moderation team.

Also, and this is important: none of these are last resorts. You do not have to wait until something is unbearable to use them. They are part of how a healthy space takes care of the people in it.

What Holds It Up

Across these three posts, we’ve described a range of practices where some might feel contradictory. It asks you to lead with connection and extend grace, while encouraging you at the same time to set and maintain boundaries, disengage, and ask for help / report to your moderation team as needed.

The tension is easier to feel once you notice that the tools themselves can be turned to more than one purpose. The same block can enforce a boundary or deliver a punishment. The same report can protect a community or settle a score. This is the line Part 1 drew between connecting and punishing, and it runs straight through the tools. Before you act, the question worth asking is which one you are reaching for, because that is the part still in your hands.

That goal changes how you act, even when the visible outcome looks similar. Someone blocked to keep a boundary and someone blocked to be punished may both simply experience being blocked, and you cannot fully control which way it lands for them. How an action is received is its own matter, with its own weight, and worth a fuller conversation another time. What you can govern in the moment is the aim, and the aim shapes the conduct around it. Protecting your own space tends to look quiet: you do it and then stop. Trying to make someone pay tends to look loud: you reach for an audience, you escalate, you keep going. The boundary closes a door. The punishment tries to follow them through it.

This approach to community care is multifaceted, rather than contradictory. The generosity of the first two posts and the limits of this one are both expressions of one purpose: building and protecting the community you actually want to live in. You can keep choosing connection, again and again, because you are not defenseless when it isn’t returned. That community is shaped as much by where you hold a line as by where you extend a hand. Both are how it gets made.

Thus far, we have described moderation from the outside, as something to reach toward when connection runs out. In future posts we’ll discuss the work of moderation itself; not the reporting that is covered here, but what happens on the other side of it.

How you can help others

We know a lot of people are running low right now, so we’ll keep the prompt light this time: what is a content filter or mute you would recommend to someone new to the Fediverse? Answer wherever feels easy, in Zulip or out on the Fediverse with #CommunityCare. As a reminder: we’re not automating the Discord to Zulip migration, so please check in Discord for information for how to be added to Zulip.