Project:Requests/User rights/Koishi-bot

User: Koishi-bot[edit]

Requested user-rights: Administrator and Bot.

Koishi-bot (talk • contribs • logs • rights • SUL utility)

Adminbot. This bot will add autopatrolled group to staff accounts (username end with -WMF, (WMF) or (WMDE)) with at least some (not decided yet, currently set to 5) if they are not in such group (and not inside sysop or translationadmin group), remove autopatrolled group to locked staff accounts. Running once per day, source code could be found at here. Stang 14:02, 2 July 2022 (UTC)[reply]

I would also add another function to this bot: When a user on Phabricator is disabled, sync such block at here. To be specific, indefinitely blocked with some reason like Vandalism or spamming on [[phab:|Phabricator]]. Stang 23:27, 2 July 2022 (UTC)[reply]

Oppose The first task does not happen anywhere near frequently enough to warrant a bot, and I don't see why the second task needs to be done. * Pppery * _{it has begun} 16:53, 3 July 2022 (UTC)[reply]

I believe every month ca. ten to twenty staff accounts' right would be updated, and that's enough to run it as a bot. I know I could do so under my account, but IMO it's not a good idea to run a script under a human account on a routine. For the second task, I would like to point it out that it was added as a block reason many years ago, and per block log, such blocking has been performed by many people for a long time. I guess some reason for such blocking is for record purpose, as query for user disable on Phabricator sucks. Stang 20:35, 3 July 2022 (UTC)[reply]

For task 2, I was under the impression that the purpose of that block reason was that (at one point in time, I don't know whether that's still the case) blocking an account on MediaWiki.org automatically disabled the corresponding account on Phabricator, and that was why the block reason existed. I have nothing more to say on Task 1, we just disagree over at what point a bot is warranted. * Pppery * _{it has begun} 22:42, 3 July 2022 (UTC)[reply]

Blocking a account on mwwiki doesn't sync over to Phab, Only wikitech does that, But The main reason I will block an account when I disable it for misuse on phabricator is so that it becomes visible in the CentralAuth world, if the user decides to continue vandalising elsewhere. P858snake (talk) 04:00, 10 July 2022 (UTC)[reply]

Well, if the people involved in disabling Phab accounts (of which I'm not despite being an admin here) think a bot should automatically mirror those to MediaWiki.org, I have no objection, but I still don't really see the point. * Pppery * _{it has begun} 18:10, 10 July 2022 (UTC)[reply]

I'd rather not see Phab disables mirrored here. In my experience accounts spamming Phab aren't usually used to spam SUL sites so this wouldn't have a practical effect in preventing spam/vandalism, and there are perfectly valid reasons to disable a Phabricator account but not block the same account on-wiki. Taavi (talk!) 19:09, 10 July 2022 (UTC)[reply]

As someone who can disable phab accounts and have seen plenty disabled, there are multiple reasons for that and they aren't always applicable to SUL accounts, so

Strong oppose mirroring blocks.

Oppose granting autopatrol automatically, I go through recent changes and do that for staff accounts occasionally, but it isn't really needed - admins can just add it when needed --DannyS712 (talk) 01:34, 15 July 2022 (UTC)[reply]

N Not done Per the multiple opposes in this request. P858snake (talk) 21:54, 30 July 2022 (UTC)[reply]