Talk:Global locks

In terms of global locks
Wouldn't be fine to create a bot that automatically replies to global lock requests on the Stewards' noticeboard? DarkMatterMan4500 (talk) (contribs) 15:46, 23 June 2022 (UTC)


 * What would the bot say, and why locks in particular? --Raidarr (talk) 15:49, 23 June 2022 (UTC)
 * I think what DarkMatterMan is requesting (and correct me if I’m wrong) is a bot that would auto-respond to lock requests and I suppose, analyze the data to determine if a lock is needed. If so, it’d globally lock the user. As for why, my thoughts are that there are a lot of lock requests, but not all of them can be answered by stewards in a timely fashion as we really only have you and Doug as active stewards, and you already have a full plate without all that. However, I would note it’d be challenging to create the bot, as there are always a lot of factors and variables that go into determining whether a global lock is the best solution. Thanks - BrandonWM (talk • contribs • global • rights) 15:59, 23 June 2022 (UTC)
 * I wouldn't trust a bot to automatically process global locks. Our current AI projects are a bit iffy as is and adding another project to utilise AI and to determine whether to process a global locks or not sounds frightening as that process may easily be abused to lock non-offending users. Agent Isai  Talk to me! 16:02, 23 June 2022 (UTC)
 * Yes, this was my other concern. AI is extremely difficult to create, and even the slightest error could cause a large amount of issues if the bot was given lock authority. Even with no errors, the data could easily be abused. These sort of decisions, in my eyes, should be made by a person. However, I still bring to attention that there aren’t enough active stewards to process all these lock requests. Maybe a separate noticeboard so they get more attention? Thanks - BrandonWM (talk • contribs • global • rights) 16:06, 23 June 2022 (UTC)
 * The issue is that we lack users with the required skills to run for Steward. A recruitment appeal on the Stewards' noticeboard asking for users to run for Steward will likely not be fruitful and may only yield users who lack the competency, skills or reasoning to run for Steward. Agent Isai  Talk to me! 16:09, 23 June 2022 (UTC)
 * Well I honestly think the problem might be partially solved if we gave this kind of lock authority to global sysops. Stewards already have so many responsibilities, and I feel like the community trusts our current GS’s enough to approve this change. Thanks - BrandonWM (talk • contribs • global • rights) 17:50, 23 June 2022 (UTC)
 * We only have one active Global Sysop who juggles a lot of hats and responsibilities already and Global Sysop was always meant to be a chiefly countervandalism role so I don't see that occurring any time soon. Agent Isai  Talk to me! 17:53, 23 June 2022 (UTC)
 * I agree, but back to the point of the bot, I don’t see it as viable or possible to pass community consensus. The bot could be glitchy, and overall the thing or person making the decision to end someone’s future on Miraheze should be able to take in a lot of factors and just use common sense with the surrounding environment. AI hasn’t proven itself capable of that. Thanks - BrandonWM (talk • contribs • global • rights) 20:33, 23 June 2022 (UTC)
 * DarkMatterMan has not elaborated his idea, so this is slightly dead in the water - but, naturally, a bot automatically actioning locks would not be a good idea, and in fact Global Sysops are capable of locking (part of why their bar is also relatively high). They just tend not to have sensitive access like CheckUser that is sometimes essential in clearing up cases. --Raidarr (talk) 23:20, 24 June 2022 (UTC)
 * I’m confused by this? Do you mean like that bot on Wikimedia Meta that responds to locked account requests if they have been locked? If so, I could try making one. -- Bukkit  [ cetacean needed ] 18:56, 26 June 2022 (UTC)
 * Pinging to elaborate. Thanks - BrandonWM (talk • contribs • global • rights) 19:07, 26 June 2022 (UTC)