Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redesign recursive timeouts #53

Open
redlizard opened this issue Feb 10, 2017 · 0 comments
Open

Redesign recursive timeouts #53

redlizard opened this issue Feb 10, 2017 · 0 comments

Comments

@redlizard
Copy link
Contributor

The current timeout protocol requires that, if Alice gets timed out and Bob does not declare a timeout for Alice, Charlie needs to timeout Bob. If Bob then sets the timeout on Alice, Charlie needs to retract the timeout for Bob.

When there are multiple additional people in the conversation doing the same thing in regards to Bob, this can lead to nasty chaotic fluctuations leading to timeouts never happening.

This aspect of the protocol probably needs some redesigning. One possibility is to have each user announce, not timeout flags, but timeout levels -- if Charlie announces that Alice is timed out with level 2, that implies that everyone who has not yet timed out Alice is timed out with level 1 according to Charlie, implicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant