Global Sysops

From Miraheze Meta, Miraheze's central coordination wiki
Global sysops


Shortcut:
GS

Global Sysops (global-sysop) on Miraheze are users who assist Stewards in supporting the community and working with communities to address issues facing them locally as well as cleaning up vandalism, preventing it when possible, and enforcing Miraheze's global policies.

Note however that they specifically do not have global access to read private wikis, or access any CheckUser or Oversight tools.

If you have an issue with an action made by a Global Sysop such as a lock or block, or you need to request CVT intervention including local blocks and global locks, you can email cvt@miraheze.org (which also gets redirected to all Stewards) or you may make a new thread on the Stewards' noticeboard.

Local interference

Global Sysops should only act in their capacity if:

  • There is disruption on a wiki and there are no local sysops or bureaucrats acting in a reasonable amount of time
  • The global Special:AbuseLog shows attempted spam that hasn't been dealt with by local sysops or bureaucrats
  • A request to intervene is made by a member of the local community
  • A global policy violation needs rectification and local sysops or bureaucrats aren't acting in a reasonable amount of time

Technical capability

Members of Global Sysop global group can do, among other things:

  • View the abuse log
  • View detailed abuse log entries
  • Create or modify global abuse filters
  • Modify abuse filters with restricted actions
  • Revert all changes by a given abuse filter
  • View abuse filters
  • Use higher limits in API queries
  • Not be affected by IP-based rate limits
  • Automatically log in with an external user account
  • Have one's own edits automatically marked as patrolled
  • Block or unblock other users from editing
  • Block or unblock a user from sending email
  • Search deleted pages
  • Administrate user-submitted comments
  • Delete pages
  • View deleted history entries, without their associated text
  • View deleted text and changes between deleted revisions
  • Delete and undelete specific log entries
  • Delete and undelete specific revisions of pages
  • Edit pages
  • Edit all user pages
  • Update other users' social profiles
  • Edit pages protected as "Allow only administrators"
  • Edit pages protected as "Allow only autoconfirmed users"
  • Delete Structured Discussions topics and posts
  • Hide Structured Discussions topics and posts
  • Bypass IP blocks, auto-blocks and range blocks
  • Retrieve information about IP addresses attached to revisions or log entries
  • Access a full view of the IP information attached to revisions or log entries
  • Mark rolled-back edits as bot edits
  • Merge the history of pages
  • Mark edits as minor
  • Move pages
  • Move category pages
  • Move root user pages
  • Move pages with their subpages
  • Move files
  • Not have minor edits to discussion pages trigger the new messages prompt
  • Not be affected by rate limits
  • Mass delete pages
  • View recent changes patrol marks
  • Change protection settings and edit cascade-protected pages
  • Purge the cache for a page
  • Quickly rollback the edits of the last user who edited a particular page
  • Perform CAPTCHA-triggering actions without having to go through the CAPTCHA
  • Not create redirects from source pages when moving pages
  • Undelete a page
  • View a list of unwatched pages

Action log

A list of Global Sysops member's actions is located on cvtwiki. The page is on the read whitelist and visible to all users.

Appointment

To be elected Global Sysop, a request needs to be made at Requests for global permissions. The community can discuss (support/oppose/abstain/comment) the request. The request will be considered successful if:

  • at least 10 users share their view
  • there is a support ratio of at least 80%
  • a period of one week has passed since it started

In addition, Global Sysops are required to have two-factor authentication enabled on their user accounts in order to perform certain Global Sysop-restricted functions and may have the right revoked temporarily from their account if they do not.

Revocation

Inactivity

Global Sysops who do not participate in Global Sysop duties in some form (countervandalism, locking abusive users, etc.) for 6 months will be deemed inactive and have their Global Sysop rights revoked by a Steward.

Votes of no confidence

The global community can initiate a vote of no confidence or a request of removal at any time. The request will be considered successful if:

  • at least 10 users share their view
  • there is a support ratio of at least 50%
  • a period of one week has passed since it started

A vote of no confidence or request for removal must include a reason for why users are requesting the removal of the Global Sysop, and it is not determined solely by the number of votes.

Emergency revocation

In the case of a blatant misuse of rights or an abuse of power, a Steward may remove a user from Global Sysop at their discretion without a community vote. If this happens, the user must undergo a no confidence vote while their rights are temporarily removed, and their rights may only be added back if the no-confidence vote does not pass. This should only be used in extreme cases and should not substitute a no-confidence vote in non-urgent situations.

Readdition of rights

Once a Global Sysop has their rights revoked for any reason, they must make a successful request that satisfies the criteria above in order to regain the rights.

List of Global Sysops

  • Page last updated: 10 March 2024
  • Total number of Global Sysops: 1
+/- User name Languages spoken Other rights Libera Chat nickname on IRC
Labster en-N autopatrolled, interface administrator


Timeline of past and current Global Sysops

The following is a chart of global sysops.
User:LabsterUser:1108-KijuUser:NotArachamUser:Universal OmegaUser:RaidarrUser:MrJaroslavikUser:CnocBrideUser:開拓者User:Sau226User:AlvaroMolinaUser:MacFan4000User:ZppixUser:Reception123User:Void


Revision history

The following Requests for Comment have shaped this policy:

See also

  • See this page for a list of Global Sysops' global permissions
  • See this page for a list of members of the global group