Thors Hammer: One Ban, Every Chat

A spammer gets banned in one of your groups and shows up in the next one a minute later. Sound familiar? Thors Hammer was built for exactly that: one ban that applies in every chat where the bot is an admin. 🔨

Its author calls it a simple global moderation bot. It does not replace the big tools with captchas and filters. It adds one narrow function next to them.

One strike, many chats

The key word is global. A normal ban closes the door to a single group. The /hammer command puts a user on a shared list, and the bot removes them from every chat it is connected to.

You can use it as a reply to a message, with a username, or with a numeric ID. The ID route helps when the offender has already deleted the account or changed names.

Everything is reversible with /unhammer. If you got the wrong person, lift the ban and move on. 🙂

The command list

You can start a command with any of three prefixes: a slash, an exclamation mark or a hash sign. Admins used to different bots will feel at home.

• /hammer and /unhammer. Global ban and unban, for global admins.
• /kick and /ban. Ordinary actions inside a single group, for that group's admins.
• /admins and /globaladmins. Any member can see who keeps order.
• /promote, /demote and /leave. Control over the bot itself, reserved for the superuser.
• /help. A help message, which you can also call in any chat through inline mode by adding a language code.

Who gets the most out of it

With one small group, Telegram's built-in tools are enough. A global ban is for people who run several chats or a team of moderators and are tired of banning the same accounts over and over.

A typical case is a network of topic chats around one community. An ad spammer gets blacklisted once, not once per chat.

Setting it up without mistakes

1. Add the bot to your group and make it an admin with the right to ban members.
2. Ask the bot's owner or team to add you as a global admin if you plan to use /hammer.
3. Test it with a spare account in a private group.
4. Agree inside your team on what deserves a global ban, so nobody swings the hammer too fast.

Without the ban permission the bot cannot remove anyone. That is the most common reason a command appears to do nothing. ⚙️

What to know about the open source code

The project is written in JavaScript, stores its data in MongoDB and keeps its source on GitHub. The latest release dates from 2017, so do not expect new features. The logic, on the other hand, is simple and easy to read.

For a job like "remove everyone who is already banned elsewhere" that is enough. For serious protection against raids, add a modern moderator bot and treat this one as a supplement. 🛡️

Handle global bans with care

A global button is powerful, so a mistake costs more. Someone banned by error vanishes from all your chats at once.

• Keep the circle small. Give global admin rights only to people you trust.
• Write down reasons. If a dispute comes up, you can explain the decision.
• Leave room for appeals. Give the person a way to contact you and sort it out.