Commons:Administrators' noticeboard/Blocks and protections

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

Shortcuts: COM:AN/B • COM:AN/P • COM:RFPP

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
20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
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
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
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

  • For page protection requests, please state protection type, file name, and proposed protection time span. See also: Protection Policy.
  • Before proposing a user be blocked, please familiarize yourself with the Commons' Blocking Policy.
  • Remember to sign and date all comments using four tildes (~~~~), which translates into a signature and a time stamp.
  • Notify the user(s) concerned via their user talk page(s). {{subst:Discussion-notice|noticeboard=COM:AN/B|thread=|reason=}} is available for this.
  • Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.


Please semi-protect. Recurring vandalism. Jonteemil (talk) 20:40, 5 October 2023 (UTC)Reply[reply]

✓ Done. One year semi-protection should be enough. Taivo (talk) 16:05, 6 October 2023 (UTC)Reply[reply]

JOSM is GPL software and its screenshots can be uploaded

Juan Villalobos (talk) 11:56, 6 October 2023 (UTC)Reply[reply]

You have a long list of files with improper or without a license. It is your responsibility to provide a license, and all information such as source, author, date, etc. I undeleted this file. You must provide a proof that this software is under a free license. Yann (talk) 18:55, 6 October 2023 (UTC)Reply[reply]
Why am I referenced here? I have never edited File:Create a osm relation 1.png; I have never performed an administrative action on it; I have never opined on JOSM software, to you or otherwise. As below, you only appear to have no idea what you're talking about. This bizarre, non-actionable request ("I ask to correct the block") seems to reflect the same lack of care and clue implicit in the referenced history of improper licensing. Эlcobbola talk 20:15, 6 October 2023 (UTC)Reply[reply]
 Not done No admin action needed. Juan Villalobos, it's clear that you don't understand Commons's licensing requirements. I recommend you fix that, as future files uploaded with incomplete or incorrect licenses will result in escalating blocks. The Squirrel Conspiracy (talk) 04:16, 7 October 2023 (UTC)Reply[reply]
@The Squirrel Conspiracy: Your answer is "yes, it is a GPL screenshot and can be used" or "no, it is a GPL-screenshot, but it can't be used"?.--Juan Villalobos (talk) 15:12, 8 October 2023 (UTC)Reply[reply]
The Squirrel's answer is basically "pon las licencias que corresponden o espera las consecuencias que correspondan" (in Spanish for his better understanding). Bedivere (talk) 05:28, 9 October 2023 (UTC)Reply[reply]
@Bedivere: great logic: "We first block and then we look what is going on". It is in any case better than Moscow trials. They ended with a definitively block. --Juan Villalobos (talk) 10:22, 9 October 2023 (UTC)Reply[reply]
@Bedivere: Right, "put the corresponding licenses or wait for the corresponding consequences". COM:EVID rules.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 12:13, 9 October 2023 (UTC)Reply[reply]

Hydrosheds.org

  • Reason for reporting: Users Yann and Taivo have blocked me [2] because, among others, the upload of File:TdFbasins.svg which has been deleted by user Jeff_G. Jeff_G. aduced that: This file is a copyright violation for the following reason: "non-commercial use only" per https://www.hydrosheds.org/terms-of-use

That is false. Indeed the page states "non-commercial use only" in the paragraph "Copyright and Limited License", but in the anterior paragraph "Data Licenses" they says that:

All data products come with specific license terms, specified on the product pages and technical documentation. By downloading any HydroSHEDS data product, the user agrees to abide by the terms of the license of that product.

The product that I downloaded is https://www.hydrosheds.org/products/hydrobasins and the paragraph "License" declares that:

The HydroBASINS database is freely available for scientific, educational and commercial use. The data are distributed under the same license agreement as the HydroSHEDS core products, which is included in the HydroSHEDS Technical Documentation. For all regulations regarding license grants, copyright, redistribution restrictions, required attributions, disclaimer of warranty, indemnification, liability, and waiver of damages, please refer to the license agreement.
By downloading and using the data the user agrees to the terms and conditions of this license.

I ask to correct the block and to reload the erased file. Juan Villalobos (talk) 12:20, 6 October 2023 (UTC)Reply[reply]

Why am I referenced here? I have never edited File:TdFbasins.svg; I have never performed an administrative action on it. In fact, you haven't referenced that admin that did delete it (Wutsje). Taivo did not block you. Jeff G. is not an admin. As below, you only appear to have no idea what you're talking about. This bizarre, non-actionable request ("I ask to correct the block") seems to reflect the same lack of care and clue implicit in the referenced history of improper licensing. Эlcobbola talk 20:15, 6 October 2023 (UTC)Reply[reply]
 Not done No admin action needed. The Squirrel Conspiracy (talk) 04:16, 7 October 2023 (UTC)Reply[reply]
@The Squirrel Conspiracy: your answer means "yes, https://www.hydrosheds.org/products/hydrobasins can be used" or "no, https://www.hydrosheds.org/products/hydrobasins can't be used"? --Juan Villalobos (talk) 15:09, 8 October 2023 (UTC)Reply[reply]
@Juan Villalobos: No, it can't be used.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 12:19, 9 October 2023 (UTC)Reply[reply]

In dubio pro reo

  • Taivo + Yann + Elcobbola
  • Reason for reporting: Both users blocked me [3] because of File:Rio pangue.png adducing its license is quite vague about commercial use, but even if we accept it as permission for commercial use, nothing is still said about derivative works. So the block is correct. I agree that the license is vague for some people, but it is their INTERPRETATION of the license. I once again emphasize INTERPRETATION. The license doesn't says that it is forbidden the use nor that it is prohibited for commerce with the image. My first laguage is Spanish and the license says for me clearly "download it, copy it, use it, change it, derivate it, sell it, delete it, download it again and again and enjoy it". The same question is said in https://www.memoriachilena.cl/602/w3-article-53557.html . The license is :"Este documento pertenece al patrimonio cultural común, por lo que puede ser utilizado y reproducido libremente." It doesn't say "creative commons", nor "commercial use allowed", nor "public domain" etc, but in my interpretation it says that same as the File:Rio pangue.png: enjoy it!. We can have a long discussion about the right interpretation of the license. For that cases the old Romans had the principle: : That means if you can't probe the delict, you have to free the defendant.

Juan Villalobos (talk) 15:36, 6 October 2023 (UTC)Reply[reply]

I have never blocked you. I have never declined, or even opposed an unblock request of yours. Accordingly, I don't know what you're talking above ("you blocked me on false assumptions" [4]), and you appear not to either. Эlcobbola talk 15:49, 6 October 2023 (UTC)Reply[reply]
 Not done No admin action needed. The Squirrel Conspiracy (talk) 04:16, 7 October 2023 (UTC)Reply[reply]

Block on User:Doclys

Flix11 (talk) 17:09, 6 October 2023 (UTC)Reply[reply]

The sources of the files you uploaded, File:Daisy JKT48.png and File:Danella JKT48.png, were not published under a CC license, which clearly violates copyright. And you should not accuse me of vandalism just for nominating deletions of your uploaded files. Doclys👨‍⚕️👩‍⚕️ 🩺💉 00:46, 7 October 2023 (UTC)Reply[reply]
✓ Flix11 blocked for two weeks for uploading non-free files after warnings, plus the above false report. Thank you for tagging the files as copyvios User:Doclys; they've been deleted. The Squirrel Conspiracy (talk) 04:10, 7 October 2023 (UTC)Reply[reply]
✓ Done. I declined unblock request of Flix11. Taivo (talk) 16:16, 8 October 2023 (UTC)Reply[reply]

User of this IP is supporting Russia and tries to demonstrate this by editing caption in russian language on this page. Translate of he's edits: "Отличная робота в Грозе, Украина" - "Nice work in Groza, Ukraine", "Уничтожение террористов в Грозе, Украина" - "Destroying of terrorists in Groza, Ukraine". Arturztrostiantsia (talk) 12:31, 7 October 2023 (UTC)Reply[reply]

✓ Done Blocked for 3 days, file deleted as copyvio. Yann (talk) 15:39, 7 October 2023 (UTC)Reply[reply]

[URGENT!] The user is one of participant in our outreach program today. He faced blockage on his way of creating account in the Wikimedia Commons due to the global block range of 2A02:26F0:0:0:0:0:0:0/29, please unblock it ASAP to prevent intereference with our program. Rapid action from admin is required. Thank you. WAqil (WMYS) (talk) 00:51, 8 October 2023 (UTC)Reply[reply]

@WAqil (WMYS): AntiCompositeNumber, the latest global blocking Steward in this case, wrote "Open proxy/Webhost: See the help page if you are affected " in the global block log. Please review those links.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 10:02, 8 October 2023 (UTC)Reply[reply]

Juan Villalobos

  — 🇺🇦Jeff G. please ping or talk to me🇺🇦 10:09, 8 October 2023 (UTC)Reply[reply]

I consider myself too involved to assess this, since I declined the block requests above, but I did want to note that this - essentially 'You supported my block, and therefore you don't know what you're doing' - is an inappropriate way to communicate on a collaborative project. The Squirrel Conspiracy (talk) 20:11, 8 October 2023 (UTC)Reply[reply]
It's not only here that Juan interacts in such erratic ways. They're a prolific Spanish Wikipedia editor but takes things very hard if you ever get across his way in a "negative" way (in his view). Behavior here is definitely concerning, but I wouldn't support a block, just a strong warning. Bedivere (talk) 05:27, 9 October 2023 (UTC)Reply[reply]

Repeated Copyvio: Wikidrifterr

Wikidrifterr (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)

Editor has uploaded more copyright violations after final warning. Whpq (talk) 12:25, 8 October 2023 (UTC)Reply[reply]

✓ Done. One week block. All uploads are either deleted or nominated for deletion. Taivo (talk) 15:51, 8 October 2023 (UTC)Reply[reply]

Repeated Copyvio: Ailyn634

Repeated copyright violations by Markos1268

Markos1268 (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)

This user is a persistent copyright violator and all of their previous uploads have been deleted as such. The recently-uploaded File:1987-88-Cadillac-Fleetwood-Sixty-Special.jpg is an obvious copyright violation. I have not yet been able to locate the source of the other two recent uploads, but it's clear that this user is only here to violate copyright. A previous block did not change the user's behavior. --Sable232 (talk) 21:30, 9 October 2023 (UTC)Reply[reply]

✓ Done Blocked for a month (2nd block). Yann (talk) 22:19, 9 October 2023 (UTC)Reply[reply]

BHARATHESHA ALASANDEMAJALU

  — 🇺🇦Jeff G. please ping or talk to me🇺🇦 15:17, 10 October 2023 (UTC)Reply[reply]

✓ Done Blocked for a week. Yann (talk) 15:43, 10 October 2023 (UTC)Reply[reply]

Juan1999dm

Uploading unidentified COM:SCREENSHOTs, some including Google aerial photography, after a final warning for false copyright claims. Belbury (talk) 16:55, 10 October 2023 (UTC)Reply[reply]

✓ Done Blocked for a week, and Commons:Deletion requests/Files uploaded by Juan1999dm. Yann (talk) 11:35, 11 October 2023 (UTC)Reply[reply]

ANAspipo11

Uploading out-of-scope/copyvio screenshots of what look like commercial emails they have received. Belbury (talk) 11:23, 11 October 2023 (UTC)Reply[reply]

✓ Done Indef., spam only. Yann (talk) 11:37, 11 October 2023 (UTC)Reply[reply]

VikDog99

User:VikDog99 has repeatedly remade their userpage, which is unambigious promotion, a total of three times now after it's been speedily deleted each time. Multiple warnings have been given, and they haven't made any constructive edits as far as I can tell. Suntooooth (talk) 22:26, 11 October 2023 (UTC)Reply[reply]

✓ Done Indef. Clearly NOTHERE. Yann (talk) 23:26, 11 October 2023 (UTC)Reply[reply]