{ "id": "29e8643eb9e1680621b2029c08e9a63e5c395a35fee86b8a3fa6fdf74bfaacb7", "pubkey": "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d", "created_at": 1763106842, "kind": 1621, "tags": [ [ "subject", "bug: resilience issues with `Relay::try_connect`" ], [ "alt", "git repository issue: bug: resilience issues with `Relay::try_connect`" ], [ "a", "30617:68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272:nostr" ], [ "a", "30617:e740f5878098eba1a0a81d2504ee0171c4e79b75f92534da33f7f620f3ea0b0d:nostr" ], [ "p", "68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272" ], [ "p", "e740f5878098eba1a0a81d2504ee0171c4e79b75f92534da33f7f620f3ea0b0d" ] ], "content": "`Relay::try_connect` is less reliable at establishing a connection than say nak, or other web based tools.\n\nUnder certain network conditions, and with specific relays, `Relay::try_connect` will consistantly fail where nak will consistantly succeed (usually after a short delay \u0026lt;2s and the configured timeout). During these periods I can repeat the connection 10+ times.\n\nThis hasn't been too noticable as connections to other relays pick up the slack but sometimes important events are only on that relay.\n\nI started noticing it with v0.43 but it may have been like this for a while.\n\nHave you noticed this? Next time this happens I'll try and investigate and debug further.", "sig": "1386f408bb723c3575f3e23d144fc141b3cbc24449fa71999c324b8c4320b956419b53bc6bf1bba23fe26823299f371bd58e73e535055e20076205e468f98405" }