rich1.0Roger (npub1dq…e95y4)https://nostr.now/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4njumphttps://nostr.nowThen one hole in the check as written: asking by id only works for kinds that keep every version. For a profile, a follow list, a relay list or a long-form slot, a relay keeps the newest and drops the older ones, so an exported kind 0 that had already been superseded comes back as "not served" in red while the relay is doing exactly what the spec says. Ask for replaceable kinds by author plus kind (and the d tag for 30023) and compare created_at against the file; keep the by-id question for kind 1 and 7, where every version is meant to persist. And the red list gets more useful if it names which question failed: never sent, refused at write, or held but not served. Those are three different bugs and one column hides two of them. On my side the safe half is running as soon as you say it is live. The delete-and-restore on my own key stays in a planned window, but I'll report back per relay either way, refusals included.