Open main menu

Wikimedia Commons β

Commons:Administratoren

(Redirected from Commons:Administratoren)
This page is a translated version of a page Commons:Administrators and the translation is 100% 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.

Shortcut: COM:A · COM:ADMIN · COM:SYSOP

Other languages:
als • ‎مصرى • ‎asturianu • ‎български • ‎বাংলা • ‎brezhoneg • ‎català • ‎dansk • ‎Deutsch • ‎Ελληνικά • ‎English • ‎Canadian English • ‎español • ‎فارسی • ‎suomi • ‎français • ‎galego • ‎עברית • ‎हिन्दी • ‎magyar • ‎Հայերեն • ‎interlingua • ‎Bahasa Indonesia • ‎italiano • ‎日本語 • ‎한국어 • ‎Lëtzebuergesch • ‎नेपाली • ‎occitan • ‎polski • ‎پښتو • ‎português • ‎русский • ‎sicilianu • ‎svenska • ‎Türkçe • ‎українська • ‎Tiếng Việt • ‎中文
Commons Administrator.svg

Diese Seite erklärt die Rolle von Administratoren (manchmal auch Admins bzw. Sysops) auf Wikimedia Commons. Bitte beachte, dass die Rolle der Administratoren und die Voraussetzungen, Administrator zu werden, von denen anderer Projekte abweichen können.

Wenn du die Hilfe eines Administrators brauchst, wende dich bitte an das Administrators' noticeboard.

Es gibt derzeit 239 Administratoren auf Commons.

Ein Admin mit Wischmop, ein typisches Symbol von Administratoren. Siehe auch: Der gute Admin.

Was ist ein Administrator?

Administrators as of August 2017 [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 239

  1. -revi, ko, en-3 (global renamer)
  2. ~riley, en, fr-1, es-1
  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. Achim55, de, en-3, nds-3, la-2
  8. AFBorchert, de, en-3
  9. Ahonc, uk, ru-4, en-2, de-1 (global renamer)
  10. Aka, de, en-3
  11. Alan, es, eu-3, en-2
  12. Alison, en, ga-3, fr-2, gd-1
  13. Alno, fr, en-3, es-2, pt-1
  14. Amada44, de, en-3, fr-1
  15. Angr, en, de-4, fr-2, ga-2, la-2, cy-1
  16. Ankry, pl, en-2, ru-1
  17. AnRo0002, de, en-2, fr-2, es-1
  18. Anthere, fr, en-3
  19. Aude, en, ar-2, de-2, es-3
  20. Avraham, en, he-2 (steward)
  21. AzaToth, sv, en-4
  22. Badseed, el, en-3, it-1
  23. Barcex, es, en-2, fr-1
  24. Bastique, en, fr-3, es-2, la-2, ga-1
  25. Basvb, nl, en-3, de-2
  26. Benoit Rochon fr, en-4
  27. Beria, pt, en-2, es-2
  28. Billinghurst, en
  29. Blackcat, it, en-3, fr
  30. BrightRaven, fr, en-3, nl-2, es-2, zh-1
  31. Butko, ru, uk-2, en-1
  32. Cambalachero, es, en-3
  33. Captain-tucker, en
  34. ChrisiPK, de, en-3, fr-1
  35. Christian Ferrer, fr, en-3, es-1
  36. Ciell, nl, en-2, de-1
  37. Common Good, en
  38. Cookie, es, en-2
  39. Courcelles, en, es-2, fr-2
  40. Czar, en
  41. DaB., de, en-1
  42. Dantadd, it, pt, en-3, es-3, fr-3, gl-3, ca-2, ro-1, el-1
  43. Darwinius, pt, en-3, es-2, fr-2, gl-2, ca-1, it-1, oc-1
  44. Davepape, en
  45. David Levy, en
  46. De728631, de, en-5
  47. Dereckson, fr, en-3, de-1, nl-1
  48. DerHexer, de, en-3, grc-3, la-3, es-1 (steward)
  49. Dharmadhyaksha, mr, en-3, hi-3
  50. DMacks, en
  51. Didym, de, en-2, fr-2
  52. Dschwen, de, en-3, fr-1 (bureaucrat)
  53. D-Kuru, de, en-2, it-1
  54. Ebrahim, fa
  55. Edgar181, en, de-1, fr-1, es-1
  56. Elcobbola en, de (checkuser)
  57. Eleassar, sl, en-3, de-2, fr-2
  58. Elitre, it, en-3, fr-2
  59. Ellin Beltz, en (bureaucrat)
  60. Emha, de, bar, en-3, fr-1
  61. Érico, pt, en-2, es-1 (global renamer)
  62. EugeneZelenko, ru, be, en-2, bg-1, pl-1 (bureaucrat)
  63. Ezarate, es-3, en-1
  64. Fanghong, zh, en-2, fr-1
  65. Flominator, de, als, en-3
  66. FunkMonk, da, en-4, no-3, fo-2, sv-2, de-1, es-1
  67. Geagea, he, ka-3, en-3, ru-1
  68. Geni, en
  69. George Chernilevsky, ru, uk-3, de-2, en-2, bg-1, la-1, be-1, fr-1
  70. Gestumblindi, als, de, en-3
  71. Gnangarra, en
  72. Golbez, en, ja-2
  73. Green Giant, en, de-1, fr-1
  74. grin, hu, en-3, de-1
  75. Gruznov, ru, en-1, fr-1
  76. Hedwig in Washington, de, en-4, nds-1
  77. Hekerui, de, en-4
  78. Herbythyme, en, fr-2, es-1, it-1
  79. Hesperian, en
  80. HJ Mitchell, en
  81. Howcheng, en, ja-2
  82. Huntster, en
  83. Hystrix, de, en-1
  84. Indeedous, de, en-3, fr-2
  85. Infrogmation, en, es-1
  86. Jameslwoodward, en, fr-1 (bureaucrat, checkuser)
  87. January, en
  88. Jaqen, it, en-2
  89. Jarekt, pl, en
  90. JarrahTree, en, id-1
  91. Jastrow, fr, en-3, ro-2, de-1, it-1
  92. Jcb, nl, en-3, es-3
  93. Jcornelius, de, lt-2, la-2, en-2, pt-2, fr-1
  94. Jdforrester, en
  95. Jdx, pl
  96. Jean-Frédéric, fr, en-4, es-1
  97. JGHowes, en, fr-2, de-1
  98. Jianhui67, en, zh-3, ms-1 (global renamer)
  99. Jmabel, en, es-3, ro-2, de-1, ca-1, it-1, pt-1, fr-1
  100. Joergens.mi, de, en-3
  101. John Vandenberg, en
  102. Josve05a, sv, en-3
  103. Juliancolton, en
  104. Julo, pl, en-2, de-1, ru-1
  105. JuTa, de, en-2, fr-1 (bureaucrat)
  106. Jusjih, zh, en-3, fr-1, ko-1
  107. Kaldari, en
  108. Kallerna, fi, en-3, sv-2, de-1
  109. Kelly, en
  110. King of Hearts, en, zh-3, es-2, ja-1
  111. Klemen Kocjancic, sl, en-3, de-2, hr-1, bs-1
  112. Krd, de, en-3 (bureaucrat, checkuser)
  113. Krinkle, nl, en-3, de-2
  114. KTo288, en, zh-4
  115. Kwj2772, ko, en-2
  116. Leit, de, en-3, fr-1
  117. Léna, fr, en-3, es-1
  118. Leyo, gsw, de, en-3, fr-3, es-1, la-1
  119. Lokal Profil, sv, en-4, pt-2, fr-1
  120. Lymantria, nl, en-3, de-2, fy-2, fr-1, zea-1
  121. Magog the Ogre, en, es-2 (checkuser)
  122. Maire, pl, en-4, es-2, fr-2, de-2, ru-1 (global renamer)
  123. Marcus Cyron, de, en-2
  124. Mardetanha fa, az, en-3, tr-2, ar-1 (steward)
  125. Martin H., de, en-2
  126. Masur, pl, en-3, de-1
  127. Matanya, en, he (steward)
  128. Materialscientist, en-4, ru-4, nl-3, fr-1, es-1
  129. Mates, cs, en-3, sk-4, de-1
  130. Mattbuck, en, fr-1, la-1
  131. Maxim, ru, en-3, fr-2
  132. MBisanz, en (steward)
  133. McZusatz, de, en-3, es-1, la-1 swg-1
  134. Mentifisto, en, mt, it-2 (steward)
  135. MichaelMaggs, en, fr-1 (bureaucrat)
  136. Micheletb, fr, en-3, it-1, es-1
  137. Missvain, en
  138. Mitchazenia, en, es-2
  139. Miya, ja, en-2
  140. Mmxx, fa, en-3
  141. Moheen Reeyad, bn, as-1, bpy-1, en-3, hi-1, hif-1
  142. Mono, en
  143. Morgankevinj, en, es-1, la-1
  144. Mormegil, cs, en-2, de-1
  145. M0tty, fr, en-1
  146. MPF, en, da-2, de-1, fr-1
  147. Multichill, nl, en-3, de-1, fr-1
  148. Mys 721tx, zh, en-3 (global renamer)
  149. Nagy, de, en-3, fr-2, es-1, sv-1
  150. NahidSultan, bn, en-3, bpy-1
  151. Natuur12, nl, en-3, de-1
  152. Neozoon, de, en-4, nl-4, fr-2
  153. Nick, en, sco-2, fr-1
  154. Nilfanion, en, fr-1
  155. NordNordWest, de, en-3
  156. notafish, fr, en-4, de-3, es-2, it-2
  157. Nyttend, en, ang-1
  158. odder, pl, en-4, de-2 (bureaucrat, oversighter)
  159. Okki, fr, en-2
  160. Otourly, fr, en-2, it-1
  161. P199, en, nl, fr-2, tl-2, de-1
  162. Perhelion, de, en-3
  163. Pi.1415926535, en, es-2
  164. PierreSelim, fr, en-3, es-1 (oversighter)
  165. Pitke, fi, en-4, sv-2
  166. Platonides, es, en-2, fr-1
  167. Pleclown, fr, en-3
  168. Poco a poco, es, de-4, en-3, fr-2, it-2, pl-2, pt-1
  169. Podzemnik, cs, en-2
  170. Polarlys, de, en-2, fr-1, no-1
  171. PumpkinSky, en, de-2
  172. Putnik, ru, en-2
  173. Pyb, fr, en-2
  174. Pymouss, fr, en-3, de-2, it-2, he-1
  175. Ragesoss, en, de-1, fr-1
  176. Ra'ike, de, en-2
  177. Rama, fr, en-3, de-2, la-2, es-1, it-1, ja-1 (oversighter)
  178. Rastrojo, es, en-3, fr-2, eo-1
  179. Raymond, de, en-3, nl-1 (oversighter)
  180. Rehman, en, si-1
  181. Reinhard Kraasch, de, en-3
  182. Revent, en (oversighter)
  183. Rimshot, de, en-4, fr-2, it-1
  184. Rodhullandemu, en, fr-1, de-1, sv-1
  185. Romaine, nl, en-3, de-2, af-1, fr-1
  186. Ronhjones, en, fr-1
  187. Rosenzweig, de, en-3, fr-1, la-1
  188. Royalbroil, en, es-1
  189. RP88, en, de-1
  190. Rubin16, ru, tt, en-3 (global renamer)
  191. Rudolphous, nl, en-3, de-2
  192. Ruthven, it, fr, en-4, es-4, nap-4, ca-2, de-1
  193. Sanandros, als, de, en-3, fr-1
  194. Sandstein, als, de, en-4, fr-3, it-1
  195. Sealle, ru, en-4, pl-2, sk-2, uk-2
  196. Shizhao, zh, en-1, ru-1
  197. Siebrand, nl, en-3, fr-1, de-1
  198. Sphilbrick, en
  199. Spiritia, bg, en-3, ru-2, mk-2, de-1
  200. Sreejithk2000, ml, en-3, hi-3, ta-1, kn-1
  201. Srittau, de, en-3
  202. Steinsplitter, bar, de-4, it-3, en-1 (global renamer)
  203. Stifle, en, ga, fr-2, de-1
  204. Storkk, en, fr-3, de-2, eo-2
  205. Tabercil, en
  206. Taivo, et, en-3, ru-3, de-1
  207. Tarawneh, en, ar, de-1
  208. Techman224, en
  209. Teles, pt, en-3, es-2 (steward)
  210. Themightyquill, en, fr-2, de-1, hu-1
  211. Thibaut120094, fr, en-2, ja-2
  212. Thuresson, sv, en-3, no-2
  213. Trijnstel, nl, en-4, de-1, fr-1 (checkuser, steward)
  214. tsca, pl, en, da
  215. Túrelio, de, en-3, es-1
  216. VIGNERON, fr, de-2, en-2, zh-1
  217. Waldir, pt, en-3
  218. Wdwd, de, en-2
  219. Well-Informed Optimist, ru, uk-4, en-3
  220. Whym, ja, en-2
  221. Wikitanvir, bn, en-3, as-2, bpy-1 (steward)
  222. WJBscribe, en, fr-3, de-1 (global renamer)
  223. Wsiegmund, en, fr-1, es-1
  224. Wutsje, fy, nl, en-3, de-2, fr-1
  225. Wuzur, de, en-3
  226. wvk, de, en-4, fa-3, fr-2
  227. Yann, fr, en-4, hi-2, gu-1
  228. Yarl, pl, en-2, de-1, ru-1
  229. Yasu, ja, en-2, de-1
  230. Ymblanter, ru, en-3, de-2, fr-2, nl-2, it-1, es-1
  231. Yuval Y, he, en-3
  232. Zhuyifei1999‎, zh, en-4
  233. Zzyzx11, en, es-1, fr-1
  234. とある白い猫, en, tr, az-3, ja-2, fr-1, nl-1
  235. CommonsDelinker, (bot)
  236. CommonsMaintenanceBot, (bot) see request
  237. Embedded Data Bot, (bot) see request
  238. GifTagger, (bot) see request
  239. KrinkleBot, (bot) see request

The system currently recognizes 239 administrators. If that is not the last number in the list above, there is an error in the list.

Technisch

Administratoren sind Benutzer mit folgenden Rechten:

  • Bilder oder andere hochgeladene Dateien löschen und wiederherstellen bzw. gelöschte Versionen einsehen und wiederherstellen
  • Seiten löschen und wiederherstellen bzw. gelöschte Versionen einsehen und wiederherstellen
  • Seiten schützen und auch den Schutz wieder aufheben sowie geschützte Seiten bearbeiten
  • Benutzer und IP-Adressen/IP-Adressbereiche sperren und entsperren
  • Seiten im MediaWiki-Namensraum bearbeiten
  • Dateien umbenennen
  • Benutzer verschiedenen Gruppen hinzufügen und wieder daraus entfernen
  • Upload Wizard-Kampagnen konfigurieren
  • Einzelne Logbuch-Einträge sowie einzelne Versionen von Seiten löschen und wiederherstellen
  • Seiten aus anderen Wikis importieren
  • Versionsgeschichten von Seiten vereinen
  • Missbrauchsfilter-Einstellungen bearbeiten
  • Beim Verschieben die Erstellung einer Weiterleitung unterdrücken
  • Die Benutzernamens-Ähnlichkeitsprüfung und die schwarze Liste unerwünschter Seiten- oder Benutzernamen außer Kraft setzen
  • Gleichzeitig Nachrichten an mehrere Benutzer senden (massmessage)
  • Höhere Limits in API-Abfragen

Diese Rechte sind allgemein als Administrationswerkzeuge bekannt.

Rolle in der Gemeinschaft

Administratoren sind erfahrene und vertrauenswürdige Mitglieder der Commons-Benutzerschaft, die zusätzliche Verwaltungsaufgaben übernommen haben und nach Konsens/Abstimmung mit den Administrationswerkzeugen ausgestattet wurden. Administratoren haben unterschiedliche Interessen- und Fachgebiete; typische Aufgaben eines Administrators sind die Bearbeitung und Erledigung von Löschanträgen, das Löschen von Urheberrechtsverletzungen, das Wiederherstellen von Dateien, das Schützen von Commons vor Vandalismus und die Bearbeitung von Vorlagen und anderen geschützten Seiten. Selbstverständlich können einige dieser Aufgaben auch von Benutzern ohne erweiterte Rechte erledigt werden.

Von Administratoren wird erwartet, dass sie die Ziele des Projekts verstehen und bereit sind, konstruktiv mit anderen auf diese Ziele hinzuarbeiten. Administratoren sollten außerdem Commons' Richtlinien verstehen und befolgen und gegebenenfalls den Konsens der Community befolgen.

Außerhalb von Rollen, die die Benutzung von Administrationswerkzeugen bedingen, haben Administratoren keine besondere redaktionelle Autorität durch ihre Position. In Diskussionen und Abstimmungen werden ihre Beiträge genauso behandelt wie die jedes anderen Benutzers. Natürlich sind einige Administratoren einflussreich, aber das liegt nicht an ihrer Position als solcher, sondern an dem Vertrauen, das sie sich in der Community erworben haben.

Vorschläge für Administratoren

Entzug von Adminrechten

Gemäß der Entzugs-Richtlinie können Adminrechte bei Inaktivität oder Missbrauch wieder entzogen werden.

Bewerbung als Administrator

Alle Benutzer, die Administratorenrechte erlangen möchten, müssen durch diesen Prozess gehen und eine Anfrage zu Administratorenrechten stellen, das schließt auch alle ehemaligen Administratoren ein, die ihre früheren Rechte wiedererlangen möchten.

Gehe als erstes auf Commons:Administrators/Howto und lies dir die Seite gründlich durch. Danach kannst du zurückkommen und im folgenden Abschnitt deine Kandidatur starten.

  • Nachdem du auf den passenden Button geklickt und die Unterseite angelegt hast, kopiere den Link zur Unterseite, beispielsweise "Commons:Administrators/Requests/Benutzername", bearbeite Commons:Administrators/Requests und füge ihn oben im entsprechenden Abschnitt ein. Danach umschließe ihn mit doppelten geschweiften Klammern (beispielsweise {{Commons:Administrators/Requests/Username}}), um die Unterseite einzubinden.
  • Wenn du von jemandem nominiert wurdest, akzeptiere bitte die Nominierung durch einen kurzen Kommentar und deine Signatur. Die Unterseite muss dann durch dich oder den Nominierenden entsprechend eingebunden werden.
Ersetze in der folgenden Box Username durch deinen Benutzernamen:



Abstimmung

Jeder registrierte Benutzer kann sich an der Abstimmung beteiligen. Wenn ein Benutzer bisher erst wenige oder gar keine Beiträge gemacht hat, könnte seine Stimme jedoch nicht vollständig gewichtet werden. Es ist gern gesehen, wenn die Gründe für   Support- oder   Oppose-Stimmen angegeben werden, da dies dem Bürokraten, der über den Antrag entscheidet, bei seiner Entscheidung hilft. Eine gute Begründung, bei Bedarf mit entsprechenden Nachweisen, kann stärker gewichtet werden als eine bloße Pro- oder Kontra-Stimme.

Damit der Antrag erfolgreich ist, werden normalerweise mehr als 75% Zustimmung und mindestens 8 positive Stimmen erwartet. Allerdings hat der bearbeitende Bürokrat einen Spielraum bei der Einschätzung des Community-Konsens und die Entscheidung muss nicht ausschließlich auf bloßen Zahlen beruhen.

  Neutrale Kommentare werden zur Ermittlung der prozentualen Pro-/Kontra-Ergebnisse nicht mitgezählt. Jedoch sind solche Kommentare Teil der Diskussion, können andere Diskussionsteilnehmer umstimmen und dem Bürokraten beim Verständnis des Community-Konsens behilflich sein.

Cache leeren Benutze den untenstehenden Bearbeiten-Link, um die eingebundene Seite zu bearbeiten.

Requests for adminship

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.

Daphne Lantier (desysop)

Vote

Daphne Lantier (talk · contributions · deleted user contributions · recent activity · logs · block log · global contribs · SULinfo)

Scheduled to end: 07:16, (UTC)

In the course of a sockpuppet investigation at en:wp, Courcelles confirmed Daphne Lantier to be a socket of INeverCry. Daphne Lantier herself confirmed the connection by blocking INeverCry, deleting INeverCry's user page, and by marking both accounts as sockpuppets of each other ([1], [2]). During the time span from 01:53 when Courcelles confirmed the connection and 04:44 when admins rights were temporarily removed by Matiia, Daphne Lantier deleted thousands of files prematurely from recent deletion requests without closing the requests. Short discussions were held at COM:AN/U#Daphne Lantier has been determined to be a sock of INeverCry and COM:BN#Daphne Lantier's admin rights. Another thread was opened at Meta by INeverCry which states

@Billinghurst:, @Trijnstel:, and to whom it may concern. I just want to let stewards know that while I was an admin at Wikimedia Commons under the sock account Daphne Lantier, the 80,000 log actions I performed were all legitimate and conscientious. I followed policy and didn't do a single log action that was bad or questionable in any way. If someone can let Commons admins and crats know this, I would appreciate it. I don't want to see anybody there wasting time looking for something that isn't there. They'll have plenty of work cleaning up my actions of tonight, but that was just a sendoff gesture. It was the only time I abused the tools as Daphne. I'm telling you this for the benefit of the admins and editors I like at Commons. Good night. Take care.

As the emergency steward action is of temporary nature it seems appropriate to determine in a regular community process whether we want to desysop Daphne Lantier in the light of the recent events. --AFBorchert (talk) 07:16, 11 August 2017 (UTC)


Votes

  •   Neutral. I trust him to be a good admin (clarification) when he is stable, but when he overreacts he can cause massive damage. I don't know how to weigh between these. --Zhuyifei1999 (talk) 07:22, 11 August 2017 (UTC)
  •   remove. I have absolutely no trust in a socking administrator where one sock nominated the other as admin, who also participated twice as OTRS member under different names ([3], [4]), and who finally leaves us plenty of work cleaning up. --AFBorchert (talk) 07:43, 11 August 2017 (UTC)
  •   remove We could have discussed the sock issue openminded, but leaving the scene by burning bridges is definitely beyond anything I could accept or apologize. Abusing the admin tools leads to removal of the admin tools, undoubtedly. --Krd 07:45, 11 August 2017 (UTC)
  •   Remove and block indef INC lost their admin rights "under a cloud" and promising to never again seek adminship. When they later broke that promise (Commons:Bureaucrats' noticeboard/Archive 2017#Return of my sysop bit..again...) the community made it very clear the answer was no. I know a few admins wanted them to continue as they are useful when they behave themselves, but many were tired of the whole thing. Then INC nominated their long-term sock account Daphne for adminship. Once this was achieved, INC stopped editing Commons. The Daphne account has been around for two years. That's long term mistrustful behaviour, not a "clean start" account newly created. This dishonesty shows such disrespect to the community. I don't believe INC/Daphne has any longer a place on Commons, either as admin nor user. I'm also very disappointed in those who appear to have known of this and kept it secret. Their participation at OTRS is also a matter of concern. No matter what one's views on the various issues facing Commons, an open wiki like this needs to be built on trust and honesty among participants. INC appears to be neither trustworthy nor honest. -- Colin (talk) 07:48, 11 August 2017 (UTC)
  •   remove per Krd. --Magnus (talk) 07:55, 11 August 2017 (UTC)
  •   remove due to the mass damage caused on Commons and subsequently across multiple projects as a result. - Cameron11598(talk) 08:07, 11 August 2017 (UTC)
  •   remove - not for being INC, but for the damage of last night. I knew this desysop was coming one day and I was on my way to vote keep, but what happened this night made that impossible unfortunately. By the end of March it must have been clear to dozens of active users that Daphne was INC. It was pretty obvious. I think the community as a whole is partly to blame here for creating a hostile environment in January. I find it very weird that first we allow them to keep our backlogs under control for 4 months and then out of the blue someone reaches out to the CUs to ask them to say what we all have been knowing for several months. INC/Daphne used to be a good admin, who did a huge amount of work. I find this a very sad situation. I urge all fellow admins to have their share in compensating the 500-700 daily log actions they used to do. Jcb (talk) 08:14, 11 August 2017 (UTC)
Jcb, not all of the community hangs out on IRC and the DR forums. The January event was mainly caused by INC's broken promise and a 'crat making an unwise decision, so don't go blaming the community. It seems some admins are willing to turn a blind eye in order to get the backlog down. I think you need to place "trust" a little higher up the requirements for admin than "highly active". Any admin who knew of this "pretty obvious" situation and permitted it should IMO resign. You've all let us down and demonstrated remarkably poor judgement. -- Colin (talk) 08:31, 11 August 2017 (UTC)
FWIW, I've never seen Jcb on IRC, and I know a few admins who knows about DL == INC, none of them filed a RfCU, except that one. --Zhuyifei1999 (talk) 08:32, 11 August 2017 (UTC)
+1. I'm not sure I'm looking for actual resignations, but I find the "Oh, I thought everyone knew" responses pretty disgusting. I guess it's sort of darkly amusing that offline, I'm probably the most cynical person I know. Clearly online, I'm a naif. I've lost a lot of trust with this revelation, and not just in the person concerned in this desysop. Storkk (talk) 09:08, 11 August 2017 (UTC)
Yes, I think every active administrator who did not recognize them months ago may be naive. Did you really think that a new administrator may start with a daily 500-700 log actions rate and maintain such a rate 7 days a week, week after week? I think even most of our most experienced admins cannot do this rate. Do you think that I should have come to a noticeboard to tell the community what everybody could see, but without being able to provide any proof for my observation? As long as they were a nett positive admin (which they were IMHO), I saw no priority to take any action. It's mainly because they double voted in two EN-wiki RfA's that the CU request was accepted and executed. Jcb (talk) 09:26, 11 August 2017 (UTC)
It took me by surprise. But I had very low levels of activity in the recent months that I did not even notice that Daphne Lantier took over the workload of INeverCry. In hindsight I see that Daphne Lantier/INeverCry did not really hide their socking. Just compare the combination of user boxes at en:wp (1, 2). The similarity is quite striking. --AFBorchert (talk) 09:41, 11 August 2017 (UTC)
Given that what I saw "Daphne" doing was pretty much exclusively robo-closing, making easy decisions, and leaving the default rationales and messages, I did not think it required a great deal of experience, no. Just a strong mouse-clicking finger and an inclination towards repetitive tasks. I do see the user/talk page similarity, but put that down to the fact that people often take other's user pages as templates. Anyway, yes I was naive... Storkk (talk) 10:45, 11 August 2017 (UTC)
It took me by surprise as well. I know we have some active admins, and some vey active dmins around, and was not that surprised that a user could close simple DRs in a fast pace, since....I only see the onces closed for the once I myself have started. I joined IRC on the ay of the SPI when the "socks" were being discussed, but without any evidence. This was the first I ad hea of it, or noticed. SO I decided to do some minor digging and try and get a CU check on enwp, since that is where ost CUs are, and where both users were still active. It's sad to see. I was telling a CU on IRC yesterday that I wuld oppose a desyops/vote keep on this vote, however the "chaos" they left us with is inexcusable, sadly. --Jonatan Svensson Glad (talk) 16:32, 11 August 2017 (UTC)
  •   remove Auch wenn wir einen sehr aktiven Admin verlieren. Das Löschen von mehr als 1.000 Dateien in einem Rutsch, aus welchem Frust auch immer, ist ein No-go. Mit der Aufarbeitung sind etliche Mitarbeiter auf Tage beschäftigt. Und diese dünne Entschuldigung von INC reicht mir nicht. Hystrix (talk) 08:19, 11 August 2017 (UTC)
  •   Remove. —MarcoAurelio 08:45, 11 August 2017 (UTC)
  •   Remove We cannot rely on admins who become unstable. Especially if it happens so often. Ankry (talk) 09:06, 11 August 2017 (UTC)
  •   Remove and indef block per Colin and AFBorchert. Storkk (talk) 09:08, 11 August 2017 (UTC)
    • To flesh out my reason for thinking an indef block is appropriate: firstly, the manner of INC's nomination of "Daphne" for admin, and secondly the flagrant determination to continue socking displayed in this comment on enwiki. Storkk (talk) 09:47, 11 August 2017 (UTC)
    • I think it worth noting here before it gets archived, that the deception appears to have been planned at least as far back as 2013 with User:Rosario_Berganza ([5]). Storkk (talk) 07:40, 14 August 2017 (UTC)
  •   Remove; but considering the health issues he had mentioned earlier, I wish if everybody keep this discussion as gentle as possible. Hope he can recover soon. Jee 09:57, 11 August 2017 (UTC)
  •   Remove; per Krd--Praveen:talk 10:06, 11 August 2017 (UTC)
  •   Remove, block the account indefinitely, as well as the INC account, and ban the user. Pleclown (talk) 10:20, 11 August 2017 (UTC)
  •   Remove and block all INC's accounts indefintely. The user should be considered banned from Commons. They also gained access to OTRS through the second account, so I will be asking the WMF about placing either a community global ban or WMF Office ban on INC. Nick (talk) 10:47, 11 August 2017 (UTC)
  •   Remove Fuck. I can't believe that Daphne is in fact a sock of INC. They lied, and an admin must be honest. No matter how many good actions they made, honesty is still the best policy (as a lot of us say). I also support a community + WMF global ban (why not just WMF you say? of course, two is better than one. no seriously, a community + WMF global ban is a sign that the community supports the ban, so there is absolutely no reason to doubt it). --Poyekhali 11:18, 11 August 2017 (UTC)
  •   Remove, per https://commons.wikimedia.org/w/index.php?title=Special:Log&page=Main+Page. This is just bizarre, coming from a longtime admin who did great work, and when I ran across en:WP:AN#Rouge Commons Admin, I thought it was some sort of a joke or massive mistake/misunderstanding, but you can't give me a better idea of a rogue admin than someone who deletes the Main Page without doing an instant "oops, wrong page!" restoration. And that's totally unrelated to sockpuppetry; having been shown the en:wp checkuser results and this edit here, there's no room to imagine that it's not abusive sockpuppetry, and abusive sockuppetry to the point that an indefinite block is needed. And indefinitely blocked users mustn't be admins. Nyttend (talk) 11:39, 11 August 2017 (UTC)
  •   Remove per Krd and Nyttend. Jianhui67 TC 11:43, 11 August 2017 (UTC)
  •   remove Nobody had more chances than INC. Nobody is forgiven more for their mistakes than INC. Even really severe once like a rogue blocking spree. But yet again this user betrays this community. Yet again this user lies to this community and yet again this user has damaged our community greatly. Will we have to look at every new person who wants to become admin with suspect because this person might be one more sock? Hours of volunteer time stolen from those who had to clean up the last rogue spree.
This user managed to gain access to the OTRS-team with a sock. A position which requires great trust. No, there no coming back from this. This is not the first time that INC burned his bridges. Burning bridges is an act which you commit when you want to close a chapter. I suggest that is what he does. Leaving and not coming back in a really long time. I would also support and indef ban for both accounts and any other sock that might be left. Natuur12 (talk) 12:13, 11 August 2017 (UTC)
  •   remove basically by Jcb above. I would have accepted a fresh restart, but events last night prove that INC/DL is definitely not fit for adminship. :( Yann (talk) 12:30, 11 August 2017 (UTC)
  •   remove I can be lenient about many things, but someone who flippant states "No worries. I've got other accounts I can use." and make a big mess on Commons for no good reason, that is not someone I want as an admin. --cart-Talk 12:36, 11 August 2017 (UTC)
  •   remove admin bit The user has from a position of trust (following being in previous positions of high trust) abused the community in a multiple ways, and most importantly deleting images through spite. Deletion in that way is solely sufficient for permanent removal of rights. I would also think that checkuser records should be taken and recorded for any future cross-check, and the checks should be coordinated with stewards, or other wikis. We know that the user will most likely try again to get rights, that is their level of fascination with the project. I believe that an extended block is also required, though it should not be permanent, there is no value in perm block.  — billinghurst sDrewth 12:44, 11 August 2017 (UTC)
  •   Remove and block indef I'm shocked. I simply can't believe what I'm reading here. May God be the judge of this liar. --A.Savin 12:47, 11 August 2017 (UTC)
  •   Remove I do not support admins with clandestine, multiple identities. The position of a Commons Admin is a position of mutual trust and respect. --CEphoto, Uwe Aranas (talk) 12:49, 11 August 2017 (UTC)
  •   Remove and block indef - I'm absolutely shocked with all this, as I've ever had INeverCry as a trustworthy editor and admin. But even if this Daphne "I'm a lady! I do lady things!" Lantier had not misbehaved, it should be desysoped and indefed for the mere fact that it's a sock, produced and used to deceive the community. Having such an account acting as a sysop here, even if they had not misbehaved so egregiously as they did, would turn Commons into a joke.-- Darwin Ahoy! 13:01, 11 August 2017 (UTC)
  •   Remove A. Savin and I have been the only 2 users for the last 3 years that have disagreed with INC still being allowed to contribute here and I hope (i have said it a few times but it did not change anything) that this is the "final nail in the coffin", lets just bury this and move on..--Stemoc 13:08, 11 August 2017 (UTC)
  •   Remove and permaban both accounts It is sad to see this happen to someone that i respected and tought highly of, be it in each account, but his attempt to go with a bang is pretty bad, to say the least and put it very mildly. Abusing multiple accounts is even worst. Tm (talk) 14:31, 11 August 2017 (UTC)
  •   remove Je ne sais plus quoi dire … — D Y O L F 77[Talk] 14:36, 11 August 2017 (UTC)
  •   Remove, per AFBorchert and many others in the same vein. Random thoughts:
    • I’m floored.
    • I never noticed it was the same painting on both user pages (duh!).
    • Both accounts do good work 99,99% of the time: the 0,01% is the problem.
    • Cannot be trusted with any kind of tools.
    • Self reported bipolar disorder and other health issues: How can the community help, at all?
    • I was a DL fan till 4h ago.
    • I was an INC fan at the beggining and moved away only very slowly and reluctantly; by the 2nd readmin request, however, I had no illusions.
    • Tranquilizing claim that disrupting edits were made “only” in the last hours of activity, but then again discloses that there’s more (dormant?) accounts that can be used to do the same again and again?!
    • Bummer.
-- Tuválkin 14:40, 11 August 2017 (UTC)
  •   Remove per so many above. I am concerned about the more accounts claim.   — Jeff G. ツ 15:14, 11 August 2017 (UTC)
  •   Remove As stated by so many above and for all the ways they said, with great sadness for the person involved, but this sort of rules-breaking has no place at Commons. Ellin Beltz (talk) 15:40, 11 August 2017 (UTC)
  •   Remove and indef. I was shocked to see this. I'm an SPI clerk at en.wiki, and I had stayed away from endorsing a check because it all seemed too far-fetched. But the level of deceit - plus the outright admission of intent to continue socking! - requires the community's condemnation. GeneralizationsAreBad (talk) 15:49, 11 August 2017 (UTC)
  •   Remove and ban from Commons for socking that affected both en.wiki and Commons: the information in the en.Wiki SPI is damning, and this has greatly impacted the community's trust. My main actions on Commons these days are tagging for deletion copyvios or improperly licensed images used on en.wiki, to which I was always impressed with this user. The amount of deceit here really is bad: I agree with Nick that a global ban might be in order due to the statement by INC on en.wiki acknowledging an intent to keep socking. TonyBallioni (talk) 16:08, 11 August 2017 (UTC)
  •   remove per so many above; and its absolutely shocking. ~ Moheen (keep talking) 17:31, 11 August 2017 (UTC)
  •   remove only -- WP:ADMINSOCK, can't be trusted. SA 13 Bro (talk) 18:07, 11 August 2017 (UTC)
  •   Remove per above, can't be trusted no more. KGirl (Wanna chat?) 19:00, 11 August 2017 (UTC)
  •   Remove and indef - I'm not only shocked to hear of this but I'm also very very saddened - INC & Daphne were quite honestly my best friends on this place and it turns out both were the exact same person!, I'm very disappointed and as I said extremely saddened, I would never in a million years have guessed they were the same person and it's a deep deep shame they chose to sock - INC was the best admin on this place by far .... I'm just so so disappointed, The community unfortunately cannot ever trust INC again so indeffing is the best option. –Davey2010Talk 19:02, 11 August 2017 (UTC)
  •   Remove. Daphne Lantier's adminship cannot be considered valid in light of the deception used to obtain it. INC has done more valuable and tedious work than almost anyone, and I'm sad that it's come to this. I do think calls for an indef ban here are inappropriate and should be taken to a different forum. Frankly, the deadminship outcome is a certainty, while bans and other sanctions deserve serious deliberation.rem Guanaco (talk) 19:27, 11 August 2017 (UTC)
    • @Guanaco: you believe that consideration of a ban is inappropriate even given this? Storkk (talk) 19:43, 11 August 2017 (UTC)
      Let's consider it carefully in a separate process. Guanaco (talk) 20:41, 11 August 2017 (UTC)
  •   Remove Obviously. Go ahead and close this vote, globally lock the Daphne account, and block INeverCry on every wiki with only editing his talk page on en.wp. This is ridiculous to even discuss. —Justin (koavf)TCM 21:30, 11 August 2017 (UTC)
  •   Remove The emergency action was clearly justified, and thanks to Matiia for removing the account's admin rights. This should obviously be made permanent, and the editor banned from all Wikimedia projects. Nick-D (talk) 22:34, 11 August 2017 (UTC)
  •   remove I long supported INeverCry, but now he crossed over a line. My line. Unacceptable behaviour. Trijnsteltalk 22:43, 11 August 2017 (UTC) PS. Because of this and this, as mentioned by Jee but I knew this for years already, I must admit it feels bad to vote against him. Especially knowing INC will never return to this project. But due to the sockpuppetry and the deletion spree I have no choice.
  •   Remove, with global lock and ban (and any other sleepers). All Wikimedia projects are the same family and such a massive deliberate breach of policy is a clear indication that the person behind these accounts is absolutely not to be trusted anywhere. Whether they have done any 'good' work or not is immaterial. Kudpung (talk) 01:43, 12 August 2017 (UTC)
  •   remove, the RfA was clearly invalid.--Ymblanter (talk) 02:49, 12 August 2017 (UTC)
  •   remove Words cannot express how perplexed and saddened I am by the whole situation right now. INC did so much for Wikimedia projects for years. I don't know why he chose to deceive the community, but since he did, I have no choice but to support the removal of all sysop bits and a block of both accounts. Unbelievable. Sportsguy17 03:30, 12 August 2017 (UTC)
  •   Remove I read this and I can't believe it. It is a real shame that a user so active and who could have dedicated his positive knowledge to the project has ended up being a abuser. To be a administrator in a project as huge as Commons is difficult to achieve and requires a lot of experience in various fields, and this situation is a lack of respect and betrayal for all administrators who spent years in the project to become what Are today. I hope that this user in the future will be able to reflect on his actions, for now support that is globally locked. —Alvaro Molina ( - ) 04:25, 12 August 2017 (UTC)
  •   Remove Hum. Explains some of this [6] Doc James (talk · contribs · email) 12:44, 12 August 2017 (UTC)
  •   Remove He had many chances to recover community trust and the recent actions let clear that is actually dangerous to the project to have him with the tools. I hope you stay better after this and think about other places where your volunteer capacities can also be useful.—Teles «Talk to me ˱C L @ S˲» 13:10, 12 August 2017 (UTC)
  •   Remove It is a great shock but a clear and strict message must go from here so it won't be repeated by anyone in future --✝iѵɛɳ२२४०†ลℓк †๏ мэ 16:42, 12 August 2017 (UTC)
  •   Remove I feel I ought to show some compassion for the health issues, but the scale of deception prevents even that. Hugely disappointed at the feet-of-clay of an apparently productive admin. Cabayi (talk) 17:55, 12 August 2017 (UTC)
  •   Remove Since INC nominated DL, and the connection between them was hidden, the RfA was illegitimate to begin with. Beyond My Ken (talk) 02:37, 13 August 2017 (UTC)
  •   Remove Global lock, global ban (and obviously remove OTRS and any other trusted access if there is any). Despicable duplicitous behaviour, can not be trusted again with anything, not even editing. (I know Commons admins do a lot of hard work which is largely "behind the scenes" to most of us at en.wiki, and you definitely don't need someone like this tarnishing it.) Boing! on Tour (talk) 12:09, 13 August 2017 (UTC)
    I've just seen an explanation that the deletion spree was down to a bipolar episode. While I can possibly accept that, it's not a plausible explanation for the lengthy socking and fraudulent RfA. Boing! said Zebedee (talk) 20:58, 14 August 2017 (UTC)
  •   remove, sadly. --Túrelio (talk) 15:04, 13 August 2017 (UTC)
  •   Remove and block indef per Colin. I am shocked at the level of deliberate deception here, particularly in the light of previous promises by INC. The calculated and deliberate breaches of community trust should and I think must result in an indefinite block/ban. We should not accept editors here who systematically lie to the community and who, if not blocked, will very likely do this again as a type of game. MichaelMaggs (talk) 19:46, 13 August 2017 (UTC)
  •   remove Wow... Daphne Lantier has handled many of my requests on Commons and I trusted this user. But we mustn't accept any destruction or unacceptable behaviors. --Arthur Crbz (talk) 21:23, 13 August 2017 (UTC)
  •   Remove I thought this person was doing a good job...but I was fooled. Trust is clearly lost with the abuse of Admin tools. Sorry, INC/Daphne. --Leoboudv (talk) 06:14, 14 August 2017 (UTC)
  •   Remove obviously after the "goodby greeting". But I'm curious how some admin backlogs will develop. --JuTa 07:39, 14 August 2017 (UTC)
It is better to have a very large backlog, rather than have a sockpuppeteer which halves the backlog every day. I think this de-RfA is a slap to Commons for relying in just one admin like INC. It is time to have a "call at arms". Poyekhali 09:34, 14 August 2017 (UTC)
  •   Remove INC has deliberately deceived the community into thinking that DL was someone else and then went on a deletion rampage for what ever reason (to be honest, there will never be a good reason for it). While I think INC/DL should be blocked indefinitely, I don't believe this is the place/forum to do so. Bidgee (talk) 09:53, 14 August 2017 (UTC)
  •   Remove the Sockpuppettery is here not the main problem. It's the deletion orgy. Do we really need this request? Here's I think is a fast solution OK. Marcus Cyron (talk) 15:05, 14 August 2017 (UTC)
I agree with you that the result of this request would be obvious, but communities are required to make a desysop request lasting 7 days (or for other wikis, an ArbCom case) for a permanent desysop to take effect. Daphne's desysop was just temporary, since it is a steward action. Poyekhali 10:04, 17 August 2017 (UTC)
I think, the issues are so immense, that a simple Desysop is an obligation. Marcus Cyron (talk) 15:41, 17 August 2017 (UTC)
  •   Remove Given the disruption that occurred when they were confronted with the CU evidence. I find this a particularly painful remove !vote since INC was one of the first people to support my RFA on en.wiki. Mkdw (talk) 20:05, 14 August 2017 (UTC)
  •   Remove This is unfortunate but sadly necessary. Deceiving the community is IMO a lifetime disqualification for any adminship on any Wikimedia project, period. While I sympathize with the mental health concerns, Wikimedia is not therapy and at some point we have to draw a line to protect the projects. --Rschen7754 06:19, 15 August 2017 (UTC)
  •   Remove, indefinitely block all related accounts and convert INeverCry and Daphne Lantier to permanent community ban. --Nemo 09:05, 15 August 2017 (UTC)
  •   remove per many others -jkb- (talk) 10:08, 15 August 2017 (UTC)
  •   remove I comment below. Taivo (talk) 10:37, 15 August 2017 (UTC)
  •   remove pretty much per Rschen7754 above. Not sure about a ban yet, but that needs to be determined elsewhere anyway. --El Grafo (talk) 11:12, 15 August 2017 (UTC)
  •   remove INeverCry/Daphne Lantier have a contributed a lot to Commons, but I see a desysop to be the only course of action here. --Lewis Hulbert (talk) 12:48, 15 August 2017 (UTC)
  •   remove what else can be done? The case is clear, and any trust has gone. -- SERGIO (aka the Blackcat) 16:43, 16 August 2017 (UTC)
  •   Remove per above. -FASTILY 18:16, 16 August 2017 (UTC)
  •   Remove Unbelievable. Daphne helps me a lot on the commons. I can't believe she is a sockpuppet of INeverCry, who also helps me on the commons. However, abusing multiple accounts is not allowed on commons. --B dash (talk) 02:49, 17 August 2017 (UTC)
  •   Remove for abusing the tools. I'm shocked, as many others. --Ruthven (msg) 05:53, 17 August 2017 (UTC)

Comments

  • You can delete this comment if it is absurd. With the same painting on the user page, I was always thinking that I Never Cry had changed name to Daphne; I never suspected of this kind of activity. I was so sure they were the same person I didn't even bother to check it. As regards the sysop issue, I have no idea about admins' affairs, but of course I would like to see her/him working here. Given the situation, better not as an admin. --E4024 (talk) 07:32, 11 August 2017 (UTC)
"Deceptively seeking positions of community trust. You may not run for positions of trust without disclosing that you have previously edited under another account. Adminship reflects the community's trust in an individual, not an account, so when applying for adminship, it is expected that you will disclose past accounts openly, or to email the arbitration committee if the accounts must be kept private. Administrators who fail to disclose past accounts risk being desysopped, particularly if knowledge of them would have influenced the outcome of the RfA."
Obviously that's an en:wp policy and not Commons (though our policy pages link to it). I think it time that Commons adapted some en:wp pages so we can have our own definitions using language and attitudes appropriate to Commons. Admins who knowingly hid INC/Daphne from the community, not because they couldn't raise an CU and wanted to, but because they were happy with this deception as it kept the backlog down, should all be thoroughly ashamed of themselves. The community did not appoint you admins so you could collectively deceive us. "trusted by the community" is what an admin is. -- Colin (talk) 10:18, 11 August 2017 (UTC)
  • I'm not much of a contributor here at Commons, but I'd like to point out INC's response to being blocked at enwiki: "No worries. I've got other accounts I can use". —DoRD (talk) 11:28, 11 August 2017 (UTC)
  • Hmm, since the Daphne account has joined the OTRS, and the OTRS requires applicants to submit a confirmed identity to the WMF, I wonder how INC managed to circumvent, or differentiate INC and Daphne to the eyes of the WMF. Maybe INC made a different identity? Or the WMF is part of INC's plan? This needs to be investigated (of course not here in Commons). Poyekhali 11:30, 11 August 2017 (UTC)
    AFAIK, it's signing a legalpad document. You don't have to send your ID to wikimedia, but whatever signature used in that legalpad document should be truthful or the signer would probably be in legal trouble --Zhuyifei1999 (talk) 11:34, 11 August 2017 (UTC)
    After some reading, it seems that the INC account never joined OTRS, that's why the Daphne sock can join the OTRS. Therefore, my questions would be considered invalid. Poyekhali 11:41, 11 August 2017 (UTC)
    [edit conflict] I believe that they've said that they retain the identification only long enough to confirm it, so it's not good for preventing sockpuppetry by high-up functionaries unless the person who checks the confirmed ID happens to be the same person both times and happens to remember. And unless INeverCry also had to confirm an identity, that wouldn't be an issue anyway. Nyttend (talk) 11:42, 11 August 2017 (UTC)
    INC is a former Commons CheckUser, so he would have identified for that position. —DoRD (talk) 11:45, 11 August 2017 (UTC)
    There was a IP 209.249.5.140 have make the request for Global lock for Daphne Lantier and INeverCry at Meta:SRG in certain past on today, but the situation seemed to be not deserves a lock, at least for now on. SA 13 Bro (talk) 18:05, 11 August 2017 (UTC)

I know en:user:Kristen Eriksen case in en.wiki and I noticed, that Kristen Eriksen and Daphne Lantier are somehow similar names. I suspected from very beginning, that Daphne is not a woman. But this is not prohibited, you may very well work under self-invented identity and that's why I supported Daphne in RfA. After that I noticed similar pattern between INC and Daphne and I started to suspect, that they are same person, but as Daphne was a good admin, I did not complain (and I was not totally sure too). Now I understand, that this was a mistake, I did not believe, that he would run amoc. I promised in Commons:Administrators/Requests/INeverCry (readmin) in comments never to support INC again in RfA. INC decieved me (and of course others too) and naturally his rights must be removed. I thought about letting him work as ordinary user, but after deleting main page he should be indefinitely banned. I thank MichaelMaggs very much for letting the request be open whole week for everyone to comment. Taivo (talk) 10:37, 15 August 2017 (UTC)

Resignation statement by Daphne Lantier

In response to my notice about the desysop process, Daphne Lantier wrote on their talk page:

@AFBorchert: You can go through that and have some fun with it, but if a resignation from me would help, than I resign as an admin. I did my 80k actions  , and I consider the account scuttled. I've also contacted WMFOffice to assure them that I never once mishandled any OTRS or CU private info, and that I have no such info saved on any device that I own. I would also remark that 1989 is not a sock of mine. Trijnstel may be able to confirm or at least comment on that, though I would think CU comparison between Daphne and 1989 here should prove beyond doubt that 1989 is not related to me in any way. I don't want to see someone else get in trouble for my actions. I don't regret a thing I did as Daphne or INeverCry, I had a good time with it overall, but the whole thing is my responsibility. I say this because it's been brought up that others may have had an inkling that I was using the Daphne sock. Never once did I tell any other person what I was doing. All anyone else could have had was guesses, but nobody had direct evidence of the socking. Good night. Daphne Lantier 05:03, 12 August 2017 (UTC)

--AFBorchert (talk) 05:22, 12 August 2017 (UTC)

DL admits guilt, resigns as Admin

See this edit for details. I move to end this process as moot.   — Jeff G. ツ 05:11, 12 August 2017 (UTC)

I've no objection, but there would need to be a statement from the bureaucrats here that 'Daphne'/INeverCry has no entitlement to the administrator toolset and cannot simply ask to have the toolset restored (I can't believe I'm even having to say that, but past behaviour suggests this is a risk). There would need to be a recognition that the resignation happened 'under a cloud' and that the de-RfA request had the virtually unanimous support (and clear consensus) of the community to remove the toolset. I would also like recognition that a deceptive RfA (or any other deceptive request) is illegitimate and grounds for immediate removal of any permissions gained, but that will probably require community discussion and I would expect there will be a desire to handle things on a case by case basis, which might mean leaving the de-RfA open for the full 7 days would be a sensible way to establish a precedent for such things. Nick (talk) 11:36, 12 August 2017 (UTC)
Hi, At this point, yes, this is quite moot. Admin right has been removed, and is not going to be restored any time soon (euphemism). Regards, Yann (talk) 15:35, 12 August 2017 (UTC)
  Info Since January of this year it has no longer been possible for an ex-admin to recover sysop privileges without going through a new RFA. The old unwritten rule whereby bureaucrats had discretion to restore rights to ex-admins who relinquished their rights in good standing has been abolished: see the current policy at Commons:Administrators#Apply to become an administrator "All intending administrators must ... submit themselves to RFA, including all ex-administrators who are seeking to return to their previous role. MichaelMaggs (talk) 20:03, 13 August 2017 (UTC)

  Comment Although it seems that this process will inevitably result in community approval for the de-sysop, I would recommend that it should continue for the full seven days in any event. It relates to a really serious matter, and editors ought to have full and proper opportunities not only to !vote but also to comment, both specifically and generally. --MichaelMaggs (talk) 20:03, 13 August 2017 (UTC)

Moving forward

  Comment. This is not a judgment on the quality of his past work. INeverCry has been respected and admired by almost all who know him (me included). Regardless of whether or not he was a good administrator, there are no words to describe what happened here on Commons in the early hours of 11 August when he spiralled out of control leading to an emergency desysop. Moreover, sockpuppetry should be grounds for automatic desysop in any Wikimedia project, imo. And it goes without saying he concealed a clean start by nominating himself for adminship. At this point it became more than obvious he is never going to return as an administrator at anytime in the future. That is utterly out of the question. I therefore suggest we move forward by closing this request for de-adminiship as the outcome is pretty clear already. RadiX 21:33, 13 August 2017 (UTC)

It is pretty clear that Daphne Lantier is to be desysopped; but it's not clear yet if INC should be banned. Several users including myself are in favor of full ban, but many others apparently do not support it. --A.Savin 22:08, 13 August 2017 (UTC)
INC can be sanctioned for "Abusing multiple accounts to mislead, deceive, disrupt, distort consensus or to evade blocks or other sanctions. Secondary accounts are typically blocked indefinitely. The primary account may or may not be subject to new or extended blocks depending on the circumstances." But it is not in scope of this discussion. It should be discussed at ANB or ANU per our blocking policy. And we have no existing policy for a permanent ban. The existing indefinite block is always eligible for an appeal (after some time). Jee 03:22, 14 August 2017 (UTC)
I'm just a simple user, and the last statement confuses me. Does that mean, that the sock-puppet will be banned but the sock-puppetier can walk away? In my opinion anything, what is decided here, should apply to both. --CEphoto, Uwe Aranas (talk) 07:05, 14 August 2017 (UTC)
It depends on the circumstances. For example, if the sock master offers a statement with a sincere promise not to sock again and the community is convinced, the sock master may be given what I would describe as "second chance ". Wikicology (talk) 07:37, 14 August 2017 (UTC)
That might be the case for normal users. But for admins? Also, I am not really deeply involved in Commons drama, but I recall, that INC had been several times severed his connctions to the projects with big tam-tam and suddenly was re-installed in his position. For my taste, there had been a lot of "second chances" before. And "No worries. I've got other accounts I can use" does not lock like a sincere promise ... --CEphoto, Uwe Aranas (talk) 07:45, 14 August 2017 (UTC)
I agree that "No worries. I've got other accounts I can use" is worrisome. Wikicology (talk) 09:21, 14 August 2017 (UTC)
CEphoto, I share the same opinion of Wikicology. Every rights of INC is removed now. So if he is allowed to edit again, that will be as an ordinary editor without any additional privileges. Little chances that even a "License reviewer" right can be gained again in near future. Jee 11:54, 14 August 2017 (UTC)
I see. Thanks for clarification. --CEphoto, Uwe Aranas (talk) 12:31, 14 August 2017 (UTC)

  Comment - as Jee already pointed out, we have no such policy as "permanent ban" on Common but if anyone feels INC/Dl behaviour is eligible for a global ban/lock, they can start a RfC at meta. Regards. Wikicology (talk) 07:28, 14 August 2017 (UTC)

Another sock

  Comment As discussed here, another sockpuppet was recently discovered which vandalized Commons and posted offending material on user pages at other projects (deleted sample which is accessible with admin privileges at de:wp). --AFBorchert (talk) 14:29, 16 August 2017 (UTC)

This sock was made only some days ago. It looks like a scorched-earth policy to turn-down all remaining sympathies and destroy every good remembrance to his work. I do not feel any pity but feel totally disgusted about that user. --CEphoto, Uwe Aranas (talk) 16:13, 16 August 2017 (UTC)
  •   Comment: Is having 5 Checkusers on WikiCommons enough for this project? This is just an inquiry....and nothing more. I just wonder what happens if there is a backlog to check on potential sockpuppet accounts. Thank You My error, it looks like there are more than 5 CU's on Commons after all as this shows. --Leoboudv (talk) 21:29, 17 August 2017 (UTC)
Commons has five checkusers but in this case the analysis was done at en:wp as INC continued to be active there along with DL. --AFBorchert (talk) 05:10, 18 August 2017 (UTC)

  Comment Another sock of INC had a short appearance at Commons tonight. --AFBorchert (talk) 05:10, 18 August 2017 (UTC)

  •   Comment: You are right. The user I cited is a CU on Wikipedia. My apologies. Hopefully 5 Checkusers on Commons is enough then. Best, --Leoboudv (talk) 08:42, 18 August 2017 (UTC)

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.

No current requests.

Requests for Oversight rights

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.

Archiv

Du findest bisherige Adminkandidaturen unter Commons:Administrators/Archive.

Siehe auch