1a85a29b1b
chore: cover community sharding with tests
...
closes : #4262
2024-01-24 14:24:57 +01:00
436d229856
Add last opened at key for community ( #4514 )
2024-01-21 12:55:14 +02:00
926f6a3c72
Revert "test: bump go-libp2p"
...
This reverts commit d0ca4447c6
2024-01-18 20:29:33 +00:00
d0ca4447c6
test: bump go-libp2p
2024-01-18 14:28:06 +00:00
a5acffc001
fix: TestFetchRealCommunity with shards fleet ( #4553 )
...
* fix: TestFetchRealCommunity with shards fleet
* fix: DefaultShardPubsubTopic
* chore: print waku query request id
2024-01-16 13:38:41 +03:00
94bee02ef7
chore: fetch comunity token metadata during handling community description ( #4562 )
2024-01-16 09:08:56 +01:00
2a5dc6dec0
chore: remove boilerplate check of `communities.GetByID` clients
...
motivated by:
https://github.com/status-im/status-go/pull/4514#discussion_r1445808116
2024-01-10 18:58:17 +01:00
e1b52f9eae
Add joined at key to communities ( #4513 )
2024-01-09 20:36:47 +02:00
405d468e0e
fix: force verifiedOwner in `handleSyncInstallationCommunity` ( #4405 ) ( #4538 )
2024-01-08 15:57:57 +00:00
5c704b2ec2
chore: check and manualy verify community if during the fetchCommunity, community was added to the verification loop ( #4533 )
2024-01-05 18:09:38 +01:00
1d3c618fb4
feat: encrypt `CommunityDescription` fields
...
Extended `CommunityDescription` with a `privateData` map. This map
associates each hash ratchet `key_id` and `seq_no` with an encrypted
`CommunityDescription`. Each encrypted instance includes only data
requiring encryption.
closes : status-im/status-desktop#12851
closes : status-im/status-desktop#12852
closes : status-im/status-desktop#12853
2023-12-22 18:17:06 +01:00
134137f9c5
feat: implemented a mechanism to retrieve shard information for a given community ID ( #4499 )
...
* feat: a mechanism to retrieve shard information for a given community ID
2023-12-22 13:37:37 +01:00
6d77fb771a
fix(windows-build): Remove free space check for archives ( #4485 )
2023-12-20 21:21:02 +03:00
a5f6a6c2f6
fix: privileged member accepted/rejected request to join action is not approved by the control node after the member leaved and tries to join the community again ( #4487 )
2023-12-19 14:45:34 +01:00
e3ef8c649a
chore: store node requests manager ( #4446 )
2023-12-15 19:50:12 +00:00
90c31afe7c
New way of sharing communities ( #4341 )
2023-12-15 13:55:32 +02:00
af9d3bc7b3
fix(history-archive): Skip dowloading data from torrent if free space is not enought ( #4449 )
2023-12-14 12:52:10 +03:00
be8568e174
Community member joins the community if he sends a request to join an… ( #4321 )
2023-12-09 14:46:30 +02:00
fe604b2806
fix: tokenMaster does not have members revealed addresses ( #4425 )
2023-12-07 17:27:14 +01:00
04c533b8d5
chore: API for getting all non-approved requests to join for all communities ( #4422 )
2023-12-05 15:50:45 +01:00
058120fad9
chore: parse all non confirmed requests to join of the community during getting all communities ( #4409 )
2023-12-04 19:20:09 +01:00
9820acd74d
refactor(communities)_: delegate Community creation in Persistence
...
In persistence.go, the lack of sufficient knowledge for constructing
fully initialized Community objects required clients to manually call
`initializeCommunity`. This commit addresses the issue by delegating
Community creation to Manager. It also removes queries and logic
duplication.
2023-12-04 12:41:39 +01:00
317ad2f906
feat: Ignore AC notifications created before the request to join the community ( #4385 )
...
* fix: Ignore AC notifications created before the request to join the community
* review fixes
2023-11-29 19:28:04 +04:00
5cd20ded4e
chore: fix sending request to join msg's to the new owner ( #4371 )
2023-11-23 16:58:43 +01:00
d198ac63fc
fix: find free port for torrent
2023-11-22 16:41:27 -04:00
c012f94681
fix: send request on non protected topics, and add missing shard information on invite
2023-11-18 12:12:06 -04:00
1794b93c16
Always set PubsubTopic in filters
2023-11-18 02:26:34 +02:00
e17d4606b1
fix: implement cancellable collectibles requests
2023-11-17 10:35:30 -03:00
2c55b9c676
feat: cache curated communities in db
...
closes : status-im/status-desktop#12277
2023-11-16 17:21:28 +01:00
2c954d42cf
feat: replace DefaultPubsubTopic by Shard 32 ( #4161 )
2023-11-09 20:29:15 -04:00
b15fa6d2c8
fix: promote self to community control node event if we are not a community member ( #4270 )
2023-11-07 14:18:59 +01:00
4fddcb54ff
refactor: extract Community.ChatID
2023-11-04 00:11:40 +01:00
953ed4c8e4
chore: update directory abi and addresses
...
closes : status-im/status-desktop#12569
2023-11-03 17:56:21 +01:00
25f25e9853
chore: populate Community with PubsubTopicPrivateKey
...
part of: status-im/status-desktop#12408
2023-11-03 11:27:43 +01:00
11a3612290
feat: support signing of a join/edit community request from within the app or keycard
2023-11-03 07:49:01 +01:00
eb437e9d8d
feat: kick all members after ownership change and auto-accept after sharing the address ( #4187 )
...
feat: kick all members after the ownership change and auto-accept after sharing the address
2023-10-31 15:20:40 +01:00
627ac9449b
refactor: remove always nil `shard` parameter in `HandleCommunityDescriptionMessage`
2023-10-31 10:03:31 +01:00
0cac2af1db
fix(community): getting kicked out of a community should still spectate ( #4217 )
...
Fixes https://github.com/status-im/status-desktop/issues/12558
When getting kicked out of a community, before we used to leave the community completely, but just keep the filters on.
That created a problem when reopening the app, because the community disappeared and could even create a problem in desktop where it tried to open the last opened community but it's no longer there.
The fix now is that when getting kicked out, we instead just remove ourselves from the community and set Joined to false, but we keep the community spectated.
2023-10-27 15:20:08 -04:00
e304fe3344
chore: enable community rekey loop
2023-10-27 16:29:26 +02:00
445135eb94
fix: ensure receivedMessage.CommunityID in chat message handler is set
...
This enables clients to obtain invitation's community ID even when
description processing is queued.
part of: status-im/status-desktop#12481
2023-10-25 20:10:01 +02:00
3452eb72a8
refactor: remove community invitation only access
2023-10-25 17:34:37 +02:00
b262d7e88c
refactor: rename Community.OnRequest() -> AutoAccept()
2023-10-25 17:34:37 +02:00
b321f28c9d
refactor: update community access enum naming
2023-10-25 17:34:37 +02:00
23f71c1125
Fix encryption id && rekey with a single message
...
This commit changes the format of the encryption id to be based off 3
things:
1) The group id
2) The timestamp
3) The actual key
Previously this was solely based on the timestamp and the group id, but
this might lead to conflicts. Moreover the format of the key was an
uint32 and so it would wrap periodically.
The migration is a bit tricky, so first we cleared the cache of keys,
that's easier than migrating, and second we set the new field hash_id to
the concatenation of group_id / key_id.
This might lead on some duplication in case keys are re-received, but it
should not have an impact on the correctness of the code.
I have added 2 tests covering compatibility between old/new clients, as
this should not be a breaking change.
It also adds a new message to rekey in a single go, instead of having to
send multiple messages
2023-10-24 20:48:54 +01:00
bd245ab45b
refactor: unify `Owned()` and `ControlledCommunities()`
2023-10-22 21:50:41 +02:00
345851c396
feat: ensure unique control node across devices
...
closes : status-im/status-desktop#11962
2023-10-22 21:50:41 +02:00
05db628406
chore: omit `CommunityDescription` queuing if owner is already verified
2023-10-19 22:11:53 +02:00
74c13fd363
fix: setup owner as CommunityDescription signer after minting community owner token ( #4168 )
2023-10-19 13:03:41 +02:00
246b68a8c0
refactor: rename and simplify `UpdatePrivateKeyAndControlNode`
2023-10-18 22:32:29 +02:00
a9cde06e44
refactor: simplify community requests logic
...
With the recent introduction of pending states, the community requests
logic became more complex. This commit simplifies the flow and
appropriately delegates logic to its corresponding abstraction levels:
messenger, manager and community. Additionally, it eliminates
redundancies in notifications and request-saving mechanism.
2023-10-18 17:11:20 +02:00
Patryk Osmaczko
Ibrahem Khalil
Siddarth Kumar
Richard Ramos
Igor Sirotin
Mykhailo Prakhov
Boris Melnik
Mikhail Rogachev
Mykhailo Prakhov
Vitaly Vlasov
Dario Gabriel Lipicar
Sale Djenic
Jonathan Rainville
Andrea Maria Piana