Commons:Amministratura

This page is a translated version of a page Commons:Administrators and the translation is 55% complete. Changes to the translation template, respectively the source language can be submitted through Commons:Administrators and have to be approved by a translation administrator.

Outdated translations are marked like this.

Shortcuts: COM:A • COM:ADMIN • COM:SYSOP

This page is considered an official guideline on Wikimedia Commons.

It illustrates standards or behaviors which most editors agree with in principle and generally follow. Feel free to update the page as needed, but please use the discussion page to propose major changes.

Il nocciolo di questa pagina: Administrators on Wikimedia Commons are users with additional technical abilities to manage the site. They can delete and restore files and pages, protect pages, block users, rename files, and perform other administrative tasks. There are currently 182 administrators on Commons. To become an administrator, users can apply and go through a voting process.

Sta pàggina spiega lu rolu di l'amministratura (a li voti chiamati admins o sysops) nta Wikimedia Commons. Teni prisenti ca li dittagghi supra lu rolu e la manera ntâ quali sunnu numinati ponnu diffiriri di l'àutri siti.

Si si voli addumannari l'aiutu di n'amministraturi, scrìviri un post nta Administrators' noticeboard.

Ci sunnu attualmenti 182 amministratura nta Commons.

Cui è n'amministraturi?

Administrators as of marzu 2025
Listing by: Language • Date • Activity [+/−]

Number of Admins: 182

1234qwer1234qwer4, ru, de-4, en-3
1Veertje, nl, en-4, de-1, fr-1
32X, de, en-2, hsb-1, ru-1
99of9, en (bureaucrat)
A.Savin, ru, de-4, en-2
Aafi, ks, ur-5, en-3, hi-2, ar-1
Abzeronow, en, fr-1
Achim55, de, en-3, nds-3, la-2
AFBorchert, de, en-3
Ahonc, uk, ru-4, en-2, de-1
Aka, de, en-3
Alno, fr, en-3, es-2, pt-1
Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
Ankry, pl, en-2, ru-1
AnRo0002, de, en-2, fr-2, es-1
Anthere, fr, en-3
AntiCompositeNumber, en, fr-2 (steward)
Aude, en, ar-2, de-2, es-3
Auntof6, en, es-2, fr-1
Bastique, en, fr-3, es-2, la-2, fi-1, pl-1
Bedivere, es, en-4, pt-1
Billinghurst, en
Blackcat, it, en-3, fr
BrightRaven, fr, en-3, nl-2, es-2, zh-1
Butko, ru, uk-2, en-1
Captain-tucker, en
Christian Ferrer, fr, en-2, es-2
Ciell, nl, en-2, de-1
Common Good, en
CptViraj, gu, hi-4, en-3 (bureaucrat)
Cromium, en, de-1, fr-1
Cybularny, pl, en-2, es-1, de-1
Czar, en
DaB., de, en-1
DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
Davepape, en
DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
Dharmadhyaksha, mr, en-3, hi-3
DMacks, en
Didym, de, en-2, fr-2
Dyolf77, ar, fr-5, en-2, it-1, es-1
D-Kuru, de, en-2, it-1
Ebrahim, en-3
Elcobbola en, de (checkuser)
Ellin Beltz, en (bureaucrat)
Ellywa, nl, en-2, de-1, fr-1
Emha, de, bar, en-3, fr-1
Érico, pt, en-2, es-1
EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
Explicit, en, es, ko-2
Ezarate, es-3, en-1
Fitindia, en-3, hi-2, mr-2
FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
Gbawden, en-3, af-1
Geagea, he, ka-3, en-3, ru-1
Geni, en
George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
Gestumblindi, als, de, en-3
Gnangarra, en, nys-1
Gnom, de, en-3, fr-2, it-2, es-1
GPSLeo, de, en-2
GreenMeansGo, en
Grin, hu, en-3, de-1
Hekerui, de, en-4
Herbythyme, en, fr-2, es-1, it-1
Hesperian, en
Holly Cheng, en, ja-2
Huntster, en
Indeedous, de, en-3, fr-2
Infrogmation, en, es-1
IronGargoyle, en, de-1
Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
Jaqen, it, en-2
Jarekt, pl, en
Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
Jdforrester, en
Jean-Frédéric, fr, en-4, es-1
Jianhui67, en, zh-4, ja-2, ms-2
Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
Joergens.mi, de, en-3
JoKalliauer, de, en-3
Jon Kolbert, en, fr-4, de-2 (steward)
Josve05a, sv, en-3
Jusjih, zh, en-3, fr-2, ko-1
Kadı, tr, en-5, fr-2, az-2
Kallerna, fi, en-3, sv-2, de-1
King of Hearts, en, zh-3, es-2, ja-1
Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
Krd, de, en-3 (bureaucrat, checkuser)
Krinkle, nl, en-3, de-2
Kritzolina, de, en-3, fr-2, it-1
Léna, fr, en-3, es-1
Leyo, gsw, de, en-3, fr-3, es-1, la-1
Lofty abyss, en, mt, it-2
Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
Magog the Ogre, en, es-2
Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
Maire, pl, en-4, es-2, fr-2, de-2, ru-1
Marcus Cyron, de, en-2
Masur, pl, en-3, de-1
Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
Matrix, en, ta-2
MB-one, de, en-3, fr-1, pt-1
MBisanz, en
Mdaniels5757, en, es-1
MGA73, da, en-3, de-2, no-1, sv-1
Mhhossein, fa, en-3, ar-1
Micheletb, fr, en-3, it-1, es-1
Mike Peel, en, pt-2, fr-1
Minorax, en, zh (oversighter)
Missvain, en
Mitchazenia, en, es-2
Miya, ja, en-2
Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
Morgankevinj, en
MPF, en, da-2, de-1, fr-1
Multichill, nl, en-3, de-1, fr-1
Mys 721tx, zh, en-3
Nagy, de, en-3, fr-2, es-1, sv-1
NahidSultan, bn, en-3, bpy-1
Natuur12, nl, en-3, de-1
notafish, fr, en-4, de-3, es-2, it-2
odder, pl, en-4, de-2 (bureaucrat, oversighter)
P199, en, nl, fr-2, tl-2, de-1
Pi.1415926535, en, es-2
Platonides, es, en-2, fr-1
Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
Podzemnik, cs, en-2
Polarlys, de, en-2, fr-1, no-1
Pyb, fr, en-2
Pymouss, fr, en-3, de-2, it-2, he-1
Racconish, fr, en-4
Ragesoss, en, de-1, fr-1
Ra'ike, de, en-2
Rastrojo, es, en-3, fr-2, eo-1
Ratekreel, ks, en-3, ur-3
Raymond, de, en-3, nl-1 (oversighter)
Red-tailed hawk, en, es-4, pt-2, ug-1
Regasterios, hu, en-1
Rehman, en, si-1
Reinhard Kraasch, de, en-3
Revi C., ko, en-3
Rimshot, de, en-4, fr-2, it-1
Romaine, nl, en-3, de-2, af-1, fr-1
Rosenzweig, de, en-3, fr-1, la-1
Royalbroil, en, es-1
RP88, en, de-1
Rudolphous, nl, en-3, de-2
Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
Sadads, en, es-3
Sanandros, als, de, en-3, fr-1
Satdeep Gill, pa, en-5, hi-5, es-3, fr-2, fa-1
Shizhao, zh, en-1, ru-1
Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
Steinsplitter, bar, de-4, it-3, en-1
Stifle, en, ga, fr-2, de-1
Storkk, en, fr-3, de-2, eo-2
Strakhov, es, en-2
TadejM, sl, en-3, de-2, fr-2
Taivo, et, en-3, ru-3, de-1
Teles, pt, en-3, es-2
Themightyquill, en, fr-2, de-1, hu-1
The Squirrel Conspiracy, en
Thibaut120094, fr, en-2, ja-1
Thuresson, sv, en-3, no-2
Triplec85, de, en-3, fr-1, hr-1, la-1
Tulsi, ne, mai, en-3, hi-2, hif-2, bh-1
Túrelio, de, en-3, es-1
VIGNERON, fr, de-2, en-2, zh-1
Wdwd, de, en-2
Well-Informed Optimist, ru, uk-4, en-3
Wikitanvir, bn, en-3, de-2, as-2, bpy-1
Wutsje, fy, nl, en-3, de-2, fr-1
Yann, fr, en-4, hi-2, gu-1
Yasu, ja, en-2, de-1
Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
Yuval CT, he, en-3
Zzyzx11, en, es-1, fr-1
علاء, ar, en-4, he-1, es-1 (steward)
Abuse filter, (automated account)
CommonsDelinker, (bot) see request
KrinkleBot, (bot) see request

If 182 is not the last number on this list, there may be an error or there are some users assigned temporarily.

Chistioni tècnichi

L'amministratura sunnu utenti câ capacità tècnica nta Wikimedia Commons pi:

Cancillari o ricupirari mmàggini e àutri file carricati, virificari e ripristinari li virsioni cancillati
Cancillari o ricupirari pàggini, virificari e ripristinari li rivisioni cancillati
Prutèggiri o livari la prutizzioni evintuali ê pàggini, canciari chiddi stissi pàggini ca foru prutiggiuti di àutri amministratura
Bluccari o sbluccari l'utenzi di l'utenti, comu puru li nnirizzi IP ndividuali o la gamma di nnirizzi IP
Canciari lu spazziu nomu
Rinuminari li file
Livari gruppi d'utenti (requests for rights)
Cunfigurari campagni pô carricamentu cu prucidura guidata
Cancillari e ripristinari vuci comu puru rivisiunari lu riggistru spicìficu di na pàggina
Mpurtari pàggini di àutri wiki
Uniri la crunuluggìa dê pàggini
Canciari li filtri d'abbusu
Nun criari rinnirizzamenti di pàggini quannu chisti hannu a èssiri spustati e canciati dô nomu origginali
Gnurari li cuntrolli di spoofing e lu tìtulu, o lu nomu utenti dâ blacklist
Mannari un missaggiu a chiù utenti e cuntimpuraniamenti (massmessage)
Utilizzari li lìmiti chiù àuti pê ntirrugazzioni API

Chisti sunnu noti ntâ cullittività comu li strummenti di l'amministratura.

Rolu ntâ Cumunità

L'amministratura sunnu membri sperti e affidàbbili dâ cumunità Commons, li quali ntrapigghiaru un travagghiu di manutinzioni ultiriuri: a iddi foru affidati li strummenti d'amministraturi e hannu un pirmissu pùbblicu pi zocchi pò èssiri un votu/cunzenzu. Diversi amministratura hannu diffirenti àrii di ntiressi e cumpitenza, nunostanti ca li còmpiti tìpici di l'amministratura cumprènninu: la ditirminazzioni e cunchiusioni d'addumannati di cancillazzioni; la cancillazzioni di viulazzioni dô copyright; lu riprìstinu di file si avissi a èssiri nicissariu; la prutizzioni ntê cunfronti di Commons di parti di dd'utenzi ca dê sò canciamenti nni fannu mutivu di vannalismu; travagghiari ntê mudelli (usualmenti chiamati e canusciuti dô tèrmini templates), e àutri evintuali canciamenti ntê pàggini ca sunnu prutiggiuti. Naturalmenti, arcuni di sti còmpiti ponnu macari èssiri svolti di utenti nun-amministratura.

Si ci aspetta ca l'amministratura cumprènninu li scopi di stu pruggettu, e sunnu priparati a travagghiari custruttivamenti cu l'àutri pi sti fini. L'amministratura noltri avìssiru a cumprènniri e seguiri li pulìtichi di Commons, e unni apprupiatu rispittari la culliggialità dâ cumunità.

Oltri ô rolu c'addumanna l'usu dê strummenti d'amministrazzioni, l'amministratura nun pussèdinu auturità edituriali spiciali n virtù dâ sò pusizzioni, e ô nternu di discussioni e vutazzioni pùbblichi li sò cuntribbuti sunnu cunzidirati â stissa manera di n'utenti edituri nurmali. Naturalmenti arcuni amministratura hannu chiù nfluenza, ma chistu nun diriva tantu dâ sò pusizzioni quantu dâ fiducia ca guadagnaru ô nternu dâ cumunità.

Suggirimenti pi l'amministratura

Lèggiti Commons:Guide to adminship.

Livamentu dê privileggi d'amministraturi

Sicunnu la de-admin policy, li privileggi d'amministraturi ponnu èssiri rivucati pi nun attività o usu erratu dê strummenti. In a de-admin request, normal standards for determining consensus in an RfA do not apply. Instead, "majority consensus" should be used, whereby any consensus to demote of higher than 50% is sufficient to remove the admin.

Addumannata p'addivintari amministraturi

All intending administrators must go through this process and submit themselves to RFA, including all ex-administrators who are seeking to return to their previous role.

Comu prima cosa abbisogna jiri ntâ pàggina Amministraturi/Howto e liggìrisi li nfurmazzioni ca sunnu ripurtati ddà. Doppudichì si pò turnari ccà p'effittuari la vostra addumannata ntâ sizzioni suttastanti.

After clicking the appropriate button and creating the subpage, copy the link to the subpage, e.g. "Commons:Administrators/Requests/Username", edit Commons:Administrators/Requests and paste it in at the top of the section, then put it in double curly brackets (e.g. {{Commons:Administrators/Requests/Username}}) to transclude it. Request a watchlist notice at MediaWiki talk:WatchlistNotice, or edit MediaWiki:WatchlistNotice to put up one if you are an administrator.

If someone else nominated you, please accept the nomination by stating "I accept" or something similar, and signing below the nomination itself. The subpage will still need to be transcluded by you or your nominator.

Use the box below, replacing Username with your username:

Voting

Any registered user may vote here although those who have few or no previous edits may not be fully counted. It is preferable you give reasons for both Support and Oppose votes as this will help the closing bureaucrat in their decision. Greater weight is given to an argument, with supporting evidence if needed, than to a simple vote.

Promotion normally requires at least 75% in favour, with a minimum of 8 support votes. Votes from unregistered users are not counted. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Bureaucrats may, at their discretion, extend the period of an RfA if they feel that it will be helpful in better determining community consensus.

Neutral comments are not counted in the vote totals for the purposes of calculating pass/fail percentages. However, such comments are part of the discussion, may persuade others, and contribute to the closing bureaucrat's understanding of community consensus.

Purge the cache Use the edit link below to edit the transcluded page.

Requests for adminship

watch

When complete, pages listed here should be archived to Commons:Administrators/Archive.

Please read Commons:Administrators before voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for bureaucratship

watch

When complete, pages listed here should be archived to Commons:Bureaucrats/Archive.

Please read Commons:Bureaucrats before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for CheckUser rights

watch

When complete, pages listed here should be archived to Commons:Checkusers/Archive.

Please read Commons:Checkusers before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

The Squirrel Conspiracy

Vote

The Squirrel Conspiracy (talk · contributions (views) · deleted user contributions · recent activity (talk · project · deletion requests) · logs · block log · global contribs · CentralAuth)

Scheduled to end: 18:20, 19 March 2025 (UTC)

Dear community,

today I would like to nominate The Squirrel Conspiracy as checkuser for Commons.

Squirrel is an experienced admin in good standing, and active in CU related areas.

They have agreed in private to accept the nomination, and will add some details later.

Thank you, yours, --Krd 18:20, 5 March 2025 (UTC)[reply]

As the other active CU, I join in strong Support for this nomination. . Jim . . . (Jameslwoodward) (talk to me) 13:57, 10 March 2025 (UTC)[reply]

Thank you for the nomination. I’m pleased to accept.

I’ve been an editor for just over 15 years (since September 2009), and I’ve been an admin from 2012-2015 and from 2020-present.

I do a grab-bag of admin tasks; mainly processing speedy and revision deletion requests, closing DRs, and monitoring the admin noticeboards to help with anti-spam and anti-vandalism efforts. I’ve filed a fair number of CU requests as a result of those efforts. Outside of admin tasks, I upload images from open access journals and do a lot of cropping borders.

Elcobbola has been inactive since October and Krd does a huge amount already (#1 by count of admin actions over the last 12 months, a huge amount of VRT work, and is the more active of the two remaining CUs), so I’ve volunteered to help share some of the CU workload. I’m familiar with how IP ranges work from taking a Security+ cert course last year, and I'm on the project pretty much daily.

I think that’s everything. Happy to answer any questions.

The Squirrel Conspiracy (talk) 18:27, 5 March 2025 (UTC)[reply]

Votes

Support Good candidate. --Yann (talk) 19:13, 5 March 2025 (UTC)[reply]
Support 1989 (talk) 19:27, 5 March 2025 (UTC)[reply]
Support Fit India 20:53, 5 March 2025 (UTC)[reply]
Support! Queen of Hearts (talk) 21:20, 5 March 2025 (UTC)[reply]
Support been nothing but impressed in my interactions with this user. Magog the Ogre (talk) (contribs) 02:22, 6 March 2025 (UTC)[reply]
Support Christian Ferrer ^(talk) 09:32, 6 March 2025 (UTC)[reply]
Support $999$ REAL 💬 ⬆ 15:32, 6 March 2025 (UTC)[reply]
Support --Robert Flogaus-Faust (talk) 16:30, 6 March 2025 (UTC)[reply]
Weak support i dont know too much about him, but also community supports. so, it is weak support. good luck. modern_primat^ඞඞඞ^----TALK 16:42, 6 March 2025 (UTC)[reply]
Support Sure thing! _signed,Aafi ^(talk) 17:10, 6 March 2025 (UTC)[reply]
Strong support per Magog, and my own experience. All the Best -- Chuck ^Talk 17:53, 6 March 2025 (UTC)[reply]
Support nihil obstat. Good luck! RodRabelo7 (talk) 17:56, 6 March 2025 (UTC)[reply]
Support unconditional support Bastique ^{☎ let's talk!} 19:37, 6 March 2025 (UTC)[reply]
Support Good candidate Abzeronow (talk) 22:51, 6 March 2025 (UTC)[reply]
Support --Adamant1 (talk) 04:07, 7 March 2025 (UTC)[reply]
Support -- Riad Salih (talk) 04:20, 7 March 2025 (UTC)[reply]
Support We are about to see one of the fastest close. Shaan Sengupta^Talk 11:36, 7 March 2025 (UTC)[reply]
Support --Takipoint123 (💬) 16:06, 7 March 2025 (UTC)[reply]
Support --Rosenzweig τ 19:47, 7 March 2025 (UTC)[reply]
Support Ternera (talk) 21:47, 7 March 2025 (UTC)[reply]
Support --— D Y O L F 77^[Talk] 11:00, 8 March 2025 (UTC)[reply]
Support Günther Frager (talk) 13:39, 8 March 2025 (UTC)[reply]
Support--Hehua (talk) 14:30, 8 March 2025 (UTC)[reply]
Support Long-term experience user, no concerns. Jianhui67^T★C 18:59, 8 March 2025 (UTC)[reply]
Support Taichi (talk) 05:22, 9 March 2025 (UTC)[reply]
Support no concerns here. Elli (talk) 06:13, 9 March 2025 (UTC)[reply]
Support HouseBlaster (talk) 06:17, 9 March 2025 (UTC)[reply]
Support --Ameisenigel (talk) 20:21, 9 March 2025 (UTC)[reply]
Support per answer given below. Glrx (talk) 23:37, 11 March 2025 (UTC)[reply]
Support no reason to oppose. --A1Cafel (talk) 04:58, 12 March 2025 (UTC)[reply]

Comments

@The Squirrel Conspiracy: can you list "what must have happened" before a checkuser uses the checkuser tools?--RoyZuo (talk) 19:47, 11 March 2025 (UTC)[reply]

RoyZuo: Sure! Before running a check, the checkuser needs to make sure the check passes three tests:

Test 1: Demonstrated disruption to the project – CheckUser is only used to combat disruption of the project where the bad actor is suspected of using multiple accounts or IPs to perpetrate that disruption. Most commonly this is spam or vandalism, but it could also be things like flooding a discussion to try to sway its outcome. The disruption is typically demonstrated in a requests for checkuser case with diffs to support the allegations.

Test 2: The check is necessary to stop the disruption – CheckUser is only used when its use is necessary to stop the disruption. Or to put it another way, if the behavioral evidence is strong enough that an admin is comfortable issuing a block without asking for a check, then they should just do so. The caveat to that is sleepers: if a filer creates a case and the behavioral evidence is strong enough to block the identified accounts without needing a check, but the filer presents a reasonable argument that - based on the actor's behavior - there are likely additional accounts that haven't been identified, the checkuser can still run a check to identify those other accounts.

Test 3: Running the check doesn't violate the privacy policy - Checkusers aren't allowed to reveal an account's IP, because that can reveal their location. If someone created a case accusing user:Example of logging out to double-vote in a discussion as IP 127.0.0.1, the checkuser would have to decline that case.

The Squirrel Conspiracy (talk) 22:36, 11 March 2025 (UTC)[reply]

Thx. Good answers.

Although there's 1 extra thing in my mind:

the reported accounts must have some similarity. that similarity needs to be backed up by url.

if the accounts are obviously two different people, or very unlikely a single person/entity, then a check might not be necessary. this is like a polar opposite to, as you mentioned, the scenario of accounts whose "behavioral evidence is strong enough", which also doesnt need a check to connect them.

In my opinion, "disruption to commons" and "similarity" are two necessary elements for a check. What do you think? RoyZuo (talk) 22:53, 11 March 2025 (UTC)[reply]

RoyZuo: In my mind, similarity was built into the first test. To make that explicit, where I said "where the bad actor is suspected of using multiple accounts or IPs", I could rephrase it as "where there is credible suspicion that the bad actor is using multiple accounts or IPs", and then where I said "The disruption is typically demonstrated" [with diffs], I could change it to "The suspicion is typically demonstrated" [with diffs]. The Squirrel Conspiracy (talk) 05:03, 12 March 2025 (UTC)[reply]

Sorry for being longwinded. I wrote the reply above purely based on common sense and logical deduction, but afterwards I realised it's already all summed up at the top of Commons:Requests for checkuser: "you must include a rationale that demonstrates (e.g., by including diffs) what the disruption to the project is, and why you believe the accounts are related."

Your answers are satisfactory. I hope you stick to such common sense. Thank you. RoyZuo (talk) 08:33, 12 March 2025 (UTC)[reply]

Requests for Oversight rights

watch

When complete, pages listed here should be archived to Commons:Oversighters/Archive.

Please read Commons:Oversighters before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

No current requests.

Talìa macari