Stewards' noticeboard
- This is not the place for stewards requests. To make a new request, see steward requests and requests and proposals.
- For illustration of steward policies and use, see the steward handbook.
- See also: Access to nonpublic personal data policy noticeboard.
- This page is automatically archived by SpBot. Threads older than 30 days will be moved to the archive.
 |
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 2 days and sections whose most recent comment is older than 30 days.
|
Global account blocking practices
[edit]Hello watchers of SN, we are doing a public consultation on global account blocking guidelines! Come see at Requests for comment/Global account blocking practices. Stewards who didn't participate in the internal discussion are welcome to comment of course (and those that did). – Ajraddatz (talk) 18:13, 25 August 2024 (UTC)
I would like to check with the stewards on whether it's worth my writing a bot to attempt to fix this bug for existing usernames (and after that, perhaps fix it as stewards suppress usernames in case MediaWiki:Gadget-globalSuppress.js isn't used, as this does tend to cause confusion for admins and patrollers). Asking in advance since I will require some sort of global suppression rights eventually, so there is no point if that cannot be given. Please ping me in a response. Leaderboard (talk) 07:48, 1 September 2024 (UTC)
- @Leaderboard: sorry but this is 99% a non-starter, global suppression rights cannot be given out for testing. Just my 2c and we will discuss at the next stewards' meeting, but the answer is probably no. – Ajraddatz (talk) 19:23, 1 September 2024 (UTC)
- @Ajraddatz Not testing (I could use the cluster for that even if that would be messy), but at the end. Or a steward runs the bot or whatever - but this kind of shows the difficulty non-stewards have in fixing such issues. Leaderboard (talk) 04:27, 2 September 2024 (UTC)
- Same for not testing. The OS policy has no provision for global OS access or even a series of local accesses that could do what you want it to. I want to put this lightly, because I do appreciate the desire to help out... but problems like these can't be resolved by a non-steward. We have a close working relationship with WMF staff for this reason, to get technology solutions respecting our tools that cannot, either technically or effectively, be made by volunteers. This issue is quite low priority, as there is a script that can be used as a workaround and the problem is relatively rare anyway. – Ajraddatz (talk) 04:57, 2 September 2024 (UTC)
- @Ajraddatz Fair, but the only problem is "the problem is relatively rare anyway" is false - just take a look at Global_statistics/Rank_data/enwikinews to see multiple examples of suppressed accounts (to give an example) and it's an issue I regularly hit as a patroller. P.S: I do have full oversight access in the beta cluster - just clarifying "Same for not testing". Thanks for answering BTW - looks like the only recourse is my being a steward from what I understand. Leaderboard (talk) 05:00, 2 September 2024 (UTC)
- Same for not testing. The OS policy has no provision for global OS access or even a series of local accesses that could do what you want it to. I want to put this lightly, because I do appreciate the desire to help out... but problems like these can't be resolved by a non-steward. We have a close working relationship with WMF staff for this reason, to get technology solutions respecting our tools that cannot, either technically or effectively, be made by volunteers. This issue is quite low priority, as there is a script that can be used as a workaround and the problem is relatively rare anyway. – Ajraddatz (talk) 04:57, 2 September 2024 (UTC)
- @Ajraddatz Not testing (I could use the cluster for that even if that would be messy), but at the end. Or a steward runs the bot or whatever - but this kind of shows the difficulty non-stewards have in fixing such issues. Leaderboard (talk) 04:27, 2 September 2024 (UTC)