How timelinize/timelinize works
Main System Components
a) Frontend Layer
• Single-page web application (evident from frontend/resources/js/spa.js)
• Multiple views (dashboard, timeline, map, gallery, conversations, etc.)
• Static resources (CSS, JS, images)
b) Backend Layer (Go-based)
• Main application server (tlzapp package)
• Timeline processing engine (timeline package)
• OAuth2 client system (oauth2client package)
• Data source processors (datasources package)
c) Storage Layer
• SQLite database (referenced in timeline/schema.sql)
• File system storage for media and imported data
Key Relationships to Highlight
a) Data Flow
• External services → OAuth2 Client → Data Source Processors
• Data Source Processors → Timeline Processing Engine → Database
• Frontend → Backend API Endpoints → Timeline Engine
• Timeline Engine ↔ File System Storage
b) Processing Flow
• Import Process: Raw Data → Data Source Processors → Timeline Processing
• Query Process: User Request → API → Timeline Engine → Database/Files → Response
Specific Components
Data Sources (group these visually):
• Social Media (Facebook, Twitter, Instagram)
• Communication (iMessage, Gmail, Telegram)
• Location (Google Location, GPX, NMEA)
• Media (Photos, Videos)
• Contacts (Apple Contacts, vCard)
Processing Components:
• Entity Recognition System
• Location Processing
• Media Processing
• Timeline Aggregation
• Search Infrastructure
Important Subsystems to Detail
a) Data Import Pipeline
• File recognition
• Format processing
• Entity extraction
• Timeline integration
b) Query Processing
• User interface requests
• API routing
• Data aggregation
• Response formatting
Technical Details
Annotations for:
• Go-based backend
• SQLite database
• HTTP/JSON API
• OAuth2 authentication
• File system organization
• Browser-based frontend