[RFC] Capability handling in federated conversations #10680
Description
When a remote conversation is used by a local user, some capabilities need to be checked/respected from the remote server, while others need to be considered from the local server.
Here is a list with the current capabilities and my understanding where they should be read from. Having said that, some capabilities can be considered to "not diverge" at the moment, e.g. features that are available. But when a new API version would ever hit that requires us to remove a capability, the Server would say again whether remote or local controls it.
Details
Outdated list, refer to the docs/capabilties.md instead and check the actual capabilities.features-local and capabilities.config-local instead
features Flags
| Feature | Server | Comment |
|---|---|---|
audio |
||
video |
||
chat-v2 |
||
conversation-v4 |
||
guest-signaling |
||
empty-group-room |
||
guest-display-names |
||
multi-room-users |
||
favorites |
🏠 Local | |
last-room-activity |
||
no-ping |
||
system-messages |
||
delete-messages |
||
mention-flag |
||
in-call-flags |
||
conversation-call-flags |
||
notification-levels |
||
invite-groups-and-mails |
||
locked-one-to-one-rooms |
||
read-only-rooms |
||
listable-rooms |
🏠 Local | |
chat-read-marker |
||
chat-unread |
||
webinary-lobby |
||
start-call-flag |
||
chat-replies |
||
circles-support |
||
force-mute |
||
sip-support |
||
sip-support-nopin |
||
chat-read-status |
||
phonebook-search |
🏠 Local | |
raise-hand |
||
room-description |
||
rich-object-sharing |
||
temp-user-avatar-api |
🏠 Local | |
geo-location-sharing |
||
voice-message-sharing |
||
signaling-v3 |
||
publishing-permissions |
||
clear-history |
||
direct-mention-flag |
||
notification-calls |
||
conversation-permissions |
||
rich-object-list-media |
||
rich-object-delete |
||
unified-search |
🏠 Local | |
chat-permission |
||
silent-send |
||
silent-call |
||
send-call-notification |
||
talk-polls |
||
breakout-rooms-v1 |
||
recording-v1 |
||
avatar |
Should use remote because we load the image from remote as well? | |
chat-get-context |
||
single-conversation-status |
||
chat-keep-notifications |
||
typing-privacy |
🏠 Local for setting / |
|
remind-me-later |
🏠 Local | ❓ I guess we would want to trigger the reminders on our own server? |
bots-v1 |
||
markdown-messages |
||
session-state |
||
note-to-self |
🏠 Local | |
recording-consent |
||
message-expiration |
||
reactions |
||
chat-reference-id |
config Flags
| Feature | Server | Comment |
|---|---|---|
attachments > allowed |
🏠 Local | |
attachments > folder |
🏠 Local | |
call > enabled |
||
call > breakout-rooms |
||
call > recording |
||
call > recording-consent |
||
call > supported-reactions |
||
call > predefined-backgrounds |
🏠 Local | |
call > can-upload-background |
🏠 Local | |
chat > max-length |
||
chat > read-privacy |
🏠 Local | |
chat > has-translation-providers |
🏠 Local / |
Could check both and use the better matching one? |
chat > typing-privacy |
🏠 Local | |
conversations > can-create |
🏠 Local | |
previews > max-gif-size |
🏠 Local | |
signaling > session-ping-limit |
⛔ Not for user land | Used by the HPB only |
signaling > hello-v2-token-key |
cc @Ivansss @SystemKeeper @mahibi @Antreesy In case you want to skim over it and leave a comment.