Age | Commit message (Collapse) | Author |
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
nextcloud/techdebt/noid/make-checksum-verification-generic
techdebt(api): Make the checksum verification generic so it can be re…
|
|
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
* Added the header X-NC-IsCustomAvatar
* Return every time a non empty string as avatarVersion
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
files into memory
Signed-off-by: Elmer Miroslav Mosher Golovin <miroslav@mishamosher.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
it's the same on all clients
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
feat(virtual-background): Add capabilities for predefined virtual bac…
|
|
backgrounds and whether users can upload custom ones
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
actor ended the call
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Revert https://github.com/nextcloud/spreed/pull/8805
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
https://github.com/nextcloud/spreed/pull/9072/files#r1142350857
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
https://github.com/nextcloud/spreed/pull/8333 introduced an optional `icon-url`
for the call objects in rich messages.
https://github.com/nextcloud/spreed/issues/8389
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
The property config isn't used at this class
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
nextcloud/feature/noid/mark-notifications-as-read-in-receive-messages
Allow to receive messages without marking notifications as unread
|
|
Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
nextcloud/feature/send-notification-when-get-upload-problem
Send notification when get upload problem
|
|
Change type of notification
Add the new type to be deleted
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Remove avatar capability
|
|
Although recordings should not fail in some cases they could (for
example, if the configuration is wrong, the disk is full...). A new
recording status, "failed", has been added to notify that situation to
the Nextcloud server from the recording server.
Typically call participants will not be able to do anything about the
failure, so the clients can just show a notification to the moderators
and hint about asking the system administrators.
In any case, even if the recording status is "failed" further recordings
can be started, which will behave as if the recording was started from
the "none" status.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
As starting the recording can take some time "starting" values were
added to signal that an audio or video recording is starting. The
status will be changed from NONE to STARTING_VIDEO/AUDIO by the
Nextcloud server when the request to start the recording succeeds, and
then the recording status will be set to VIDEO or AUDIO by the recording
server once the recording actually started.
Stopping the recording, on the other hand, should be quite fast, so no
STOPPING status were added.
The system messages were also adjusted to be sent only once the
recording really started or stopped.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
The participant will be in turn forwarded again to the Nextcloud server
once notified that the recording started or stopped so it retains the
proper participant (for example, in system messages) rather than using
the recording server.
The actor is optional when stopping the recording, as the recording
could be implicitly stopped when the last participant leaves the call.
Nevertheless, this causes the system message to be assigned to a guest
(as the request comes from the recording server), which is unexpected,
so this may need to be adjusted.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
This makes possible to set a different participant than the current user
as the participant who started or stopped the recording, which is needed
now that the recording status is changed in a request from the recording
server.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
nextcloud/use-internal-client-of-signaling-server-for-recording
Use internal client of signaling server for recording
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
The signaling settings for a specific conversation could be got only by
the participants of that conversation. Now it is possible to get them
too from the recording server through the recording secret.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
The owner of the recording must be provided when starting it to be able
to later store it.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
If the external signaling server is used, when a participant is
disinvited it is expected that the client leaves the conversation if
still in it. Therefore, self-joined users should not be disinvited when
they disconnect from a conversation, as they can still have other
sessions in it.
To ensure that self-joined users will be disinvited when their last
session leaves the conversation now a USER_REMOVE event is explicitly
triggered when that last session leaves and the user is, in fact,
removed from the conversation.
Note that this does not cause the system message about the participant
leaving to be sent, as it is explicitly guarded against self-joined
users leaving the conversation. However, this change will cause other
handlers to be called now, like those to invalidate resources, but it is
very likely that they should have been called and that this change is
actually a fix too in that regard.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
When the breakout room status changes a "switchto" message is sent to
all the active sessions in either the parent or the breakout rooms
(depending on whether they are being started or stopped) with the token
of the room that they have to switch to.
When the breakout rooms are started the message is sent only to non
moderators, as moderators do not have a single breakout room assigned.
On the other hand, when the breakout rooms are stopped the message is
also sent to all moderators (who are in a breakout room and not already
in the parent room), as all participants need to switch to the parent
room.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|