Closed BrunswickBTC closed 1 year ago
Add support for pubkey prefixes (truncated key) in subscription requests.
@BrunswickBTC can you please provide here some examples of "pubkey prefixes (truncated key)"
@motorina0 I don't understand your request. Can you be more specific?
@motorina0 I don't understand your request. Can you be more specific?
Yes:
Add support for pubkey prefixes (truncated key)
- I do not know what these (
pubkey prefixes
) are, can you please provide some examples- in what NIP are they defined?
It is defined in NIP-01. Pubkey is the same as npub. What kind of detail are you looking for?
It is defined in NIP-01. Pubkey is the same as npub. What kind of detail are you looking for?
This is nip-01: https://github.com/nostr-protocol/nips/blob/master/01.md Please paste here what part of this spec the PR solves/fixes.
Since I submitted this PR they changed the spec.
The `ids` and `authors` lists contain lowercase hexadecimal strings, which may either be an exact 64-character match, or a prefix of the event value. A prefix match is when the filter string is an exact string prefix of the event value. The use of prefixes allows for more compact filters where a large number of values are queried, and can provide some privacy for clients that may not want to disclose the exact authors or events they are searching for.
I don't know how they can do that without breaking all the clients, but at this point I wash my hands of it.
Add support for pubkey prefixes (truncated key) in subscription requests.