Add Discord community API and live parties #26
Labels
No labels
status:done
status:in-progress
status:ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rexlManu/garmith-app#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Build a self-hosted TypeScript API with Discord OAuth, short-lived desktop pairing, friend requests, private parties, live WebSocket presence and persistent session runs. Store only required identity and run fields. Local development first, document Coolify configuration and migrations. Do not store Discord access tokens in the desktop renderer.
Source implementation complete in
2349360anddc4747f. Elysia/SQLite API includes Discord OAuth, one-time desktop pairing, revocable tokens, friends, private parties, authenticated WebSocket roster, stored runs and public leaderboards. Death events and schema v1 are persisted. Public rows contain character names, not Discord identity. API typecheck, 9 focused tests, full pnpm typecheck and pnpm test pass. Real Discord credentials, two-account traffic and Coolify are tracked in #29.Follow-up in
23df899: API schema v2 stores the Discord username from OAuth and rotates long party codes to six characters without changing party IDs or members. A friend request resolves an exact username among accounts that have signed in. Existing accounts must sign in again once to populate their username. Eleven API tests and workspace typecheck pass.