Nostr Web Client

Replying to

hodlbod

To all client developers:

- Stop using note1 entities, or add e tags with hints when quoting stuff

- Add pubkey hints to e tags (https://github.com/nostr-protocol/nips/pull/1171)

- Publish kind 10002 relay selections so other clients can find your users' content

Coracle frequently has trouble loading quotes because some popular client or other is doing none of these things.

Ademan 1y ago

As a side note, it might be useful for NIP-56 reports and NIP-32 labels to be able to provably associate an e tag with a pubkey by providing the signature from the offending event.

NIP-56 requires a p tag for the event author, but the report author could have lied about the pubkey unless you fetch the (potentially illegal) event. But with (pubkey, event id, signature) you can be sure of authorship without ever fetching it.

(A side-side note: why does NIP-56 even exist separately from NIP-32? It seems like just a special case of NIP-32?)

Reply to this note

Please Login to reply.

Discussion

hodlbod 1y ago

I agree, I drafted NIP 32 as a response to 56 which I thought was too narrow. But backward compatibility being what it is, 56 is never going away. Which is ok, I've learned since then that use-case specific nips are normally better than highly generic ones. NIP 32 has good use cases, but more protocol-specific interoperable features deserve first-class support.

Ademan 1y ago

Hah I didn't realize you wrote NIP-32, nor that NIP-32 is newer than NIP-56... how are numbers even assigned? lol

hodlbod 1y ago

They're squatted in PRs by NIP authors because fiatjaf has an arbitrary limit of 100 😂