260819: Latte v. Reggie

Field	Value
Incident	260819
Chat(s)	CatShark TreeHouse (primary); other channels
Date(s)	19 to 20 August 2026
Severity	High
Status	Monitoring

What Happened

On the afternoon of 19 August 2026, during a casual conversation in the CatShark TreeHouse chat, a member made a passing remark that touched on ethnicity. Another member disagreed with it. The exchange got heated for a few messages and then died down on its own within about ten minutes, after a third member changed the subject.

About half an hour later the topic was brought up again in the chat, this time by staff. Several admins joined in over the following minutes. The conversation moved from the original remark to whether it had been appropriate, a rule change on the subject was announced in the chat, and the member who made the original remark said they no longer felt comfortable and stopped replying for a while.

The discussion continued afterwards in other channels and in private messages between some of the people involved.

Outcome

A disagreement that had already ended was reopened and became a longer, more public discussion than it needed to be. Nobody was happy with how it went, members included. The team reviewed the whole sequence the next day.

Actions Taken

Following the review, the team took these actions.

• Extended Rule 2 of the Network Rules with § 2.5 and § 2.6: discrimination based on ethnicity is now explicitly prohibited, not only discrimination based on race, and grouping or judging anybody by their ethnic background is banned outright, whichever group is being talked about. Rule 2 also now states that an admin may ask you to drop a topic. See the Network Rules.
• Extended Rule 4 of the Network Rules with § 4.4 and § 4.5: remain civil. Disagreement is not a license to tell somebody to shut up; explain yourself once or step away, and report it if it continues. See the Network Rules.
• Removed two members from the network, and temporarily banned a third for one week. Each decision was based on the member’s overall history with the network, not on this conversation alone. All three are listed in the ban register.
• Reviewed how staff handled the situation, and used that review to write the Moderation Strategy.

What We Learned

1. A topic that has died should stay dead. If it needs follow-up, that happens in private, not in the chat.
2. Moderate conduct, not opinions. Whether a remark was right or wrong is not a moderation question. How people treat each other is.
3. One voice at a time. When several staff respond to the same situation at once, the chat gets louder, not calmer. One person handles a live situation; everyone else stays out of the member chat.
4. Private matters stay private. Requests, warnings and anything about a specific member are handled in direct messages.
5. Rules are not made mid-incident. Changes to the rules go through the owners and are announced once they are decided, not during a heated moment.

What Changes

These lessons are now written down as the Moderation Strategy, and the rule change is recorded in the Network Rules under § 2 and § 4.

Statement

On 19 August a short disagreement between two members in the CatShark TreeHouse chat ended on its own. Staff then brought it back up, and what followed was not moderation. Several of us spoke at once, a member was argued with in public instead of being spoken to in private, a rule change was announced in the middle of it, and the person who had made the original remark said they no longer felt comfortable there. Members watched this happen. We don’t expect it left you with much confidence in the team, and we understand why.

We are not going to describe this as a misunderstanding or a bad day. The team handled it badly, and the people it affected were members of this community who had every right to expect better from the people running it.

Three members were banned after the review. None of those decisions rests on this one conversation alone. The review made the team look at each person’s conduct with the network as a whole, including earlier warnings. We are not naming them here; the ban register records each ban with its reason, as it does for every ban.

Some of what was said, in the chat and around it, was about ethnicity, and we want to be plain about where we stand. This is a multicultural team. None of the three owners is ethnically white. We say that not to claim a pass, but so nobody mistakes what follows for self-interest: this network does not tolerate talk that discriminates against any ethnic group, whichever one it is and whatever the speaker’s own background. We do not believe that any race or ethnic group is superior to any other, and we will not host the claim that one is. Judging a person by the group they were born into is the same act no matter which direction it points. That is now written into the rules (§ 2.5 and § 2.6), and it will be enforced the same way for everyone.

To the members who were in the chat that afternoon: we are sorry. You came to a place that is supposed to be relaxed and safe, and instead you watched the people in charge of it lose the thread. A request to handle the matter quietly was refused in the open, and a member was told to leave by someone who should have taken it to private messages. Those things were wrong whatever else was true about the situation, and they won’t happen again.

Here is what changes. The Network Rules have been rewritten so that every rule is a set of short, numbered clauses that staff cite when they act, and several clauses come directly out of this: ethnicity is explicitly covered under Rule 2, Rule 4 now says how to report a problem, including a problem with a member of staff, and asks everyone, members and staff alike, to remain civil when they disagree. Rule 17 guarantees that rules are never applied backwards and that a closed case stays closed.

The team has also written down, for the first time, how it moderates: the Moderation Strategy. The part that matters most for what happened here is simple. From now on, one admin handles a live situation. If they need help, they bring in supporting admins, who work through them and stay out of the member chat. Nobody else joins in, a topic that has died is not reopened in the chat, anything about a specific member is handled in private messages, and no rule is changed in the middle of an incident. Had that been the practice on 19 August, most of this record would not exist.