You might think that relays ought to send notes among themselves, but that is not the case. Nostr relays do not form a network amongst themselves, and behave mostly as a single hop to "relay" notes between two clients.
So in order to actually see the notes you want to see, you have to get notes from a lot of different relays. And you, as the client, must be responsible for making sure your recipients' relays have your notes.
So with the clients handling the logic of routing notes to their correct destinations, would it not be more prudent to call them the Relays? And with relays dependent on clients to provide their content, are they not, rather, the Clients?
Replies (4)
Wait there's no goddamn way they made the client figure out where to put notes. The Outbox relays are where you put notes. You have to be wrong. If not, what the fuck are Amethyst and nostr devs even doing?!
An aggregator/proxy relay can be added to make the client more efficient as regards fetching notes. If I am not mistaken, the aggregator itself requests notes and makes copies of them. Relay to relay. I use one. The aggregators can themselves use the Outbox model to ensure it fetches all the right notes. And I thought they used published Outboxes in Outbox model, on a nostr event that describes your Outboxes, not info from the client.
What we should be doing is having blaster relays that shoot their shit to other relays according to an Inbox model in addition to this.
It's my understanding, and I could be wrong, that you put notes in your Outbox relays. But when you reply to someone's note, it makes sense to also send those replies to the mentioned users' Inbox relays. And when you want a user's notes, you get them from that user's Outbox relays.
I think that's what Amethyst does now. And now I'm all thought up in knots, and I'm going to take a break.
🤣🤣🤣🤣 it is really complex :turtlehappy:
