Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Else, the mute state is ignored, causing the new member to be able
to listen from the host even if the host muted itself.

jami-client-android#1351
Change-Id: Ic0e4f7ac99fd945847f47c9e2e4573fa1d6a1b1a

Xavier Jouslin de Noray authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I42922bdff891b572e0193f5e0fdf9050c9a81c3a

Change-Id: I7a5a0f1f1b97ec7681b15eaea535f400219c4cc9

Change-Id: I3f6ef655d88039e401ff00bcad5992db38357c69

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I2f41093e1a5ef4ec31b5e3ba1c9a79c8b9e7826c

Nothing prevents setup() to be used while deleting onSuccessfulSetup_
So checking if (onSuccessfulSetup_) in setup() can cause a crash.
loop_.join() should prevent any call to onSuccessfulSetup_ and
any potential crash

Change-Id: I5fef00edbcc9701a3129a31b247472e62b6453d9

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

jami-client-qt#1354
Change-Id: I1153a1dfd3215b3fb03afe9b3ac4f39aad99fdf8

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I22b1b79a484b55701570db44dcd2c0387703ff9b

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I259a0ca7cdc7d98f89d93ecf37c362af16d9cf85

Alexander Lussier-Cullen authored 1 year ago and Adrien Béraud committed 1 year ago

Normally with 1440p or higher video, the upward bitrate adjustment can
take awhile to reach acceptable levels for the resolution. Starting
these at a higher bitrate will allow the adjustment to be made more
quickly. Also, the maximum bitrate of 6000kbps is potentially
insufficient for these higher resolutions, so this is also adjusted.

The constant values used for the bitrate and max bitrate calculation
are mostly arbitrary and simply fit what values seem to work best for
1440p and 4k video.

Change-Id: I746eeddae5ac8183039cb757bba881475b9e2907

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

737e2f11 introduces a regression
where "uri.crt" is replaced by "uri/crt", causing incorrect path
and breaking the vote system

Change-Id: Ibe5dff8335c2f989dc1de944c1cc538d4a7f6489

Change-Id: I4e87c32581695ca535cc431dfa8b8a1c64e06028

Change-Id: I85ce6b6b8596a755648b20ade3aabc314e4e259a

Change-Id: I1f0db645d5d84462825a1630430673ad8b8f50ff

Change-Id: Ia2f2eada788e6dd81e2442a0f384943ea3efa8ad

Change-Id: Ifc8e85cad40def55606591c4267a81b0a3d90951

Change-Id: I566a66b7405afe680bacd0e343ea7ac0901b912c

Change-Id: I4482ddabb8c6a7a22b2ed897a2294fab576efaa3

Change-Id: I30915805e03c2600f038fe465e744163d81a4b08

Change-Id: I5cca1a60c496ce4b638b599649fdb41312b4e534

Change-Id: I537b966c8698a1c8ed366877ff971bfba05bdfab

Adrien Béraud authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I680b550f6412925e0fac0e732f40e7e319f01cc8

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

Change-Id: I78452bbf94852c63f298d7fa0392909b1ef93c37

Change-Id: I4037895ce57758541e61a89b7efeaccd71e79c5a

Change-Id: I3b9fd9da90d153b2b4ce8254fa14216ea87eb7bd

Change-Id: I0ecc36493d10399c72a52aa1aa2dad48ee182296

Change-Id: Ibe9b4979375b71d9516ed6670ed234086bbb7f84

GitLab: #1356
Change-Id: I15d0633ea97283bee31e3dd5dcb382c0d8156f7f

GitLab: #897
Change-Id: I4c95c34601c4361476b0a520c262b93fb1da99c2

Change-Id: Ifb8766660941c75f9ab394b53a4dc62e7cca8e3d

GitLab: #898
Change-Id: I95a78e9b0745da6ed84b494d6ed9a95c89b9d392

+ bump opendht

NOTE (Windows): we move the gnutls_global_init function such that it's called prior to initializing the plugin manager

GitLab: #896
Change-Id: I85ddced2ee39912e14e477ea930f0e84e6e5830b

Change-Id: I30a9173b556b24b749735efea24f825eed8b0819

Adrien Béraud authored 1 year ago and Sébastien Blin committed 1 year ago

Change-Id: I51c2058d9916c0f7307ce026aa08fc6b060fa85e

Change-Id: I88dd2fdd903946e09b8647c6801a2ee706f94470

Sébastien Blin authored 1 year ago and Adrien Béraud committed 1 year ago

If a new device is doing some actions for the first time, the merge
will detect a new certificate that is not yet in the certificate
store (unless if the sender is the new device).
This will block the validation. So, instead, use the certificate
in the processed commit.

GitLab: #892
Change-Id: I0ab492e700a2aa7ef4258e2bf711117f67e29fae

Change-Id: I9b65b0121d228ab62abaf781c4dc11a6a9380ab4

Change-Id: Ie23601dcec4846e043457c83604edcc916d2917e

Change-Id: Iebff35b4ff943a7bf515909d6663484d95312d6d

Change-Id: I0c1a0f7a3238f45b3dcb69d0714b24b5d78eed52