In T370974#10060878, @Chlod wrote:

Indeed it was me. I think we also discussed if it was possible to use MediaViewer with TheDJ? Not sure if there was anything specifically blocking, though.

Indeed it was me. I think we also discussed if it was possible to use MediaViewer with TheDJ? Not sure if there was anything specifically blocking, though.

I got a couple of suggestions for this page's behaviour at Wikimania (I forget from who now, perhaps @Chlod?, sorry!):

• A column in the table that signifies whether the creator was the only contributor or not - there are Nuke use cases for deleting pages where the only contributor was a particular user, but further investigation might be warranted if multiple users have edited the page. This could perhaps be a Yes/No datapoint or displaying the total number of page editors.
• We should do a mockup with image thumbnails for when Nuke is used on images. Also, the behaviour with thumbnails is poor right now, because clicking an image takes you to the page for that image. Clicking the back button prompts you to resubmit the form. Instead we could explore integrating Media Viewer, like in articles, so that clicking the image has it pop up, but is closable, without taking you off the page.

If someone decides to pick up this work, Design-System-Team is happy to support.

T354542 is just waiting for QA, so this should be unblocked.

Stalled on T354542: Create new Rest API endpoint that takes an IP address and returns temporary accounts that have used that address

@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.

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.

Anything left to do here?

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

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.

@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"?

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.

I completely missed Hooks.php! Guess I'll file another patch to cover that one... 😅

With thanks to @Chlod for the great work expanding coverage to close to 100%!