Posting to TOO MANY relays #771

Closed
opened 2024-05-27 14:49:04 +12:00 by mikedilger · 3 comments
mikedilger commented 2024-05-27 14:49:04 +12:00 (Migrated from github.com)

After the nip-17 work, normal top level posts are going to far too many relays.

After the nip-17 work, normal top level posts are going to far too many relays.
mikedilger commented 2024-05-27 14:51:20 +12:00 (Migrated from github.com)

probably post.rs get_others_relays() cause I tagged myself, and somehow storage.get_best_relays() is giving LOTS and we aren't cutting them off.

probably post.rs get_others_relays() cause I tagged myself, and somehow storage.get_best_relays() is giving LOTS and we aren't cutting them off.
mikedilger commented 2024-05-27 14:55:41 +12:00 (Migrated from github.com)

We need a way to call get_best_relays that only gets declared read/write relays OR a limited set (num_relays_per_person) if nothing is declared. Because we want to post to ALL their declared read relays, but we want to limit it when we are guessing.

We need a way to call get_best_relays that only gets declared read/write relays OR a limited set (num_relays_per_person) if nothing is declared. Because we want to post to ALL their declared read relays, but we want to limit it when we are guessing.
mikedilger commented 2024-06-17 09:53:22 +12:00 (Migrated from github.com)

I believe this is fixed now in 9d0b441263

I believe this is fixed now in 9d0b44126322adf40cbce7435f1b2bd63bdf8de2
Sign in to join this conversation.
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#771
No description provided.