obscura-server 0.6.2

A server for relaying secure messages using the Signal Protocol
Documentation
# Architecture

Obscura Server acts as a passive relay between Signal Protocol clients. It manages the discovery of cryptographic material and the queuing of encrypted blobs.

## Message Relay Flow

The following diagram illustrates how Alice sends an end-to-end encrypted message to Bob using the Obscura relay.

```mermaid
sequenceDiagram
    participant A as Alice (Client)
    participant S as Obscura Server
    participant B as Bob (Client)

    Note over A,B: Registration
    A->>S: Upload Identity & PreKeys
    B->>S: Upload Identity & PreKeys

    Note over A,B: Message Exchange
    A->>S: Request Bob's PreKey Bundle
    S-->>A: Bob's Public Keys (Identity, Signed, One-Time)
    A->>A: Perform X3DH (Generate Shared Secret)
    A->>S: Send Encrypted Message (Bob)
    S->>S: Store Opaque Blob
    S-->>B: Real-time Poke (WebSocket/Push)
    B->>S: Fetch Pending Messages
    S-->>B: Bob's Encrypted Blobs
    B->>B: Decrypt with Shared Secret
```

## System Components

- **API Layer**: Handles REST requests for account management, key uploads, and attachment handling.
- **Gateway Service**: Manages long-lived WebSocket connections for real-time delivery.
- **Background Workers**: 
    - **Cleanup**: Periodically prunes expired messages and attachments.
    - **Push Notifications**: Sends fallback notifications when clients are offline.
- **Storage Adapters**:
    - **PostgreSQL**: Stores persistent user metadata, keys, and message envelopes.
    - **Redis (Valkey)**: Powers the real-time notification bus and task queue.
    - **S3**: Stores encrypted attachments.