Program/bot/service for telegram/weber/instagram/text

Development of a Telegram bot: a closed platform-marketplace for experts I am looking for a developer (or a small team) to create a Telegram bot — a closed platform that connects verified experts and clients for solving professional tasks. The model is similar to a service marketplace with a supervising administrator, rather than a fully automated service. What is ready: A detailed technical specification (30+ pages) — user roles, step-by-step UX flows with button texts, status models for Requests/Cases, data model, payment status model, admin panel. Key functionality: - Two user roles (client / expert) with the possibility of combination - Verification of experts through the administrator (without automatic decision approval) - Selection and moderation of requests by the curator - Internal communication space within the bot (without disclosing contacts between parties) - Payment status model: escrow, confirmation of funds receipt, payments - Referral system with bonuses - Administrative panel with extended access rights Expected stack: at the discretion of the developer (Python/Node.js), the main thing is — experience with Telegram Bot API, working with states (FSM), databases, and payment integrations. Collaboration format: work based on the ready technical specification, discussion of deadlines and budget after reviewing the document. What to send: examples of implemented Telegram bots (preferably — with complex state logic or payments), an estimated timeline and cost.

Technical assignment for the client search automation system in Telegram Development 1. General task It is required to create an MVP system for automatic client search in Telegram chats with the provision of found users to sales department operators. The system should consist of: user bots based on Telethon; Telegram bot for operators; Telegram bot (or a separate administrative section within the bot) for the administrator; PostgreSQL database; Docker configuration for deployment in configuration. A web panel is not required at this stage. 2. Working with multiple Telegram accounts The system must not be limited to one Telegram account. It is necessary to ensure support for multiple accounts (for example, 5 or more) with the ability to increase their number without changing the configuration. For each account, there should be the ability to: authorize via Telethon; maintain its own session; connect a new account; disconnect an account; replace an account without losing the database. The administrator should be able to independently connect new Telegram accounts. 3. Distribution of chats among accounts The system will use a large number of Telegram chats (approximately 800 or more). All chats are included in a single system. The system should automatically: manage chats among connected accounts; observe Telegram restrictions; Handle the need to transfer a chat to another account; Prevent duplication of one chat by multiple accounts (unless specifically included). It is desirable to ensure load balancing among accounts. 4. Managing the chat list The administrator should be able to do this without the developer's involvement: connect a chat; delete a chat; import a list of chats from a file; bulk upload chat costs; enable or disable monitoring of individual chats; restart history collection for a selected chat. After adding a new chat, the system automatically includes it in one of the key accounts. 5. Data collection For each connected account, it is necessary to implement: Initial parsing After adding a chat: loading message history for the specified period; saving all available information. Monitoring After the initial loading is completed: constant tracking of new messages; saving new users; saving new activity of existing users. 6. Handling Telegram blocking requires proper handling: FloodWait; PeerFlood; temporary Telegram restrictions; erroneous connections; connection breaks; possible reconnections; temporary unavailability of the account. If one account is temporarily blocked by a restriction, the rest of the work continues. 7. User data storage. For each user, the following should be saved: Telegram ID; first name; last name (if available); username; profile link; list of all chats; message text; date and time of the message; link to the message (if obtainable from Telegram). User merging is performed exclusively by Telegram ID. If a user has written in 20 chats — they display one card. 8. User card The operator should see: first name; username; Telegram ID; profile link; list of all chats; messages; activity date. Example: User: Ivan Ivanov ID user : 123456789 Chat "Business": Message: "Good day, interested in advertising" Date: 01.03.2026 12:15 Chat "Marketing": Message: "Who is handling promotion?" Date: 05.03.2026 18:42 9. Operator work The system should automatically form a queue of clients. After receiving a client: the user is assigned to an operator; the second operator cannot receive the same client; maintain a history of actions. Statuses: Took the client; Unavailable; Could not reach; Refusal; In progress; Call back; Delete. After selecting a parameter, the next client will automatically open. 10. Reissuing users There should be an option to configure user reissuance. For example: never; after 30 days; after 60 days; after 90 days; arbitrary period. 11. Administrative section The administrator should be able to: Account management add an account; delete an account; view account status; view account restrictions; replace an account. Chat management add; delete; import; export; disable monitoring; disable monitoring. Operator management add; delete; block; change rights. Parser management start collection; stop collection; rebuild history; view current status. Statistics View: number of users; number of messages; number of processed clients; number of active operators; number of connected accounts; number of active chats. 12. Database Use PostgreSQL. It is necessary to store: users; messages; chats; activity; Telegram accounts; operators; processing statuses; processing history; distribution of chats among accounts. 13. Scalability The architecture should provide the ability to: connect 10, 20 or more Telegram accounts; connect thousands of Telegram chats; handle load; export data; work with CRM; connect new features without a complete project overhaul. 14. Docker The executor should set up: docker-compose.yml; Dockerfile; launch instructions; update instructions; database backup instructions. The system should manage the command as one.

Bot for mirroring positions on Binance Futures (Python) A bot is needed that reads my positions on Hyperliquid (public API) and Bitget Futures (my read-only key) and proportionally replicates them on my Binance USDT-M Futures via API. Logic: opening, increasing, partial closing, full closing — everything is mirrored with a customizable size ratio. Polling every 5–10 seconds. Correct handling of partial closures and averaging is mandatory. Requirements: notifications in Telegram about trades and errors; config (pairs, ratio, limits); deployment on my VPS + instructions; source code is transferred to me. I will enter the keys myself. Stages: 1) Hyperliquid→Binance, test with small amounts; 2) Bitget→Binance. Payment through safe in stages. In your response, indicate your experience with exchange APIs and how you will handle a partial closure of 30% of the position by the leader.

A Telegram bot needs to be created with a program that will monitor listings on three apartment rental websites (olx, lun, rieltor.ua) and send them structured in Telegram.

Project: Develop a Professional Crazy Time Live Dashboard Application (.NET C#)Project Overview I am looking for an experienced C#/.NET desktop developer to build a professional Windows application for displaying, storing, and analyzing live and historical Crazy Time game data obtained from a legitimate API provider. The application should feature a modern dark-themed interface, real-time updates, and a scalable architecture for future enhancements.Required Technologies C# (.NET 8) WPF (preferred) or WinForms Visual Studio 2022/2025 SQLite REST API WebSocket JSON Async/Await MVVM (if WPF is used)Main Features Modern dark dashboard API Key Manager REST API integration WebSocket support Real-time live data display Historical data storage Automatic synchronization Connection monitoring Error logging Statistics dashboard Data filtering Export to CSV and Excel Application settingsDashboard Modules The application should include: Dashboard Live Results History Statistics Connection Status API Manager Round Information Performance Monitor Settings Database ManagerData Analysis The software should provide analytical tools for available historical and live data, including: Frequency analysis Trend analysis Statistical reports Graphs and charts Data filtering Historical search Performance metrics The application should analyze available data only and should not claim to predict future outcomes of independent games.User Interface I want a premium-quality UI similar to professional trading or monitoring software. Requirements: Modern dark theme Rounded panels Smooth animations Professional icons Responsive layout High-quality UI/UX Fast performanceCode Quality The code should be: Clean and well-structured Fully documented Modular and scalable Easy to maintain Optimized for performance Built using best practicesDeliverables Complete Visual Studio solution Full source code Database Documentation Installation guide Future support (optional)Developer Requirements Please include: Experience with C#/.NET desktop applications Experience with REST APIs and WebSockets Portfolio of similar projects Estimated development time Fixed price or hourly rate I am looking for a long-term collaboration with a skilled developer who can build a high-quality and expandable application.