status-go/static
Pascal Precht f6c9ec7838 refactor: Require request access for all communities
This commit introduces a few changes regarding users accessing
communities:

While the APIs still exist, community invites should no longer be
used, instead communities should merely be "shared".
Sharing a community to users allows users to "join" the community,
which in reality makes them request access to that community.
This means, users have to request access to any community, even if
the community has permissions set to NO_MEMBERSHIP
Only difference between ON_REQUEST and NO_MEMBERSHIP is that
ON_REQUEST communities require manual approval of the owner/admin
to access a community. NO_MEMBERSHIP communities accept
automatically (as soon as owner/admin receives the request).
This also implies that users are no longer optimistically added to the
member list of communities, but only after they have been accepted.

This introduces a bit of a message ping-pong for users to know that
someone is now part of a community
2022-07-08 13:16:12 +02:00
..
keys Streamline configuration in status-go. Part of #1180 (#1183) 2018-09-13 18:31:29 +02:00
mailserver_db_migrations Shorten loop on waiting for community 2021-09-24 10:12:42 +01:00
test-0.97.3-account chore: test that login still works with 0.97.3 (#2661) 2022-05-04 10:46:49 -04:00
bindata.go refactor: Require request access for all communities 2022-07-08 13:16:12 +02:00
emojis.txt feat: add visual identity service (#2550) 2022-03-11 16:17:48 -05:00
static.go feat: add visual identity service (#2550) 2022-03-11 16:17:48 -05:00