guest-display-names - Display names of guests are stored in the database, can be set via API (not WebRTC only) and are used on returned comments/participants/etc.
multi-room-users - Users can be in multiple conversations at the same time now, therefor signaling now also requires the conversation token on the URL.
chat-v2 - Chat messages are now Rich Object Strings and pagination is available, the previous chat is not available anymore.
locked-one-to-one-rooms - One-to-one conversations are now locked to the users. Neither guests nor other participants can be added, so the options to do that should be hidden as well. Also a user can only leave a one-to-one conversation (not delete). It will be deleted when the other participant left too. If the other participant posts a new chat message or starts a call, the left-participant will be re-added.
read-only-rooms - Conversations can be in read-only mode which means people can not do calls or write chat messages.
config => attachments => allowed - Whether the user can upload files into a chat
config => attachments => folder - User defined folder where items should be uploaded to
config => conversations => can-create - Whether the user can create public and group conversations, if not only one-to-one conversations are allowed
force-mute - "forceMute" signaling messages can be sent to mute other participants.
conversation-v2 - ~~The conversations API v2 is less load heavy and should be used by clients when available. Check the difference in the Conversation API documentation.~~ Replaced by API v4 when conversation-v4 is set.
chat-reference-id - an optional referenceId can be sent with a chat message to be able to identify it in parallel get requests to earlier fade out a temporary message
conversation-v3 - ~~Whether conversations API v3 is available~~ Replaced by API v4 when conversation-v4 is set.
sip-support - Whether SIP can be configured and enabled by moderators. The conversations API will come with some new values sipEnabled which signals whether this conversation has SIP configured as well as canEnableSIP to see if a user can enable it. When it is enabled attendeePin will contain the unique dial-in code for this user.
chat-read-status - On conversation API v3 and the chat API the last common read message is exposed which can be used to update the "read status" flag of own chat messages. The info should be shown only when the user also shares their read status. The user's value can be found in config => chat => read-privacy.
listable-rooms - Conversations can searched for even when not joined. A "listable" attribute set on rooms defines the scope of who can find it.
phonebook-search - Is present when the server has the endpoint to search for phone numbers to find matches in the accounts list
raise-hand - Participants can raise or lower hand, the state change is sent through signaling messages.
room-description - A description can be get and set for conversations.
config => chat => read-privacy - See chat-read-status
config => previews => max-gif-size - Maximum size in bytes below which a GIF can be embedded directly in the page at render time. Bigger files will be rendered statically using the preview endpoint instead. Can be set with occ config:app:set spreed max-gif-size --value=X where X is the new value in bytes. Defaults to 3 MB.
delete-messages - Allows to delete chat messages up to 6 hours for your own messages or when being a moderator. On deleting the message text will be replaced and a follow up system message will make sure clients and users update it in their cache and storage.
rich-object-sharing - Rich objects can be shared to chats. See OCP\RichObjectStrings\Definitions for more details on supported rich objects and required data.
conversation-call-flags - Whether the room api provides the callFlag to tell apart video and audio calls
temp-user-avatar-api - Whether a temporary api is available to allow users to upload an avatar to their profile via an OCS endpoint.
conversation-v4 - Whether conversations API v4 is available. This also means that v1, v2 and v3 are not available anymore. The changes on API v4 allow a user to have multiple sessions in the same conversation on different devices which is incompatible with the data structure that was used by the previous APIs.
signaling-v3 - Whether signaling API v3 is available. This also means that v1 and v2 are not available anymore. The TURN and STUN server data is now returning all defined servers instead of a random one. Multiple entries for the same server are combined and using the urls array correctly now.
geo-location-sharing - Whether the geo-location rich object is defined and can be shared to the rich-object sharing endpoint.
voice-message-sharing - Shared files can be flagged as voice messages and are then presented differently in the interface
publishing-permissions - Whether the publishing permissions can be set for the attendees.
direct-mention-flag - The conversation list populates the boolean unreadMentionDirect when the user was mentioned directly (ignoring @all mentions) since their last visit
notification-calls - Whether the API to opt out of call notifications is available
conversation-permissions - Whether the default and custom permissions can be set for attendees.
~~config => chat => translations - List of translations tuples, JSON encoded sample {"from":"de","fromLabel":"German","to":"en","toLabel":"English"}. Those tuples should be provided as options when translating chat messages.~~ Due to some providers the list was too big causing issues in various clients. So the capability was replaced by boolean config => chat => has-translation-providers in Talk 18.
config => call => predefined-backgrounds - List of predefined virtual backgrounds. The files are in Talks img/ folder, accessible via the normal image path methods. The list is cached for 5 minutes.
config => call => can-upload-background - Boolean flag whether the user can upload a custom virtual background (requires an account and non-zero quota). Uploads should be done to Talk/Backgrounds/ (respecting the user's attachment directory setting).
config => call => supported-reactions - A list of emojis supported as call reactions. If the list is absent or empty, clients should not show the emoji reaction option in calls.
config => chat => typing-privacy - User defined numeric value to enable 1 or disable 0 the typing indicator to other users
media-caption - Whether media caption can be added to shared files
session-state - Sessions can mark themselves as inactive, so the participant receives notifications again
note-to-self - Support for "Note-to-self" conversation exists
recording-consent - Whether admins and moderators can require recording consent before joining a call
sip-support-dialout - Whether admins can enable SIP dial-out
config => chat => has-translation-providers - When true, translation tuples can be loaded from the OCS Translation API.
config => call => recording-consent - Whether users need to consent into call recording before joining a call (see constants list)
config => call => sip-enabled - Whether SIP is configured on the server allowing for SIP dial-in
config => call => sip-dialout-enabled - Whether SIP dial-out is configured on the server, additionally requires config => call => sip-enabled
config => call => can-enable-sip - Whether the current user is a member of the groups that are allowed to enable SIP dial-in on a conversation or use SIP dial-out