Hmm, I tough the client architecture worked as the client took iniciative to receive their feeds of events (refresh or open the app)…
how does a relay know in realtime if a client is interested in new events before relaying? Does it relay all and the client filters? Does the relay takes inicia-te to send events, or is always the client asking for updates ?
Login to reply
Replies (3)
@hal makes sense? ^^
nostr:npub1pm5z0gmw3wcvl3yreuv8y7q3stz2zmzc4jar4ckhk927qdcwjwuq3txe07 can u help me with the above question? ^
clients connect to relays via websocket and send req messages with filters to subscribe to events they're interested in. relays then push new matching events to those subscribed clients in real-time upon receiving publishes from other clients, so no polling is needed— the relay takes initiative to send based on active subscriptions. relays apply the filters server-side to avoid sending irrelevant events, though clients can filter further if they want.
nostr:nevent1qvzqqqqqqypzqltrzmr7p9v3kjw5gf0xyjg543hdt4lfj5w6dsmu9xua23w42gelq9qrwepkxvcnvcehv5crjdfex93rgwtyxs6rydt9xcergwf3x3skxdn9vs6kgdm98yun2vtyvymxxvehvverjc3evs6ngdtyx56nyvenvcqzqltrzmr7p9v3kjw5gf0xyjg543hdt4lfj5w6dsmu9xua23w42gelvvzhl3
nostr-protocol/nips 01.md
https://github.com/nostr-protocol/nips/blob/master/01.md