Skip to content
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

Open
securitybrahh opened this issue Feb 28, 2025 · 6 comments
Open

Inter Relay Communication #1814

securitybrahh opened this issue Feb 28, 2025 · 6 comments

Comments

@securitybrahh
Copy link

I don't see any discussion on this. so wanted to know why this is not something we want?

@kehiy
Copy link
Contributor

kehiy commented Feb 28, 2025

check nip-77.

@melvincarvalho
Copy link

I don't see any discussion on this. so wanted to know why this is not something we want?

It's important, but a wide topic. Could you narrow to some use case(s)

@securitybrahh
Copy link
Author

check nip-77.

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.

It's important, but a wide topic. Could you narrow to some use case(s)

one use case would be, a relay that combines events from 2 or more relays.

@mikedilger
Copy link
Contributor

Relays can behave as clients and connect to other relays using the nostr protocol.

@securitybrahh
Copy link
Author

securitybrahh commented Mar 3, 2025

from nostr.wine's filter relay

  • Improve performance and reliability (no duplicate notes, one high performance relay connection instead of 10+)
  • Reduce battery and data usage on mobile devices
  • Improve content discovery (see notes outside of your follows but still within your trusted network)
  • Reduce spam (by default "global" on filter.nostr.wine is limited to the accounts you follow + the accounts your followers follow)
  • Full text search of all aggregated notes (https://search.nostr.wine or NIP-50

So I think having some inter-relay spec in these NIP's can halp us provide these things even not fully but still.

In addition to NIP-65, these are the public relays Filter is currently broadcasting events to in real time:

These are the relays that we are currently aggregating events from in real time:

@staab
Copy link
Member

staab commented Mar 3, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants