How johnw7789/forge works
Main Components
• Frontend Client: Representing the React/Next UI that comprises the user interface. This includes subcomponents for account management, addresses, cards, tasks, and settings. Note the use of NextUI for components and Recoil for state management.
• Backend Service: The core Go application split into various modules:
– General application entry points such as main.go, app.go, and other high-level orchestrators.
– Dedicated modules in the “backend” folder:
• antibot: Contains modules (captcha.go, secure.go, useragent.go) handling anti-detection techniques.
• request: Handles different types of account requests (Amazon, Alexa, 2FA, etc.) and encapsulates complex logic for generating account payloads.
• sms: Organizes support for multiple SMS providers (DaisySMS, SMS Man, SMSpool).
• email: Deals with IMAP functionalities for OTP retrieval.
• discord and shr: Likely for additional integrations and shared utilities.
– Support modules in the root (accounts.go, profiles.go, proxies.go, settings.go, task.go) that possibly tie frontend inputs with backend account operations.
• Wails Bridge: While not a separate “module” folder, the integration layer provided via Wails (see wails.json and wailsjs directories) serves as the communication bridge between the frontend and the Go backend.
– 2Captcha for captcha solving.
– IMAP email services for OTP retrieval.
– SMS providers (DaisySMS, SMS Man, SMS Pool).
– (Potentially) iCloud and Hide My Email (HME) for authentication.
Component Relationships & Interactions
• User interactions in the Frontend trigger calls via the Wails bridge that invoke backend functionalities.
• The Backend orchestrates account generation processes by routing requests to the appropriate modules (antibot strategies, SMS/email verifications, etc.).
• Some backend modules interface directly with external services (e.g., sending HTTP requests to 2Captcha endpoints, fetching OTP emails via IMAP, contacting SMS providers).
• Data flows from the backend back to the UI to update user accounts, tasks status, and settings.
Architectural Patterns & Design Principles
• Separation of Concerns: Clearly partition the system into frontend, backend modules, and external service integrations.
• Modular Structure: Each subfolder in the backend denotes a set of responsibilities (antibot techniques, request handling, SMS/email communications). This modularity is a key design principle.
• API-Driven Communication: Utilize Wails for binding Go functions to the React frontend. This ensures that the UI remains decoupled from the backend logic while remaining tightly integrated.
• Extensibility: The project is designed to easily support additional account types or integration with more external services in the future.
Relevant Technologies and Frameworks
• Wails – The desktop application framework bridging Go and React.
• Go – Powers the backend logic and integrations.
• React/Next.js – Implements the modern UI for the frontend.
• NextUI and Recoil – For UI components and state management.
• External APIs – 2Captcha, IMAP server protocols, SMS provider APIs.