How arun017s/autodelete works
AutoDelete is a Telegram bot that queues eligible chat messages for deletion after a configured delay. Its main process filters messages and records their expiry; a separately launched worker polls due records, deletes the Telegram messages, and removes processed records. Configuration supplies the chat, timing, and user-list settings, while a small Flask route provides a health page. The README also documents user-account and bot-only variants; the sampled code shows the user-account mode. Connections reflect the shown calls and launches.
Main entry points: main.py Message listener · delete.py Expiry worker · database.py Message repository · info.py Runtime settings
Components 9
Message intake
- Message listener
main.py
Configuration and state
- Runtime settings
utils/info.py - Message repository
utils/database.py
Expiry processing
- Expiry worker
utils/delete.py
Health endpoint
- Health route
utils/server.py
Other components
- Telegram users
- Telegram API
- MongoDB
- HTTP client
Connections 12
- Telegram users → Message listener: send messages
main.py - Message listener → Runtime settings: reads settings
main.py - Message listener → Message repository: saves expiry
main.py - Message repository → MongoDB: writes records
utils/database.py - Message listener → Expiry worker: launches worker
main.py - Expiry worker → Runtime settings: reads settings
utils/delete.py - Expiry worker → Message repository: queries and clears
utils/delete.py - Message repository → MongoDB: reads and deletes
utils/database.py - Expiry worker → Telegram API: deletes messages
utils/delete.py - Telegram API → Telegram users: deletion takes effect
- Message listener → Health route: launches server
main.py - HTTP client → Health route: requests page