How bluesky-social/statusphere-example-app works
Main Components
a) Client-Side Components:
• Frontend UI Layer (src/pages)
• Authentication Module (src/auth)
• Lexicon Type System (src/lexicon)
b) External Services:
• AT Protocol/Bluesky Services
• OAuth Authentication Service
c) Data Flow Components:
• Ingester (src/ingester.ts)
• ID Resolver (src/id-resolver.ts)
• Database Interface (src/db.ts)
[Client Layer]
[Application Layer]
[External Services Layer]
Detailed Component Representation
a) Client Layer (Top):
• Auth Client module
• Use rounded rectangles for UI components
b) Application Layer (Middle):
• Create sections for:
• Lexicon System (showing type definitions)
• Data Ingestion Pipeline
• Database Interface
c) External Services (Bottom):
• AT Protocol Services
• OAuth Provider
Connection and Data Flow
• Authentication flow from Login → Auth Client → OAuth → AT Protocol
• Data flow from AT Protocol → Ingester → Database
• Profile and status data flow through the Lexicon system
• Client-side data requests through the view layer
Technical Details to Highlight
• OAuth Authentication Flow
• Custom Status Schema Implementation
• Profile Information Handling
• Network Firehose Integration
Remember to include notes about:
• Environment Configuration (.env)
• TypeScript Implementation (shown by tsconfig.json)
• Static Asset Handling (public folder)
• Lexicon Definitions (lexicons folder)
This will provide a comprehensive view of both the application's structure and its interaction with the AT Protocol ecosystem.