Steward requests/Global permissions
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).
Quick navigation:Cross-wiki requests |
---|
Meta-Wiki requests |
Requests for global rollback permissions
| Please be sure to follow the instructions below:
Global rollback for Hasley
- Global user: Hasley (edits (alt) • CA • global groups • crossactivity • verify 2FA)
- Not ending before 7 November 2019 21:58 UTC
Hello everyone, I am Hasley. A few months ago I joined the SWMT. Since then, I have been active doing countervandalism, mainly finding LTAs and cross-wiki spammers and patrolling small projects from #cvn-sw, SWViewer and RTRC. I think global rollback could be very useful for me . Kind regards, —Sgd. Hasley 21:58, 2 November 2019 (UTC)
- Support without hesitation. --TheSandDoctor Talk 22:03, 2 November 2019 (UTC)
- Support without a doubt. ~riley (talk) 22:03, 2 November 2019 (UTC)
- Support of course. Valid use case, a few months of experience, trustworthy editor. Thank you for volunteering, Vermont (talk) 22:04, 2 November 2019 (UTC)
- Support Wow, at last! One of most actives SWMT-members. In less than a month 860+ reverts (via undo) in 104 wikis (SWV).—Iluvatar (talk) 22:27, 2 November 2019 (UTC)
- Support Active in SWMT.-MrJaroslavik (talk) 22:28, 2 November 2019 (UTC)
- Support --Krd 22:31, 2 November 2019 (UTC)
- Support, It's about time. -- CptViraj (📧) 02:36, 3 November 2019 (UTC)
- Support - They are doing well, and I trust them. 100% Competent. Good to go. Kind regards, — Tulsi Bhagat (contribs | talk) 02:49, 3 November 2019 (UTC)
- Support sure. TonyBallioni (talk) 03:11, 3 November 2019 (UTC)
- Support about time. 大诺史 (Talk/留言/토론/Discussion) 03:46, 3 November 2019 (UTC)
- Support Always faster than me on SWViewer :D --WhitePhosphorus (talk) 04:25, 3 November 2019 (UTC)
- Support -J. Ansari Talk 06:08, 3 November 2019 (UTC)
- Support --Catherine Laurence discussion 06:31, 3 November 2019 (UTC)
- Strong support Like--Turkmen talk 07:28, 3 November 2019 (UTC)
- Support. I see eswiki brings active cross-wiki vandal fighters :) Stryn (talk) 08:04, 3 November 2019 (UTC)
- Support --Novak Watchmen (talk) 14:22, 3 November 2019 (UTC)
- Strong support Jianhui67 talk★contribs 14:33, 3 November 2019 (UTC)
- Support Trusted. --Streetdeck (Talk) 15:01, 3 November 2019 (UTC)
- Support good work on hr.wiki --Mateo K 01 (talk) 15:08, 3 November 2019 (UTC)
- Strong support thought they were already a GR, can be trusted --DannyS712 (talk) 15:59, 3 November 2019 (UTC)
- Support--WikiBayer 👤💬 16:44, 3 November 2019 (UTC)
- Support Good edit matrix, and does good anti-vandalism work on the wikis I monitor. Looks fine to me. Leaderboard (talk) 19:04, 3 November 2019 (UTC)
- Support I've been waiting! Very, very active. Will be very useful. Esteban16 (talk) 21:01, 3 November 2019 (UTC)
- Support. Could've sworn they were already; no issues here. Hiàn (talk) 02:25, 4 November 2019 (UTC)
- Support Has experience, did good work, very easy to support.—Ah3kal (talk) 06:57, 4 November 2019 (UTC)
- Support the best person for GR--Infinite0694 (Talk) 07:44, 4 November 2019 (UTC)
- Support--Hamish 03:15, 5 November 2019 (UTC)
- Support – Ammarpad (talk) 04:26, 5 November 2019 (UTC)
- Support, sufficient experience and proven goodwill. -- Xinbenlv (talk) 22:44, 5 November 2019 (UTC)
- Support--BRP ever 10:06, 6 November 2019 (UTC)
- I have just one complain, just one. He is very quick to revert! I don't even get chance to revert edits when he is online!
- Just kidding. I have no complains. Happy patrolling. Support Masum Reza☎ 11:37, 6 November 2019 (UTC)
Global rollback for MrJaroslavik
- Global user: MrJaroslavik (edits (alt) • CA • global groups • crossactivity • verify 2FA)
- Not ending before 12 November 2019 18:08 UTC
Hi everyone!
I' m currently rollbacker and patroller on cswiki, rollbacker and pending changes reviewer on enwiki and autopatroller on few projects. I started cross-wiki patrol through SWViewer. Throughout the process I have gained experience in removing vandalism made in various languages (even if I don't speak them). I would like to get global rollback to facilitate my work against vandalism. These rights would be useful for example to suppress abuse filters, which sometimes forbids me from editing. I would also definitely use the right markbotedit
(for example, if multiple pages are vandalized at the same time). If you have any questions, feel free to ask. Thanks! -MrJaroslavik (talk) 18:08, 7 November 2019 (UTC)
Requests for global sysop permissions
| Please be sure to follow the instructions below:
Requests for global rename permissions
Steward requests/Global permissions/Global renamers
Global rename for Turkmen
- Wiki: meta.wikimedia.org (list 'crats • bot policy • summary • 'crats rights)
- User: Turkmen (talk • edits • logs • UserRights • activity • CentralAuth • email • verify 2FA)
- Not ending before 12 November 2019 20:11 UTC
Hello. I'm a global rollbacker and a global sysop. Furthermore, I'm a local sysop on multiple projects. I'am familiar with the global rename policy. I can speak and understand multiple Turkic languages. Thus, I believe that I can help as a global renamer. Also, I can help in reducing the queues in large projects and Meta-Wiki. Thank you!--Turkmen talk 20:11, 29 October 2019 (UTC)
- Support Trusted. --Streetdeck (Talk) 04:20, 30 October 2019 (UTC)
- Support -MrJaroslavik (talk) 13:48, 30 October 2019 (UTC)
- Support --Novak Watchmen (talk) 14:27, 30 October 2019 (UTC)
- Support --janbery (talk) 14:03, 31 October 2019 (UTC)
- Support -J. Ansari Talk 16:43, 1 November 2019 (UTC)
- Support - trusted editor - Taketa (talk) 10:04, 2 November 2019 (UTC)
- You're an administrator on five content projects, four of which you don't edit frequently anymore, and a global sysop/global rollbacker. At what point are you spreading yourself too thin? Vermont (talk) 10:42, 2 November 2019 (UTC)
- Hello dear @Vermont:. You gave a reasonable question. Yes, my activity went downwards since September 10. This is related to my education in the university. I will repair my activity on November 4. But please check out my acitivity from June to September of this year. You also witnessed my activity during that time period. I would not apply for this right if I was going to be an inactive user. Thanks!--Turkmen talk 17:17, 2 November 2019 (UTC)
Requests for global IP block exemption
| Please be sure to follow the instructions below:
Global IP block exempt for IP Range of WikiLoop Battlefield
- Global user: [[User:all logged in users with m:WikiLoop Battlefield webapp|all logged in users with m:WikiLoop Battlefield webapp]] ([[luxo:all logged in users with m:WikiLoop Battlefield webapp|edits]] ([[:xtools:globalcontribs/all logged in users with m:WikiLoop Battlefield webapp|alt]]) • [[Special:CentralAuth/all logged in users with m:WikiLoop Battlefield webapp|CA]] • [{{fullurl:Special:GlobalGroupMembership/all logged in users with m:WikiLoop Battlefield webapp}}?user-reason=per+%5B%5Bm%3ASpecial%3ARedirect%2Fpage%2F135805%7Crequest%5D%5D global groups] • crossactivity • verify 2FA)
Statement
I am a developer, and we are building a counter-vandalism tool called WikiLoop Battlefield, and here is its source code. We recently start to roll out Oauth login and in-place revert feature. When we move our test from localhost to our dev and canary(staging) environment, we noticed that we received the following error.
{ "error": { "code": "globalblocking-ipblocked-range", "info": "'''Your IP address is in a range which has been blocked on all wikis.''' The block was made by [//meta.wikimedia.org/wiki/User:Jon_Kolbert Jon Kolbert] (meta.wikimedia.org). The reason given is ''[[NOP|Open Proxy]]: Webhost: Contact [[m:Special:Contact/stewards|stewards]] if you are affected ''. * Start of block: 2019-07-23T12:01:56 * Expiration of block: 2021-01-23T11:01:56 You can contact [//meta.wikimedia.org/wiki/User:Jon_Kolbert Jon Kolbert] to discuss the block. You cannot use the \"Email this user\" feature unless a valid email address is specified in your [[Special:Preferences|account preferences]] and you have not been blocked from using it. Your current IP address is 3.86.232.24, and the blocked range is 3.86.0.0/16. Please include all above details in any queries you make.", "*": "See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes." }, "servedby": "mw1346" }
We host our server on Heroku, does it mean that the IP address of heroku is being blocked globally for MediaWiki API? Can we apply to be whitelisted for our legit use-case?
Thank you!
Responsess
- @Xinbenlv: Heroku is a shared host, and Wikimedia discourages hosting service in third-party shared hosts (it may host VPN or reverse proxy, which can hide users' IP address). You should either:
- Move the project to Toolforge (recommended) or Cloud VPS
- Create a edit service in Toolforge similar to toollabs:widar, and invoke the service (you must use GET or JSONP, Cloud does not support POST from third-party service) in the project (not recommended, this may have security issues)
--GZWDer (talk) 18:41, 17 October 2019 (UTC)
- @GZWDer: thank you.
- First sorry I just noticed I didn't use the template (which doesn't apply to IP range extemption for al IPs), I updated it.
- Second, here we are building an app that requires a user to login with Oauth. We only conduct edit on-behalf of loged-in users and their username will show up.
- 3rdly, with respect to your suggestion, We've considered porting the project to Toolforge but we are waiting for the Toolforge to support modern Kubernates https://phabricator.wikimedia.org/T214513.
- It is not particularly feasible for all users to rely on IP addresses because as many of people who submit for permissions here, IP addresses are only largely available in USA and a few developed countries who took part in early Internet infrastructure development discussions. Many other countries they have to rely on NAT that shares limited IP addresses. Our app hope to expand to all language locales to help users with counter-vandalism efforts. If we block IP addresses, it will reduce the access of these users from Non-USA/developed countries who would like to help.
- In summary, can we apply for unblocking any IP addresses if we have allowed users to identify themselves with login? Thank you!
Xinbenlv (talk) 21:21, 17 October 2019 (UTC)
- all, I don't know who to send this argument to... Xinbenlv (talk) 10:36, 25 October 2019 (UTC)
- I start a discussion en:User:Xinbenlv/Propose:Allow_Login_Users_By_Default_When_IP_Range_Blocked
- There is a block configurations to let logged in users edit while on blocked IP: However we usually do not allow it on NOP blocks. We cannot let anyone using your tool be exempt from the block, this is a software restrictions. There's just no way to do that. And since we are not going to unblock AWS — thus Heroku — I think your only bet is to follow GZWDer's advice. — regards, Revi 07:54, 4 November 2019 (UTC)
- @-revi:, @GZWDer: thanks for answering. How about the following solutions sound to admins?
- if we use certain way to crypt-sign a request from our app's server, can you grant app-specific exception for this use-case? (rather than unblocking all IP-addresses but unblockgin all users who have signed in and use our app)?
- if we managed to find a fixed IP address, can you unblock individual IP address of the one that we use for our webapp?
- Xinbenlv (talk) 22:37, 4 November 2019 (UTC)
- @-revi:, @GZWDer: thanks for answering. How about the following solutions sound to admins?
- #1: There's no such feature(tm) to do so. #2: I think I can do that, with two conditions: You notify us when you stop your project (thus releasing the IP to the shared pool) and you absolutely always require authentication. — regards, Revi 04:40, 5 November 2019 (UTC)
- @-revi: thank you! Yes. We are likely to use at most 3 IP addresses at this moment:
- 35.222.141.110 for dev
- 34.67.56.51 for canary (staging)
- 34.69.252.115 for prod
- and I agree to both terms: we will absolutely require authentication(in fact you can just allow only login users to edit from these IP addresses) and we will notify you when we stop project and release the IP to the shared pool. (once the Toolforge support mount on Root or custom domain, or we are approved for WMF Cloud VPS)
- Xinbenlv (talk) 06:13, 5 November 2019 (UTC)
- Note individual IPs can not be globally whitelisted (phab:T42439). They can only be whitelisted locally.--GZWDer (talk) 19:58, 5 November 2019 (UTC)
- @GZWDer:, thank you!
- Do I understand it correctly that both the global and local needs to unblock the IP for any IP address to be used? While I will work on applying for individual local wiki's IP whitelist approve, can I ask why individual IPs can not be globally whitelisted? In particular, is it a policy or a technical reason?
- If it's a policy, I'd argument by fixing the static IP, it's no longer an Open Proxy since being reserved and occupied by an application, a random internet user cannot use it. Given that we promise that we only authenticate users, it's a fixed set of users (only registered Wikipedian users) rather than open to public.
- If it's a technical issue, I'd argument previously we are blocking IP range IP1 to IP3, now if we have a static IP2 to unblock, you can block [IP1, IP2), (IP2, IP3]
- Dear global admins, what do you think? Thank you!
- Xinbenlv (talk) 21:35, 5 November 2019 (UTC)
- Please let me know if there are other information you would love me to provide accompanying this application Xinbenlv (talk) 22:49, 7 November 2019 (UTC)
- @-revi: thank you! Yes. We are likely to use at most 3 IP addresses at this moment:
Global IP block exempt for Nurseways
- Global user: Nurseways (edits (alt) • CA • global groups • crossactivity • verify 2FA)
Hi, I only connect to the internet through a VPN due to freedom of speech limitations in my country. For instance, see this recent news article from MSN Brazil (content from Deutsch Welle Brazil) about the current far-right government trying to censor a Wikipedia article and seeking legal prosecution of an editor:
I can supply other examples if needed. The IP I am editing from is my personal VPN, not an open proxy - I am the sole person with access to this IP. I received an error message regarding an IP block when I tried to create an account at the Brazilian Wikipedia directing me to contact user Jon Kolbert who directed me to make a request for an IP Block exemption here. May I use Wikipedia with this VPN? I do not need an exemption for any other IP, thanks --Nurseways (talk) 12:15, 3 November 2019 (UTC)
Global IP block exempt for 78Lepic
- Global user: 78Lepic (edits (alt) • CA • global groups • crossactivity • verify 2FA)
Hello, I'm French and I'm trying to publish on Wikipedia.fr a page about an academic. The page is 151.80.0.0/16. (Jean Marie Barbier, by 78Lepic) and my IP address is 151.80.176.105. My IP is blocked. Could tell me why and/or help me to restaure it by a global IP block exemption? I am also wondering if the wikification of the page is complete enough for it to be published. Thanks for you help. 78Lepic
PS : feel free to contact me on oliviermarty@yahoo.fr, if it is more convenient for you, thanks, --78Lepic (talk) 16:50, 5 November 2019 (UTC)
Requests for 2 Factor Auth tester permissions
Please be sure to follow the instructions below:
|
2FA Tester for Cooltey Feng
- Global user: Cooltey Feng (edits (alt) • CA • global groups • crossactivity • verify 2FA)
I would like to enable the 2FA to further enhance the account security level, thanks, --Cooltey Feng (talk) 19:08, 5 November 2019 (UTC)
- Have you read the documentation? Ruslik (talk) 20:49, 5 November 2019 (UTC)
- Yes, I have read the documentation. Cooltey Feng (talk) 19:59, 7 November 2019 (UTC)
2FA Tester for DrVes
- Global user: DrVes (edits (alt) • CA • global groups • crossactivity • verify 2FA)
I would like to increase the security of my account by enabling 2FA, thanks, --DrVes (talk) 19:07, 6 November 2019 (UTC)
- Have you read Help:Two-factor_authentication?--Shanmugamp7 (talk) 12:08, 7 November 2019 (UTC)
2FA Tester for Christer1987
- Global user: Christer1987 (edits (alt) • CA • global groups • crossactivity • verify 2FA)
I would like to enable 2FA for my account. I am well aware of the requirements esp. on recovery codes, thanks, --Christer • Talk 10:57, 7 November 2019 (UTC)
Requests for other global permissions
Please be sure to follow the instructions below:
|
IP BLOCK
Bonjour, pourquoi ne puis-je plus modifier les articles de Wikipedia ? --Caspien06 (talk) 17:42, 31 October 2019 (UTC)
- Analysant la situation je m'aperçois que j'utilise Avast Security line qui génère des IP aléatoires. Je viens de le débloquer temporairement et je constate que le phénomène de blocage par Wikipédia disparaît. Qu'en pensez-vous ?--Caspien06 (talk) 08:45, 1 November 2019 (UTC)
- @Caspien06: S.V.P. faire un requête pour IPBE ici. Tu es bloqué parce que tu utilises un proxy pour éditer. Jon Kolbert (talk) 09:38, 3 November 2019 (UTC)
Global abuse filter helper for Nullzero
- Global user: Nullzero (edits (alt) • CA • global groups • crossactivity • verify 2FA)
I just started working on a research project regarding correctness of abuse filters and the abuse filter language. My research has already discovered bugs in public filters and the filter language in the past week (1 2 3 4 5 6 7 8 9 10 11 12 13 14).
Being granted the role of global abuse filter helper would allow me to contribute and progress my research further. In particular:
- Fixing a bug or adding a feature could alter the semantics of existing filters in Wikimedia projects, including private filters to which I currently have no access. For that reason, the abusefilter-view-private right would be very helpful for me to make sure that any changes to the language will not break existing filters.
- Similarly, with the abusefilter-view-private right, I would be able to point out bugs in the private filters in addition to the public ones.
- Both abusefilter-view-private and abusefilter-log-private would allow me to obtain more data points to develop the research tool.
It is my hope that by the end of the project, I will produce an open-source tool to automate the (currently manual) bug finding process, and potentially integrate it back to the abuse filter extension.
Incidentally, I have been a sysop at Thai Wikipedia for 6 years, and contributed to various MediaWiki projects, including the abuse filter extension, several years ago.
Thanks, --Nullzero (talk) 00:58, 7 November 2019 (UTC)
- Support I can vouch for the excellent job @Nullzero is doing for the AF parser. --Daimona Eaytoy (talk) 11:14, 7 November 2019 (UTC)
- Support Seems good candidate for the right. ‐‐1997kB (talk) 14:35, 7 November 2019 (UTC)
- Support --Novak Watchmen (talk) 16:57, 7 November 2019 (UTC)
- Support clear use case --DannyS712 (talk) 17:04, 7 November 2019 (UTC)
- Support Why not? Masum Reza☎ 02:18, 8 November 2019 (UTC)
See also
- User groups — Information on user groups
- Global rights log — Log of global permissions changes
- Archives
General requests for: help from a Meta sysop or bureaucrat · deletion (speedy deletions: local · multilingual) · URL blacklisting · new languages · interwiki map
Personal requests for: username changes · permissions (global) · bot status · adminship on Meta · CheckUser information (local) · local administrator help
Cooperation requests for: comments (local) (global) · translation