You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an option to RelayOptions which will automatically disconnect/blacklist/mark a relay once we receive:
too many events in a subscription (x more than the sum of all limit in the subscription filter array)
or an event that does not match the subscription filter
Use case
I trust the relays that the user specified in their nip65, but sometimes we need to connect to unknown relays which we should treat with caution because they might be malicious or buggy and sending us too many or even wrong events. It would be nice if we could easily close the connection once one of these cases are detected.
Additional context
I'm using your nostr-relay-pool crate
The text was updated successfully, but these errors were encountered:
Thanks for suggestion, I'll try to check how to implement this.
I'm using your nostr-relay-pool crate
In what project? I'm always curious to see how devs use Client or RelayPool in their app, to know how I can improve/fix the SDK (I usually don't work on frontends).
In what project? I'm always curious to see how devs use Client or RelayPool in their app, to know how I can improve/fix the SDK (I usually don't work on frontends).
It's a GUI for nostr git issues but it's still very early, only started it a few days ago. I will tag you on nostr once I release the first version.
Describe the enhancement
Add an option to
RelayOptions
which will automatically disconnect/blacklist/mark a relay once we receive:limit
in the subscription filter array)Use case
I trust the relays that the user specified in their nip65, but sometimes we need to connect to unknown relays which we should treat with caution because they might be malicious or buggy and sending us too many or even wrong events. It would be nice if we could easily close the connection once one of these cases are detected.
Additional context
I'm using your
nostr-relay-pool
crateThe text was updated successfully, but these errors were encountered: