Skip to content
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.

Nectar/waggle should try to call registrar a few times before giving up #10

Closed
EmiM opened this issue Sep 13, 2021 · 2 comments
Closed

Nectar/waggle should try to call registrar a few times before giving up #10

EmiM opened this issue Sep 13, 2021 · 2 comments
Projects
Quiet

Comments

@EmiM
Copy link
Contributor

EmiM commented Sep 13, 2021

No description provided.

@EmiM EmiM created this issue from a note in Quiet (On hold for now) Sep 13, 2021
@EmiM EmiM changed the title Nectar should try to call registrar a few times before giving up Nectar/waggle should try to call registrar a few times before giving up Sep 13, 2021
@holmesworcester
Copy link

For this I think it should actually retry forever, on some cycle. This way, when both the admin user (running the registrar) and the invited user are online at the same time, a connection will be made and registration can take place.

@holmesworcester
Copy link

Nectar / waggle would communicate this "registrar offline, retrying" state to the frontend so that the user could be notified

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
Quiet
Archived in project
Quiet
Backlog - Desktop & Backend
Milestone
No milestone
Development

No branches or pull requests
3 participants
@holmesworcester @EmiM @vinkabuki