Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do a final log check for related actions before protection and block actions #1940

Open
danielquinlan opened this issue Jan 24, 2024 · 2 comments

Comments

@danielquinlan
Copy link

I realize there's an unavoidable race condition (at least without API changes) with many administrator actions, but I see a lot of overlapping actions where the time between two administrators making the same or similar actions is more than a few seconds, but less than about 5 minutes (usually it's just a minute or two because that's how long it sometimes takes to customize a complex protection reason or block reason in the Twinkle dialog). The time is not really long enough for a human to avoid unless you're continually refreshing multiple pages, but it's very easily detected by Twinkle.

What I'm requesting is a quick final check right when someone pushes the final protect/unprotect button or the block button that checks the log and if a different administrator has an related action in the last 5 minutes (maybe even 10 minutes). If there is such an action put up a dialog showing the action and allow the administrator to cancel.

@NovemLinguae
Copy link
Member

if a different administrator has an related action in the last 5 minutes

Just to clarify, I assume you mean "if a different administrator performs the same action (block, protect) to the same user/page in the last 5 minutes"?

@danielquinlan
Copy link
Author

Yes. I would say the same action or the inverse action. So, for example, if the user is protecting a page and there's an recent unprotection action, pop up the dialog for that too. The same for blocks/unblocks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants