diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2025-11-11 11:12:27 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2026-02-04 19:22:23 -0300 |
| commit | cc45433791b9f26a1bdb9c209cd3a6eb598a156e (patch) | |
| tree | 26bccc6830119dab9afc230a1516053d1dcb50c7 | |
| parent | c07cf7a13a81ec417493ac7a3f081d489ebeae7d (diff) | |
add repost filter.
| -rw-r--r-- | 45.md | 3 |
1 files changed, 2 insertions, 1 deletions
| @@ -60,8 +60,9 @@ And finally the absolute count can be estimated by running some methods I don't | |||
| 60 | 60 | ||
| 61 | This NIP defines (for now) two filters eligible for HyperLogLog: | 61 | This NIP defines (for now) two filters eligible for HyperLogLog: |
| 62 | 62 | ||
| 63 | - `{"#p": ["<pubkey>"], "kinds": [3]}`, i.e. a filter for `kind:3` events with a single `"p"` tag, which means the client is interested in knowing how many people "follow" the target `<pubkey>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<pubkey>` value as a base-16 number then adding `8` to it. | ||
| 64 | - `{"#e": ["<id>"], "kinds": [7]}`, i.e. a filter for `kind:7` events with a single `"e"` tag, which means the client is interested in knowing how many people have reacted to the target event `<id>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it. | 63 | - `{"#e": ["<id>"], "kinds": [7]}`, i.e. a filter for `kind:7` events with a single `"e"` tag, which means the client is interested in knowing how many people have reacted to the target event `<id>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it. |
| 64 | - `{"#e": ["<id>"], "kinds": [6]}`, the same as above, but for `kind:6` reposts. | ||
| 65 | - `{"#p": ["<pubkey>"], "kinds": [3]}`, i.e. a filter for `kind:3` events with a single `"p"` tag, which means the client is interested in knowing how many people "follow" the target `<pubkey>`. In this case the `offset` will be given by reading the character at the position `32` of the hex `<pubkey>` value as a base-16 number then adding `8` to it. | ||
| 65 | - `{"#E": ["<id>"], "kinds": [1111]}`, i.e. a filter for the total number of comments any specific root event has received. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it. | 66 | - `{"#E": ["<id>"], "kinds": [1111]}`, i.e. a filter for the total number of comments any specific root event has received. In this case the `offset` will be given by reading the character at the position `32` of the hex `<id>` value as a base-16 number then adding `8` to it. |
| 66 | 67 | ||
| 67 | ### Attack vectors | 68 | ### Attack vectors |