Global Sysops

From WikiTide Meta
This page contains changes which are not marked for translation.

Global sysops


Global Sysops (global-sysop) on WikiTide are highly trusted users who assist Stewards in supporting the global community as well as working with local communities to address issues facing them. Stewards may delegate some of their responsibilities to them from time-to-time.

Global Sysops have administrator and interface administrator rights on all public wikis. They utilize these rights to help clean up and prevent vandalism, perform general maintenance, help administrators upon request, and enforce WikiTide's global policies. On wikis without any active administrators, they act in their stead but have no extra editorial control.

Note that Global Sysops do not have global access to read private wikis, or access to 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(at) (which also gets redirected to all Stewards) or you may make a new thread on the Steward requests.

Local interference[edit | edit source]

Global Sysops should only act in their capacity if:

  • There is disruption on a wiki and local administrators or bureaucrats have not acted in a reasonable amount of time
  • The global Special:AbuseLog shows attempted spam that hasn't been dealt with by local administrators or bureaucrats
  • A request to intervene is made by a member of the local community
  • A global policy violation needs rectification and local administrators or bureaucrats aren't acting in a reasonable amount of time
  • There are no active local administrators on a wiki to process an administrative request (such as page deletion, block of a disruptive user, etc.)
  • An administrator asks for assistance in doing an action

Technical capability[edit | edit source]

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[edit | edit source]

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

Eligibility criteria and requesting[edit | edit source]

Global Sysops are elected by the community. Candidates must satisfy the following eligibility criteria in order to run or be elected. A candidate must:

  • Have at least 1000 total global edits on WikiTide (on more than one wiki, unless that wiki is Meta Wiki) (Note: These edits may not consist of directly copy/pasting content from other wikis, they must be edits done by the user);
  • Have had their WikiTide account for at least 6 months; and,
  • Be involved in some way in community matters (in discussions on the Community portal, active in assisting others on Discord, etc.)

Appointment[edit | edit source]

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 permission temporarily revoked from their account if they do not.

Revocation[edit | edit source]

Inactivity[edit | edit source]

Global Sysops who do not consistently participate in Global Sysop duties in some form (counter-vandalism, locking abusive users, assisting community members, etc.) for 6 months will be deemed inactive and have their Global Sysop permissions revoked by a Steward. Merely doing an action every few months to avoid being removed for inactivity is not sufficient and is grounds for revocation.

Votes of no confidence[edit | edit source]

The global community can initiate a vote of no confidence or a request for 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. Stewards will close the discussion and determine consensus based on arguments posed.

Emergency revocation[edit | edit source]

In the case of a blatant misuse of rights or 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 permissions are temporarily removed, and their permissions 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.

Re-addition of rights[edit | edit source]

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

List of Global Sysops[edit | edit source]

  • Page last updated: 01 October 2023
  • Total number of Global Sysops: 0
+/- User name Languages spoken Other rights Libera Chat nickname on IRC
NotAracham en-N, es-1, ja-1 administrator

Timeline of past and current Global Sysops[edit | edit source]

The following is a chart of global sysops.

See also[edit | edit source]

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