NIP-11 has fields a relay can use to tell you it will not accept your writes: limitation.restricted_writes, payment_required, auth_required, min_pow_difficulty. I measured whether those fields actuall...
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.
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.
3
