mirror of https://github.com/lukaszraczylo/go-telegram.git synced 2026-06-05 22:43:59 +00:00

Files

T

History

lukaszraczylo 1ff26006f7 chore(examples): use api.Ptr for optional pointer fields

Replace the throwaway-local-var-then-take-address pattern with
api.Ptr in the polls and moderation examples. Net effect: 14 lines
gone, the pointer wrangling no longer steals visual focus from the
actual API call.

2026-05-09 18:20:00 +01:00

main.go

chore(examples): use api.Ptr for optional pointer fields

2026-05-09 18:20:00 +01:00

README.md

Initial release of go-telegram

2026-05-09 13:09:27 +01:00

README.md

moderation

Group moderation commands: /kick, /ban, /mute, /warn, /unwarn.

What it shows

OnCommand for each moderation action
api.BanChatMember / api.UnbanChatMember for kick and ban
api.RestrictChatMember with ChatPermissions for muting
errors.Is(err, client.ErrForbidden) to surface missing-permissions errors cleanly
In-memory warn counter via sync.Map (auto-bans at 3 warnings)

Required bot permissions

The bot must be an admin in the group with "can ban users" and "can restrict members" permissions. Without those rights, commands will reply with a friendly error message instead of crashing.

Usage

All commands work by replying to a target user's message:

/kick   — remove from group (can rejoin)
/ban    — permanent ban
/mute   — silence for 1 hour
/warn   — issue a warning (3 warnings = auto-ban)
/unwarn — remove the last warning

Production notes

The warn counter is in-memory and lost on restart. For production, back it with Redis or a database.
Consider adding an admin check (see examples/admin) so only group admins can invoke these commands.

Running

export TELEGRAM_BOT_TOKEN=123456:ABC...
go run ./examples/moderation