On Fri, Oct 22, 2021 at 05:38:27PM -0400, Nick Mathewson wrote:
> In this circumstance, we _could_ say that we only build circuits to G1,
> wait for them to succeed or fail, and only try G2 if we see that the
> circuits to G1 have failed completely. But that delays in the case that
> G1 is down.
>
On Fri, Oct 22, 2021 at 05:36:48PM -0400, Nick Mathewson wrote:
> Title: Randomized schedule for guard retries
> Author: Nick Mathewson
> Created: 2021-10-22
> Status: Open
Looks great. It's an obvious improvement, and I don't see any downsides.
--Roger
__
```
Filename: 337-simpler-guard-usability.md
Title: A simpler way to decide, "Is this guard usable?"
Author: Nick Mathewson
Created: 2021-10-22
Status: Open
```
# Introduction
The current `guard-spec` describes a mechanism for how to behave when
our primary guards are unreachable, and we don't kn
```
Filename: 336-randomize-guard-retries.md
Title: Randomized schedule for guard retries
Author: Nick Mathewson
Created: 2021-10-22
Status: Open
```
# Introduction
When we notice that a guard isn't working, we don't mark it as retriable
until a certain interval has passed. Currently, these inte
