How retarduser404/telegrambot works
Project type and purpose
• Type: A single-service, bot-style application (Python Telegram Bot).
• Purpose: Secure password management via Telegram, using Fernet symmetric encryption, with per-user encrypted storage in a JSON file.
File structure
• Top-level:
• bot.py (or main.py): entry point, implements Telegram Bot handlers.
• requirements.txt: dependencies (python-telegram-bot, cryptography).
• data.json: encrypted payload store.
• utils/ folder: encryption & validation helper modules.
• Patterns:
• Modular separation of “transport + handler” vs. “business logic (utils)” vs. “storage.”
• Single process: polling or webhook loop.
README for additional insights
• Uses Telegram Bot API for user interaction.
• Uses cryptography.Fernet to generate keys and encrypt/decrypt data.
• Persists data in JSON; future plans for DB.
• Flow: Telegram ↔ Bot ↔ Encryption utils ↔ JSON storage.
Main components
a. External Client: Telegram User
b. External Service: Telegram API / Servers
c. Bot Application (hosted on VM/container):
• Transport Layer: Bot.py (message polling/webhook)
• Business Logic Layer: Command handlers (add/retrieve/delete)
• Security Layer: Encryption utils (Fernet)
• Storage Layer: JSON file (data.json)
d. (Future) DB Layer: SQLite/Postgres
e. External Libraries: python-telegram-bot, cryptography
Relationships and interactions
• On /start or inline button, Telegram pushes update.
• Bot pulls via polling or receives webhook.
• Within Bot: Transport → Handler → Encryption Utils → Storage
• Encryption utils generate or retrieve user’s key, encrypt/decrypt payload.
• Read/write to data.json.
• Bot → Telegram Servers → User: bot sends reply messages.
Architectural patterns & design principles
• Layered: Transport / Business Logic / Security / Storage
• Single responsibility per module (utils folder)
• Stateless handlers aside from on-disk storage
• Future extensibility: swap JSON for a relational DB with minimal changes to storage interface
Elements
• Clear labels on each component (e.g., “EncryptionUtils (Fernet)”)