Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
I suggest there may be a desire for a "Also skip backpan" option for very fast deletes where a backup copy is undesirable, for example, cases where private details leak in to a release, this gets it killed before replication happens and without needing to get proper takedowns performed manually.
Without that option, I would desire some sort of priority signal sent to the backpan mirror to make that version backup happen ASAP, with PAUSE checking backpan every hour or so for slated removals to be replicated, and then nuke them when backpan has mirrored it.
This desire can only be rejected, it is unfulfillable. CPAN
I don't mean that it will be "flawless", you will still of course need some other kind of ass-cover for everywhere else it replicates to.
Its just a "minimize damage" step. Though I guess if its already hit a primary mirror then you're already screwed I guess.