stale[bot]
commented
1 year ago This issue is unconfirmed, and has been labelled as stale due to inactivity. It will be closed automatically if no further activity occurs.
A project maintainer can mark an issue as confirmed by adding the help wanted label, the wontfix label, or an assignee.
Concept
Right now, mass deleter collects all of the posts in your drafts/queue before deleting any of them. This means that if you have a large number of posts to delete, closing the browser tab a long way into the collect action results in nothing happening, requiring the user to wait a long time to try again.
Deleting the posts continually (every time there are 100 to delete) would result in interruptions to the action saving one's progress.
I think I would lean towards or at least consider intentionally not making this change in the case of tag replacer, since it increases the ability for a user to wind up in a partial state; this makes sense for mass deleter IMO (you're deleting everything regardless) but is potentially weird for tag replacement.
Honestly I think doing this for mass deleter is pretty whatever; it's more useful for my mass privater PR and hypothetical bulk quick flag PR, which could both plausibly have a "I will perform this action on my most recent posts and stop it when I feel like it's gone deep enough that I don't care about the rest" use case which deleting your drafts/queue in reverse chronological order don't have (presumably you would want to delete the old ones).
Now, if you could query your drafts/queue/etc in chronological order, that's a whole different story. Any Tumblr backend devs reading this? :3