This page is semi-protected against editing.

Commons:Administrators

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Translate this page

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.
Other languages:
This page in a nutshell: 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 186 administrators on Commons. To become an administrator, users can apply and go through a voting process.

This page explains the role of administrators (sometimes called admins or sysops) on Wikimedia Commons. Note that details of the role, and the way in which administrators are appointed, may differ from other sites.

If you want to request administrator help, please post at Administrators' noticeboard.

There are currently 186 administrators on Commons.

What is an administrator?

Administrators as of January 2024
Listing by: Language • Date • Activity [+/−]

Number of Admins: 186

  1. -revi, ko, en-3
  2. 1234qwer1234qwer4, ru, de-4, en-3
  3. 1Veertje, nl, en-4, de-1, fr-1
  4. 32X, de, en-2, hsb-1, ru-1
  5. 99of9, en (bureaucrat)
  6. A.Savin, ru, de-4, en-2
  7. Abzeronow, en, fr-1
  8. Achim55, de, en-3, nds-3, la-2
  9. AFBorchert, de, en-3
  10. Ahonc, uk, ru-4, en-2, de-1
  11. Aka, de, en-3
  12. Alno, fr, en-3, es-2, pt-1
  13. Андрей Романенко, ru, en-3, uk-3, be-2, fr-2, lv-2
  14. Ankry, pl, en-2, ru-1
  15. AnRo0002, de, en-2, fr-2, es-1
  16. Anthere, fr, en-3
  17. AntiCompositeNumber, en, fr-2 (steward)
  18. Aude, en, ar-2, de-2, es-3
  19. Benoît Prieur, fr, en-3, pt-2, es-1, it-1, hy-1
  20. Billinghurst, en
  21. Blackcat, it, en-3, fr
  22. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  23. Butko, ru, uk-2, en-1
  24. Captain-tucker, en
  25. Christian Ferrer, fr, en-2, es-2
  26. Ciell, nl, en-2, de-1
  27. Common Good, en
  28. CptViraj, gu, hi-4, en-3
  29. Cromium, en, de-1, fr-1
  30. Cybularny, pl, en-2, es-1, de-1
  31. Czar, en
  32. DaB., de, en-1
  33. DarwIn, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  34. Davepape, en
  35. De728631, de, en-5
  36. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  37. Dharmadhyaksha, mr, en-3, hi-3
  38. DMacks, en
  39. Didym, de, en-2, fr-2
  40. Dyolf77, ar, fr-5, en-2, it-1, es-1
  41. D-Kuru, de, en-2, it-1
  42. Ebrahim, fa, en-3
  43. Elcobbola en, de (checkuser)
  44. Ellin Beltz, en (bureaucrat)
  45. Ellywa, nl, en-2, de-1, fr-1
  46. Emha, de, bar, en-3, fr-1
  47. Érico, pt, en-2, es-1
  48. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  49. Explicit, en, es, ko-2
  50. Ezarate, es-3, en-1
  51. Fitindia, en-3, hi-2, mr-2
  52. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  53. Gbawden, en-3, af-1
  54. Geagea, he, ka-3, en-3, ru-1
  55. Geni, en
  56. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  57. Gestumblindi, als, de, en-3
  58. Gnangarra, en, nys-1
  59. GPSLeo, de, en-2
  60. GreenMeansGo, en
  61. Grin, hu, en-3, de-1
  62. Hekerui, de, en-4
  63. Herbythyme, en, fr-2, es-1, it-1
  64. Hesperian, en
  65. Holly Cheng, en, ja-2
  66. Huntster, en
  67. Indeedous, de, en-3, fr-2
  68. Infrogmation, en, es-1
  69. IronGargoyle, en, de-1
  70. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  71. Jaqen, it, en-2
  72. Jarekt, pl, en
  73. JarrahTree, en, id-1
  74. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  75. Jdforrester, en
  76. Jean-Frédéric, fr, en-4, es-1
  77. Jianhui67, en, zh-4, ja-2, ms-1
  78. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  79. Joergens.mi, de, en-3
  80. JoKalliauer, de, en-3
  81. Jon Kolbert, en, fr-4, de-2 (steward)
  82. Josve05a, sv, en-3
  83. Julo, pl, en-2, de-1, ru-1
  84. Jusjih, zh, en-3, fr-2, ko-1
  85. Kadı, tr, en-5, fr-2, az-2
  86. Kaldari, en
  87. Kallerna, fi, en-3, sv-2, de-1
  88. King of Hearts, en, zh-3, es-2, ja-1
  89. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  90. Krd, de, en-3 (bureaucrat, checkuser)
  91. Krinkle, nl, en-3, de-2
  92. Kritzolina, de, en-3, fr-2, it-1
  93. Leit, de, en-3, fr-1
  94. Léna, fr, en-3, es-1
  95. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  96. Lofty abyss, en, mt, it-2
  97. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  98. Magog the Ogre, en, es-2
  99. Mahagaja, en, de-4, fr-2, ga-2, la-2, cy-1
  100. Maire, pl, en-4, es-2, fr-2, de-2, ru-1
  101. Marcus Cyron, de, en-2
  102. Masur, pl, en-3, de-1
  103. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  104. MB-one, de, en-3, fr-1, pt-1
  105. MBisanz, en
  106. Mdaniels5757, en, es-1
  107. MGA73, da, en-3, de-2, no-1, sv-1
  108. Mhhossein, fa, en-3, ar-1
  109. Micheletb, fr, en-3, it-1, es-1
  110. Mike Peel, en, pt-2, fr-1
  111. Minorax, en, zh (oversighter)
  112. Missvain, en
  113. Mitchazenia, en, es-2
  114. Miya, ja, en-2
  115. Moheen, bn, as-1, bpy-1, en-3, hi-1, hif-1
  116. Morgankevinj, en
  117. MPF, en, da-2, de-1, fr-1
  118. Multichill, nl, en-3, de-1, fr-1
  119. Mys 721tx, zh, en-3
  120. Nagy, de, en-3, fr-2, es-1, sv-1
  121. NahidSultan, bn, en-3, bpy-1
  122. Natuur12, nl, en-3, de-1
  123. Nick, en, sco-2, fr-1
  124. notafish, fr, en-4, de-3, es-2, it-2
  125. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  126. Otourly, fr, en-2, it-1
  127. P199, en, nl, fr-2, tl-2, de-1
  128. Pi.1415926535, en, es-2
  129. Platonides, es, en-2, fr-1
  130. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  131. Podzemnik, cs, en-2
  132. Polarlys, de, en-2, fr-1, no-1
  133. Pyb, fr, en-2
  134. Pymouss, fr, en-3, de-2, it-2, he-1
  135. Racconish, fr, en-4
  136. Ragesoss, en, de-1, fr-1
  137. Ra'ike, de, en-2
  138. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  139. Rastrojo, es, en-3, fr-2, eo-1
  140. Raymond, de, en-3, nl-1 (oversighter)
  141. Red-tailed hawk, en, es-4, pt-2, ug-1
  142. Regasterios, hu, en-1
  143. Rehman, en, si-1
  144. Reinhard Kraasch, de, en-3
  145. Rimshot, de, en-4, fr-2, it-1
  146. Romaine, nl, en-3, de-2, af-1, fr-1
  147. Rosenzweig, de, en-3, fr-1, la-1
  148. Royalbroil, en, es-1
  149. RP88, en, de-1
  150. Rubin16, ru, tt, en-4
  151. Rudolphous, nl, en-3, de-2
  152. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  153. Sanandros, als, de, en-3, fr-1
  154. Satdeep Gill, pa, en-5, hi-5, es-3, fr-2, fa-1
  155. Shizhao, zh, en-1, ru-1
  156. Spiritia, bg, en-3, ru-2, mk-2, de-1
  157. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  158. Steinsplitter, bar, de-4, it-3, en-1
  159. Stifle, en, ga, fr-2, de-1
  160. Storkk, en, fr-3, de-2, eo-2
  161. Strakhov, es, en-2
  162. TadejM, sl, en-3, de-2, fr-2
  163. Taivo, et, en-3, ru-3, de-1
  164. Tarawneh, en, ar, de-1
  165. Teles, pt, en-3, es-2
  166. Themightyquill, en, fr-2, de-1, hu-1
  167. The Squirrel Conspiracy, en
  168. Thibaut120094, fr, en-2, ja-1
  169. Thuresson, sv, en-3, no-2
  170. Trijnstel, nl, en-4, de-1, fr-1 (checkuser)
  171. Tulsi, ne, mai, en-3, hi-2, hif-2, bh-1
  172. Túrelio, de, en-3, es-1
  173. VIGNERON, fr, de-2, en-2, zh-1
  174. Wdwd, de, en-2
  175. Well-Informed Optimist, ru, uk-4, en-3
  176. Wikitanvir, bn, en-3, de-2, as-2, bpy-1
  177. Wutsje, fy, nl, en-3, de-2, fr-1
  178. Yann, fr, en-4, hi-2, gu-1
  179. Yasu, ja, en-2, de-1
  180. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  181. Yuval CT, he, en-3
  182. Zzyzx11, en, es-1, fr-1
  183. علاء, ar, en-4, he-1, es-1 (steward)
  184. Abuse filter, (automated account)
  185. CommonsDelinker, (bot) see request
  186. KrinkleBot, (bot) see request

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

Technical

Administrators are users with the technical ability on Wikimedia Commons to:

  • delete and undelete images and other uploaded files, and to view and restore deleted versions
  • delete and undelete pages, and to view and restore deleted revisions
  • protect and unprotect pages, and to edit admin-protected pages
  • block and unblock users, individual IP addresses and IP address ranges
  • edit less-restricted interface messages (see also Commons:Interface administrators)
  • rename files
  • add and remove user groups
  • configure Upload Wizard campaigns
  • delete and undelete specific log entries and revisions of pages
  • import pages from other wikis
  • merge the history of pages
  • modify abuse filters
  • not create redirects from source pages when moving pages
  • override the spoofing checks and title or username blacklist
  • send a message to multiple users at once (massmessage)
  • use higher limits in API queries

These are collectively known as the admin tools.

Community role

Administrators are experienced and trusted members of the Commons community who have taken on additional maintenance work and have been entrusted with the admin tools by public consensus/vote. Different admins have different areas of interest and expertise, but typical admin tasks include determining and closing deletion requests, deleting copyright violations, undeleting files where necessary, protecting Commons against vandalism, and working on templates and other protected pages. Of course, some of these tasks can be done by non-admins as well.

Administrators are expected to understand the goals of this project, and be prepared to work constructively with others towards those ends. Administrators should also understand and follow Commons' policies, and where appropriate, respect community consensus.

Apart from roles which require use of the admin tools, administrators have no special editorial authority by virtue of their position, and in discussions and public votes their contributions are treated in the same way as any ordinary editor. Some admins may become more influential, not due to their position as such, but from the personal trust they may have gained from the community.

Suggestions for administrators

Please read Commons:Guide to adminship.

Removal of administrator rights

Under the de-admin policy, administrator rights may be revoked due to inactivity or misuse of sysop tools. 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.

Apply to become an administrator

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.

First, go to Commons:Administrators/Howto and read the information there. Then come back here and make your request in the section below.

  • 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.


Kallerna (de-adminship)

Related requests:

Vote

Kallerna (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth) (Activity: Talk Commons DR)

Scheduled to end: 01:43, 15 January 2024 (UTC)

A consensus (with 17 supports vs 3 opposes) to start this process was reached on this Administrators' Noticeboard thread. The rationales are pretty much the same as in the first de-adminship attempt (which was closed as inadmissible because there was no clear consensus at that point). The current problems with Kallerna are wheel-warring (unblocking a user without prior attempt to contact the admin who performed the block), and use of admin privileges despite possible conflict of interest. Additionally: problematic behaviour, arrogancy, uncivil remarks such as "Please do not block users who do not share the same views as you", "I'm here to contribute to the project, not to discuss with trolls".

With that said, I hereby request to review whether Kallerna still has the trust of Commons community to hold the admin flag. Thanks --A.Savin 01:43, 8 January 2024 (UTC)Reply[reply]

Votes

  •  Remove as nominator, for reasons already stated in the previous RfDA, and on ANU discussion. --A.Savin 01:43, 8 January 2024 (UTC)Reply[reply]
  •  Remove regretfully, per above.  Keep Their apologies seem reasonable and well-meant. We also are in huge need of admins. One less is no solution. However, the point should be made: no repetition of past mistakes. --Bedivere (talk) 02:41, 8 January 2024 (UTC)Reply[reply]
    Commons needs more admins, but not admins who cannot use their tools properly. --SHB2000 (talk) 04:43, 9 January 2024 (UTC)Reply[reply]
  •  Remove regretfully, per above.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 03:45, 8 January 2024 (UTC)Reply[reply]
  •  Remove Per ANU discussion and their comment about other people trolling. --Adamant1 (talk) 05:25, 8 January 2024 (UTC)Reply[reply]
  •  Remove While I would not have blocked Karelj, the unblock was performed without the mandatory consultation and the subsequent lack of accountability leaves us little choice. Guido den Broeder (talk) 06:06, 8 January 2024 (UTC)Reply[reply]
  •  Remove Regretully. Kallerna never fully addressed the issues raised on AN in my opinion Gbawden (talk) 06:14, 8 January 2024 (UTC)Reply[reply]
  •  Remove The following quote shows are huge misunderstanding of Commons policies: You are not a admin, and you are not involved in the matter - I did not have any reason to communicate with you. [1] (the part before the comma should be irrelevant) --Schlurcher (talk) 08:01, 8 January 2024 (UTC)Reply[reply]
  •  Remove Per ANU discussion. --Kritzolina (talk) 08:02, 8 January 2024 (UTC)Reply[reply]
  •  Remove regretfully, per my statement in the ANU discussion. --AFBorchert (talk) 08:11, 8 January 2024 (UTC)Reply[reply]
  •  Remove I'm not a frequent voter, and I'm rather a low-key contributor. Admin behavior referenced and linked by other voters is one of most discouraging parts of contributing to Wikipedia and Commons. --Tupungato (talk) 11:19, 8 January 2024 (UTC)Reply[reply]
  •  Keep I accept Kallerna's explanation and apology. Taivo (talk) 11:56, 8 January 2024 (UTC)Reply[reply]
  •  Keep No reason. Htm (talk) 13:13, 8 January 2024 (UTC)Reply[reply]
    @Htm: could you please elaborate by "no reason"? --SHB2000 (talk) 04:43, 9 January 2024 (UTC)Reply[reply]
  •  Keep Kallerna statement is far sufficiant, I quote: "I want to apologize everyone involved" or "This was obviously a mistake". If they do ten times the same thing, ok, but for the first error as administrator... that should be sufficiant IMO. Christian Ferrer (talk) 14:25, 8 January 2024 (UTC)Reply[reply]
  •  Keep Kallerna has apologized for his behavior (controversial unblocking) and offending remarks, and I feel no need to pursue the matter further. 0x0a (talk) 15:03, 8 January 2024 (UTC)Reply[reply]
  •  Delete They said they apologise, but I have the impression the don't understand the problem at any level and still consider the feedback a big waste of time. --Krd 16:32, 8 January 2024 (UTC)Reply[reply]
  •  Remove Regretfully. I do not find any sense in the responses from Kallerna. A well-sought sorry could have worked but I'm not finding it, and I seriously don't like ifs and buts.─ The Aafī (talk) 17:03, 8 January 2024 (UTC)Reply[reply]
  •  Remove I'd have been fine with a warning if they showed they understood that they screwed up majorly here, but they've doubled down on their behavior, they've never addressed their conflict in interest as far as the unblock because they were w:WP:Involved in the incident that caused the block, they clearly don't understand that Karelj's block was within policy and seems to have prevented future disruption. Abzeronow (talk) 18:07, 8 January 2024 (UTC)Reply[reply]
  •  Remove Commons deserves better. Natuur12 (talk) 18:46, 8 January 2024 (UTC)Reply[reply]
  •  Remove as the nominator of the original de-adminship nom – too bad they couldn't admit their mistake and apologise to A.Savin. --SHB2000 (talk) 04:41, 9 January 2024 (UTC)Reply[reply]
  •  Keep The initial block and removing the block were both done incorrectly. The related discussions after that were somewhat subpar, but I hope that participants will learn something from this and next time co-operation would work better. --Zache (talk) 06:00, 9 January 2024 (UTC)Reply[reply]

Comments

The Truth Is Out There —kallerna (talk) 08:53, 8 January 2024 (UTC)Reply[reply]

And this smörgåsbord of several difflinks should say what exactly? --A.Savin 12:12, 8 January 2024 (UTC)Reply[reply]
I did not want to make a long explanation all over again. I would just like to see you apologize Karelj for your inadequat block. If the community thinks I should not have admin tools after my mistake and following apology, then I respect that view. —kallerna (talk) 13:27, 8 January 2024 (UTC)Reply[reply]
Pointing out a possible error by another admin doesn't excuse your behavior. Instead of abusing your tools, you could have started a discussion about that block. Guido den Broeder (talk) 14:31, 8 January 2024 (UTC)Reply[reply]
It's a pretty minor mistake in the grand scheme of things, but still not good. If you do lose the privilege I encourage you to continue contributing and reply at some point in the future since it's that major of an issue to begin with. --Adamant1 (talk) 15:46, 8 January 2024 (UTC)Reply[reply]
You are correct Guido, that is why I have apologized my actions. Adamant1, I have been here for more than 15 years, I have no intentions to stop my contributions. —kallerna (talk) 18:05, 8 January 2024 (UTC)Reply[reply]
Strange that you are expecting me to seek Karel's pardon. I didn't treat him uncivil, unlike he treated Cart (and never apologized for this). The block was not abusive or bad-faith in any event. But if you are convinced that admins should apologize for past blocks, then feel encouraged to demand some Russian Wikipedia admins to do so first, who had abusively blocked me several times for void reasons, probably over political hate. --A.Savin 20:12, 8 January 2024 (UTC)Reply[reply]
@A.Savin: As I said earlier, admins should understand each other reasons rather than being right. I explain how I see what happened. From Kallerna's point of view, your rationale for blocking Karelj based on the given examples was insufficient. In this case, one example was extended in your blocking rationale to repeated very disrespectful comments at FPC recently. Based on Karelj voting comments, your claim was not true. When the admin makes such claims as part of the block, it tarnishes the target's reputation, and action will be required when one notices it. From your side, I think you thought that Karelj's comments were enough for blocking. It is also complex to explain when negative opinnion is bad as the integral part of FPC is also that users can give opposing and critical opinnions. So I would like not to be too harsh if somebody tries to make commenting more friendly. -- Zache (talk) 05:46, 9 January 2024 (UTC)Reply[reply]

Minor terminology quibble: wheel warring is when an admin action is reinstated, not when one is undone. The unblock was inappropriate, though, to be clear. — Rhododendrites talk |  16:34, 8 January 2024 (UTC)Reply[reply]

TheAafi

Related requests:

Vote

TheAafi (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth) (Activity: Talk Commons DR)

Scheduled to end: 11:56, 11 January 2024 (UTC)

Hello everyone, this is my second nomination. My first nomination failed in February 2023. I take any kind of criticism positively and learn from any mistakes that I make. I feel glad to say sorry if I make an error and try to rectify it. I believe that I have addressed the concerns that were raised in my previous nomination and have also tried to contribute in certain admin-related areas. Over the last few months, I have been occupied elsewhere and couldn't contribute very actively to projects, but I am at my pace now and would like to contribute in closing explicit deletion requests, cleaning up files that have not received permissions on time, and also on other related areas to VRT, most notably. I consider myself a learner, and look forward to learning more with time. I do not feel awkward in seeking advises from others in matters where I feel I'm in doubt. I have sought advises from AFBorchert and others in the past, and would continue to do so in the future. I am comfortable in Kashmiri, Urdu, Hindi, and know some bits of Arabic as well. I have 5519 edits on my main account, and around 137 edits on my mobile account AafiOnMobile. I look forward to your observations, and support. Best regards, ─ The Aafī (talk) 11:56, 4 January 2024 (UTC)Reply[reply]

Votes

Comments

1989

Related requests:

Vote

1989 (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · CentralAuth)

Scheduled to end: 19:14, 9 January 2024 (UTC)

Hello. I am a contributor for over ten years and I was an active administrator from 2019–20. If I were to hold the role again, I would continue closing DRs, handling copyvio and speedy requests, dealing with spammers, etc. I feel I have addressed my actions that led to my clouded resignation and later events on my previous requests already. If I missed something or you want a newer perspective, let me know. 1989 (talk) 19:14, 2 January 2024 (UTC)Reply[reply]

Votes

  •  Oppose --A.Savin 21:59, 2 January 2024 (UTC)Reply[reply]
    Could you please argument your oppose? Thanks, A09 (talk) 09:59, 3 January 2024 (UTC)Reply[reply]
    Same as previous run. --A.Savin 12:00, 3 January 2024 (UTC)Reply[reply]
  •  Support -- I think 1989 should be given a chance.FitIndia Semi-retired 15:00, 3 January 2024 (UTC)Reply[reply]
  •  Support We can give a second chance and we face a high demand for new admins. GPSLeo (talk) 17:13, 3 January 2024 (UTC)Reply[reply]
  •  Support I didn't support the desysop in the first place. Andy Dingley (talk) 20:05, 3 January 2024 (UTC)Reply[reply]
  •  Support OK, it's been three years, I'm willing to give him a chance as long as he's able to take it. EPIC (talk) 23:36, 3 January 2024 (UTC)Reply[reply]
  •  Support * Pppery * it has begun... 01:48, 4 January 2024 (UTC)Reply[reply]
  •  Oppose.--RZuo (talk) 05:39, 4 January 2024 (UTC)Reply[reply]
  •  Support --Minorax«¦talk¦» 08:45, 4 January 2024 (UTC)Reply[reply]
  •  Support Admittedly I've never dealt with 1989 that I'm aware of, but it seems like what they lost the privilege for in the first place was pretty biennial and the fact that other admins support this helps reassure me that the problems aren't chronic. So I don't see any reason why they shouldn't receive a second chance at being an administrator. I'm sure there will be increased scrutiny this time around and that they will lose the tools again if they do anything to justify it. --Adamant1 (talk) 12:43, 4 January 2024 (UTC)Reply[reply]
  •  Support --Bedivere (talk) 14:59, 4 January 2024 (UTC)Reply[reply]
  •  Support per Adamant1. T CellsTalk 21:46, 4 January 2024 (UTC)Reply[reply]
  •  Support Definitely deserves a second chance -- 94rain Talk 23:48, 4 January 2024 (UTC)Reply[reply]
  •  Support --Mirer (talk) 23:52, 4 January 2024 (UTC)Reply[reply]
Changed to support. Last time I gave an AGF-pro (we need hundreds of admins more ...), why not this time. Just stay away from conflicts. ;-) --Mirer (talk) 01:27, 5 January 2024 (UTC)Reply[reply]
I think we are losing more then we are accepting at this point. Someone needs to make a list of reputable users and ask them to apply. --Adamant1 (talk) 01:58, 5 January 2024 (UTC)Reply[reply]
  •  Support like last time --Ameisenigel (talk) 09:49, 5 January 2024 (UTC)Reply[reply]
  •  Oppose the answers don't convince me that past issues won't be repeated. Natuur12 (talk) 16:33, 5 January 2024 (UTC)Reply[reply]
  •  Support Юрий Д.К 17:11, 5 January 2024 (UTC)Reply[reply]
  •  Oppose Thanks for offering to work on the backlog of DRs. This is much needed and I am open to second chances. However, I cannot fail to notice that there is barely any activity at Commons since the desysop with two exceptions, one significant peak in December 2021 short before the candidacy in January 2022 and now a small peak in November 2023. I expect more continuous activity from prospective admins to keep up with current developments. And I noticed in November a long series of similar DRs that should be handled as mass deletion request using VisualFileChange. Otherwise this puts unnecessary burden on the closing admins. --AFBorchert (talk) 22:44, 5 January 2024 (UTC)Reply[reply]
    I don't do mass DRs on backlog review categories as it causes issues like this to happen. 1989 (talk) 23:26, 5 January 2024 (UTC)Reply[reply]
    It would be great if the subpage could be more easily changed in VFC. But it is still possible to avoid this problem by creating a temporary category, adding this category to the to be deleted files (can be done using VFC), and then executing VFC on that category. This way you will get a unique DR page name. --AFBorchert (talk) 00:09, 6 January 2024 (UTC)Reply[reply]
  •  Oppose I also think that second chances are good however I have concerns about actual activity as outlined by AFBorchert I'm afraid. Herby talk thyme 08:27, 6 January 2024 (UTC)Reply[reply]
  •  Oppose Thanks for volunteering, but your very low activity since your desysop is not enough for me to support your candidacy. I'd like to see some sort of an endurable track record with laudable and friendly edits as a regular editor before an editor becomes an admin.Paradise Chronicle (talk) 10:22, 6 January 2024 (UTC)Reply[reply]
  •  Support I'm willing to give him a second chance. Jianhui67 T★C 10:56, 6 January 2024 (UTC)Reply[reply]
  •  Oppose per Herby --Mateus2019 (talk) 11:04, 6 January 2024 (UTC)Reply[reply]
  •  Support Thank you for volunteering. Christian Ferrer (talk) 12:19, 6 January 2024 (UTC)Reply[reply]
  •  Support As a gesture of good faith and redemption. The candidate is knowledgeable and long serving. I sincerely hope they have a sober appreciation of the impacts of previous interactions. We are servants and not masters. Take that seriously. If there is another fire that needs put out, it will be the last one. GMGtalk 14:32, 6 January 2024 (UTC)Reply[reply]
  •  Support I think its time to give them a second chance. A hard working admin and we need more of those right now Gbawden (talk) 18:41, 6 January 2024 (UTC)Reply[reply]
  •  Support go forth and prosper --Jonatan Svensson Glad (talk) 22:39, 6 January 2024 (UTC)Reply[reply]
  •  Oppose Has been inactive for months over the past years. I'm willing to offer a second chance to the candidate, but not at this point. --A1Cafel (talk) 09:56, 7 January 2024 (UTC)Reply[reply]
    That argument would apply if this was a new user applying for adminship. 1989 has sufficient experience and edits on Commons. Sometimes taking a break from being on Commons is good for balance. Gbawden (talk) 05:45, 8 January 2024 (UTC)Reply[reply]
  •  Oppose I agree with User:A1Cafel. Sorry. --Robert Flogaus-Faust (talk) 14:17, 7 January 2024 (UTC)Reply[reply]
  •  Support --MZaplotnik(talk) 15:07, 7 January 2024 (UTC)Reply[reply]
  •  Support --Estopedist1 (talk) 16:20, 7 January 2024 (UTC)Reply[reply]
  •  Support -- per GMG above -- Schlurcher (talk) 08:04, 8 January 2024 (UTC)Reply[reply]
  •  Oppose Taivo (talk) 11:52, 8 January 2024 (UTC)Reply[reply]
  •  Support Jon Kolbert (talk) 21:25, 8 January 2024 (UTC)Reply[reply]
  •  Neutral Per the questions below. I would have liked to give my support but I think they need to refresh their understanding of what a derivative work is and what types of works are covered by COM:Screenshot. From Hill To Shore (talk) 21:35, 8 January 2024 (UTC)Reply[reply]
  •  Support An admin who is active even one month out of the year will do more to reduce the backlog than a user without the mop. Pi.1415926535 (talk) 23:40, 8 January 2024 (UTC)Reply[reply]

Comments

  • Question Today you marked File:Jembatan teluk lais musi banyuasin.jpg for speedy deletion as a file containing derivative elements without evidence of permission. What aspects of the file do you see as derivative? From Hill To Shore (talk) 12:22, 3 January 2024 (UTC)Reply[reply]
    The whole picture really. It looks like a screenshot, and the information provided by the uploader was quite vague. It was also unlikely this image was released under a CC 3.0 license, as there was no proof of that. If the image is in the Public Domain, they would need to provide verifiable information. Also, a speedy deletion would mean the file being removed ASAP. The tag I added gives the uploader seven or more days to resolve the concern regarding the image. 1989 (talk) 16:46, 3 January 2024 (UTC)Reply[reply]
    I was hoping that you would either acknowledge the image has no derivative elements or identify a derivative aspect I may have missed. In this case {{Dw no source since}} appears to be the wrong option and {{No source since}} would probably have been better. It may seem like a minor difference as they both allow deletion after 7 days but the key difference is giving advice on derivative elements when there aren't derivatives is likely to confuse editors. From Hill To Shore (talk) 15:34, 6 January 2024 (UTC)Reply[reply]
    Screenshots are considered derivative works. 1989 (talk) 15:52, 6 January 2024 (UTC)Reply[reply]
    There is nothing in the image to indicate it is a en:Screenshot. It is a simple photograph sourced from an unknown medium. Whether the uploader scanned it from a physical source, saved it from a website or used screen capture software to extract only the photograph (and no other aspects of the screen) doesn't make much of a difference. With a single item subject to copyright, there are no considerations of derivatives regardless of source. It is simply a matter of the licence for the single item in the file. From Hill To Shore (talk) 16:29, 6 January 2024 (UTC)Reply[reply]
  •  Question Do you apologize for things like this [2]? And can we trust that things like this will not happen again? GPSLeo (talk) 14:46, 3 January 2024 (UTC)Reply[reply]
    Yes. It was in the heat of the moment, but like Rubin16 said, I should have not reacted so quickly. There are moments like that where I wished I could have logged off. During that time, I found the threatening message repulsive as I don't think I've done anything so bad as to get reported to WMF. It also didn't help that earlier on, I had told them to leave me alone. I felt during that time maybe I needed something stronger to help them get the message. However, a simple "stay away from my talk page" would have been sufficient. I later realized from that point moving forward, especially after the ANU drama, that me and A.Savin should avoid each other at all costs. As for if it would happen again, very unlikely. It should be the first and last time I tell someone to fuck off. 1989 (talk) 16:24, 3 January 2024 (UTC)Reply[reply]
    @GPSLeo: Please note that a) there never was any personal apology for the f-word summary, and b) this edit is only one single example out of the long track of hatespeech by 1989 against me; including demand of my ban in the discussion linked above, and also the block of mine is part of that. It's been always a puzzle to me what have I done to deserve this. --A.Savin 23:01, 5 January 2024 (UTC)Reply[reply]
  •  Comment Please enable receiving emails from other users in Special:Preferences#mw-prefsection-personal. --EugeneZelenko (talk) 15:08, 3 January 2024 (UTC)Reply[reply]
    ✓ Done 1989 (talk) 16:24, 3 January 2024 (UTC)Reply[reply]
  •  Question A major reason for your desysop was your blocking, on separate occasions, of two different admins. What precautions do you plan to take in the future before blocking well-established users? -- King of ♥ ♦ ♣ ♠ 17:57, 3 January 2024 (UTC)Reply[reply]
    If I feel there is a situation where an admin or a well-established user is doing misconduct, I will bring that to the attention of an appropriate discussion board like ANU. Anything like a compromised account or blatant admin abuse like deletion / blocking sprees, should be met with swift action to protect the community. 1989 (talk) 18:11, 3 January 2024 (UTC)Reply[reply]
  •  Question Were you active in another Wikimedia project when you were not active on commons? I mean you have very few edits on commons mainspace and own user talk since 2020 and maybe it would be good to have a track record of some friendly talk page behavior. Your past RfAs are not showing the best of you and judging from them I tend to oppose.Paradise Chronicle (talk) 00:38, 4 January 2024 (UTC)Reply[reply]
    The only other place I edit is enwiki. I've gotten very little messages since 2020, which explains why there are a few edits on my talk page. Regarding the Commons namespace, most edits there were me closing a lot of deletion requests. 1989 (talk) 20:33, 4 January 2024 (UTC)Reply[reply]
I'm sure your cognizant of this already, but the deletion request back log really needs to be dealt with. So it would be great if you continued to mainly work on closing deletion requests if or when you get the privileges back. --Adamant1 (talk) 05:22, 5 January 2024 (UTC)Reply[reply]
Sure thing. 1989 (talk) 23:27, 5 January 2024 (UTC)Reply[reply]
  •  Question In your last Rfa you said to me that I was "lucky", I quote: " (...) being lucky to keep their bit". 1/ I never felt lucky of that outcome as I already said, and I still don't feel "lucky", I would give a lot for a different ending of that story. 2/ to think that the result of a Rfa or a Rfda is the result of luck is somewhat insulting towards the community vote. Hence my very simple question: when you have writted the statement for this request, and when you answered to your colleagues above, are you sincere? or do you count on "luck"? The question is very simple and expect a very simple and short answer. Christian Ferrer (talk) 08:56, 6 January 2024 (UTC)Reply[reply]
    Yes Christian Ferrer, I'm being sincere. 1989 (talk) 12:18, 6 January 2024 (UTC)Reply[reply]

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.

No current requests.

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.

See also

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Administrators&oldid=815381973"