This approach seems a little odd, why not post discrete events to follow and unfollow instead of editing and republishing a list? Just curious why we settled on that approach at the protocol level?
I’m not a protocol developer, so this is probably a better question for someone like @fiatjaf or @Ben Arc, but you can read the docs to see how events are handled.
Here’s how I understand it: Your client has to sign a JSON message using your privkey and post it to all of the connected write relays. There’s no way to guarantee which relay has the most recent version of the event, it if even has it at all, so the protocol assumes the one with the newest timestamp is the only one that matters. Sending little bits of data and hoping they will somehow be reassembled correctly on the other side doesn’t play nice with decentralization, unless you’re talking about mining and blockchains, and we’re not.
https://nips.nostr.com/1#kinds
Here’s how I understand it: Your client has to sign a JSON message using your privkey and post it to all of the connected write relays. There’s no way to guarantee which relay has the most recent version of the event, it if even has it at all, so the protocol assumes the one with the newest timestamp is the only one that matters. Sending little bits of data and hoping they will somehow be reassembled correctly on the other side doesn’t play nice with decentralization, unless you’re talking about mining and blockchains, and we’re not.
https://nips.nostr.com/1#kinds
2❤️2🤔1
