How iray/teletor works
Main Components
a) External Services:
• Telegram Bot API
• Transmission BitTorrent Client
b) Core Application Components:
• Main Bot Application (teletor.py)
• Message Handler System (handlers/)
• Configuration Management (config/)
• File Management System (files/)
[User/Telegram Client] <---> [Telegram Bot API] <---> [TeleTor Bot] <---> [Transmission Client]
Detailed Component Breakdown
a) External Layer:
• User's Telegram Client
• Telegram Bot API
• Transmission BitTorrent Daemon
b) Application Layer:
• Main Bot Process (teletor.py)
• Message Handler (handlers/message.py)
• Utility Functions (handlers/utils.py)
• Configuration Manager (config/settings.py)
Data Flow Representation
• Incoming messages from Telegram (commands, torrent files, magnet links)
• Outgoing responses and status updates
• Configuration data flow
• Transmission client commands and responses
Implementation Details
• The bot's role as a bridge between Telegram and Transmission
• The configuration management system
• The message handling pipeline
• The file processing system
Key Interactions to Highlight
• User authentication process
• Command processing
• Torrent management operations
• Status monitoring and updates
[User/Telegram Client] → [Telegram Bot API]
• ↓
• [Authentication Layer]
• ↓
• [Main Bot Application]
• ↙ ↓ ↘
• [Config Manager] ← [Message Handler] → [File Handler]
• ↓
• [Transmission Client]
Additional Notes:
• Notes for important configuration points (auth, paths, etc.)
• Command processing pipeline
Remember to include error handling flows and the configuration feedback loop, as these are critical for the bot's operation.
This system design should clearly communicate how the bot serves as a bridge between Telegram users and their local Transmission client, while maintaining security through the authentication system defined in the config.yaml file.