Python developer

Hello!

Updating data every 1–60 minutes for 30–50 channels easily hits the daily quota of 10,000 units by default, especially if videos.list/search.list is called thoughtlessly with details. Therefore, a separate quota scheduler can be created that selects methods with minimal cost (for example, combining videos.list with a previous cache of IDs, not using search unnecessarily).

Regarding query aggregation, it is necessary to pull statistics in batches of several videos and channels, rather than one video - one request + fallback mode, where as the limit approaches, the update frequency is automatically reduced and missed slots are logged.

For 30–50 channels, there will be 30–50 separate refresh tokens; YouTube/Google can revoke them when the password changes, suspicious activity occurs, or limits are exceeded, so a centralized token manager is needed. Required: encrypted storage of refresh tokens (KMS/key in secret manager, AES encryption at the database level), an automatic re-auth mechanism: if the refresh token stops working, the system sets the account to "re-authorization needed" status and displays a banner in the UI. And of course, it is necessary to make a fine distinction between app vs user quota and use server-side OAuth with offline access, as recommended by Google.

Best regards,
… Georgiy
Senior Software Engineer

Show original

Translate

Hello!

I have carefully studied the task and fully understand that the project involves the development of a full-fledged web application: server-side (Python), client interface (React / Next.js), data storage, and automatic analytics collection.

I have been working with the YouTube API for a long time, am well acquainted with quotas, limitations, OAuth2 tokens, and request optimization to avoid unnecessary quota costs when dealing with a large number of channels.

🔧 What exactly can I implement:
1. Connecting 30–50 YouTube channels via OAuth

… Implementation of a secure OAuth flow.

Encryption and storage of refresh tokens.

Automatic updating of access tokens.

Quota control and redistribution of requests across accounts.

2. Automatic data collection every 1–60 minutes

Background scheduler (Celery / APScheduler / built-in cron workers).

Collection of:

views for the last 60 minutes and 48 hours;

statistics of the latest videos;

list of trending videos;

basic information about channels.

Smart aggregation → minimum requests = quota savings.

3. Analytical dashboard

I will create a user-friendly UI on React / Next.js:

📊 General overview of all channels

📁 List of channels: views, growth, activity

🎬 Detailed page: graphs, latest videos, dynamics

🔥 Trending videos in real-time

🟢 Online data updates (WebSocket or polling)

The interface will be fast, neat, without unnecessary elements — only useful analytics.

4. Backend in Python

FastAPI / Flask (your choice)

Optimized requests to the YouTube API

Caching and buffering of data

PostgreSQL or MongoDB (depending on the storage model)

Docker containers for convenient deployment

🧠 Why me?

✔ I have excellent knowledge of the YouTube API, its limitations, and optimization methods.
✔ I have implemented services that work with multiple YouTube channels simultaneously.
✔ I know how to properly build the architecture of multithreading and scheduling.
✔ I write stable and scalable backend services.
✔ I can easily set up a frontend on React with a user-friendly interface.

I understand that this is a combined job: API + analytics + UI + architecture, and I am ready to handle the entire cycle turnkey.

Show original

Translate

Good day, I have experience working with Python as well as Telegram bots, I can complete everything quickly and efficiently, write to discuss the details.

Show original

Translate

Good day! I am ready to complete this project. Great experience in developing various applications.

Show original

Translate