Питон ООП правки в готовый проект

A system needs to be created for managing OnlyFans/Fansly accounts. The technical specifications are attached. Please indicate the price and deadlines for the entire project in your bid according to the technical specifications. Feel free to ask any questions or clarifications in the discussions -- I will respond. Please review the technical specifications before submitting your bid.

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).

A local solution (script/emulator/proxy) for Windows is required, which will provide the Lovense Cam Extension in the browser with a constant status of a connected toy (Lush 3). Main goal: The extension in Chrome should show “green” (Connected) 24/7 without the involvement of a mobile phone, original USB dongle, and without a real Bluetooth device. What is submitted as a result: Complete source code of the repository/archive (without obfuscation). A README.md file with a detailed manual for deployment from scratch on a clean Windows. Demonstration of operation: with the script running, the Lovense Cam Extension in Chrome shows a stable “Green” status. When responding, please first write the anti-bot word: dsqwueq

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.

Auto-notification system for inventory replenishment analytics. On 8n8. Small automation for e-commerce. Once a day, the system calculates the sales velocity for each product and sends a message in Telegram indicating when to reorder (with the recommended quantity) and how many days the remaining stock will last. What we do: Data retrieval: KeyCRM API (order history) + stock/orders from Rozetka (API or export) Storage in SQLite on my VPS (Contabo, Linux) Calculation of average sales, days of stock, reorder point ABC analysis: prioritization of which product to replenish first (class A — main by revenue — more important) Daily Telegram bot + cron job All thresholds (lead time, safety stock, target stock) — in the config