Refinement and stabilization of the Python application Teleton for Telegram

There is a ready-made desktop Python application called Teleton. It already has the main sections implemented: accounts/proxies, import of Telegram sessions/TData, chat and channel templates, audience parsing, mailings, cyclic campaigns, channel commenting, auto-responder, account profile management, announcements, logs, and settings.

The goal is not to write the project from scratch, but to take the current version, check all tabs, fix errors, stabilize the operation, and bring the application to a state where it can be used without constant freezes, manual guesses, and unclear statuses.

Deadline: up to 3 days.

What needs to be done:

1. Go through each tab of the application separately and check that each function works:

- Accounts/Proxies;

- Chat/Channel Templates;

- Parsing;

- Audiences;

- Mailing tasks;

- Commenting;

- Auto-responder;

- Account;

- Announcements;

- Logs/Statistics;

- Settings.

2. Stabilize mailings and cyclic campaigns:

- launching a single campaign should work stably;

- multiple accounts/campaigns should work clearly and predictably;

- Start/Stop/Stop All buttons should effectively manage processes;

- the application should not show "running" if the process is not actually working;

- the status should clearly indicate: which campaign is running, which account is being used, current goal, next goal, last successful send, and last error.

3. Improve the interface of the "Mailing Tasks" section:

- currently, some statuses are hard to read;

- a more user-friendly status panel is needed;

- the user should immediately understand whether the process is ongoing or not;

- it would be preferable to show the nearest goals in the correct order: current, next, last successful, last errors.

4. Refine the "Announcements" tab:

A convenient logic for announcements with buttons, like in Telegram bots, needs to be created.

For example: announcement text + "Write", "Contact", "Open chat" button.

There should be an option to specify where the button leads and create a simple dependency: if the user wants to write, they click the button and go to the desired account/chat/link.

5. Check the import of accounts/TData/sessions:

- the import should only add real accounts;

- if the import fails, there should be a clear reason;

- bulk import should work correctly with a folder containing multiple accounts;

- after import, it should be clear: which account was added, which was not added, and why.

6. Check parsing and audiences:

- parsing results should save user_id, username, message text, date, chat source, and message link;

- there should be an option to delete unnecessary audiences from the interface;

- filters should be clear: keywords, excluding words, post length, period or number of messages;

- if the AI filter is enabled, there should be a clear error if there is no API key or limits.

7. Check the auto-responder:

- it should work stably in personal messages;

- the "reply once" mode should be clearly understandable;

- if a repeated response is needed, there should be a separate clear mode;

- errors like session/database locked/needs_reauth should be explained clearly.

8. Logs and diagnostics:

- the log should explain the problem in simple language;

- if an account cannot perform an action, the reason should be shown: no access, flood wait, no rights, reauthorization needed, proxy error, empty text, etc.;

- it would be preferable to add a short diagnostic panel: how many accounts are active, how many tasks are running, how many errors, which campaigns are actually working.

What is already available:

- a ready-made application in Python;

- GUI;

- SQLite database;

- main tabs and functions;

- the current version of the project will be provided;

- Telegram accounts and proxies for testing will be provided separately.

Main problems now:

- sometimes the application is open, but the process is not actually working;

- it is not always clear whether a task is ongoing or not;

- Start/Stop buttons do not always behave as expected;

- multiple campaigns/accounts do not work as transparently as needed;

- TData import sometimes adds unclear technical records;

- the interface is overloaded in places, statuses are hard to read;

- some errors have to be searched manually in the logs.

Work requirements:

- deadline: up to 3 days;

- a short report every day: what has been done, what remains, what problems have been found;

- before handing over the finished version, a video of the tests must be sent;

- the video must clearly show the application launch, checking the main tabs, starting/stopping a campaign, working logs, and absence of freezes;

- do not break already working functions;

- all changes should be briefly described: which files were changed and why;

- the final version should be delivered in a separate folder/archive.

Readiness criterion:

I should be able to open the application, select an account/template/campaign, press the necessary button, and see a clear result: process started, stopped, error is clear, status is displayed correctly. Without needing to manually search for the reason in the code or logs.

Important:

A developer is needed who will not just fix one button, but will go through the entire workflow from start to finish and bring the current version to a stable, clear, and user-friendly build.