4 ms·

> nostr is stateless it’s just a streaming protocol for messages I've brainstormed ways to solve this on top of Nostr. Perhaps I could write a program that dow

> nostr is stateless it’s just a streaming protocol for messages I've brainstormed ways to solve this on top of Nostr. Perhaps I could write a program that downloads all of the history of Nostr (or perhaps just the users I'm interested in?) and then my server would sign when I received the messages and create order out of that. Then if I get a message that claims to be from the past at some point in the future, I'd instantly be able to see that. I'd also be able to periodically ping relays and see what messages that are no longer being relayed and I'd have some curiosity about why that is happening. I just kind of wish this was baked into the protocol. But I sailed here from the Scuttleverse. I'm open to ideas about how to do this well.

curtisblaine 3y ago
> Perhaps I could write a program that downloads all of the history of Nostr Is this even possible? Won't relays throw away older messages at some point? Or are they supposed to scale infinitely?
- gkbrk 3y ago
  Some relays try to store messages for as long as possible (aside from cleaning up some really large spammy ones), some others keep a certain number of messages. There are some relays that have no storage at all, they only relay messages between connected clients and then discard the messages.
kdragon 3y ago
nostr has an early NIP that talks about publishing timestamp commitments to the bitcoin blockchain, using the open timestamp protocol