OK. I don't really know all that much about it, I'm just an ...

1db113ebbf6dca15...

npub1rkc386aldh9p28pfw87guc0r0rft9j2mtvpf0zdfjm4y0fm469hs6cy8dq

hex

88920e0d6074907c08b03127a79f5946870937a169b246bb78210ab294b2a736

nevent

nevent1qqsg3yswp4s8fyrupzcrzfa8nav5dpcfx7sknvjxhduzzz4jjje2wdsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgspmvgnawlkmjs4rs5hrlywv83h354je9d4kq5h3x5ed6j85a6azmc3ajkj3

Kind-1 (TextNote)

2026-03-14T13:14:43Z

↳ Reply to Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)

A relay can therefore replace (only keep the newest of similar events) or version (keep multiple iterations of similar events), but not both. It coul...

OK. I don't really know all that much about it, I'm just an amateur not a coder.

It seems there are 2 different things: hacking the events by producing a new event with an existing event id, forcing the relay to have to decide which is the real one or "updating" its record of which one is authoritative, and explicitly saying "this is a new event (with a different event id) that references and obsoletes this other event" which is a protocol level thing that has to be explicitly coded

Raw JSON

{
  "kind": 1,
  "id": "88920e0d6074907c08b03127a79f5946870937a169b246bb78210ab294b2a736",
  "pubkey": "1db113ebbf6dca151c2971fc8e61e378d2b2c95b5b029789a996ea47a775d16f",
  "created_at": 1773494083,
  "tags": [
    [
      "e",
      "b5acc8b8ca6ed8c23387120147190e726db473c23edb6b993ce9a98fbd4d3629",
      "wss://espelho.girino.org/",
      "root",
      "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
    ],
    [
      "e",
      "c736a7d481ac271ccc02aeb808fe974865aaf86ad33f931a3646c2d414be5069",
      "wss://espelho.girino.org/",
      "reply"
    ],
    [
      "p",
      "1db113ebbf6dca151c2971fc8e61e378d2b2c95b5b029789a996ea47a775d16f"
    ],
    [
      "p",
      "70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9"
    ],
    [
      "p",
      "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
    ],
    [
      "r",
      "wss://knostr.neutrine.com/"
    ],
    [
      "r",
      "wss://greensoul.space/"
    ],
    [
      "r",
      "wss://nos.lol/"
    ],
    [
      "r",
      "wss://nerostr.xmr.rocks/"
    ],
    [
      "r",
      "wss://atlas.nostr.land/"
    ],
    [
      "r",
      "wss://eden.nostr.land/"
    ],
    [
      "r",
      "wss://nostr.mom/"
    ],
    [
      "r",
      "wss://nostr-pub.wellorder.net/"
    ],
    [
      "r",
      "wss://nostr-pub.semisol.dev/"
    ],
    [
      "r",
      "wss://nostr.land/"
    ],
    [
      "r",
      "wss://nostr-verified.wellorder.net/"
    ],
    [
      "r",
      "wss://relay.nostrplebs.com/"
    ],
    [
      "r",
      "wss://nostr.noones.com/"
    ],
    [
      "r",
      "wss://nostr21.com/"
    ]
  ],
  "content": "OK. I don't really know all that much about it, I'm just an amateur not a coder.\n\nIt seems there are 2 different things: hacking the events by producing a new event with an existing event id, forcing the relay to have to decide which is the real one or \"updating\" its record of which one is authoritative, and explicitly saying \"this is a new event (with a different event id) that references and obsoletes this other event\" which is a protocol level thing that has to be explicitly coded",
  "sig": "760e6725f50cdb3df8ab1bd1546aa5b26e8293b6cf7eab0f5be9b3000eac644ff0dad838000f1fd6da3d6647ebd9ec76631269d9c24b80521c660359ade3a119"
}