Parting content with login details (python)

It is necessary to refine the existing desktop application in Python (about 9000 lines of code). The program is already operational and has a graphical interface. The following are used: Python 3 Selenium Tkinter / CustomTkinter SQLite asyncio requests Telegram Bot API The project does not require development "from scratch." It is necessary to understand the existing code and make changes. Reason for refinement After the update of platform X (Twitter), the interface and logic of chats have changed. As a result, part of the functionality related to chat operations no longer works or works incorrectly. It is necessary to adapt the program to the new version of the interface. What needs to be done 1. Analysis of the existing project It is necessary to: study the structure of the program; find all modules responsible for chat operations; determine dependencies between them; create a plan for making changes. 2. Refinement of functionality The program needs to be adapted to the new chat interface of X. In particular, implement correct operation of: opening the chat list; opening a specific chat; determining the active chat; receiving new messages; sending messages; working with group chats; error handling and non-standard situations. 3. Preserve the existing logic of the program During the work, it is necessary to: not disrupt the operation of the graphical interface; not change the existing logic of other modules; maintain compatibility with the SQLite database; preserve the existing settings system; minimize the number of changes in the code. 4. Code requirements The code must be: clear; structured; without duplication; compatible with the current architecture of the project. 5. Verification After completing the work, it is necessary to: check the program launch; ensure there are no errors; test the implemented functionality. What will be provided The contractor will be provided with: the source code of the program; a description of the current functionality; information about problematic areas; test data (if needed). Experience in web interface automation and refactoring existing code will be an advantage.

Telegram bot for trading signals and registration automationIt is necessary to develop a Telegram bot for a trading project that automates the user journey from registration to receiving trading signals.Main functionality: user registration via Telegram; redirecting to registration via a partner link; receiving and storing the trading account ID; automatic verification of registration and deposit via API / Postback / Webhook, if supported by the platform; granting access to signals after the necessary conditions are met; sending trading signals in Telegram; displaying the asset, direction, entry time, and expiration; ability to specify the result of the signal WIN / LOSS; automatic notifications to users; admin panel for managing users, signals, and accesses; statistics on registrations, deposits, and active users; mailing system.It is preferable to implement the project in Python + aiogram + PostgreSQL with the possibility of further scaling.Before starting work, it is necessary to assess the integration capabilities with the trading platform and propose the optimal method for automatic verification of registrations and deposits.In your response, please indicate: development cost; estimated timelines; technologies; examples of similar Telegram bots; whether you have experience with API, Postback, and Webhook.

Hello, I need a fix for the parser. It used to work with the curl_cffi library, but now all requests return 403. I need to investigate the resource, figure out how to implement the fix, apply the fix, and test it with the data results.

We are looking for a developer (Python / AI / Integration) to create a Telegram bot that will completely replace the operator for receiving orders for the supply of vegetables and fruits from restaurants. The main task of the bot is to accept unstructured requests in any format (text, photos of handwritten lists, voice messages), convert them to our nomenclature, and send the completed order to 1C. Key functionality: Receiving and recognizing requests (AI module): Recognition of free text, voice messages (Whisper / SpeechKit), and photos/scans (Vision OCR). Entity extraction: item, quantity, unit of measure (kg, boxes, pieces). Nomenclature mapping: Mapping of client slang/abbreviations (“potato”, “cherry”, “bulb onion”) to the official product catalog of the company. Feedback function: if the item or quantity is unclear, the bot asks a clarifying question to the client in the chat. Confirmation and integration: Displaying the final order to the client for confirmation (“Your order: Potatoes — 50 kg, Cherry Tomatoes — 10 kg. Is everything correct?”). Sending the generated order via API to 1C (creating a “Customer Order” document). Implementation stages (MVP and beyond): Stage 1: Bot logic, processing text/voice/photos, and outputting structured JSON. Stage 2: Setting up mapping with the nomenclature database. Stage 3: Setting up data transfer to 1C (REST API / HTTP services). Requirements for the performer: Experience working with OpenAI / Claude APIs and speech/photo recognition libraries. Proficient in Python (Aiogram / Telebot / FastAPI). Experience integrating external services with 1C (having ready cases will be a key advantage).

General information: There is a Telegram bot written in Python (aiogram v3, aiohttp, MySQL, Redis). This is a service for interaction between clients and performers (profiles, projects, etc.). Required skills: - Confident experience with aiogram v3 (not v2!), asyncio, aiohttp; - Knowledge of Telegram Bot API (webhooks); - Experience with MySQL, Redis; - Ability to understand someone else's code; - Communication skills, responsibility. I need to fix a bug in the current version of the bot directly on the server. The problem is as follows: The chats (Nooks) are not functioning properly; there should be a cleaner that works according to an algorithm, but right now it is working with bugs and not cleaning on schedule. - A chat between the client is needed for discussing work matters with the performer. - Chats (nooks are already created, they need to be cleaned and queued. - The user bot creates chats (pair nooks, which we already have) and puts them in the queue; if a deal is made in the chat, the interlocutors are present (one chat for the performer, another chat for the client); if the chat is closed or there was no deal made and users did not write there for 7 days, the bot removes clients or performers from there and puts this chat (nook) back in the queue. - The client can switch to a chat with any performer who responded to the order. - The client and performer are in two parallel chats, so there is no possibility to see the direct account of the interlocutor and no possibility to write to them directly. * We do not change the operation of the chats and everything else. The main thing is that the fix does not lead to other problems.