Add seperation of voice channels, creation of new ones, and move around users
This commit is contained in:
@@ -136,7 +136,7 @@ The API service normalises every `ServerInfo` response, filling in `sourceId`, `
|
||||
|
||||
`ServerInfo` also carries the server-owned `channels` list for each room. Register and update calls persist this channel metadata on the server, and search or hydration responses return the normalised channel list so text and voice channel topology survives reloads, reconnects, and fresh joins.
|
||||
|
||||
The renderer may cache room data locally, but channel creation, rename, and removal must round-trip through the server-directory API instead of being treated as client-only state. Server-side normalisation also deduplicates channel names before persistence.
|
||||
The renderer may cache room data locally, but channel creation, rename, and removal must round-trip through the server-directory API instead of being treated as client-only state. Server-side normalisation deduplicates channel names within each channel type, so a text `general` channel and a voice `General` channel can coexist while duplicate voice-to-voice or text-to-text names are still rejected.
|
||||
|
||||
## Default endpoint management
|
||||
|
||||
|
||||
Reference in New Issue
Block a user