How apperside/thunderclone works
Main Components Overview
A. Browser Extension (Chrome)
• Content Scripts (UI layer)
• Background Service
• Message Handling System
B. Desktop Application (Electron)
• Main Process
• Renderer Process
• WebSocket Server
• File System Operations
Browser Extension Layer
• Content Script Component (injects UI)
• Background Service (handles communications)
• Password Authentication UI
Desktop Application Layer
• WebSocket Server
• Repository Manager
• Password Verification System
• File System Interface
• Configuration Manager
Component Relationships and Data Flow
[GitHub Repository Page] → [Chrome Extension]
• ↓
[Injected Clone Button] → [Password Dialog]
• ↓
[Signature Generation] → [WebSocket Message]
• ↓
[Desktop App WebSocket Server] → [Auth Verification]
• ↓
[Clone Operation] → [Local File System]
Specific Implementation Details
Technical aspects:
• WebSocket connection on local port
• Password-based security system
• Repository cloning path structure
• Content script injection points
Security Flow Representation
Security workflow:
[Password Input] → [Signature Generation]
• ↓
[Timestamp + URL + Password Hash]
• ↓
[Signature Verification]
• ↓
[Clone Authorization]
Configuration Flow
Configuration system:
[User Preferences] → [Desktop App Storage]
• ↓
[Clone Directory Settings]
• ↓
[System Startup Config]
Important Notes
• Clear separation between browser and desktop environments
• WebSocket communication channel
• Temporary nature of password storage
• Future implementation points (AI integration, config panel)
• Error handling paths
• Path for repository cloning structure