There are deletes, but they are not always enforced by the relay operators.

It's quite possible that the second boost would be considered as an "undelete" of the prior event (a boost delete request), and therefore get ignored.

According to nip-09:

> Publishing a deletion event against a deletion has no effect. Clients and relays are not obliged to support "undelete" functionality.