forked from leeola/PowerDeleteSuite
-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
Given what people are using this for (overwriting existing content with perhaps something protesting the API changes), and given the rate limit and other 'restore' like shenanigans that's going on, it might be an idea to actually test if the comment in question needs updating, and only trigger API writes for those that don't match the current edit box? I've re-run this several times now, and many many comments don't need 'fixing', just a handful left. It would reduce the API hits, and be faster I would think?
Shockkota and ZarK
Metadata
Metadata
Assignees
Labels
No labels