How ezioxtn/instabooster works
Project type and purpose
• This is a monolithic, CLI-driven Python tool (“Instagram Booster”) whose sole purpose is to automate Instagram interactions (follow, like, comment, view) based on a JSON configuration or command-line flags.
File structure
• Top-level files only:
• main.py – the entry point and orchestration layer
• config.json – user settings (credentials, target, actions, debug)
• comments.txt – payloads for comment action
• README.md / LICENSE – documentation
• No separate frontend/backend directories → single process
README for insights
• Enumerates features (followers, views, likes, comments)
• Describes required Python modules (requests, httpx, threading, concurrent.futures, prettytable, etc.)
• Explains config format and CLI args
Main components
a. Presentation Layer (CLI Interface)
• Parses command-line flags and/or reads config.json
b. Core Engine
• Scheduler / Orchestrator in main.py
• Concurrency module: threading + concurrent.futures executor
c. Action Modules (Plugins)
• FollowAction
• LikeAction
• CommentAction (uses comments.txt)
• ViewAction
d. HTTP Client Layer
• requests or httpx wrapper for all Instagram HTTP calls
• Rate-limiting / backoff logic (time module)
e. Data Layer
• Config loader (json module)
• Comments loader (plain text)
f. Reporting / Logging
• prettytable for tabular output
g. External Service
• Instagram Web Endpoints (public API / scraping endpoints)
Relationships & data flow
• CLI → Core Engine (passes config+flags)
• Core Engine → Concurrency Executor → dispatches to each Action Module
• Action Module → HTTP Client → Instagram endpoints
• HTTP Client → returns responses → Action Module → updates metrics
• Core Engine → Reporting Layer → console output / logs
Architectural patterns & principles
• Modular “plugin” pattern for each Action
• Separation of concerns: CLI parsing, orchestration, HTTP calls, data/config, reporting
• Concurrency pattern: thread pool for parallel requests
Essential details to capture
• Shared HTTP client and concurrency executor used by all actions
• How config.json and command-line args merge into a single settings object
• Output directed to prettytable/log console
1. Sketch the high-level flow: CLI → Engine → Actions → HTTP → Instagram → Reporting
2. Break down into components and subcomponents (plugins + shared services)
3. Resource nodes (config.json, comments.txt)
4. Concurrency pool as an infrastructure block between engine and actions
7. Review against README features to ensure completeness (followers, likes, comments, views)