You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the initial implementation, the invite data on the server can provide the information required for a peer to connect to the network, but it doesn't need to provide message history or channels.
As a very basic implementation, we could do something like the following. When joining via a v2 invite link, the user calls a new DOWNLOAD_INVITE_DATA endpoint where the backend fetches the invite data from the server and returns it to the user. The backend can fetch the invite data from the server using purely NodeJS to start with. Once, the invite data is returned to the user, the user continues as they normally do to connect to the network by calling CREATE_NETWORK/LAUNCH_COMMUNITY.
The text was updated successfully, but these errors were encountered:
leblowl
changed the title
Prepare client's data fetching & injecting module
Update Quiet to connect to server when joining community
Feb 21, 2024
leblowl
changed the title
Update Quiet to connect to server when joining community
Relay: Update Quiet to connect to server when joining community
Feb 21, 2024
leblowl
changed the title
Relay: Update Quiet to connect to server when joining community
QSS: Update Quiet to connect to server when joining community
Mar 4, 2024
For the initial implementation, the invite data on the server can provide the information required for a peer to connect to the network, but it doesn't need to provide message history or channels.
As a very basic implementation, we could do something like the following. When joining via a v2 invite link, the user calls a new DOWNLOAD_INVITE_DATA endpoint where the backend fetches the invite data from the server and returns it to the user. The backend can fetch the invite data from the server using purely NodeJS to start with. Once, the invite data is returned to the user, the user continues as they normally do to connect to the network by calling CREATE_NETWORK/LAUNCH_COMMUNITY.
The text was updated successfully, but these errors were encountered: