Not according to Vitor Pamplona (nprofile…deau). To be fair, NIP-01 states:
> for kind n such that 10000 <= n < 20000 || n == 0 || n == 3, events are replaceable, which means that, for each combination of pubkey and kind, only the latest event MUST be stored by relays; older versions MAY be discarded.
So, my interpretation is the same as yours (i.e., Amethyst / clients should be filtering for the latest event instead of expecting relays to return only the most up-to-date event). Still, upserting replaceable events by kind and pubkey is a reasonable suggestion. Either way, I just want one side to fix this so that Amethyst stops spamming my relays :D.
Anthony Accioly
npub1a6…w0tyc
2024-10-26 15:10:04
in reply to nevent1q…lptu
Author Public Key
npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tycPublished at
2024-10-26 15:10:04Event JSON
{
"id": "3cc8ffc071579dfebe1e6d78e6812e722b198e40cefbe9c4d29a43ae8b6a5b69",
"pubkey": "ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64",
"created_at": 1729955404,
"kind": 1,
"tags": [
[
"e",
"70c9519bbacae63453cfa6fb3d702ae51fe0e43c40d7fac90ec64bdc670c5f2d",
"",
"root"
],
[
"e",
"76aaa7d524b3ecbf24d14e96618c6ce9f4ca5e46fca244c7206d8927457fb626",
"",
"reply"
],
[
"p",
"7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"",
"mention"
],
[
"p",
"e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"7bbe9e6e5d2c5ec10ab2bdcacc6971710fd2797741f6b283015fc34fe409df44"
]
],
"content": "Not according to nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau. To be fair, NIP-01 states:\n\n\u003e for kind n such that 10000 \u003c= n \u003c 20000 || n == 0 || n == 3, events are replaceable, which means that, for each combination of pubkey and kind, only the latest event MUST be stored by relays; older versions MAY be discarded.\n\nSo, my interpretation is the same as yours (i.e., Amethyst / clients should be filtering for the latest event instead of expecting relays to return only the most up-to-date event). Still, upserting replaceable events by kind and pubkey is a reasonable suggestion. Either way, I just want one side to fix this so that Amethyst stops spamming my relays :D.\n",
"sig": "32a5a11a7fbeb236c4b2b5b77ebdef4281d1abf74dd87200c822433e3e3b5d1835c3416ff5c9526bf14c2683c21b3ff97b75749c6c8195d8e86105c8266416c1"
}