Commons:Administrators' noticeboard

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

Shortcut: COM:AN

This is a place where users can communicate with administrators, or administrators with one another. You can report vandalism, problematic users, or anything else that needs an administrator's intervention. Do not report child pornography or other potentially illegal content here; e-mail legal-reports@wikimedia.org instead. If reporting threatened harm to self or others also email emergency@wikimedia.org.

Vandalism
[new section]
User problems
[new section]
Blocks and protections
[new section]
Other
[new section]

Report users for clear cases of vandalism. Block requests for any other reason should be reported to the blocks and protections noticeboard.


Report disputes with users that require administrator assistance. Further steps are listed at resolve disputes.


Reports that do not suit the vandalism noticeboard may be reported here. Requests for page protection/unprotection could also be requested here.


Other reports that require administrator assistance which do not fit in any of the previous three noticeboards may be reported here. Requests for history merging or splitting should be filed at COM:HMS.

Archives
22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1

Note

  • Remember to sign and date all comments using four tildes (~~~~), which translates into a signature and a time stamp.
  • If appropriate, notify the user(s) concerned. {{subst:Discussion-notice|noticeboard=COM:AN|thread=|reason=}} is available for this.
  • Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.


experiencing high backlog

Hello admins (and license-reviewers monitoring this page),

We're currently at with 4028 files waiting for us as of the time I save this page.

4000 files stuck in the queue for few months are not good, so please help to empty the queue. Thanks! — regards, Revi 18:37, 12 May 2018 (UTC)[reply]

Just for reference sake, 3,300 of them are videos. Videos take a lot longer to review since there are multiple parts that all have to comply with licensing standards and you have to actually watch the videos (or at the very least scroll through them). It seems like we have a lot of people scrapping YouTube for any and all Creative Commons licensed vidoes and uploading them here. Regardless of whether or not they are actually useful in any way. --Majora (talk) 22:11, 12 May 2018 (UTC)[reply]

Currently at 4688 images. — regards, Revi 08:02, 11 June 2018 (UTC)[reply]

Bad Flickr account

Please add 8527875@N04 to Commons:Questionable Flickr images/Users.

Twitter may or may not have been the actual source, but everything on that account looks iffy. - Alexis Jazz ping plz 06:57, 29 May 2018 (UTC)[reply]

I just had to bring this thread back from the dead. It was not done. - Alexis Jazz ping plz 19:29, 5 June 2018 (UTC)[reply]

Bad Flickr account 2

Please add 48973657@N00 to Commons:Questionable Flickr images/Users.

While it has a CC-BY-SA license, the description says (not just for this photo):

"You may syndicate this content for non-commercial purposes as long as you attribute credits to me. Commercial usage will be considered on a case-by-case basis."

So it's actually more like CC-BY-SA-NC. - Alexis Jazz ping plz 19:29, 5 June 2018 (UTC)[reply]

Discussion at Commons:Deletion requests/Files found with insource:"48973657@N00". - Alexis Jazz ping plz 20:27, 5 June 2018 (UTC)[reply]

My default language is Belarusian Taraškievica (be-tarask), so in Wikidate Infobox I see the information in Belarusian Taraškievica. But if I want to read the article in Belarusian Taraškievica Wikipedia (be-tarask.wikipedia.org) and click on link "Вікіпэдыя" (the name of Wikipedia in Belarusian Taraškievica) it leads me to the corresponding article in Belarusian Wikipedia (be.wikipedia.org). It seems like there is an issue with Sitelinks parameter in Wikidate Infobox. Could you please help me to fix this issue? --Kazimier Lachnovič (talk) 19:04, 14 June 2018 (UTC)[reply]

@Kazimier Lachnovič: This is very odd. It looks like the problem is with {{BaseLang}}, which returns "be" rather than "be-tarask" (which is correct for the case of "en-gb" -> "en", but not here). @RexxS: can you have a look at this please? (For reference: the sitelinks are generated by {{#invoke:Wikidata2|getSiteLink|{{BaseLang}}wiki|qid=Q2}} -> Earth Thanks. Mike Peel (talk) 13:31, 16 June 2018 (UTC)[reply]
@Kazimier Lachnovič and Mike Peel: there's an issue with {{BaseLang}}, but also with the way the MediaWiki software works. We need to map from the user's language to what is called the "globalSiteId" for that wiki. For both en and en-gb, the correct globalSiteId is enwiki, but for be-tarask, it is not bewiki. After some trial and error (because of the non-existent documentation for globalSiteId), I eventually worked out that the globalSiteId for be-tarask is "be_x_oldwiki". I'll write a quick and dirty hack to map the code "be-tarask" to "be_x_oldwiki" as an exception.
  • {{#invoke:Wikidata2|getSiteLink|{{BaseLang}}wiki|qid=Q2}} → Earth
  • {{#invoke:Wikidata2/sandbox|getSiteLink|{{BaseLang/sandbox}}wiki|qid=Q2}} → Earth
  • {{BaseLang}} → en
  • {{BaseLang/sandbox}} → en
If that looks ok, would one of you copy the contents of Module:Wikidata2/sandbox over Module:Wikidata2, please? Or ping me and I'll do it if you're satisfied. Let me know if problems arise. --RexxS (talk) 18:29, 16 June 2018 (UTC)[reply]
@RexxS: I did the replacement, but e.g. for Category:Church of Vitaut the Great, Hrodna the result was [1]. So I tried to replace "be_x_old" with "be-x-old" and the link just disappeared from infobox. --Kazimier Lachnovič (talk) 19:18, 17 June 2018 (UTC)[reply]
@Kazimier Lachnovič: The globalSiteId for code "be-tarask" is "be_x_oldwiki", and I've checked that. There is no globalSiteId with the value "be-x-old", so there will be no link and if you try to use that, it will disappear of course. The problem now lies in Template:Wikidata Infobox, I think.
@Mike Peel: I believe that the infobox employs a hack using {{BaseLang}} to create different values: (1) the globalSiteId such as enwiki used in getSiteLink; (2) the language code such as en used to create an interproject link. I note that there is also the possibility of creating urls such as en.wikipedia.org, but I haven't seen those. The general pattern for most languages is that the globalSiteId is created by appending "-wiki" (or "-wikiquote", etc.) to the basic language code (e.g. en instead of en-gb), so de gives dewiki, dewikisource, etc. Unfortunately, for old-style Belorussian, the code returned by {{int:lang}} is "be-tarask", but the globalSiteId is "be_x_oldwiki", and the language code is "be-x-old", while the site url is "be-tarask.wikipedia.org". That means we can't use {{BaseLang}} for both getSiteLink and the interproject link (nor the site url if we ever needed it). Some documentation is at meta:Special language codes.
Now, I've tried to work out the 'Sitelinks' code in {Wikidata Infobox}, but it looks broken to me. Here's what I see if I unpack the clump of code:
{{#if:
	{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wiki |qid={{getQID |qid={{{qid|}}} }} }}
	{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikiquote |qid{{getQID |qid={{{qid|}}} }} }}
	{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikisource |qid{{getQID |qid={{{qid|}}} }} }}
	{{#invoke:Wikidata2 |getSiteLink |specieswiki |qid{{getQID |qid={{{qid|}}} }} }}
	{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikivoyage |qid={{getQID |qid={{{qid|}}} }} }}
	|
	<tr><td colspan=2 style="text-align: center; font-weight: bold;">
	{{#if:
		{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wiki |qid={{getQID |qid={{{qid|}}} }} }}
		|
		[[:{{BaseLang}}:{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wiki |qid={{getQID |qid={{{qid|}}} }} }}
		|
		{{#invoke:WikidataIB |getLabel |Q52}}]]
	}}
	{{#if:
		{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikiquote |qid={{getQID |qid={{{qid|}}} }} }}
		|
		<br />[[:wikiquote:{{BaseLang}}:{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikiquote |qid={{getQID |qid={{{qid|}}} }} }} |{{#invoke:WikidataIB |getLabel |Q369}}]]
	}}
	{{#if:
		{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikisource |qid={{getQID |qid={{{qid|}}} }} }}
		|
		<br />[[:wikisource:{{BaseLang}}:{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikisource |qid={{getQID |qid={{{qid|}}} }} }} 
		|
		{{#invoke:WikidataIB |getLabel |Q263}}]]
	}}
	{{#if:
		{{#invoke:Wikidata2 |getSiteLink |specieswiki |qid={{getQID |qid={{{qid|}}} }} }}
		|
		<br />[[:species:{{#invoke:Wikidata2 |getSiteLink |specieswiki |qid={{getQID |qid={{{qid|}}} }} }}
		|
		{{#invoke:WikidataIB |getLabel |Q13679}}]]
	}}
	{{#if:
		{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikivoyage |qid={{getQID |qid={{{qid|}}} }} }}
		|
		<br />[[:wikivoyage:{{BaseLang}}:{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikivoyage |qid={{getQID |qid={{{qid|}}} }} }}
		|
		{{#invoke:WikidataIB |getLabel |Q373}}]]
	}}
	</td></tr>
}}
It looks to me that you've got links [[ ]] broken across the then and else parts of several {#if: } statements. or am I not reading them correctly?
My apologies, but I have to sort out the forked version of WikidataIB on enwiki first, then I'll add two new functions to map the base language code to the root of the globalSiteId and to the interproject-link code. You'll be able to use those to create the proper links for be-tarask and others. --RexxS (talk) 21:30, 17 June 2018 (UTC)[reply]
@RexxS: The | you're seeing is part of the wikilink, not the if statement. So e.g., [[:wikivoyage:{{BaseLang}}:{{#invoke:Wikidata2 |getSiteLink |{{BaseLang}}wikivoyage |qid={{getQID |qid={{{qid|}}} }} }}|{{#invoke:WikidataIB |getLabel |Q373}}]] is all inside the if statement. (If that wasn't the case, then it wouldn't work!) If there could be a neater way of implementing this, that would be nice though! Thanks. Mike Peel (talk) 21:39, 17 June 2018 (UTC)[reply]
BTW, I think there's an ongoing migration of be_x_old to be-tarask. Try searching for 'be-tarask' on phabricator and you'll find a bunch of tickets about it. So maybe it's best to report this inconsistency there and ask for it to be solved by the WMF devs, rather than adding exceptions for the case here... Thanks. Mike Peel (talk) 21:43, 17 June 2018 (UTC)[reply]
The WMF devs? Give me a break. I'd like to see it done sometime in this lifetime. There are multiple exceptions, according to meta:Special language codes, so it makes sense to me to bundle those up inside an opaque Lua function (with a wrapper template of course) so that we can deal with exceptions as they come to our attention without any further re-writes of the infobox code. I'll have them done soon. --RexxS (talk) 21:53, 17 June 2018 (UTC)[reply]
  • {{#invoke:WikidataIB|siteID}}wiki → enwiki
  • :{{#invoke:WikidataIB|projID}}: → :en:
  • {{siteID}}wiki → enwiki
  • :{{projID}}:: → :en:
Done. --RexxS (talk) 22:45, 17 June 2018 (UTC)[reply]
@RexxS: OK, is this implementation correct? Thanks. Mike Peel (talk) 22:53, 17 June 2018 (UTC)[reply]
Possibly, Mike. I mean it looks right to me, but I think I'd rather wait for Kazimier Lachnovič to tell us whether it's giving the correct sitelinks for him now. --RexxS (talk) 22:58, 17 June 2018 (UTC)[reply]
@RexxS: Should I modify some code? Because for now the problem didn't gone. E.g. for Category:Earth the link "Wikipedia" in Infobox leads to [2] instead of [3]. --Kazimier Lachnovič (talk) 09:48, 18 June 2018 (UTC)[reply]
@Kazimier Lachnovič: Can you test this version please? Thanks. Mike Peel (talk) 10:31, 18 June 2018 (UTC)[reply]
@Mike Peel: This version works well. Thank you! --Kazimier Lachnovič (talk) 10:35, 18 June 2018 (UTC)[reply]
@Kazimier Lachnovič: OK, the new infobox version is now live. If you see the wrong link again, then try clearing your cache (?action=purge at the end of the URL), and if it still doesn't work then let us know. Thanks. Mike Peel (talk) 11:26, 18 June 2018 (UTC)[reply]
Everything is OK. Thanks a lot for your help! --Kazimier Lachnovič (talk) 11:34, 18 June 2018 (UTC)[reply]

Missing rules in Mobile.css

Please, someone of you copy these rules for geo coordinates from MediaWiki:Common.css to MediaWiki:Mobile.css:

/* Geographical coordinates defaults. See [[Template:Coord/link]]
 for how these are used. The classes "geo", "longitude", and
 "latitude" are used by the [[Geo microformat]].
 */
.geo-default, .geo-dms, .geo-dec { display: inline; }
.geo-nondefault, .geo-multi-punct { display: none; }
.longitude, .latitude { white-space: nowrap; }

And by the way you could also fix the typo paramter in Mobile.css.

Because these are missing all coordinates are shown twice in mobile view, cf. examples in Template:Inline coordinates in desktop and mobile mode.

I did not use {{Edit request}} because the according category Commons protected edit requests has not been processed for months (a request of mine is from 22 March this year).
— Speravir – 22:44, 14 June 2018 (UTC)[reply]

✓ Done--Steinsplitter (talk) 13:34, 16 June 2018 (UTC)[reply]

File names need to be swapped

This seems a bit too complicated to fix with the permissions of a normal user:

For verification of what Marina Elliott looks like, see [4] and [5]. For Becca Peixotto, see [6].

I could try to swap the JPG pictures by uploading new versions of each file, but I don't know if I'm supposed to upload completely new images over the old ones. The PNG of Ms. Peixotto looks like an inferior duplicate of the JPG, but at least it's named correctly. Should the PNG be deleted as a duplicate, changed to a redirect, or kept? And could someone swap the names of the two JPG images? Philbert2.71828 03:38, 15 June 2018 (UTC)[reply]

@Philbert2.71828: , maybe this image can be helpful. Lotje (talk) 04:50, 15 June 2018 (UTC)[reply]
I decided to swap the images by uploading new versions of each one. I don't know I was supposed to do it that way, but it means that all three files are named correctly now. The file histories of File:Becca Peixotto.jpg and File:Marina Elliott.jpg now show that the images were swapped. I think this is resolved, unless I wasn't supposed to do it that way. Philbert2.71828 12:19, 16 June 2018 (UTC)[reply]

Video deleted

Hi File:Kylie Jenner2.png is a free photo. But the video have been deleted by the owner of the YouTube channel. What is the solution ? I know that for YT or Flickr when the licence is changed the file remains free. --Panam2014 (talk) 15:31, 16 June 2018 (UTC)[reply]

There is a license review so I would not worry myself. Sjoerd de Bruin (talk) 15:39, 16 June 2018 (UTC)[reply]
@Sjoerddebruin: please see that archive. I have uploaded the file and the reviwer have seen the file. --Panam2014 (talk) 15:40, 16 June 2018 (UTC)[reply]

Uploaded a new version of a video, but the old version plays, instead

File:7. user sandbox+ prepare library's article templates.webm.

Thank you,--ManosHacker (talk) 06:29, 17 June 2018 (UTC)[reply]

@ManosHacker: This isn't an administrative problem. It is your cache. This is a rather common occurrence. Hold down the shift key and press F5 to ignore your cache while reloading the file information page and it will be fine. --Majora (talk) 06:33, 17 June 2018 (UTC)[reply]
Thank you, Majora. Shift F5 had not worked, but manually clearing the browser's cache did.--ManosHacker (talk) 06:40, 17 June 2018 (UTC)[reply]

Out of scope?

Hi, can someone take a look at these contributions? Thank you for your time. Lotje (talk) 04:29, 18 June 2018 (UTC)[reply]

Deleted, blocked (a long history of spam using multiple accounts). Materialscientist (talk) 04:45, 18 June 2018 (UTC)[reply]
Materialscientist, Special:Contributions/Wso.louise might be another one I think. Best, --Achim (talk) 14:06, 18 June 2018 (UTC)[reply]

"Missing evidence of permission" On File:S133e006372 Stitch Stitch.jpg From Admin who doesn't Understand NASA Copy Right

I recently uploaded an image I created in 2011 of the Space shuttle Discovery and the International Space Station created using multiple stitched screen captures I took at the time from NASATV. I added the NASA licensing to the image as it was derived from their channel, however they give permission for use as seen here:

NASA copyright release: "NASA content - images, audio, video, and computer files used in the rendition of 3-dimensional models, such as texture maps and polygon data in any format - generally are not copyrighted. You may use this material for educational or informational purposes, including photo collections, textbooks, public exhibits, computer graphical simulations and Internet Web pages. This general permission extends to personal Web pages.

News outlets, schools, and text-book authors may use NASA content without needing explicit permission. NASA content used in a factual manner that does not imply endorsement may be used without needing explicit permission. NASA should be acknowledged as the source of the material. NASA occasionally uses copyrighted material by permission on its website. Those images will be marked copyright with the name of the copyright holder. NASA's use does not convey any rights to others to use the same material. Those wishing to use copyrighted material must contact the copyright holder directly."

https://www.nasa.gov/multimedia/guidelines/index.html

I HAve mentioned this to the admin, but they continue to refuse to release the "Missing evidence of permission: hold on the file.

@Ronsmytheiii:If the file regarding is from NASA, then please provide us a link to that image. What I am concerning at that time is that the file lacks a verifiable source to NASA, and other users cannot prove it is from NASA.廣九直通車 (talk) 00:34, 18 June 2018 (UTC)

Again, the image used NASATV footage, of which I screen captured and stitched together myself. There is no link to the Image as I made it myself. Ronsmytheiii (talk) 05:28, 18 June 2018 (UTC)

OK, I originally thought that NASA TV is some sort of YouTube channel owned by NASA. After searching for some more information, I think that the issue about the source is better to be asked on COM:VPC, as more experienced users may provide assistance.廣九直通車 (talk) 07:16, 18 June 2018 (UTC)

So the admin doesn't have enough experience, but still leave the lock/deletion flag on? I think I have more than documented fair use for this file. I have covered NASA for years, and know their copyright, plus it is mentioned right on the media guidelines that I provided! — Preceding unsigned comment added by Ronsmytheiii (talk • contribs) 20:06, 18 June 2018 (UTC)[reply]

Fair-use material is not allowed on Commons; it needs to be uploaded locally, if the project allows it, such as :en. --Túrelio (talk) 20:18, 18 June 2018 (UTC)[reply]
廣九直通車 is not an admin ("So the admin doesn't have enough experience, but still leave the lock/deletion flag on?") This is the Administrators' noticeboard; exactly what admin intervention is required here? And how do you reconcile your position with COM:EVID? Эlcobbola talk 20:22, 18 June 2018 (UTC)[reply]
(Edit conflict) First of all, 廣九直通車 is not an administrator but a regular editor, but they were totally right to tag the image. We need verifiable evidence such as links to the actual NASA TV footage of this mission which you used for your combined image. You are of course right that original NASA works are in the public domain, but you as the uploader need to provide evidence and not just assertions that your work does not infringe upon any possible copyrights. Moreover, we don't allow fair use images here at all, so why did you think that this was relevant? So, blaming 廣九直通車 for being inexperienced where you were clearly at fault is a no-go. As there are hardly any private photographers out there who could possibly claim copyright for these original images I do believe that this is NASA material, but please try to find the original TV footage so we can verify your claim. De728631 (talk) 20:25, 18 June 2018 (UTC)[reply]
For someone familiar with the material, this is an obvious situation. Works created by NASA are in the public domain, without exception. Regarding this image, the only question is who created it (NASA, Roscosmos, ESA, or JAXA). It can easily be determined to 1) be from a camera on the International Space Station P6 Truss segment, which is owned by NASA and 2) was broadcast on NASA TV (the network bug is visible bottom left). De728631, I'm unaware of publicly available archives of live NASA TV footage, so your request is likely impossible. Huntster (t @ c) 00:10, 19 June 2018 (UTC)[reply]
Alright, thank you for clarifying the matter. This "bug" logo may also serve as evidence of origin. So unless anyone objects, I'm going to pass the original PD status. De728631 (talk) 00:19, 19 June 2018 (UTC)[reply]

Confirmed socks

Please block AchaksurvisayaUdvejin and Volume345. They are confirmed socks of each other and they have made legal threats and tried to impersonate an admin on en.wiki. ANI thread. Also please see my checkuser results. Here on Commons, they are trying to manipulate this deletion request.
⋙–Berean–Hunter—► 13:07, 21 June 2018 (UTC)[reply]

✓ Done One blocked, the other warned. Yann (talk) 13:23, 21 June 2018 (UTC)[reply]
Thank you.
⋙–Berean–Hunter—► 13:38, 21 June 2018 (UTC)[reply]