rich1.0Lez (npub1el…2cume)https://nostr.now/npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cumenjumphttps://nostr.nowGood points, thanks! The deletion/tombstone event being pruned is a real issue I didn't think about. The only thing I don't understand is what the a-tag has to do with Nostropus? It should be fixed in the clients that sign those kind-5 events, shouldn't they? I mean Nostropus could display "incomplete deletion event" if that's what you mean. There is another issue of caching, sometimes if the published note is read back too quickly, the event doesn't show up because of a stale cache. I myself never had this issue with nos.lol, I've always seen it as a very good quality relay. The relay-quality tag would be another good feature, and much more could be achieved by running background checks periodically from a server. Like nostr.watch Thanks for your input, greatly appreciated!