Persistent Chat Rooms

[salmad3]

Overview:

Based on the team’s and Jae’s insights, we'd like to introduce first‑party rooms that teams can create, keep private or public, and rely on long‑term. v1 can prioritize fast launch and owner controls over encryption.

Objectives:

• Replace external chats with native rooms
• Minimize learning curve (owner/admin/member)
• Provide REST/WebSocket primitives for future clients

Requirements:

Room Creation & Lifecycle

• Logged‑in users can create rooms (+ New Room)
• Metadata: name, description, visibility (public, invite‑only, unlisted)
• Creator becomes owner; ownership transferable with confirmation
• Rooms do not auto‑delete; mark inactive (>90d) but keep accessible

Membership & Invites

• Public rooms discoverable via search + permalink (/rooms/{slug})
• Private rooms via invite; expiring links for owners/admins
• Unlisted rooms require direct invite (no listing/search)
• Membership list shows role and join date; exportable

Roles & Permissions

• Roles: owner, admin, member
• Admin toggles (invite, pin, delete messages, mute members)
• Per‑room ability presets; sensible defaults

Messaging UX

• Real‑time WebSocket feed with optimistic send + retry
• Message types: text, emoji reactions, attachments, system events
• Pin messages; topic/announcement banner
• Typing/presence indicators for up to 50 participants

Security & Abuse Controls

• Kick, ban, mute (duration + reason) by owner/admin
• Integrate with the moderation command center
• Per‑room rate limits to prevent spam

Current State:

• No rooms, room_members, or message tables exist
• No WebSocket servers, pub/sub, or room routes
• Frontend has no room components/routes; single‑feed only
• No room‑scoped moderation or permissions
• Auth/session not designed for chat subdomain/token exchange
• No broker, rate limiting, or monitoring for chat traffic

Dependencies:

1. Auth/session sharing between main app and chat surface
2. Messaging broker and WebSocket service
3. Moderation hooks from the admin/mod command center
4. Media pipeline reuse for attachments