Talk:Global sysops
Add topic![]() | For requesting global sysop action, see Global sysops/Requests or Steward requests/Miscellaneous. |
A proposal for assisting global users on various local wikis
[edit]Hello there, everyone, in order to assist our invaluable and diligent GS/GR/SWMT members, if/when they get into unfortunate situations on a particular local wiki, I propose that we set up a dedicated global support/help (sub)page/(sub)section on Meta-Wiki for reporting and handling such unwanted scenarios. For this very reason, I pioneer, volunteer and thus nominate myself to the position of a local helper on 6 (six) different Serbian Wikimedia projects. Local administrator of the Serbian Wikipedia, نوفاك اتشمان (talk) 17:25, 13 January 2025 (UTC)
- +
Comment Moved from: Steward requests/Global permissions#Global sysop for Ternera, so please consult this previous discussion below. --نوفاك اتشمان (talk) 17:44, 13 January 2025 (UTC)
discussions on نوفاك اتشمان's repetitive reminder. Collapsed for obvious reasons. |
---|
.
|
- I'd support such a help page. There are some small wikis out there known to be quite hostile and unfriendly to global sysops (etwikiquote, bswiki and ttwiki are some of the first that come to mind) – I suppose a dedicated help page could alleviate some of the concerns. --SHB (t • c) 05:51, 14 January 2025 (UTC)
- I am still unsure on what exactly is being proposed. To me it sounds like the local community should work together to desysop sysops that cause unnecessary issues to global sysops? Either the community should all be on board or the wiki should be opted-out of GS. Leaderboard (talk) 15:36, 14 January 2025 (UTC)
- Hi, my idea is to start a general and unified place for coordinating and organising global users facing difficulties from local users, instead of leaving them confused there or having them go to various places (for example, SRM, and IRC) in order to seek help. Namely, such a dedicated place would also handle much more serious matters, like facilitating removals of both accidental and abusive local blocks directed at global users – I can provide links to some of these examples, if necessary, that is. In addition, that specific instance has already been successfully dealt with, while the wiki in question still is actively and closely being monitored. --نوفاك اتشمان (talk) 09:23, 16 January 2025 (UTC)
- Why can't this be done at SN or similar? Leaderboard (talk) 10:09, 16 January 2025 (UTC)
- Hi, to be honest, that's a really good question. So, are the stewards the default address for that stuff? And, if yes, are there some kind of guidelines/instructions for global users, then? --نوفاك اتشمان (talk) 10:56, 16 January 2025 (UTC)
- Generally yes, if any issues have come up, SRM is usually the de facto go-to venue (recent examples include this, this or this). --SHB (t • c) 11:05, 16 January 2025 (UTC)
- Hi, if that's the case, let's add a line or two of text to some appropriate pages on Meta-Wiki, such as GS/GR/SWMT, then. --نوفاك اتشمان (talk) 13:24, 16 January 2025 (UTC)
- Generally yes, if any issues have come up, SRM is usually the de facto go-to venue (recent examples include this, this or this). --SHB (t • c) 11:05, 16 January 2025 (UTC)
- Hi, to be honest, that's a really good question. So, are the stewards the default address for that stuff? And, if yes, are there some kind of guidelines/instructions for global users, then? --نوفاك اتشمان (talk) 10:56, 16 January 2025 (UTC)
- Why can't this be done at SN or similar? Leaderboard (talk) 10:09, 16 January 2025 (UTC)
- Removed & DENY Velimir LTA. --نوفاك اتشمان (talk) 05:59, 16 January 2025 (UTC)
- What? --SHB (t • c) 05:03, 16
- Hi, this is actually that LTA Velimir from Serbia, who is constantly attempting to open new, active fronts and to expand old ones (aka attrition warfare) against Serbian/other South Slavic local users and global users aiding them (+ 2 examples from yesterday concerning 2 global users). + "WP:DUCK" blocks are allowed, while tagging suspected sockpuppets is being practised. --نوفاك اتشمان (talk) 06:59, 16 January 2025 (UTC)
- What? --SHB (t • c) 05:03, 16
- Hi, my idea is to start a general and unified place for coordinating and organising global users facing difficulties from local users, instead of leaving them confused there or having them go to various places (for example, SRM, and IRC) in order to seek help. Namely, such a dedicated place would also handle much more serious matters, like facilitating removals of both accidental and abusive local blocks directed at global users – I can provide links to some of these examples, if necessary, that is. In addition, that specific instance has already been successfully dealt with, while the wiki in question still is actively and closely being monitored. --نوفاك اتشمان (talk) 09:23, 16 January 2025 (UTC)
- I am still unsure on what exactly is being proposed. To me it sounds like the local community should work together to desysop sysops that cause unnecessary issues to global sysops? Either the community should all be on board or the wiki should be opted-out of GS. Leaderboard (talk) 15:36, 14 January 2025 (UTC)
Automoderator for small Wikipedias
[edit]Hi, I'm the Product Manager for the mw:Moderator Tools team. You may be aware that we've been working on a product called Automoderator, anti-vandalism software which uses a machine learning model to identify and revert vandalism. We want to provide the opportunity for trusted global contributors to use Automoderator on small Wikipedia projects (see T372280) for an overview and some prior discussion. To that end, at last week's Stewards/Foundation call we discussed piloting Automoderator on a handful (5-10) of small projects, so that you could discuss configurations and evaluate effectiveness. I've filed a detailed Phabricator ticket at T388254 with the specific questions that need answering for this pilot to proceed. Please take a look at the ticket and post answer to any of the questions that you have opinions on. I'm happy to answer questions about Automoderator here or on Phabricator. Samwalton9 (WMF) (talk) 16:21, 10 March 2025 (UTC)