Technical assignment for the development of an organic YouTube view emulation system
1. General Information
Project: Automated video view emulation system on YouTube using real accounts, proxies, and user behavior modeling.
Goal: Create server software with a user-friendly interface for Windows management that allows scalable, stable boosting of YouTube video views through organic user behavior simulation. The system should offer flexibility in configuration, scalability, ease of deployment, and secure operation.
2. Project Architecture
2.1 Overall Logic
The server component is deployed on a Linux server and handles all operations: session launching, account management, streams, proxies, logs, etc.
System management is carried out via a separate Windows application connecting to the server via API.
The system must be ready to operate in high-load mode with hundreds of concurrent streams and thousands of operations per day.
3. Key Modules and Functional Blocks
3.1. Video Search and Launch Module
Accepts input data: video link + set of keywords.
Performs video search on YouTube using specified keywords (not direct link navigation).
Simulates manual search: scrolling through search results until the desired video is found.
Clicks on the video in search results and transitions to viewing.
3.2. User Behavior Emulation
During video viewing, the session should perform the following actions:
Fast forward/backward.
Pause/resume playback.
Page scrolling.
Mouse hover and clicks.
Transitions to similar videos (based on specified probability).
Support for multiple behavioral activity templates with random selection capability.
3.3. Account Management
Use of pre-logged-in Google accounts.
Loading accounts via file or database (cookies, tokens, etc.).
Session storage support: accounts should not log out between sessions.
In case of authorization errors — logging and automatic exclusion of the account from the queue.
3.4. Proxy Support
Mandatory use of individual proxies for each session.
Support for HTTP, SOCKS5, mobile proxies.
Proxy functionality check before session start.
Automatic IP rotation (via list or proxy service API).
3.5. Multithreading and Scalability
Support for launching 100–500+ concurrent streams.
Each session is fully isolated:
Unique account,
Individual proxy,
Separate User-Agent,
Own cookie session.
Flexible control of stream count via management panel.
4. Client-Server Architecture
4.1 Server Side (Linux)
Operates as backend on a Linux server.
Handles all session behaviors, data storage, task execution.
REST API for remote management from Windows application.
Automatic installation via script or Docker (bash install.sh).
Ability to update core software without reinstallation.
4.2 Client Side (Windows)
Simple application for management:
Add tasks (video and keywords).
Upload accounts and proxies.
Configure behavior, schedules, and streams.
View logs, errors, current task statuses.
Connect via IP and API key.
Ability to use multiple servers from one client.
5. Interface and Management
Dashboard with sections:
Tasks: list of videos, keywords, progress.
Accounts: list of uploaded profiles, login status.
Proxies: list, status, session binding.
Settings: viewing depth, behavior templates, limits.
Statistics: number of successful views, errors.
Log: record of all actions, errors, statuses with export options (CSV, JSON).
6. Technical Requirements
Component
Description
Server OS
Linux (Ubuntu/Debian), root access or Docker
Server Language
Python / Node.js / Go (developer's choice)
API Interface
FastAPI / Flask / Express.js
Windows Interface
Electron / Python PyQt / C# WinForms (discussed)
Browser Engine
Puppeteer / Playwright / Headless Chrome
Database
SQLite / PostgreSQL
Proxies
Support for HTTP/SOCKS5/mobile, IP rotation
Accounts
Cookie handling, session saving, problematic login exclusion
Multithreading
From 10 to 500+ threads (configurable)
Logging
Export logs, errors, events in JSON/CSV
Security
API key authorization, IP access restriction
7. MVP Functionality (first version)
Video search and playback emulation.
Use of proxies and accounts.
Behavior emulation within videos.
Minimum 10 concurrent streams (testing).
Session saving.
Windows management panel.
Logs and task execution control.
8. Additional (optional, phased)
Automatic check if view was counted (via API or indirectly).
Support for likes, subscriptions, comments.
Work schedule by hours/days.
Notifications via Telegram for success/issues.
Implement functionality for some accounts to randomly like videos (enter number of likes each time)
