In many countries, the word "nuke" is taken lightly, but that's not true everywhere in the world. Also, with current geopolitics I feel it's a bit in poor taste to use the name of a devastating weapon in an extension for cleaning up wikis.
I'd like to rename the extension and the special page to something like MassDelete, although for compatibility I think it's fine if the old special page name silently redirects.
Renaming extensions is extremely difficult; in practice, this is "re-make the Nuke extension under another name, deploy both to production, then slowly move users over and phase out the old one". The effort may not be worth the benefit, though I see the point.
@Jdforrester-WMF and @RheingoldRiver would using a special page alias that's configurable by communities, in a similar manner to the GrowthExperiments Extension work to allow some form of custom naming that would avoid the use of the work "Nuke"?
For users' familiarity across wiki installations, I might prefer creating one single alternative name and setting a toggle so that wikis can config between the two. Then whichever one is not chosen redirects to the other.
But in general yes, I think renaming the special page fixes 95% of the issue, not very many people will ever go to the Special:Version page.
Good to know that the rename special page rename may get us 95% of the way there. Interested to know how the 5% that wouldn't be covered looks like
That would be renaming the extension (or "forking" it and then moving to the new version), so that "Nuke" doesn't show up on Special:Version either, and documentation is listed under MassDelete, etc.
@Jdforrester-WMF could we also update the i18n messages for the extension name without disruption? That would change what's displayed on Special:Version too.