Budget: 27000 UAH Deadline: 12 days
Hello. I work with Python. I am ready for collaboration. Feel free to contact me.
Oleh Ovchynnykov
Winning proposal- Projects 53
- Rating 4.3
- Rating 3 170
Budget: 13000 UAH Deadline: 10 days
Good afternoon
I can help with your task
Write to me, I will be happy to assist with the execution
Budget: 10000 UAH Deadline: 10 days
Hello!
I am interested in your project.
I have experience with Python, FastAPI, Celery, and FFmpeg.
I am ready to implement your specifications using clean architecture: authorization (including Gmail), video upload and processing with a queue of streams and asynchronous processing.
I would be happy to discuss the details and get started on the work.
Budget: 5500 UAH Deadline: 1 day
Hello! I am interested in your project, ready to start working, everything in the terms of reference is clear, I have no questions for now. I will be glad to cooperate with you!
Proposals are currently absent
Current freelance projects in the category Python
I want to create a company like Push House and hire a team. The name will most likely be SuperTraffic https://push.house/panel/dashboard. This is the Push House website.
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
The program is intended for internal use and is designed to maintain a dictionary with search, editing, and data export functions. The criteria for evaluating the result are as follows: The program must meet the specifications, function correctly for all features, be user-friendly, and allow for future expansion of functions.
Our old custom system has outlived its usefulness, we need to grow. We are looking for an experienced professional to implement ERPNext. Must have experience, our field is wholesale and retail trade. There will be a lot of different standard and non-standard solutions, as well as classic connections to PRRO, Bank Mono and Privat, Nova Poshta, marketplaces, and so on. Ready?! :) Then send your resume and let's get to know each other.
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.



