Tim, recall you talking about nostr in the past. If the content I'd signed (and presumably encrypted), then it is protected and verifiable as to the source with the public key.
Question, what about the sender and destination (routing)? How does nostr protect against detecting comes between parties. Asking this in the context that the ToIP "Trust Spanning Protocol" spent a lot of effort on strategies to prevent tracking routing between to parties or identification of the parties. How does nostr provide that while using public routing/distribution?
Routing is taken care of by relays. A more recent specification (NIP-17) does ‘gift wrapping’ in addition to encryption to take care of the metadata leaks. To the outside observer, it looks like you are receiving messages from completely random one-off senders that can’t be correlated. IMHO it solves most of the problems that TSP is concerned with.
Tim, recall you talking about nostr in the past. If the content I'd signed (and presumably encrypted), then it is protected and verifiable as to the source with the public key.
Question, what about the sender and destination (routing)? How does nostr protect against detecting comes between parties. Asking this in the context that the ToIP "Trust Spanning Protocol" spent a lot of effort on strategies to prevent tracking routing between to parties or identification of the parties. How does nostr provide that while using public routing/distribution?
Routing is taken care of by relays. A more recent specification (NIP-17) does ‘gift wrapping’ in addition to encryption to take care of the metadata leaks. To the outside observer, it looks like you are receiving messages from completely random one-off senders that can’t be correlated. IMHO it solves most of the problems that TSP is concerned with.
This NIP-17 - Private Direct Messages?
https://github.com/nostr-protocol/nips/blob/master/17.md
Appreciate this Tim! Best in 2025 🚀