Change-Id: I3a320c8f58633a2bfb271ff513732e53a0335d5a

Kateryna Kostiuk authored 3 years ago and Sébastien Blin committed 3 years ago

This reverts commit bbda1066.

Reason for revert: <prevent contact removal for one_to_one>

Change-Id: I88dfa67def9af9d1bd517384df48d1f59e4c34a6

Compress the image to a value under 48k to be able to send it
through the DHT.

Change-Id: I4eee67e0a667bb278d2099abaf5305ca0a767efc

+ use QFileLock on profiles to avoid any potential problems with
parallel updates
+ Do not update write files if nothing is updated

Change-Id: Iff1e1ac6a0363a0531f67d0e3a40ee99fa67a32d

Amin Bandali authored 3 years ago and Adrien Béraud committed 3 years ago

Change-Id: I948ea21e577d4ff9ccd69bfb22261432be7ba8b4

Change-Id: Ifaa93b3e92c5c932b18a83758c45ea48878e3cfb

Change-Id: I07633e7e1d6b689af30b38648d6c2d354cf2c029

Logic is handled by the daemon, nothing to do for removeConversation

Change-Id: I4bdf41c5d7d21cfd523409602004b668627ecadc
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I22b4fe8cd05d7f9c6b29f78fa00c6327f418032b

if there is other conversations with a contact, only the conversation
is removed, not the others

Change-Id: I6a7aa6fc4953c34fb46e68c7682d1891511b0017

After a sync, contactAdded will be emitted. But lrc was generating
a new conversation without the "added" information stored by the
daemon. Causing a smartlist with incorrect informations.

Change-Id: I5f05a905e831ec06353002fed40be403e3c753da
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: Ic1dca07904907ba9cfaefdc6b4a2df3737a97c50

Change-Id: I68fcfca5abff072741ae9e28cab44b29640b270d

Change-Id: I72e58f8aef09c07752169fbbc6194a2ef33b36d5

Change-Id: Ife955833aeb2cbfdbbeab0124558cbbcfe0ca6c7

Change-Id: I9679df3bda97d4401ea137088d006820154d141b

without it jami-client-gnome won't build

Change-Id: Ife26e5820a20740f6972bb70346e14e0489d6ba0

Use a few more accurate variable names, remove some redundant or old
logic, and better choice of displayed best name or id (also depends on
client-side change).

Change-Id: Iddd5d03649537813143a91702da521e631e1b2f2

Sébastien Blin authored 3 years ago and Amin Bandali committed 3 years ago

avoid changing the display.

Change-Id: If58239293bd2675064c694e32861cbae623ef163
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: I8e9e55951de044065e7e4540606c107246e67bb7

This makes sense only in one to one. For swarm, there will be no
read only as we can add a new conversation member. Also, we should
not see readOnly = true for conversations with self.

Change-Id: Ic404a6b58e7812fedfe2fede91beb77b44436526
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I6c16d3bd9890ce962c978a2aa1ac0a529deb9b27

Change-Id: Iba7814b2f849de7ac2424312c9460286e19f5fc5

Consider a conversation's read-only attribute when querying for indices
that match a given uri. This is done when searching for a conversation
associated to an interaction(in the rare case that more than one 1to1
conv exists).

Also remove all the conversations for a contact once the contactRemoved
slot is called.

Gitlab: #475
Change-Id: I637dbcf677a5e00b6b52320c3cd24fcd08cfacd6

GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282
Change-Id: Ie90a520acf900c5053ddbca980ff5b5bba3dcd63

Amin Bandali authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I0380ae8afa81ccf8ef18c624e44f97cc6517431e

Change-Id: Iee6512a8379a8414a84f843713732a35e0c375fc

Also fix setMessageDisplayed for clients

Change-Id: Ia2f8f586d88736a597e2271d2fd59402664ea3e6
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

The conversationUpdated signal can be used.

Change-Id: I5c61483e7d66840d07df5a76697527553b3c429a

Change-Id: I31f3177b0c7a2889d1097892a4d08e8d3c5d8beb
GitLab: https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/600

Change-Id: I88eadef0bcf272b74ffb73d3f0c41cdff6549731

Change-Id: I3a085db384848387d43cc9398eedb0439e8fe57f
GitLab: https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/599

Change-Id: I0045444f2f9f26bba8167d0da52da98ec3f3a2c7

If all other members have left the conversation, set a flag to
indicate a read-only status to be consumed by the UI.

Change-Id: I737688e52a2e28b30fb2f1a74ca5167c9c72911f
jami-client-qt#475

Ming Rui Zhang authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: Ia3264cee8f7649bb2e4e966a2c8d093947354834

To differentiate from accountStatusChanged

accountStatusChanged is emitted in onAccountDetailsChanged
any client code that actually depends on accountDetails and
connects to accountStatusChanged should switch the connection
to listen for accountDetailsChanged

Change-Id: I131493b831a2a6d32fae67c5c1af798a066e38a7

Change-Id: I97638128e6ebfe474f588ce55beb07ca34b76d28

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: Icfc67edcc2312b2b81b14768213c1f16038afcf6
GitLab: https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/592

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

GitLab: https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/591
Change-Id: I87dfe44f70fd0edf4ed6ad4276f4de813da462dd

After a conversation is made permanent, and a contact is added, the
conversation view will reload with the info hash in the header and
message send bar because the conversation becomes ready prior to the
contact being added to the list allowing for profile info queries to
be successful. This patch adds a PENDING contact item that will be
upgraded once the daemon adds the contact.

Gitlab: #479
Change-Id: Ie680bb61803812165f8f061e1cb8c21f77b381f7