Users

The account surface: signing in at /login (Google, GitHub, or Facebook — see the auth architecture) and managing your identity at /user/settings — display name, biography, and profile image, the identity every product (posts, messages, achievements) renders.

How it works

• Login — a provider-button card (LoginButton per provider) driving better-auth's social sign-in; the guest middleware keeps signed-in users out.
• Settings — an introduction card plus a sidebar of sections: Profile, Linked Accounts, and Sessions, each highlighted as it scrolls into view (section navigation). Name and biography save through user.updateUser (biography length enforced by the users schema).
• Profile image — the standard two-step SAS upload: user.generateProfileImageUploadUrl returns a one-hour write SAS for the fixed blob ${userId}/ProfileImage in the public user-assets container, the client PUTs the image, and the stable public URL is saved on the user.
• Account linking — one account can hold several social providers, listed and managed at /user/settings. See account linking.
• Public profile — every user has a public page at /user/[id] showing their identity, achievement showcase, and posts. See public profile.
• Sessions — every active session listed at /user/settings, revocable one at a time or all but the current one, with push subscriptions and live connections going with the session. See session and device management.
• Message-scoped user state (presence/status, voice settings, per-room personas) is esbabbler's, not this page's — see profiles and presence and settings.

Procedures

Key files

Paths relative to packages/app/app.

Open work: roadmap. Decided ideas: deferred, rejected.