Commons:Administradores
Shortcuts: COM:A • COM:ADMIN • COM:SYSOP

Esta página explica o papel dos administradores (por vezes chamados admins ou sysops) na wiki Wikimedia Commons. Note que os detalhes das funções, e a maneira como os administradores são eleitos, podem ser diferentes de outros sites.
Para pedir a ajuda de um administrador, publique o pedido no quadro de avisos dos administradores.
Neste momento há 182 administradores na wiki Commons.
O que é um administrador?
Administrators as of março 2025 Listing by: Language • Date • Activity [+/−] |
Number of Admins: 182
If 182 is not the last number on this list, there may be an error or there are some users assigned temporarily. |
Papel técnico
Os administradores são utilizadores da wiki Wikimedia Commons com a capacidade técnica de:
- Eliminar e restaurar imagens e outros ficheiros carregados, e ver e restaurar versões eliminadas.
- Eliminar e restaurar páginas, e ver e restaurar revisões eliminadas.
- Proteger e desproteger páginas, e editar páginas cuja edição só está disponível para administradores.
- Editar o espaço nominal MediaWiki.
- Alterar os nomes dos ficheiros.
- Acrescentar e retirar grupos de utilizadores.
- Configurar campanhas do assistente de carregamentos (Upload Wizard).
- Ocultar e restaurar entradas do registo e revisões de páginas.
- Importar páginas de outras wikis.
- Fundir os historiais de páginas.
- Modificar os filtros de abusos.
- Não criar redirecionamentos da origem ao mover páginas.
- Ser imunes às verificações contra a mistificação da identidade (spoofing) e às listas negras de títulos de páginas e de nomes de utilizadores.
- Mandar uma mensagem a vários utilizadores de uma só vez (massmessage).
- Usar limites mais altos nas consultas pela API.
Em conjunto, estas são chamadas as ferramentas de administração.
Papel comunitário
Os administradores são membros experientes e de confiança da comunidade da wiki Commons que assumiram tarefas adicionais de manutenção e a quem foram confiadas as ferramentas de administração por um processo público de consenso ou votação. Os diferentes administradores têm diferentes áreas de interesse e experiência, mas as tarefas típicas de um administrador incluem endereçar e fechar pedidos de eliminação, eliminar violações de direitos de autor, restaurar ficheiros se necessário, proteger a wiki Commons contra vandalismo e trabalhar nas predefinições e noutras páginas protegidas. Claro, algumas destas tarefas também podem ser feitas pelos utilizadores que não são administradores.
Espera-se que os administradores compreendam os objetivos deste projeto e estejam preparados para trabalhar de forma construtiva com os restantes para atingir esses objetivos. Os administradores também devem compreender e seguir as normas da wiki Commons e, quando apropriado, respeitar o consenso da comunidade.
Além das funções que exigem o uso das ferramentas de administração, os administradores não têm autoridade editorial especial em virtude da sua posição. Nas discussões e votações públicas as contribuições dos administradores são tratadas da mesma forma que as de qualquer editor normal. Alguns administradores podem tornar-se mais influentes, não devido à sua posição mas devido à confiança pessoal que possam ter ganho da comunidade.
Sugestões para administradores
Leia o Commons:Guide to adminship, por favor.
Remoção dos privilégios de administrador
De acordo com as normas de revogação dos privilégios de administrador, estes privilégios podem ser revogados por inatividade ou uso indevido das ferramentas de administração. 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.
Candidate-se a administrador
Todos os interessados em se tornarem administradores devem passar por este processo e submeterem-se a um RFA, incluindo todos os ex-administradores que pretendem retomar esta função.
Em primeiro lugar, leia as informações em Commons:Administrators/Howto. Depois volte aqui e faça o seu pedido na secção abaixo.
- Depois de clicar o botão apropriado e criar a subpágina, copie a hiperligação para a subpágina (por exemplo: «Commons:Administrators/Requests/Nome de utilizador»), edite Commons:Administrators/Requests, insira a hiperligação no início da secção e envolva-a com chavetas duplas (por exemplo: {{Commons:Administrators/Requests/Username}}) para transcluí-la.
- Se foi nomeado por outro utilizador, aceite a nomeação indicando «aceito» ou algo semelhante e assinando por baixo da nomeação, por favor. A subpágina tem de ser transcluída por si ou pelo seu nomeador.
Na caixa abaixo, substitua "Username" pelo seu nome de utilizador: |
Votação
Qualquer utilizador registado pode votar aqui, embora os votos daqueles que tenham poucas edições ou nenhuma edição anterior possam não ser totalmente contados. É preferível que apresente razões tanto para apoiar como para se
opor porque isto ajuda o burocrata que encerrar o pedido a decidir. Uma argumentação que apresenta provas tem maior peso do que um voto simples.
A promoção normalmente requer 75% de votos a favor, com um mínimo de 8 votos favoráveis. Não são contados os votos de utilizadores não registados. No entanto, o burocrata que encerra a nomeação pode usar o seu poder discricionário para determinar o consenso da comunidade, pelo que a decisão pode não ser baseada necessariamente no número de votos.
Os comentários com a indicação neutro não são contados para determinar o resultado da votação. No entanto, fazem parte da discussão, podem persuadir outros utilizadores e permitir que o burocrata compreenda melhor o consenso da comunidade.
Purgar a cache Use a hiperligação de edição abaixo para editar a página transcluída.
Requests for adminship
Quando concluídas, as páginas listadas aqui deverão ser arquivadas em Commons:Administradores/Arquivar.
- Por favor, leia Commons:Administradores antes de votar aqui. Qualquer utilizador autenticado pode votar, embora aqueles que têm poucas ou nenhuma edição anterior pode não ser totalmente contados.
No current requests.
Requests for bureaucratship
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
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 (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)
As the other active CU, I join in strong Support for this nomination. . Jim . . . (Jameslwoodward) (talk to me) 13:57, 10 March 2025 (UTC)
- 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.
Votes
Support Good candidate. --Yann (talk) 19:13, 5 March 2025 (UTC)
Support 1989 (talk) 19:27, 5 March 2025 (UTC)
Support Fit India 20:53, 5 March 2025 (UTC)
Support! Queen of Hearts (talk) 21:20, 5 March 2025 (UTC)
Support been nothing but impressed in my interactions with this user. Magog the Ogre (talk) (contribs) 02:22, 6 March 2025 (UTC)
Support Christian Ferrer (talk) 09:32, 6 March 2025 (UTC)
Support REAL 💬 ⬆ 15:32, 6 March 2025 (UTC)
Support --Robert Flogaus-Faust (talk) 16:30, 6 March 2025 (UTC)
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)
Support Sure thing! signed, Aafi (talk) 17:10, 6 March 2025 (UTC)
Strong support per Magog, and my own experience. All the Best -- Chuck Talk 17:53, 6 March 2025 (UTC)
Support nihil obstat. Good luck! RodRabelo7 (talk) 17:56, 6 March 2025 (UTC)
Support unconditional support Bastique ☎ let's talk! 19:37, 6 March 2025 (UTC)
Support Good candidate Abzeronow (talk) 22:51, 6 March 2025 (UTC)
Support --Adamant1 (talk) 04:07, 7 March 2025 (UTC)
Support -- Riad Salih (talk) 04:20, 7 March 2025 (UTC)
Support We are about to see one of the fastest close. Shaan SenguptaTalk 11:36, 7 March 2025 (UTC)
Support --Takipoint123 (💬) 16:06, 7 March 2025 (UTC)
Support --Rosenzweig τ 19:47, 7 March 2025 (UTC)
Support Ternera (talk) 21:47, 7 March 2025 (UTC)
Support --— D Y O L F 77[Talk] 11:00, 8 March 2025 (UTC)
Support Günther Frager (talk) 13:39, 8 March 2025 (UTC)
Support--Hehua (talk) 14:30, 8 March 2025 (UTC)
Support Long-term experience user, no concerns. Jianhui67 T★C 18:59, 8 March 2025 (UTC)
Support Taichi (talk) 05:22, 9 March 2025 (UTC)
Support no concerns here. Elli (talk) 06:13, 9 March 2025 (UTC)
Support HouseBlaster (talk) 06:17, 9 March 2025 (UTC)
Support --Ameisenigel (talk) 20:21, 9 March 2025 (UTC)
Support per answer given below. Glrx (talk) 23:37, 11 March 2025 (UTC)
Support no reason to oppose. --A1Cafel (talk) 04:58, 12 March 2025 (UTC)
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)
- 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)
- 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)
- 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)
- 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)
- 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)
Requests for Oversight rights
Quando concluídas, as páginas listadas aqui deverão ser arquivadas em Commons:Oversighters/Archive.
- Por favor, leia Commons:Supervisores antes de votar aqui. Qualquer utilizador autenticado pode votar, embora aqueles que têm poucas ou nenhuma edição anterior possam não ser totalmente contados.
No current requests.