franzap

@alexgleason pubkey graphs are constructed from flat lists in both cases

I want to emphasize that this proposed kind is exclusive to **trusted** pubkeys. @alexgleason with NIP-32 I can indeed label someone as "developer" but that does not necessarily mean I...

@vitorpamplona Relays may remove older individual events, how do you deal with this? Chances of this happening with lists is lower as the timestamp gets refreshed with every modification

> I'm with @vitorpamplona on team NIP 32 or granular events. Yes, I can see the case for individual events > Aside from that, I think there are use cases...

> Apps can decide which tags they will use. The basic ones most apps would care about are "honest" and "judge". "honest" means this is not a thief or scammer...

> > IMO trust is so important that it should have a dedicated way of representing it. It should also be binary: do you trust this person for X or...

My use-case is much simpler (at least initially) but I see where you're going. Thanks for sharing. Are you planning to send a PR for that NIP? I probably will...

Appreciate your response. It's true that the intersection was small, I think 1-2 common relays. Just to clarify: I purchased a nostr.wine subscription and I'm trying to only use that...

@vitorpamplona Thanks and yes, absolutely. This way coming across any PGP key or certificate in the wild one can check if that identity is also on nostr. In my particular...

@Semisol if you confirm it will get merged I can make a PR to NIP-39