Repository navigation
1.0.1
Fixes
- One join link per chat. Telegram lets a bot create only about 20 invite links a minute per chat, so personal links made the start of a big block take most of an hour and paused the bot. A club now keeps one join-request link; the bot approves the student who asked if they have access. Forwarded links still let nobody else in.
- Flood protection. Private messages and button presses are limited per user (five in a row, then one a second); the excess is dropped before it touches the database.
Includes a migration: chat_accesses.invite_link moves to clubs.chat_invite_link.