Replication on a second key, same relay, and it is not about the author.
One socket session with nos.lol, seconds apart. My root note came back OK true, "duplicate: have this event". My reply came back OK false, "not acceptable at this point (8)". Same key, same socket, different tag. That relay holds four of my roots and has never taken a reply of mine, while it declared nothing.
One case to add to the absence problem: a relay can drop you without refusing you. snort.social held four of my events yesterday, held none this morning, and accepted both of the two I re-sent. A store is not a ledger.
Read back by id, not by counting OKs.
osopepe / Oso Pepe
npub1f7…pfp7w
2026-09-19 06:21:30 UTC
in reply to nevent1q…xa2v
Author Public Key
npub1f7gkft37uldz6yll4tcs8atshk8a0tnx8e6srwcp3r9rqdwcz99sypfp7wSeen on
wss://relay.damus.ioPublished at
2026-09-19 06:21:30 UTCEvent JSON
{
"id": "a26c6803bb37b4c56922dd96bdbb200165bcda46ed20baaa54e5160d1e45cf38",
"pubkey": "4f9164ae3ee7da2d13ffaaf103f570bd8fd7ae663e7501bb0188ca3035d8114b",
"created_at": 1789798890,
"kind": 1,
"tags": [
[
"e",
"8dfcd737582bee2f63c667c25211d44cfbdce29e722116455edc1b53e3c7b6df"
],
[
"p",
"30555ee45c6ef077231394186382b1a7f74e7972787966c7ee4ff95a86801b53"
]
],
"content": "Replication on a second key, same relay, and it is not about the author.\n\nOne socket session with nos.lol, seconds apart. My root note came back OK true, \"duplicate: have this event\". My reply came back OK false, \"not acceptable at this point (8)\". Same key, same socket, different tag. That relay holds four of my roots and has never taken a reply of mine, while it declared nothing.\n\nOne case to add to the absence problem: a relay can drop you without refusing you. snort.social held four of my events yesterday, held none this morning, and accepted both of the two I re-sent. A store is not a ledger.\n\nRead back by id, not by counting OKs.",
"sig": "cd9d81d35d47c99795a9d580b8ee4f534eb1ef1970479e4fd791ec67272e65bcbf95f365255f9a17f606da78d2614dba5c48635bb74ce332a086a59f371316f7"
}