Concerns Raised Over Benji Raspberry’s Handling of a Community Dispute

Benji Raspberry, as an administrator of the Telegram community, had moderation control over the group and used that authority to mute Danny for one week. The concern raised by the incident is how that moderation authority was used during a public and increasingly hostile exchange.

According to screenshots reviewed for this article, Benji used the /mute @dannydeaf 1w command, resulting in Danny being muted for one week. A moderation bot then publicly confirmed the action in the community.

Shortly afterwards, Benji wrote that Danny had been “blowing up” his direct messages after finding an issue with the VPS. Benji said the issue had already been fixed after he saw Danny’s messages.

However, the discussion became increasingly hostile. Benji told Danny to “stfu and stop fucking around” and accused him of trying to exploit things and “testing in prod” on a large server.

The concern was therefore not only that Danny had been muted. Benji’s criticism and accusations were made publicly where other members of the Telegram community could see them.

This changed what appears to have started as a technical disagreement into a wider public confrontation. Danny was being blamed and criticised in front of other members rather than the issue being discussed only between those directly involved.

Benji later referred to previous warnings involving Danny. However, the main concern raised by this incident is not simply whether warnings had been given. The more serious issue is the way the disagreement was handled publicly.

Administrators may sometimes need to warn or mute members when they believe rules have been broken. However, using insulting or aggressive language while publicly accusing someone of causing problems can make the situation more confrontational and embarrassing for the person involved.

At the time the Telegram screenshot was taken, Benji’s messages criticising Danny were still visible in the community. The available evidence cannot show whether those messages were removed at a later date, so this article does not claim that they remained there permanently.

The screenshots also do not show the disagreement being moved into a calmer private discussion immediately after the moderation action.

Danny later attempted to contact Benji privately about what had happened. In Discord messages shown in the evidence, Danny questioned why such serious action had been taken and said that he did not believe he had been trying to cause trouble.

Danny also asked why his behaviour had been treated as fighting when he believed there had been nothing seriously wrong with what he was doing.

The provided Discord screenshot does not show Benji responding to those messages at that time. It is not possible to establish from the screenshot why no response is visible, so it would not be appropriate to claim that Benji deliberately refused to resolve the issue.

What the evidence does show is that Danny attempted to discuss the situation privately after the public confrontation.

Other messages shown in the evidence suggest that there were different opinions about Danny’s behaviour. One person described his actions as causing “more hassle”, while another discussed previous warnings.

Those comments provide context for why some members may have had concerns about Danny’s actions. However, they do not remove the separate concern about how Benji chose to communicate and moderate the situation publicly.

The screenshots do not establish that either Danny or Benji was entirely responsible for the original technical problem. They do clearly show that the disagreement developed beyond a VPS issue and became a wider problem involving moderation, public criticism and communication.

Danny has also said that the incident caused him significant distress and affected his wellbeing. He described hostile situations and public criticism as particularly difficult for him.

The screenshots alone cannot independently prove the full effect that the incident had on Danny’s mental health. However, his account is relevant when considering how the public confrontation affected him personally.

Being publicly blamed or criticised in front of a community can be upsetting, particularly when aggressive language is involved. This is one reason why administrators should consider how moderation decisions are communicated, even where action against a member may be necessary.

A clearer approach could have included explaining what rule Danny was believed to have broken, what behaviour needed to stop, why a one-week mute was considered appropriate, and how he could privately discuss or challenge the decision.

The situation highlights the difference between moderation and public confrontation. Administrators may need to take firm action, but that does not require personal insults or hostile language.

Clear explanations, calm communication and a fair way to discuss moderation decisions can help prevent a technical disagreement from becoming a larger community conflict.