Trivially, this a provably wrong take.
One dev making a decision not to add delete requests is not the same as all of nostr not adding delete requests.
See table of nostr projects that have added or plan to add delete: https://github.com/nostrability/nostrability/issues/68
The whole point of nostr is competition, and devs making independent decisions. The opposite of bluescam, x sole decision maker approach etc.
Yeah and I fought for that tooth and nail and will continue to fight for it. We need to force devs to understand
It is amazing to me that fiatjaf only just realized this issue with not storing delete requests. If fiatjaf didn’t realize this right away from the spec then i suspect many devs implementing deletes will also have issues with this.
There’s a reason damus has delayed this feature. I have been trying to set up a design in nostrdb that tracks deletes reliably. 
Cache invalidation literally being the first one of “only two hard things in computer science” 😅😅😅
