How saghen/heimdall works
Main Components
a. Browser Extension Layer
• Extension's content script and service worker components
• Permission management system
• Proxy routing system
• Cookie and storage management
b. Web Application Layer
• Frontend components (React-based)
• Parser system for different platforms
• Video player implementation
• Cache management system
Extension Infrastructure
┌─ Browser Extension ─────────────────┐
• Service Worker │
• Content Script │
• Permission Manager │
• Proxy Router │
• ┘
Core Application
┌─ Web Application ──────────────────┐
• UI Components │
• Video Player │
• Navigation │
• Content Views │
• State Management │
• ┘
Parser System
┌─ Platform Parsers ────────────────┐
• YouTube Parser │
• Twitch Parser │
• Standard Parser Interface │
• ┘
External Services Integration
┌─ External APIs ─────────────────┐
• YouTube API │
• Twitch API │
• ReturnYouTubeDislike API │
• Other Platform APIs │
• ┘
Use these visual elements:
Important Relationships to Show:
Cache and storage management across components
Key Technical Considerations:
• How the proxy system intercepts and modifies requests
• Parsing pipeline for different platforms
• Demonstrate the video player's integration with platform-specific features
• How the caching system interacts with different components
Specific features:
• SponsorBlock integration
• Closed captions system
• Platform-specific authentication flows
• Cross-platform content aggregation
Remember to:
Use consistent iconography
• The extension's role in enabling cross-platform functionality
• The modular parser system
• The unified player experience
• The caching and performance optimization systems