Open main menu

Wikimedia Commons β

Commons Administrator.svg
Nåværende administratorer [+/−]
Listing by language
Listing by date
Listing by activity

Number of Admins: 237

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

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

Commons:Administratorer gir deg all viktig informasjon om administratorer på Wikimedia Commons, samt avstemninger om nye administratorer. Botstatussaker tas også opp her.

Hva er administratorer?Edit

Administratortilgang gis til pålitelige bidragsytere som er kjent med Commons' retningslinjer. Administratorstatus tilsier ikke at brukeren har noe mer redaksjonelt ansvar enn andre brukere. Administratorer har muligheten til å:

  • låse og åpne sider
  • slette og gjenopprette sider
  • slette og gjenopprette bilder og andre filer
  • blokkere og avblokkere brukere
  • redigere brukergrensesnittet og andre låste sider.

Administratorer med checkuser-rettigheter kan også sjekk om en bruker har brukt mer enn én konto (såkalte sockpuppets). Byråkrater har også muligheten til å:

Hva ventes av en administrator?Edit

Du kan bli en kandidat til administrator på Commons dersom du møter følgende krav:

  • Du er kjent med Wikimedia-prosjektene. Du må ha vært en bidragsyter i minst to måneder, og forstå prosjektets mål.
  • Du har en brukerside på Commons og ha minst 200 redigeringer her (opplastinger eller tekst), og interessert i Commons-samfunnet. Du bør med andre ord ha deltatt på sider som Commons:Deletion requests og Commons talk:Licensing (for eksempel ved å lete etter opphavsrettsbrudd, finne savnede kilder, og hjelpe anre). Folk kan også ha egne personlige standarder som krever mer.
  • Du følger retningslinjene og respekterer konsensusen.

Som med administratorpolitikken på Meta, blir inaktive administratorer fjernet når de ikker har hatt noen redigeringer de siste seks månedene, og mindre enn 50 redigeringer det siste året. Inaktive administratorer kan søke om å bli administrator på nytt på den vanlige måten.

AdministratorkandidaterEdit

  • Nominasjonen er åpen for stemmer og kommentarer i sju dager. Administratorstatus vil bli gitt med en majoritet på minst 75 %, og minst 4 støttende stemmer. Dersom kandidaten møter disse krava, vil en byråkrat gjøre brukeren til administrator.
  • Merk at denne siden brukes for å få andre tillatelser også; for eksempel for å få botstatus må man søke her.
  • Tidligere kandidater listes opp i arkivet.

Hvordan bli administratorkandidatEdit

Lag en underside Commons:Administrators/Requests and votes/brukernavn med følgende tekst, og inkluder sida øverst her:

===[[User:Brukernavn|]]===
{{custom edit|Template:Administrators/Requests and votes/Username|text='''Vote'''}}

Grunner til at du burde bli administrator. ~~~~

====Votes====

Nåværende kandidaterEdit

Oppdater sida

Shortcut
COM:VOTE
This project page in other languages:

This is the requests and votes page, a centralized place where you can keep track of ongoing user requests, and where you can comment and leave your vote. Any user is welcome to comment on these requests, and any logged in user is welcome to vote.

When requesting rights that do not need the support of the community (e.g. filemover) please go to Commons:Requests for rights!

How and where to apply for additional user rights on CommonsEdit

How to comment and voteEdit

Any logged-in user is welcome to vote and to comment on the requests below. Votes from unregistered users are not counted, but comments may still be made. If the nomination is successful, a bureaucrat will grant the relevant rights. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Among other things, the closing bureaucrat may take into account the strength of any arguments presented and the experience and knowledge of the commenting users. For example, the comments and votes of users who have zero or few contributions on Commons may at the bureaucrat's discretion be discounted.

It is preferable if you give reasons both for   Support votes or   Oppose ones as this will help the closing bureaucrat in their decision. Greater weight is given to argument, with supporting evidence if needed, than to a simple vote.

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

Requests for Oversight rightsEdit

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.

Requests for CheckUser rightsEdit

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 bureaucratshipEdit

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 adminshipEdit

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.

GuanacoEdit

Vote

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

Scheduled to end: 23:19, (UTC)

I'm happy to nominate Guanaco as our next admin. He is experienced and has been actively participating in various DR, AN, FPC, staying mellow and often showing a deep understanding of our policies and best practices. In addition, being an admin will make his OTRS work much easier. A significant amount of files is already deleted before an OTRS-agent processes them. If Guanaco would have the admin toolsset this would speed up his OTRS-work and save admins valuable time because he will be able to do his own deletions andbe able to view deleted files. I believe he will be a good and active admin, and I hope the community agrees. --Zhuyifei1999 (talk) 18:59, 21 September 2017 (UTC)

Candidate's acceptance: Thank you Zhuyifei1999. I accept, and I hope to live up to your high expectations. If my candidacy is successful, I intend to be cautious with my use of the tools. The more experience I gain in dealing with international copyright and other complex issues, the more I find I don't know. I intend to take the time and continue learning and developing my ideas, while helping to keep the backlogs short. If there are any questions, I'll do my best to answer them. Guanaco (talk) 23:19, 21 September 2017 (UTC)

VotesEdit

  •   Support doh. Natuur12 (talk) 23:25, 21 September 2017 (UTC)
  •   Support I've been waiting to support this candidate for quite some time, and I'm glad to be able to do so. Nick (talk) 23:31, 21 September 2017 (UTC)
  •   Support. -- Geagea (talk) 23:39, 21 September 2017 (UTC)
  •   Support - Jcb (talk) 23:56, 21 September 2017 (UTC)
  •   Support --— D Y O L F 77[Talk] 00:04, 22 September 2017 (UTC)
  •   Support I'm late --Zhuyifei1999 (talk) 00:50, 22 September 2017 (UTC)
  •   Support -- King of ♠ 01:34, 22 September 2017 (UTC)
  •   Oppose – not now, especially if the candidate has contributed in under 6 months, and makes mistakes like this (falsely accepting an image in a license review). I would also like to mention that they had a Arbcom case against them in 2004 and 2006 on enwiki for admin abuse and was desysopped as a result twice. -- 1989 01:44, 22 September 2017 (UTC)
  •   Oppose - sleeper, active in 2004, somewhat in 2005 and 06, disappeared, appeared 10 years later..active all of a sudden and then requests adminship less than 1 year after becoming active again, nope commons have had too many shitty admins over the years with a <Redacted> history, not sure if i can support another one.--Stemoc 01:54, 22 September 2017 (UTC)
  •   Support --jdx Re: 02:05, 22 September 2017 (UTC)
  •   Oppose per above, no confidence --A.Savin 02:15, 22 September 2017 (UTC)
  •   Strong Oppose - Sorry but the candidate has only 3 months experience .... sure people pick things up quickly I get that but you don't pick up policies, guidelines ... essentially the way things are done ... in 3 months, The candidate has no interest in DRs either so I don't really see why they need the tools, needless to say I'm disappointed with this community and after the INC debacle I would've expected the community to be a lot more stricter on RFAs ... not more lenient. –Davey2010Talk 02:44, 22 September 2017 (UTC)
Struck as per Taivo - FWIW I do want to state I have nothing against Guanaco I don't believe we've ever interacted - I just want candidates who have been here for more than a year (and FWIW I have the same "standards" at EN so just want to reiterate it's nothing personal). –Davey2010Talk 11:37, 22 September 2017 (UTC)
It's worth remembering that Commons has an effective and functional de-RfA system, INeverCry (as Daphne Lantier) had their administrator permission removed by unanimous community consent, whilst concurrently, H-stt was removed by majority community consensus. It's also now impossible to resign and return as an administrator following changes to the RfA process, which will prevent a repeat of the regular resignations and returns that characterised INeverCry's two periods as an administrator. I don't think we need to go over the top with our requirements when we're not stuck with problematic administrators in the way other projects are (such as en.wp). Nick (talk) 11:43, 22 September 2017 (UTC)

CommentsEdit

  • @Guanaco:, I vaguely remember that you have previously desysopped for cause in the English Wikipedia. If this is the case, could you please briefly outline what the problem was and (if it applies) what have you learned from this to avoid problems here in the future? Thanks.--Ymblanter (talk) 10:32, 22 September 2017 (UTC)
    @Ymblanter: In 2004, there was an aggressive edit warrior on "revert parole", whereby he was restricted to three reverts in 24 hours. I misread a page history, and I blocked him incorrectly. He then spammed admin talk pages and noticeboards with such things as "DESYSOP GUANACO" using a sockpuppet IP, rather than requesting unblock through accepted channels. I reverted this without reading the text in detail. Once it had stopped, I read the postings and realized my error, so I unblocked him. He took me to ArbCom with the allegation that I had been trying to cover up my actions. ArbCom didn't accept this theory, but in light of other controversies, the decision was that I had to pass a new RFA. I didn't, the first time. Then in 2006, there was a controversial movement to remove all userbox templates which stated personal opinions. There was no consensus to delete these templates, but a certain admin did so out of process, substing them and deleting them as "orphaned". I used rollback and undelete to revert this, and I let my anger get the better of me; I blocked him for a short time. I was desysopped, and I ultimately decided to leave the project.
    I was age 14-16 during these events, and I've become much more mellow and effective at communicating as an adult. I would say specifically I've learned that if I'm angered by an on-wiki event, it's best to take a step back and let someone else handle it. There are other users who can help. Even in the worst cases of vandalism or admin abuse, it's better to handle things calmly with no appearance of personal involvement. I've also learned that it's critical for a wiki project to avoid adversarial proceedings whenever possible. I remember feeling cornered and overwhelmed, which helps explain but doesn't justify my actions at the time. In light of this experience, I've tried to maintain an civil environment on Commons, even for those who are clearly in the wrong. Guanaco (talk) 20:37, 22 September 2017 (UTC)
    Thanks for the answer, very clear.--Ymblanter (talk) 20:40, 22 September 2017 (UTC)


Requests for license reviewer rightsEdit


Requests for permission to run a botEdit

Before making a bot request, please read the new version of the Commons:Bots page. Read Commons:Bots#Information on bots and make sure you have added the required details to the bot's page. A good example can be found here.

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

Any user may comment on the merits of the request to run a bot. Please give reasons, as that makes it easier for the closing bureaucrat. Read Commons:Bots before commenting.

AliciaFagervingWMSE-bot (talk · contribs)Edit

Operator: Alicia Fagerving (WMSE) (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Uploading freely licensed images from (primarily GLAM) collaborations with Wikimedia Sverige.

Bot's tasks for which permission is being sought: Image uploads

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One run per batch.

Maximum edit rate (e.g. edits per minute): ~ 3/min

Bot flag requested: (Y/N): Y

Programming language(s): Python / pywikibot

The particular task the bot account will be used for is uploading freely licensed images from the Swedish National Heritage Board. This will be a continuation of the most recent upload by AndreCostaWMSE-bot, using the same codebase and category structure, incl. maintenance categories.

Alicia Fagerving (WMSE) (talk) 11:59, 27 June 2017 (UTC)

DiscussionEdit

  • Is there a reason why this is better than creating a generic WMSE upload account which can be run by WMSE on defined projects? As an observation, you don't need a bot flag on an upload account like this. -- (talk) 12:04, 27 June 2017 (UTC)
As for the bot flag, it's necessary for the account to be able to upload files via url, as opposed to from the local machine. We also prefer to use separate accounts to make it clearer who's responsible for specific tasks. Since institutional accounts are discouraged on some wikis anyway, we've decided to stick to one account per person. --Alicia Fagerving (WMSE) (talk) 15:12, 4 July 2017 (UTC)
Agreed that institutional accounts remain controversial (though they do exist), however having a bot flag makes no difference to uploading via URL as far as I'm aware. So if the concern is that the person doing the uploads needs to be accountable, then you can just use your existing WMSE account. There may be a good case to use a separate account if you want to run the uploads as a distinct project and there are going to be a lot of images (like 10,000+), but even then, there is no special benefit in having a bot flag, you can just create the account and start using it. -- (talk) 17:04, 4 July 2017 (UTC)
You need upload_by_url permission to do so, and it's restricted to image reviewers, bots, and admins. Guanaco (talk) 21:53, 14 July 2017 (UTC)
Thanks, my mistake. I vaguely recall a discussion early in the year about relaxing the restriction. It does seem slightly arbitrary considering there are few restrictions on upload tools that do the same thing by proxy. -- (talk) 06:49, 15 July 2017 (UTC)
  • Bot flag set, please make some test edits for final approval. --Krd 06:33, 15 July 2017 (UTC)
    @Alicia Fagerving (WMSE): ? --Krd 13:35, 8 August 2017 (UTC)

Closing as stale as there was no answer and no test edits. --Krd 16:47, 20 August 2017 (UTC)

Reopened on request. --Krd 08:50, 20 September 2017 (UTC)
@Krd: Thank you! I've uploaded some files to Category:Media contributed by RAÄ: 2017-09. They follow the same structure as our previous batch, Category:Media contributed by RAÄ: 2017-06. Do you know if it's possible to disable the Small jpeg's uploaded by users with low editcount filter? Some of our files get caught in it.--Alicia Fagerving (WMSE) (talk) 09:17, 20 September 2017 (UTC)
Looks good to me. --Krd 09:23, 20 September 2017 (UTC)

Cewbot 4 (talk · contribs)Edit

Operator: Kanashimi (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Cleanup Panoramio files needing categories

Automatic or manually assisted: automatic

Edit type (e.g. Continuous, daily, one time run): weekly

Maximum edit rate (e.g. edits per minute): 12 per minute

Bot flag requested: (Y/N): No

Programming language(s): cleanup_Panoramio_files_needing_categories.js

Kanashimi (talk) 15:06, 31 August 2017 (UTC)

DiscussionEdit

  • Please do some test edits. --Krd 02:43, 2 September 2017 (UTC)
@Krd:I have do some test edits. Please check if they are OK. Thank you. --Kanashimi (talk) 08:07, 2 September 2017 (UTC)
Looks OK for me, but will be also good idia to replace Panoramio_upload_bot with Panoramio upload bot. --EugeneZelenko (talk) 13:54, 2 September 2017 (UTC)
Surely I will do. --Kanashimi (talk) 15:25, 2 September 2017 (UTC)
  • Does it exclude maintenance categories from consideration? --Zhuyifei1999 (talk) 15:15, 2 September 2017 (UTC)
@Zhuyifei1999: I exclude only bot edits and /Panoramio|Unidentified|Taken with/i now (see the source for detail). Are there any list of maintenance categories? --Kanashimi (talk) 15:25, 2 September 2017 (UTC)
Categories marked with __HIDDENCAT__ are almost always maintenance / user categories. --Zhuyifei1999 (talk) 15:34, 2 September 2017 (UTC)
  Fixed Thank you. I will exclude categories marked with __HIDDENCAT__. --Kanashimi (talk) 15:39, 2 September 2017 (UTC)

Convert category tags to templates?Edit

@Kanashimi, Krd, Shizhao: Files are categorized to these maintenance categories through a simple category tag e.g.
[[Category:Photos from Panoramio needing categories as of 2017-07-15]]
If we convert the category tags to the standard template {{Uncategorized}} (the template can be a bit adapted by new parameters), categorization tools as Hot-Cat and Cat-a-lot can manage them immediately when the image is categorized and the needless delay of the maintenance tag can be avoided. Is it possible to transform the maintenance-category tags by a bot? And Panoramio upload bot can be also changed to use the template tag instead the direct category tag. --ŠJů (talk) 19:49, 3 September 2017 (UTC)

It is OK to do the things. --Kanashimi (talk) 09:51, 4 September 2017 (UTC)
Sadly I cannot follow. Can you please elaborate in different words? Thank you. --Krd 07:14, 20 September 2017 (UTC)
Thank you for your attention on this task. I can convert the category tags to the standard template {{Uncategorized}}, but since more than one week passed and no one reply to the idea, I don't know if this part have reached a consensus. Maybe I should just clean the categories. --Kanashimi (talk) 09:30, 20 September 2017 (UTC)

Oudabot (talk · contribs)Edit

Operator: Mohamed Ouda (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Sending messsages to talk pages of users who will contribute in Wiki Loves Africa Contest Automatic or manually assisted: automatic

Edit type (e.g. Continuous, daily, one time run): continuous

Maximum edit rate (e.g. edits per minute): 10

Bot flag requested: (Y/N): yes (I already have the bot flag on Arabic Wikipedia)

Programming language(s): python Mohamed Ouda (talk) 17:03, 6 September 2017 (UTC)

DiscussionEdit

Mass posting should remain the responsibility of the poster, so an operator would still need to sign and may as well run the script directly. Is there a reason why the existing MassMessage would not be used? -- (talk) 07:29, 11 September 2017 (UTC)

OK , Please can I have access to use MassMessage --Mohamed Ouda (talk) 08:44, 15 September 2017 (UTC)

The MassMessage interface is available for admins only, but your can prepare your message and ask any admin to send it. Please see e.g. Commons:Wiki Loves Monuments/Documentation/Send a mass message for short instructions. --Krd 06:59, 20 September 2017 (UTC)

Requests for commentEdit