Create a new article
Write your page title here:
We currently have 7,016 articles on Polandball Wiki. Type your article name above or create one of the articles listed here!

    Polandball Wiki

    Polandball Wiki:Administrators

    Revision as of 03:31, 22 February 2023 by Agent Isai (talk | contribs) (→‎List: Update)
    (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

    Administrators on Polandball Wiki are users who are in charge of monitoring the wiki and handling administrative tasks.

    Administrator abilities

    These additional functions include:

    • Deleting and undeleting pages, and uploaded files.
    • Protecting certain pages so they cannot be edited or renamed by users without admin rights or autoconfirmed status.
    • Blocking IP addresses or user names from editing and and very quick "rollback" of undesirable edits.
    • Resolving issues that appear in the community.
    • Give confirmed, autopatrolled, rollbacker and moderator rights to trusted users.

    A special type of administrators, interface administrator may edit interface messages, allowing changes to the wiki's look and behavior. This right is granted at the discretion of Polandball Wiki bureaucrats, following consensus, and they must have 2FA enabled.

    They can grant several rights depending on what is needed. Moderators have many of the page management abilities admins do, but cannot block or make major wiki decisions on their own. Rollbackers can quickly revert undesirable edits made by a single user. Autopatrolled is an indication of trust, that one's edits do not need to be 'patrolled'.

    Appointment & Revocation


    Administrators may be appointed by the community following a request at Polandball Wiki:Requests for rights.

    In order to apply for administrator, a user must:

    1. Have at least 500 local edits
    2. Have a local (not global) account age of at least 6 months; and,
    3. Be on the Polandball Wiki Discord Server

    In order to win a request for rights, the candidate needs to:

    1. Have at least 7 unique votes. Any user who uses sockpuppetry, meatpuppetry, or canvasses their vote will be disqualified immediately and will be barred for a year from requesting any rights. The user may also face a local ban. Should they have any local rights (apart from autoconfirmed), it will be revoked and all associates in the plot will also suffer the same consequences if not harsher.
    2. Have a support ration of at least 70%.
    3. Have had their requests for rights opened for at least 1 week.

    Bureaucrats will be in charge of closing local requests for rights and will serve as scrutineers, ultimately holding the power to discard votes which are deemed to have been casted fraudulently or overrule local consensus for rights if a majority of bureaucrats deem that the candidate is unfit to be administrator or have doubts in the vote results. Bureaucrats may request Stewards scrutinize the results via a CheckUser if they suspect voter fraud. Bureaucrats should provide ample evidence for this if that is the case. Bureaucrats may also close requests early if it seems that the candidate will not win by a large margin. Only users who have have at least 100 edits and 1 month of account age locally (not globally) will be able to vote on Request for rights.


    Administrators are held to a high conduct standard and may have their rights revoked if their conduct falls below standards. This includes causing drama and issues on-wiki, off-wiki and on other wikis if the issues affect Polandball Wiki, its users, or reputation (bureaucrats may assess on a case-by-case manner what constitutes off-wiki drama). Administrator conduct also falls below standards if they misuse their rights to cause damage to the wiki (vandalism, attacking other users, etc.) or lack competency and maturity (competence is required of administrators). Administrators should never misuse their tools to their own advantage or to apply pressure to fellow editors to get their way or to get a dispute resolved in their favor, doing so may result in revocation.

    The community may also start a vote of no confidence and recall administrators at any time at Project:Requests for rights. To recall an administrator, the vote must have at least 10 votes with a support ratio of over 70% and must be open for a minimum of 1 week (though the period may be extended by bureaucrats to 1 month). All users voting on the vote of no confidence must have at least 100 edits and 1 month of account age locally (not globally). As with appointment via the Requests for rights process, bureaucrats will be in charge of the vote (including closing it and assessing consensus), will serve as scrutineers and hold the power to discard votes only if they believe they have been casted fraudulently through sockpuppetry, meatpuppetry, or if a user canvassed the vote. As with the previous section, users caught engaging in dishonest voting practices face revocation of all rights for a year and a possible ban. A majority of bureaucrats may also rule to override consensus on revocation or may close a vote of no confidence early if:

    1. They believe the request has been made in bad-faith or lacks merit.
    2. They believe the request will fail by a large margin (bureaucrats should only close after 4 days if such is the case)
    3. They believe the request lacks no merit, is completely true and shows that the administrator has engaged in wrongdoing. In such case, the bureaucrat may close the vote of no confidence early in favor of revoking the right and may revoke the right per bureaucrat discretion.

    Bureaucrats, as a majority and through consensus, may remove administrators at any time.

    Admistrators may be demoted if they do not have at least 1 log action done in at least 3 months. Should that happen, they may reapply through another Request for rights.

    Who are this wiki's administrators?

    Administrators are trusted members of the community appointed through community consensus. Typically, they are established users within the Polandball Wiki community with long term involvement and strong contributions to the community, as well as the skills to use their power responsibly. Bureaucrats are the most trusted of these users and act as the leaders.

    For a complete list of users with administrator access, see Special:ListUsers/sysop.


    Warning: This table may fall out of date from time to time. The above ListUsers page provides up-to-date information always.

    Name Country Joined Bureaucrat Admin Moderator Rollback Forum
    AgentIsai-icon.png Agent Isai USA-icon.png US 2021 Yes Yes Auto Auto Auto Yes
    Collisions-icon.png Collisions Taiwan-icon.png TW 2015 Resigned Yes Auto Auto Auto Yes
    ShiningflairV2-icon.png Shiningflair USA-icon.png US 2021 No Yes Auto Auto Auto Yes
    TheElectricBomb-icon.png TheElectricBomb USA-icon.png US 2021 No Yes Auto Auto Auto No
    Icantthinkofanamexd-icon.png Icantthinkofanamexd Indonesia-icon.png ID 2020 No No Yes No No No
    Avery-icon.png MxMelody Canada-icon.png CA 2018 Yes Yes Auto Auto Auto Owner
    Raidarr-icon.png Raidarr USA-icon.png US 2021 No Yes Auto Auto Auto No
    TGC-icon.png TheGermanicCanadian Canada-icon.png CA 2019 No Yes Auto Auto Auto Owner
    IntenCity999-icon (Hat).png IntenCity999 Philippines-icon.png PH 2017 No Yes Auto Auto Auto Yes
    Shanguy400 1V-icon.png ShanGuy400 Thailand-icon.png TH 2018 No No Yes Yes Yes No
    LumiNyte-icon.png LumiNyte Turkey-icon.png TR 2019 No No Yes Yes Yes No
    Enjania-icon.png Enjania USA-icon.png US 2018 No No No No Yes Yes
    Kitty-Icon.png ShadowSpirits8877 USA-icon.png US 2017 No No No No No Yes
    Azzy-icon.png Isabeljolly115 USA-icon.png US 2018 No No No No No Yes
    BlazingBlood-icon.png Blazingblood UK-icon.png UK 2019 No No No No No Yes
    Siberia-icon.png Siberiaball Russia-icon.png RU 2010 Yes Yes Auto Auto Auto No
    Blank-icon.png SexyMordecai5 404-icon.png ?? 2012 Yes Yes Auto Auto Auto No
    IDrowzee-icon.png IDrowzee USA-icon.png US 2013 Yes Yes Yes Yes Yes No
    Antonio-icon.png Antonio12ITA Italy-icon.png IT 2014 Yes Yes Yes Yes Yes Yes
    ChocoMingo-icon.png ChocoMingo USA-icon.png US 2016 Yes Yes Yes Auto Yes Yes
    Mtcat101-icon.png Mtcat101 USA-icon.png US 2020 No Yes Yes Yes Yes Yes
    Byz-icon.png Byz-Venetikos (banned) Canada-icon.png CA 2017 No No Yes No Yes No
    Voztok-icon.png Voztok 404-icon.png ?? 2014 No Yes Auto Auto Auto No
    Mysterious-icon.png IohannesIohannium Italy-icon.png IT 2015 No No Yes Auto No No
    Killlakil-icon.png Killlakil USA-icon.png US 2015 No No No No No Yes
    Duchy of Masovia-icon.png Luki1223 Poland-icon.png PL 2015 No Yes Yes Auto Yes No
    Bre icon.png Bresbeba Czech-icon.png CZ 2015 No No Yes Auto Yes No
    Finns new-icon.png Finns USA-icon.png US 2016 No No No No No Yes
    Meeerko-icon.png Meeerko Serbia-icon.png RS 2016 No No Yes Auto No Yes
    Pescavelho-icon.png Pescavelho Portugal-icon.png PT 2016 No No Yes Auto No Yes
    WKBK-icon.png WestKoreaBestKorea USA-icon.png US 2018 No Yes Yes Auto No No
    Nashorntangle-icon.png HerrSpiridus Australia-icon.png AU 2017 No No No No No Yes
    • Administrators have all privileges from inferior groups.
    • Moderators can perform rollbacks.

    How do I use administrator powers?

    If you are unsure how to use powers, feel free to ask a more senior administrator or bureaucrat for advice. Alternatively, you may request rights on the Miraheze Public Test Wiki, where you can experiment with powers at any time to see what is possible.

    What can administrators not do?

    Administrators should be conservative in using their powers, especially to block, protect or delete things if they are not outright vandalism or severe policy violations. For minor issues or community disputes, diplomacy should be used. Administrators should be responsible and arbitrate issues, not make them worse. It's preferred to assume good faith that a user was trying to do good and to correct them, rather than punish them. In most cases, an administrator should be a regular user who happens to have powers when an issue appears.

    See also

    Cookies help us deliver our services. By using our services, you agree to our use of cookies.
    Cookies help us deliver our services. By using our services, you agree to our use of cookies.