This page hosts requests for global permissions. To make a request, read the relevant policy (global rollback, global sysop, global rename, …) and make a request below. Explain why membership is needed for that group, and detail prior experience or qualifications.
This is not a vote and any active Wikimedia editor may participate in the discussion.
Global rollback and global interface editor requests require no fewer than 5 days of discussion while abuse filter helper and maintainer requests require no fewer than 7 days. Global renamer and global sysop requests require no fewer than 2 weeks of discussion. For requests that are unlikely to pass under any circumstances, they may be closed by a steward without further discussion (after a reasonable amount of input).
Please note that Global rollbackers discussions are not votes. Comments must present specific points in favor of or against a user's approval.
Instructions for making a request
Before requesting, make sure that:
You have sufficient activity to meet the requirements to be allocated the global rollback flag
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable.
=== Global rollback for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
::''Not ending before {{subst:#time:j F Y H:i|+5 days}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than 5 days (other than requests that are unlikely to pass under any circumstances, no other exceptions are allowed, no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential.
Hello! I'm requesting global rollback to help out with fighting cross-wiki vandalism and spam, having used both SWViewer and TwinkleGlobal together for a few months now. I have extensive anti-vandalism experience and have local rollback on the English and Simple English Wikipedias. —k6ka🍁 (Talk · Contributions) 15:26, 17 April 2024 (UTC)[reply]
Support - Piling up, agreeing with those who preceded me, and also adding a thank for the work already done. --M/ (talk) 08:23, 18 April 2024 (UTC)[reply]
Hi! I'm requesting global rollback to help out with fighting cross-wiki vandalism and spam, i use tool SWViewer, TwinkleGlobal or manual .I also have extensive anti-vandalism experience and local rollback, I hope I can help with the task and I will be happy if I am accepted. thanks
🍃Zulf🍃talk06:29, 18 April 2024 (UTC)[reply]
I won't discuss it here, but may I say a little, things like modules and others need to be monitored, especially local wikis that are not touched 🍃Zulf🍃talk07:02, 18 April 2024 (UTC)[reply]
You don't need to be an admin to edit modules, and this is a request for global rollback which has nothing to do with modules, nor do multiple of the rights you have requested? EPIC (talk)07:10, 18 April 2024 (UTC)[reply]
Oppose thanks for offering your help. Per global rollback users must be „demonstrably active in cross-wiki counter-vandalism or anti-spam activities (...) and make heavy use of revert on many wikis“. Looking at your xwiki contributions [10] I see a handful of reverts in the past 24 hours, but other than that you don't seem particularly active in fighting xwiki vandalism/spam, which is also demonstrated by looking at the SWViewer logs: 31 log entries (undo/warnings/deletion requests) in the past 48 hours, no previous usage at all. Like EPIC I've also noticed your many requests for permissions without having the necessary experience for most of them. I would expect demonstrable xwiki anti-vandalism activities for multiple months before global rollback is an option. --Johannnes89 (talk) 07:07, 18 April 2024 (UTC)[reply]
Oppose unfortunately; it does not appear to me that you know what you're doing. I do not see sufficient evidence that you have "extensive anti-vandalism experience", given that you have rollback in only one project, and no evidence of otherwise having a good edit matrix (i.e, having had prior experience reverting in multiple projects). As I indicated to you on MediaWiki, you're falling quite quickly into the "hat-collecting" pit which is something you don't want as it will make things harder for you even when you are qualified. Also: rollback tends to be an area where there are already tools you can use that do not require specalist rights (such as SWViewer and Twinkle) - you do have to mention why those tools aren't enough. Leaderboard (talk) 07:09, 18 April 2024 (UTC)[reply]
@Zulf:, I still don't understand. If you prefer manual, why not use undo? And if you saw global rollback incorrectly being used, why not contact that user? Leaderboard (talk) 13:01, 18 April 2024 (UTC)[reply]
with my language skills, not all projects should be touchable, right? I once saw a global rollback that wasn't correct because of the possibility of his language skills, so it seemed like they were complementary. Thank 🍃Zulf🍃talk12:03, 18 April 2024 (UTC)[reply]
Oppose Please note that users don't generally get "limitations" on anti-vandalism activity. Permissions, and especially global or advanced ones, are wholeheartedly given to those who demonstrate incontrovertibly that they need them for doing even better something that they are already doing in an impeccable manner. --M/ (talk) 08:03, 18 April 2024 (UTC)[reply]
Thank you for your attention, i think i want to be better at that.and I also saw that those who were given the rights were doing something wrong, such as returning them. 🍃Zulf🍃talk12:14, 18 April 2024 (UTC)[reply]
@Zulf: Oh dear, a few ideas but confused. How can you be sure that resigning is wrong? For instance, one can take a pause: I've returned the rights in 2016, still when I got active again, there was a consensus to reinstate the permissions I needed for my activity. Vice-versa, if your activity is low, people tend to be quite conservative in responding to right requests. I strongly suggest you to withdraw this request ASAP, and to keep a steady level of contribution for another six months at least *before* attempting again at any request for permission on all the WMF projects. This would signify that you take in serious consideration all the comments that other fellow editors expressed. --M/ (talk) 17:06, 18 April 2024 (UTC)[reply]
@M7 Not a bad idea either, but I'll leave it to those concerned, and I'm also a little busy taking care of implementing Moderator Tools Automoderator on the local wiki. sorry for my behavior. 🍃Zulf🍃talk18:23, 18 April 2024 (UTC)[reply]
Oppose, sorry. The low cross-wiki activity and very little to no reverts, if at all, and the hat-collecting requests for permissions are not what I expect for a global anti-vandalism/spam user to do. Codename Noreste 🤔 𝙇𝙖 𝙎𝙪𝙢𝙖12:51, 18 April 2024 (UTC)[reply]
@Zulf: Before you request for extra permissions, you need to show us that you are trustworthy enough to hold the rights. Requesting so many permissions in a short period of time does not leave a good impression on other people. I would suggest you slow down and do actual counter-vandalism work for about 6 months before requesting again. Jianhui67talk★contribs18:42, 18 April 2024 (UTC)[reply]
You are logged in on this wiki, and the account is part of your global account;
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global sysop for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential. Please note: Since 2019 all global sysops are required to have two-factor authentication (2FA) enabled.
When you give someone global rename rights, please add them to the list of global renamers and ask them to subscribe to the global renamers' mailing list.
You are logged in on this wiki, and the account is part of your global account;
You have considered the addition of a user language box to your user page
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global rename for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = meta.wikimedia <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). While all input is welcome, there is a hard 80% support requirement for this role as per the global renamer policy.
Hello everyone. Recently, I requested to usurp a username at en:Wikipedia:Changing username/Usurpations, since then, I have been reading local and global guidelines on renaming. I would like to assist with requests on my local English Wikipedia. I have also been reading and reviewing experienced renamers logs. I've read all the local and global guidelines, and I assure everyone I will use this tool with responsibility. Thank you. Kentuckian (talk) 18:29, 18 April 2024 (UTC)[reply]
Your request might be rejected if you don't follow the instructions. Please review Global IP block exemption. You may request Global IP block exemption via stewardswikimedia.org if you can not edit this page.
Please note: Global IP block exemption does NOT make one immune to locally-created blocks of any sort, only global blocks.
If you want to edit the Chinese Wikipedia, usually global IP block exemptions will not help you. Please see this instruction to request a local IP block exemption.
Instructions for making a request
Before requesting global IP block exemption, make sure that:
You are logged in on this wiki, and the account is part of your global account;
To request global IP block exemption
Copy the template below to the bottom of this section and explain why you need the access and why you're suitable. If needed, link to relevant discussions.
=== Global IP block exempt for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = {{subst:REVISIONUSER}}
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if there is demonstrated need for the permission, such as bypassing a global block from someone who is not the intended target.
Your request might be rejected if you don't follow the instructions.
Instructions for making a request
Before requesting additional global permissions, make sure that:
You are logged in on this wiki;
No specific section on this page exists for the permission you want to request;
To request additional global permissions
Copy the template below to the bottom of this section and explain what kind of access you need and why. If needed, link to relevant discussions. If you hold, or have previously held, the right and are asking for either a renewal or revival of that right, please add a link to the previous discussion.
=== <Add requested permission here> for [[User:Foo|Foo]] ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = Username
|discussion=
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if consensus to do so exists after a short period of consideration. A steward will review the request.
I often have problems in non-GS wikis because I often exceed the standard limits through my work. This affects my work, so it would be good if I could add to the group. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫👤💬08:06, 13 April 2024 (UTC)[reply]
I query a lot of data with scripts to get the information faster than with the normal interface. It would of course also be an alternative to include the apihight limits right in the GR group, as this is only a technical right and would be uncontroversial.--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫👤💬08:19, 13 April 2024 (UTC)[reply]
I think the latter option is better, though I don't see the issue with your getting API high limit requestors, so support regardless. Leaderboard (talk) 08:58, 13 April 2024 (UTC)[reply]
I am leaving the discussion open here. the insertion of the right into the GR group can basically be discussed on any page. Personally, I don't care how this is technically solved. I only care about the higher api limit to fix problems. whether this is done through a new group or not is irrelevant to me.---𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫👤💬17:24, 15 April 2024 (UTC)[reply]
Support I have absolutely no problems with this being granted. Honestly, I'd probably support any request for this from anyone even moderately experienced (read: more than like, a thousand cross edits or so), given that as far as I can tell from a basic read, this is really only restricted to prevent massive server load. EggRoll97 (talk) 11:05, 17 April 2024 (UTC)[reply]
I don’t think it’s right to oppose just because we want it added to the GR bitset. Requester has a valid use case and I’m willing to Support this. - XXBlackburnXx (talk) 09:10, 18 April 2024 (UTC)[reply]
Hello! I'd like to request abuse filter helper. I'm kowiki admin, and I often handle JavaScript maintenance tasks(Please see ko:사용자:기나ㅏㄴ/User_Scripts including ko:user:기나ㅏㄴ/RedWarn etc., simple:special:diff/9117268...). Recently, there has been a need for importing filters for moving page and user script usage restrictions. Also, the policies I'm pushing for have passed,(ko:백:빠삭 which is same as enwiki's en:wp:CSD, ...) so I need other Wikipedia's abuse filter references for those policies. I'm majoring in computer science, so I'm good at regular expressions.(And I'm maintaining several abuse filters) I want to import good abuse filters from other wiki. Best regards, --ginaan(T/C)14:31, 15 April 2024 (UTC)[reply]
Hi guys! I'm Sohom, a volunteer developer who has worked on the technical side of Wikisource for a while. The primary motivation behind this request is the fact that I'm planning to do some work on T348078 and bring some JS gadgets/userscripts in Wikisources in line with the recently introduced Stable interface policy. This work might require making some uncontroversial maintainance edits to various onwiki JS gadgets and userscripts on Wikisource and I'd like to be able to make them without having to bother interface administrators of a wiki (or in cases where the wiki is small, Global sysops). --Sohom (talk) 16:54, 17 April 2024 (UTC)[reply]
A good example of a uncontroversial change is have scripts switch from using $( '.prp-page-image img' ).attr( 'src' ) to mw.proofreadpage.openseadragon.getCurrentImage() which allows for scripts to interface with the Openseadragon UI instead of using the (mostly) deprecated .prp-page-image element. Sohom (talk) 17:14, 17 April 2024 (UTC)[reply]
@Leaderboard You are correct, at this time I do not have interface administrator rights on any wiki. I have however, previously had limited Global interface editor privleges to work on similar edit related to Wikisource. (The same GIE request also has a run down of my technical contributions related to Wikisource) :) Sohom (talk) 19:07, 17 April 2024 (UTC)[reply]
Support - didn't realise that you already had this right. Works for me, though I presume that your work will only be limited to Wikisource projects? Leaderboard (talk) 07:11, 18 April 2024 (UTC)[reply]
@Xaosflux For this specific project, I would estimate the maximum time to be anywhere from 6 months to a 1 year (factoring in the fact that I might need to make patches to ProofreadPage which can/might take time to be reviewed). I can re-request rights if I need them beyond that point. Sohom (talk) 14:05, 18 April 2024 (UTC)[reply]
This bot is a part of the tool CampWiz which assists organizers of various edit-a-thon to host, manage campaign, evaluate submissions, publish results (As of now, about 30 campaigns are hosted and 9500+ articles were submitted through this tool). One of its sibling tool helps organizers to generate a list of articles which are not present on their wiki based on topic (As of now, 233k+articles in 150+ lists were harvested). One of our main targets was to reduce the security issue and liability along with privacy issue. As such, this tool uses a single bot account to interact with mediawiki which eliminates the need of storing the user's access token on the server. This bot mainly interacts with mediawiki API using two of the following cases:
FnF List Generator: When determining the missing articles, it uses the categories (in enwiki) to get through its members. It has to go through all of the category members and needs to check whether they are missing in selected language or not. There the performance of this tool heavily depend of each batch size. apihighlimits would allow the performance to improve drastically. Therefore, it needs this right on enwiki.
CampWiz: This tool allows the campaign to have a restriction based on the contributions of the submitter. That is, it can also determine how many bytes + words the submitter added during the campaign period. This is done via retrieving all the revisions during that period and performing calculations. If we get this right on each of the language the tool deals with, the overall speed of submission scrutiny would increase significantly. This needs the right globally.
So, after considering both of the scenerio, I think it would be appropriate to have global apihighlimits flag on this account. (For additional information, this bot has bot flag in several wiki for some write operation. But this global apihighlimits would be used for read operations only). Thanks, --Nokib Sarkar (talk) 19:18, 17 April 2024 (UTC)[reply]
Support As a lead for Wiki Loves Folklore international project these tools have been revolutionary for our Feminism and Folklore writing campaign that ran on Wikipedia and is in Jury phase now. We have plans to open-source this tool for other wiki campaigns also only after intensive testing and confidence for which this userright is requested. Thank you. Tiven2240 (talk) 04:31, 18 April 2024 (UTC)[reply]
Support sure --TenWhile6 (talk | SWMT) 15:34, 17 April 2024 (UTC)
Comment I'm not going to vote here, but I note that the amount of cross-wiki requests for different permissions in a short time [1][2][3][4][5][6][7][8][9] is a little concerning. EPIC (talk) 06:43, 18 April 2024 (UTC)
Oppose thanks for offering your help. Per global rollback users must be „demonstrably active in cross-wiki counter-vandalism or anti-spam activities (...) and make heavy use of revert on many wikis“. Looking at your xwiki contributions [10] I see a handful of reverts in the past 24 hours, but other than that you don't seem particularly active in fighting xwiki vandalism/spam, which is also demonstrated by looking at the SWViewer logs: 31 log entries (undo/warnings/deletion requests) in the past 48 hours, no previous usage at all. Like EPIC I've also noticed your many requests for permissions without having the necessary experience for most of them. I would expect demonstrable xwiki anti-vandalism activities for multiple months before global rollback is an option. --Johannnes89 (talk) 07:07, 18 April 2024 (UTC)
Strong oppose the links raised by EPIC are concerning - even outside of the various advanced rights, two requests for autopatrol (which is generally one of the lowest threshold rights) were declined - Meta:Requests for help from a sysop or bureaucrat/Archives/2024-04#Request for autopatroll rights and mw:Project:Requests for permissions/Zulf --DannyS712 (talk) 07:46, 18 April 2024 (UTC)
Not done Based on the comments received, it's clear that the request has no chance to pass. Thanks to @Zulf for volunteering. ~ Yahya (talk • contribs) 18:56, 18 April 2024 (UTC)
Question: @Sohom Datta what is the duration of the project you will need this access for? — xaosflux Talk 13:23, 18 April 2024 (UTC)
