-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inter Relay Communication #1814
Comments
check nip-77. |
It's important, but a wide topic. Could you narrow to some use case(s) |
https://github.com/nostr-protocol/nips/blob/negentropy/77.md this? it just seems to be a bandwidth optimization when same events from different relays are there.
one use case would be, a relay that combines events from 2 or more relays. |
Relays can behave as clients and connect to other relays using the nostr protocol. |
from nostr.wine's filter relay
So I think having some inter-relay spec in these NIP's can halp us provide these things even not fully but still.
|
To repeat Mike, the client/relay paradigm is just the sort of basic gist of how nostr is architected. Clients can act like relays, and relays can act like clients. Relays can have varying policies, additional protocols can be created to complement relays/clients (examples: blossom for files, multiplextr for deduplicating results server-side, primal-server, bitvora's stuff for wot filtering, algorithms, etc). These solutions are application architecture level and don't really need to be specified per se. The selection of different solutions can happen on the client level, and even on the user level. |
I don't see any discussion on this. so wanted to know why this is not something we want?
The text was updated successfully, but these errors were encountered: