diff options
author | Joas Schilling <coding@schilljs.com> | 2019-07-05 18:01:54 +0300 |
---|---|---|
committer | Joas Schilling <coding@schilljs.com> | 2019-07-05 18:01:54 +0300 |
commit | 09255e8beae5a59f06cd4522cbd5a6ec4d80c54b (patch) | |
tree | 144e1561d61a767cf148bee7bc59ce8c5b76d19e /docs/capabilities.md | |
parent | 4e65251fa3caa4d797a0cf7cfa3af648aa264952 (diff) |
Start converting to readthedocs
Signed-off-by: Joas Schilling <coding@schilljs.com>
Diffstat (limited to 'docs/capabilities.md')
-rw-r--r-- | docs/capabilities.md | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/docs/capabilities.md b/docs/capabilities.md new file mode 100644 index 000000000..494c06272 --- /dev/null +++ b/docs/capabilities.md @@ -0,0 +1,34 @@ +--- +title: Capabilities +--- + +## 3.0 (Initial Talk release) +* `audio` - audio is supported +* `video` - video + screensharing is supported +* `chat` - simple text chat is supported, superseded by `chat-v2` + +## 3.1 +* `guest-signaling` - Guests can do signaling via api endpoints +* `empty-group-room` - Group conversations can be created without inviting a Nextcloud user group by default + +## 3.2 +* `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](https://github.com/nextcloud/server/issues/1706) and pagination is available, the previous `chat` is not available anymore. + +## 4.0 +* `favorites` - Conversations can be marked as favorites which will pin them to the top of the conversation list. +* `last-room-activity` - Conversations have the `lastActivity` attribute and should be sorted by that instead of the last ping of the user. +* `no-ping` - The ping endpoint has been removed. Ping is updated with a call to fetch the signaling or chat messages instead. +* `system-messages` - Chat messages have a `systemMessage` attribute and can be generated by the system +* `mention-flag` - The conversation list populates the boolean `unreadMention` when the user was mentioned since their last visit +* `in-call-flags` - A new flag `participantFlags` has been introduced and is replacing the `participantInCall` boolean. + +## 5.0 +* `invite-by-mail` - *Replaced by `invite-groups-and-mails`* Guests can be invited with their email address +* `notification-levels` - Users can select when they want to be notified in conversations +* `invite-groups-and-mails` - Groups can be added to existing conversations via the add participant endpoint + +## 6.0 +* `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. |