Replying to Avatar Repeatedly nuked profile

-A relay might not record the time it received an event

-A relay might record the time it received an event but this information isn't exposed to clients

-A relay might record the time it received an event and this information is exposed to a given client but that client might not care to compare timestamps

-A relay might record the time it received an event and this information is exposed to a given client and that client might care to compare timestamps but from a discrepancy is unable to determine whether something suspicious is going on (are the event date and receipt date out of sync for THAT relay only, perhaps because the event was rebroadcast, and then which other relays to cross-reference before feeling confident enough to make a determination...)

And then someone indexes every known relay in the Nostr universe and offers an API for this specific purpose and that solves the problem :)
Avatar
ynniv 10mo ago

Nostr is Available and Partitionable, but not Consistent. I think it's a good tradeoff. If you want Consistency you can use open timestamps on the blockchain (which is Consistent and Available but not Partitionable)

Reply to this note

Please Login to reply.

Discussion

Avatar
Repeatedly nuked profile 10mo ago

Yup. As for the 'temptation of consistency', I think the direction it's going is multiple parties will simply crawl and index (or try to) all of Nostr to fill in the gaps. Primal does it, Ditto does it, Nostr.band does it, npub.world does it... who else? I can't see that train stopping.