User:MSK/emf
| Description | a tool to help undo edits buried in page histories. |
|---|---|
| Author | MSK (+Claude Code) |
| Maintainer | MSK |
| Status | Alpha |
| First released | October 21, 2026 |
| Version | 0.0.0 |
| Updated | 30 October 2026 |
| Browsers | All ES5 browsers |
| Skins | Should work on every skin |
| Source | User:MSK/emf.js |
| GitHub repository | evenmorefire |
(kill it with) even more fire! A spiritual successor to KIWF, used to help undo edits buried in page histories.
Usage
[edit]even more fire! can be opened when viewing the history of a page, when viewing the contributions of a user, or from an AINB page.
Page history
[edit]When opened from the page history, even more fire! will allow you to select the "tainted" edits that will be "intelligently" undone, that is, attempt to stitch together sections of the page such that the added in the tainted edits is removed. The reason parameter will affect the edit summary. Once tainted edits are selected, you can then proceed, which will open the review UI, where "rationales" for changes made will be provided.
User contributions
[edit]When opened from a user's contributions, even more fire! will have three steps. Step one allows you to configure which edits will be "tainted" and then cleaned. Step two is where you configure how cleanup will be done, e.g. automatically LLMPRODing/AI tagging page creations, or automatically updating the AINB tracking page. Automatic cleanup will enable automatically applying cleanup edits. Using this is strongly discouraged, since right now even more fire! is still in alpha and there are too many unaccounted edge cases. Do not undo bot edits will, as the name suggests, no longer mark bot edits as "acceptable collateral damage" when doing reverts. In step three, you can then review, and apply, the cleanup edits.
Automatic tagging
[edit]If you want to automatically LLMPROD and AI tag article creations, do the following:
- Select "Include page creations" on step 1, along with other config options.
- Go to step 2, and set reason to "AI". Check LLMPROD page creations with more than % authorship" and "AI tag article creations with more than % authorship".
- Set the authorship percentages--85% for LLMPROD and 25% for AI tags is a good baseline.
- Optionally, enable "Automatically apply LLMPRODs and AI tags" to automatically apply these tags (cleanup will still need manual review), and put in a tracking page so that those entires will be marked "Ongoing" and "Tagged" in the tracker, respectively.
- Proceed to step 3. Profit.
AINB
[edit]even more fire! will add a button to the left of each AINB entry, if User:DVRTed/AINB-helper is installed, which will allow you to undo all the diffs linked on the right.
AI use disclaimer!
[edit]I'm experimenting with using AI much more liberally during coding. Most of the tests are written by AI, and so are some parts of the actual code/logic (mostly the UI, and parts of scrubber/deprecated). I, obviously, have reviewed all code.
