nostr/gossip

Fallback read relays #160

New issue

Closed

opened 2023-01-22 15:37:05 +13:00 by mikedilger · 1 comment

mikedilger commented

2023-01-22 15:37:05 +13:00

(Migrated from github.com)

Most clients have a set of read relays. We read from anywhere. But sometimes we don't have enough data to know where to read from, and in those cases it would be nice if the user specified a few relays to try. The idea is if we can't figure out enough good relays to match settings.num_relays_per_person (which might get renamed as this is per event too), then we use the fallback read relays to pad it out.

Ideally we would keep trying if all those relays failed, but that's not gonna be ready for 0.4.

Most clients have a set of read relays. We read from anywhere. But sometimes we don't have enough data to know where to read from, and in those cases it would be nice if the user specified a few relays to try. The idea is if we can't figure out enough good relays to match settings.num_relays_per_person (which might get renamed as this is per event too), then we use the fallback read relays to pad it out. Ideally we would keep trying if all those relays failed, but that's not gonna be ready for 0.4.

mikedilger commented

2023-02-06 11:58:28 +13:00

(Migrated from github.com)

solved in #199

solved in #199

Sign in to join this conversation.

No labels

Good first issue

Major feature set

You're dreamin'

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

nostr/gossip#160

No description provided.