Commons:Administrators' noticeboard/User problems

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

Shortcuts: COM:AN/U • COM:ANU • COM:ANI

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
21, 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
Translate this page
COMMONS DISCUSSION PAGES (index)

Note

  • Before reporting one or more users here, try to resolve the dispute by discussing with them first. (Exception: obvious vandal accounts, spambots, etc.)
  • Keep your report as short as possible, but include links as evidence.
  • 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/U|thread=|reason=}} is available for this.
  • It is important to keep a cool head, especially when responding to comments against you or your edits. Personal attacks and disruptive comments only escalate a situation; Please try to remain civil with your comments.
  • Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

Subject: Request for Permanent Block of A1Cafel[edit]

The following discussion is archived. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
It's clear that there is not currently a consensus to permanently block A1Cafel (or to ban them from using the tool). However, I would encourage A1Cafel to use this as a wake-up call, as they are frequently brought to this noticeboard, and if that continues to happen, eventually enough people are going to lose patience with them that a ban request will stick. The Squirrel Conspiracy (talk) 03:18, 6 November 2023 (UTC)Reply[reply]

Dear sysops,

I believe that the actions of User:A1Cafel are inappropriate, contrary to the collaborative spirit, and demotivating for other contributors. I request that the possibility of an indefinite block be discussed, as this user has received multiple warnings and has been blocked four times in less than a year for reasons related to the concerns I am raising [1].

Specifically:

  1. Excessive and Unwarranted Deletion Nominations for Images: User:A1Cafel has been excessively nominating images for deletion, often citing reasons related to Freedom of Panorama (FOP) or the lack thereof in a specific country. This includes not only legitimate nominations for images but also nominations for items like plaques affixed to sculptures, which may not be justified.
  2. Stalking Contributions: I have noticed a pattern of User:A1Cafel closely tracking my contributions, with deletion nominations appearing in reverse chronological order based on my recent edits. This behavior, apart from being unsettling, contradicts the Wikipedia principle of "Assume Good Faith." I am not the only contributor affected by this problematic approach; prominent contributors like Chabe01 and to a lesser extent Romainbehar seem to have faced similar situations, and there may be others I have not yet documented.
  3. Intensity of Nominations: The intensity of User:A1Cafel's actions is also a concern. Aside from acting as a self-appointed watchdog, the lack of discernment is evident. For instance, the nomination of both a legitimate sculpture image and an accompanying plaque for deletion highlights a lack of careful consideration. The contributor in question does not allow for sufficient time for analysis and response, with new deletion nominations coming in daily in my case.
  4. Contributor Demotivation: Lastly, User:A1Cafel's behavior has a demotivating effect on contributors. In my own case, I have fallen behind on uploading nearly a thousand photos from three or four countries due to User:A1Cafel's recent conduct. I had maintained a daily upload rate until these disruptions. While this is a personal experience, it is likely that this negativity affects others as well. In any case, User:A1Cafel's actions do not align with the fundamental principles of collaborative work.

Thank you for your attention, --Benoît (d) 13:22, 28 September 2023 (UTC)Reply[reply]

First, photographing sculptures and statues is a kind of derivative work. You need to either obtain the permission of the artist, or they have been dead for 70 years, especially for those countries with no FoP, or their FoP applies to buildings only. Your country, France, has a non-commercial FoP, but that is not accepted on Commons. Second, I didn't stalk anyone on nominating DRs. I just found the information of the sculptures using French Wikipedia. Lastly, I don't think this is a demotivation of the project. As an user, you should confirm that your uploads are complying with COM:L. If there is any violation of that, they cannot stay here and need to be deleted. I understand you may feel frustrated to see some of your valuable images were deleted, but copyright is copyright, we must respect it. --A1Cafel (talk) 13:38, 28 September 2023 (UTC)Reply[reply]
Read me attentively, I don’t complain about COM:L, I don’t feel frustrated by images deletion when they must be deleted. I complain about your behavior. Your answer consolidates my opinion you don’t get the issue, or don’t want to understand, and you are not able to call yourself into question regarding your behavior here. It is my 5th point: unability to reconsider his/her own behavior, is an aggravating factor. ----Benoît (d) 15:23, 28 September 2023 (UTC)Reply[reply]
If you think I make too many nomination that may hinder other's attention, I can slow down the nomination rate. --A1Cafel (talk) 15:31, 28 September 2023 (UTC)Reply[reply]
  • As an user, you should confirm that your uploads are complying with COM:L.
OK, so why don't you do that? I see two regular sorts of edit from you here, both in great bulk. Tagging others' uploads for deletion under FOP claims, and uploading images yourself which have just the same issue (from your talk: page right now, File:Floralis Genérica (20964656646).jpg & File:Floralis Genérica (16429027530).jpg). Why are you so adamant at enforcing a rule on others when you won't follow it yourself? Andy Dingley (talk) 15:29, 28 September 2023 (UTC)Reply[reply]
They are uploaded a few years ago. At that time, I think that they can fall under de minimis. --A1Cafel (talk) 15:34, 28 September 2023 (UTC)Reply[reply]
  • I would have to agree with the nominator here. A1Cafel's actions overall are a nett negative to the project and they've been told about this repeatedly, for as long as I've seen them here. Andy Dingley (talk) 15:24, 28 September 2023 (UTC)Reply[reply]
I have to disagree. Admittedly they had some problems early on, but I deal with them a lot myself and at least from what I've seen recently their DRs are usually pretty spot on. They also seem to know the relevant copyright laws and guidelines well. I guess there isn't a way to check what a nominators DR success rate is on Commons like they have for Wikipedia, but IMO to justify a block there would have to be clear evidence of them repeatedly opening DRs that were closed as keep. Including ones related to the person who opened this complaint. I haven't seen either one myself though. And at least when it comes to the person who opened this they clearly have had a problem with uploading COPYVIO in the last year. Their accusations that A1Cafel is somehow intentionally stalking them and excessively nominating their images for deletion in the process is also clearly spurious since A1Cafel has only nominated 15 of their uploads for deletion in the last 4 months, isn't the only one doing it, and the amount of nominations is directly related to how much COPYVIO someone uploads anyway. But so far it seems as all of their nominations have resalted in delete. So this is clearly an issue with Benoît Prieur not knowing or following the guidelines. --Adamant1 (talk) 15:36, 28 September 2023 (UTC)Reply[reply]
  • You mean we should be grateful that they've abandoned their old practice (for which they were blocked) of also threatening to block those they DR'ed? Andy Dingley (talk) 15:42, 28 September 2023 (UTC)Reply[reply]
+1@Adamant1 I think on average I close around a dozen of their DRs every day, and besides very few cases where I came to a different conclusion, I think 99% or more end in "deleted per nomination". I also don't see any "attitude" in the DRs, and the rational is mostly above average. Is anybody of the opinions that we should silently ignore FoP violations? Krd 15:46, 28 September 2023 (UTC)Reply[reply]
I agree with Krd here. I close usually 6 to 10 DRs a day and FOP cases are something I frequently close. I don't notice any particular attitude as far as the user's nominations, and I just added an Undelete category because the user brought it to our attention at UNDEL. I definitely don't think we should ignore FoP violations, and I look on with interest to efforts to bring FOP to countries like the Philippines and South Africa. Abzeronow (talk) 16:07, 28 September 2023 (UTC)Reply[reply]
Seems to me that remark from Krd and assent from Abzeronow) should settle the matter. I'm a little surprised to see a claim of "99% or more" in terms of anyone's DRs, though. Do we never (or almost never) end up with anyone getting the relevant permission from the copyright holder, or deciding that something is de minimis where A1Cafel didn't think so, or discovering that a building or sculpure is a older than A1Cafel thought? - Jmabel ! talk 17:08, 28 September 2023 (UTC)Reply[reply]

̈*@Adamant1 Since I need to justify myself, I must clarify that I have an excellent knowledge of the rules related to Freedom of Panorama (FOP) in all the countries where I have had the opportunity to travel. To the extent that I have my own process, allowing me to store images that may be uploaded someday (due to changes in the law, or whatever). I have a personal storage for this, as well as a Flickr account. I am also a contributor to non-wiki projects where I always try to adhere as closely to CC0 (Creative Commons Zero) as possible and use them as secondary storage until the upload is possible on Commons. Examples include [2], [=icreator:%22Prieur,%20Beno%C3%AEt,%201975-....%22], among others.

Of course, I am not infallible, and sometimes photos slip through this initial personal filter (lack of information about the artwork, etc.). What is statistically puzzling is that A1Cafel has identified around fifteen copyright violations in the past four months, given that I typically take an average of ten photos per day for Commons:

  • Lille, France (two days spent, late 2020)
  • Paris, Panthéon, France (one day spent in August 2023)
  • Cibeins, France (20 minutes stopover in 2017)
  • Nice, France (1.5 days in March 2022)
  • Monaco, Monaco (2 days in November 2021)
  • Bourg-en-Bresse, France (I go there often, but these are photos from 2016)
  • Cannes, France (two days spent in April 2023)
  • Dagneux Cemetery, France (an afternoon in 2016)
  • NYC, June 2023
  • Paris, 2021

All these copyright violations are effective and have been rightly removed. the laws of statistics being stubborn, I only wonder how A1Cafel managed to identify all of this in such a short time, unless through stalking me. I am very interested, assuming there was no stalking involved, in learning about the modus operandi (parent category, etc.) that led to such a "coincidence." ----Benoît (d) 17:14, 28 September 2023 (UTC)Reply[reply]

@Benoît Prieur: Sorry if that de-motivates you, but I would hope you are not saying that we should retain copyvios to keep you motivated, or that your work should not be subject to scrutiny despite someone finding some actual problems. If you can point at half a dozen specific examples in the last year or so where A1Cafel nominated your images for deletion but the consensus was to keep them, I might see this differently. And, if so, then Krd and Abzeronow should reconsider their remarks. But right now, I'm inclined to take their remarks at or near face value. - Jmabel ! talk 17:20, 28 September 2023 (UTC)Reply[reply]
The deletion is not demotivated me at all. I'm clearly happy to see deletion of pictures which must not be on Commons for copyright reason. I'm demotivated by the obvious stalking (I can provide similar studies for others stalked contributors) and by the way of considering it a good behavior as long as it detects copyright violations, whereas I find it completely creepy and in contradiction with our values. Please try to understand that what depresses me is not the deletion of photos (for valid reasons). It's a behavior that I personally identify as toxic. ----Benoît (d) 17:26, 28 September 2023 (UTC)Reply[reply]
Just an FYI, but if I'm reading A1Cafel's edit history from the last few days correctly they have nominated upwards of 500 files for deletion just since yesterday. Of which you uploaded like what, 3 of those? So the accusation that they are singling you out in some way is clearly baseless. --Adamant1 (talk) 17:44, 28 September 2023 (UTC)Reply[reply]
@Jmabel, These are some examples of DR's by A1Cafel on my uploads in the recent 6 months *** All were "Kept":
Commons:Deletion requests/File:Nathalie Orozco.jpg
Commons:Deletion requests/File:U.S. Ambassador to Nicaragua Kevin K. Sullivan welcomed 222 individuals who had been imprisoned by the Government of Nicaragua for exercising their fundamental freedoms- U.S. Department of State in Washington, D.C., on March 31, 20
Commons:Deletion requests/Files found with Foto Martin Lätt
Commons:Deletion requests/Files found with Photo by Gaurav Dwivedi
Which is similar to this still open DR from June - Commons:Deletion requests/Files found with Photo by Milburn Fernandes
Commons:Deletion requests/Files found with Photo by Rakesh Malholtra
Commons:Deletion requests/File:Bucha Summit, March 31, 2023.jpg
Commons:Deletion requests/File:Attorney General Merrick B. Garland met with President of Ukraine Volodymyr Zelenskyy, United for Justice Conference, Lviv, March 3, 2023 - 52744852495.jpg
Commons:Deletion requests/File:Attorney General Merrick B. Garland met with President of Ukraine Volodymyr Zelenskyy, United for Justice Conference, Lviv, March 3, 2023.jpg
Commons:Deletion requests/File:International Holocaust Remembrance Day, Jan. 27, 2023.jpg
and this most recent DR for alleged COM:OOS of the now burned famous Lahaina Banyon Tree (largest in the US) Commons:Deletion_requests/File:Maui_-_Shawn_-_5462362804.jpg. Thanks, -- Ooligan (talk) 10:51, 29 September 2023 (UTC)Reply[reply]
@Ooligan: I'd say that looks like someone who might be too inclined to start DRs, but certainly also indicates that he wasn't particularly stalking Benoît. - Jmabel ! talk 15:39, 29 September 2023 (UTC)Reply[reply]

(Edit conflict) Firstly, I would like to second Krd and Abzeronow that stress that the nomination of FoP violations is not a problem per se. Hence, I do not see here any reason why we should admonish or even block A1Cafel as, so far, we do not have any proof of a practice of abusive nominations by A1Cafel. Secondly, I would like to add that we should take some care in FoP nominations, i.e. naming the relevant country and, if possible after some research, identify the artist and their life span. This makes it easier to undelete these images when eventually the artwork is in the public domain. I asked recently A1Cafel to improve their FOP-related DRs in this regard and my impression is that A1Cafel's nominations got better. Finally, I would like to ask A1Cafel to review their own older uploads in regard to FOP and to make sure that the focus in nominations is not on selected users. If we run across an image that needs to be nominated, then nominate it. But nobody should run systematically through all contributions of an individual user if there is no good reason for this. I do not know if this has actually happened here but I mention it as Benoît got this impression (unfortunately without evidence to evaluate this further). --AFBorchert (talk) 17:48, 28 September 2023 (UTC)Reply[reply]

A1Cafel has a long history of cross-wiki sockpuppetry, that's all I know about them. Lemonaka (talk) 07:32, 29 September 2023 (UTC)Reply[reply]
@AFBorchert I don't agree! A1Cafel has been recently abusing of the DR tool (recently = September 2023), when he repeatedly, and continued after being warned, to nominate WLM files. This is disruptive for the project, because it gets in the way of the main photographic competition on Commons that implies many local chapters besides WMF. These files have regular permissions that are made public by the organisers, thus nominating the files for deletion discourages potential new users, attracted here by the competition.
I fully support Benoît Prieur's request. A1Cafel is here to "delete the project", not to contribute to make it grow. If undef block seems too much (but I wonder why), then I propose indef ban on DRs, so to force him to contribute positively. (of course, any sockpuppetry would imply a full block without having any AN/U, from my point of view). --Ruthven (msg) 14:15, 6 October 2023 (UTC)Reply[reply]
  • @Ruthven: you don't provide any links there, so I have to ask: were these WLM files deleted? Or were these things that shouldn't have been DR'd? - Jmabel ! talk 15:42, 6 October 2023 (UTC)Reply[reply]
    @Jmabel There are links in A1Cafel's talk page, but also, e.g. Commons:Deletion_requests/Files_in_Category:Biblioteca_Sandro_Penna, Commons:Deletion_requests/Files_in_Category:The_Infantryman_Monument_(Salsomaggiore_Terme), File:Piemonte (174).JPG, etc. To have them deleted or not is not important, because it stresses the users, kick them out of the project, and reinforce the fear that, "whatever is done, on Commons they'll delete our files". It depreciates WLM in the same occasion. The best solution to prevent this is a block.
    @AFBorchert I reckon that, if there are no issues in his tending categories, he should do that, and no other activity on Commons. Note that I warned him in the past about repeatly requesting file deletion, even after an undel. This is to persist in a negative activity for the project. Ruthven (msg) 07:59, 11 October 2023 (UTC)Reply[reply]
    @Ruthven, naïve question of mine: why don’t WLM files have to adhere to FoP policies? RodRabelo7 (talk) 08:21, 11 October 2023 (UTC)Reply[reply]
    @RodRabelo7 That's exactly the point. WLM have permission from the copyright holders for publication under a free license. Ruthven (msg) 12:46, 11 October 2023 (UTC)Reply[reply]
    • @Ruthven: " WLM have permission from the copyright holders for publication under a free license." Could you clarify that? There's no mention of any special arrangement like that in en:Wiki Loves Monuments nor in Commons:Wiki Loves Monuments. I see that in most countries with little freedom of panorama, we simply don't run WLM. But are you saying that there are countries where there is limited FoP and WLM has permission from copyright-holders to publish photographs of (at least some) subjects that would normally be excluded by lack of FoP? Or have I misunderstood you? - Jmabel ! talk 15:37, 11 October 2023 (UTC)Reply[reply]
      The whole work behind WLM, implying local chapters and volunteers, in countries where there is little FoP is to obtain the permissions for the monuments (photograph and publish under a free license). These authorizations are usually put online by the organizers. When a monument is "free" for WLM (or even outside of the competition, if the authorization is wider), there is a little template materializing it in the File page. This is true for Italy, for instance (which is the local version that I know the most, and where there are no copyright rules for many monuments), but the concept is similar for other countries. Monuments that are in the public domain, usually do not need a permission (Italian do have them, because of the no copyright rules above that we can ignore on Commons, but that the local chapter wants to avoid). Maybe some organizers from different countries can explain their workflow. Ruthven (msg) 08:01, 12 October 2023 (UTC)Reply[reply]
@Ruthven: I guess by "no copyright rules" you mean the it:Codice dei beni culturali e del paesaggio (COM:Italy#Additional restrictions for cultural heritage assets). But aside from that, I've seen several times now the claim that "WLM have permission from the copyright holders" (or similar). From what I have seen, WLM has authorizations by various Italian cities, regions etc. to photograph various buildings, monuments etc. As I gathered, these cities etc. are allowed to give such authorizations accd. to the Codice mentioned above, but this is not about copyright, but about non-copyright restrictions. The codice explicitely says such authorizations must adhere to copyright. Also, the cities might be the owners of the various buildings and monuments listed in these authorizations (though I have my doubts if that is really true for every single of them), but does that really make them the copyright holders? I've seen various theories that Italian copyright law (some article or paragraph 11) gives them the copyright in various cases (for works made "on their behalf"), but I also have my doubts about that. The WLM authorizations I have seen did not mention copyright at all. You might want to participate in Commons:Deletion requests/File:Il Grande Ferro R, Alberto Burri, pala De André, Ravenna.jpg (which was not started by A1Cafel).
All of this WLM Italy business is rather unclear, and frankly, I am not convinced that everything is all right as far as copyright is concerned. And I'm an admin here and do know a thing or two about copyright I think.Maybe I'm missing something, but if that is the case, it should be thoroughly explained how everything is in order then in these WLM Italy cases. COM:Italy isn't very helpful here. And if people like me and JWilz12345 (who started the DR mentioned above) don't see it, it must be explained better, and it's unfair to hold it against A1Cafel. --Rosenzweig τ 08:44, 12 October 2023 (UTC)Reply[reply]
@Rosenzweig: thanks for mentioning me. Regarding the very-unique case of WLM-Italy authorizations from Italian comunes or cities (from Ravenna to Assisi) over copyrighted buildings and monuments, the best place is actually at COM:VPC. All involved users must be pinged there for participation, and the deletion requests with mentions to the WLM-Italy MiBAC permissions or city (comune) permissions must be tagged with "on hold" templates pending the finality of the discussion. Or do you want me to start the (nth) thread? JWilz12345 (Talk|Contrib's.) 09:15, 12 October 2023 (UTC)Reply[reply]
@JWilz12345: Please do start the thread, I can't right now (but will participate later). --Rosenzweig τ 09:22, 12 October 2023 (UTC)Reply[reply]
@Rosenzweig The general idea is that the organizers contact the copyright holders (the City Council for monuments, and the Diocese for churches, generally) in order to have a permission to publish photographs under free license. This solves both FoP restrictions, and the Codice dei beni culturali e del paesaggio.
As far as I've checked so far, these permissions are correctly stated and OK for Commons purposes.
Then, somewhere it has been asked to validate them via VRT. This is honestly not doable, and we must trust the organizers, simply because VRT hasn't the number of agents sufficient to perform such a large verification. Ruthven (msg) 12:35, 12 October 2023 (UTC)Reply[reply]
Where is this about WLM and permissions documented? It's news to me, and I'm a 20-year veteran of Wikipedia, have been on Commons almost since it started, and an an admin both here and on en-wiki. If I haven't heard about it, and can't find it anywhere, it almost certainly should be more prominent. And I certainly would not have expected any particular user to be familiar with it, or to sanction them for not having known. - Jmabel ! talk 18:07, 12 October 2023 (UTC) I see that a separate discussion has been started at COM:VPC, I will ask there instead. - Jmabel ! talk 18:15, 12 October 2023 (UTC)Reply[reply]
  • @Ruthven: These are strong statements but without any diffs, any statements whether A1Cafel has been warned and how he continued afterwards. The claim that “A1Cafel is here to "delete the project", not to contribute to make it grow” does not seem to be justified given that A1Cafel also uploads files, tends to categories etc. etc. --AFBorchert (talk) 17:09, 6 October 2023 (UTC)Reply[reply]
    Anyone need some evidence for their Long-term sockpuppetry? Lemonaka (talk) 08:14, 8 October 2023 (UTC)Reply[reply]
    Do you have "... evidence of Long-term sockpuppetry?" -- Ooligan (talk) 21:16, 18 October 2023 (UTC)Reply[reply]
    Do you need? Lemonaka (talk) 01:02, 30 October 2023 (UTC)Reply[reply]
    Yes, please, as that can also be a reason to seek for a global ban. Liuxinyu970226 (talk) 10:58, 31 October 2023 (UTC)Reply[reply]
    Contacting me through email if you need. Lemonaka (talk) 13:59, 4 November 2023 (UTC)Reply[reply]
    @Lemonaka, Almost one month ago (8 October) you wrote above,
    "Anyone need some evidence for their Long-term sockpuppetry?"
    You have shared your opinions elsewhere, such as the Italy-related Long Term Abuser (LTA). Please, share a few of yours observations here. Respectfully, --Ooligan (talk) 03:34, 5 November 2023 (UTC)Reply[reply]
    @Ooligan Ok, thanks, please take a look on their English Wikipedia talk page, and their previous block logs just on this project. You can easily find some CU request against her, if you want to digging more, you can have a try. Lemonaka (talk) 03:37, 5 November 2023 (UTC)Reply[reply]
    Italy-related Long Term Abuser, eh, I don't quite sure which one you are pointing at. Lemonaka (talk) 03:37, 5 November 2023 (UTC)Reply[reply]
  •  Comment I was unaware of the sockpuppetry. That's very troubling. But in terms of A1Cafel's nominations under their own username, I speak as someone who took great exception to their earlier work as slipshod and uncollegial and say that from what I've seen in the last several months at least (and while I didn't see everything, I do look through COM:DR frequently), their work has generally looked quite good, competent and well-justified, and I've had no objection to their tone, either. In a few cases in which they were shown to have made a mistake, I've seen them accept it without trouble. So at least in terms of their work under their own username, I oppose any kind of block beyond existing limitations. If anyone wants to propose some form of discipline for the socking, that would be different, and I would bow out of a discussion on that basis and defer to the judgment of those who know more about how severe or minor it is, but I have no objection whatsoever to A1Cafel's deletion requests for photos of French art and architecture on the basis of a lack of commercial FoP, although they could probably sometimes be more careful about what might be de minimis. So consider this a qualified vote of confidence for A1Cafel at this point. -- Ikan Kekek (talk) 06:33, 1 October 2023 (UTC)Reply[reply]
@AFBorchert. Above I wrote a response to @Jmabel-
"These are some examples of DR's by A1Cafel on my uploads in the recent 6 months *** All were "Kept":" (Please, see all recent DR links from my talk page in my above reply).
I offered those examples of failed Deletion Requests as an example of a pattern of behavior that I personally experienced by this User. My response was to Jmabel writing,
"If you can point at half a dozen specific examples in the last year or so where A1Cafel nominated your images for deletion but the consensus was to keep them, I might see this differently. And, if so, then Krd and Abzeronow should reconsider their remarks. But right now, I'm inclined to take their remarks at or near face value."
So, a dozen DR involving me that have all been "kept." Jmabel wanted "a half a dozen specific examples in the last year..." I gave a dozen specific examples in the last six months.
I suggest this is the proof you asked to have provided. It is not specific to @Benoît Prieur, however it does answer respond to the behavior related to your question,
"... we do not have any proof of a practice of abusive nominations by A1Cafel."
and you further wrote,
"Finally, I would like to ask A1Cafel to review their own older uploads in regard to FOP and to make sure that the focus in nominations is not on selected users. If we run across an image that needs to be nominated, then nominate it. But nobody should run systematically through all contributions of an individual user if there is no good reason for this. I do not know if this has actually happened here but I mention it as Benoît got this impression (unfortunately without evidence to evaluate this further). "
Lastly, I want to thank Benoît Prieur for taking his time to make this submission.
Sincerely, -- Ooligan (talk) 21:26, 1 October 2023 (UTC)Reply[reply]
@Ooligan: COM:AN/U is not a board to submit requests for further research. Convincing evidence needs to be presented here including diffs. See also this comment (first paragraph) by me on Benoît's talk page. --AFBorchert (talk) 05:49, 2 October 2023 (UTC)Reply[reply]
@AFBorchert, Did you see this diff (my 3 consecutive earlier edits) further above? -- Ooligan (talk) 01:33, 1 November 2023 (UTC)Reply[reply]
  •  Comment: I completely agree with Benoît Prieur. A1Cafel indeed stalks contributions and harasses users. Take a look at these absurd deletion requests: [3], [4], [5] etc… If you still don’t believe the opening of those deletion requests was pure harassment, let me explain: minutes before they were opened, I removed from this category some duplicates uploaded by A1Cafel. In fact, the whole category was duplicated. (Funnily enough, A1Cafel has some obscure fetish uploading everything they can regarding the coronation of Charles and Camilla, while nominating to deletion everything they had not uploaded themself!) Not to mention this sort of harassment: [6], [7] etc… I don’t have much time available for this, so I won’t spend the little I have left collecting more and more evidences.
    Honestly, their POV-pushing behavior is tiresome, and it was one of the reasons that made me decide to take a break from Commons (in addition, of course, to personal problems, such as a tumor). I always try to learn with mistakes, some of them being sort of childish, but A1Cafel seems not to. I don’t know if a permanent block would be a solution (I am permanently blocked on ptwiki, and I don’t think that is something nice), so I would suggest something like a three- to six-months block. That would have helped me there, I suppose… RodRabelo7 (talk) 02:53, 9 October 2023 (UTC)Reply[reply]
     Another comment: I haven’t read the whole discussion. RodRabelo7 (talk) 02:55, 9 October 2023 (UTC)Reply[reply]
  •  Comment I suggest a permanent ban for the user from opening whatever RfD. Maybe is beyond their intentions but their actions are disruptive, not helpful at all. -- Blackcat 15:18, 12 October 2023 (UTC)Reply[reply]

Topic ban of A1Cafel from uploads with Flickr2Commons[edit]

See Commons:Deletion requests/Files uploaded by A1Cafel, yet again. Also Commons_talk:Flickr2Commons#Duplicates_2

A1Cafel has been requested over and over to stop doing batch uploads with Flickr2Commons that duplicate batches which have already been imported. This is a time-sink for other editors, they clearly have no intention of changing their behaviour over this.

Accordingly, they should lose access to this tool. The project does not need these uploads, they are just a source of extra work for others. No other measure, i.e. requests to A1Cafel, seems effective.

Their access to the Upload Wizard for doing similar uploads should also be considered (I express no opinion on that point as yet) Andy Dingley (talk) 13:35, 8 October 2023 (UTC)Reply[reply]

  •  Support Yes! Yes! I entirely support that. A1Cafel must stay away from Flickr2Commons, because he does not care for due diligence. The Upload Wizard on the other hand is a much surer tool, it is duplicate-proof, and anyone should be allowed to handle it. --Edelseider (talk) 14:11, 8 October 2023 (UTC)Reply[reply]
@Edelseider, New duplicates by A1Cafel today. Here: Special:FileDuplicateSearch/Eclipse anular 2023, Edzna, Campeche (53266776761).jpg and here: Special:FileDuplicateSearch/Eclipse anular 2023 (53267245920).jpg -- Ooligan (talk) 09:02, 19 October 2023 (UTC)Reply[reply]
@Ooligan: What can I say? He's incorrigible. Edelseider (talk) 09:48, 19 October 2023 (UTC)Reply[reply]
  •  Support I sadly see no other way of them changing their behaviour. --SHB2000 (talk) 08:27, 11 October 2023 (UTC)Reply[reply]
  •  Oppose It appears that there's been a discussion on Commons talk:Flickr2Commons about it allowing people to upload duplicates since at least 2015 and there's been no response from the dev after multiple comments, new threads about it, and 8 years. So my suggestion is to block access to the tool until the developer feels like solving the issue since it's clearly a bug and isn't something only A1Cafel has an issue with. I don't think it's fair to block someone for something that is clearly an issue with Flickr2Commons though. More so since the developer is apparently unwilling to fix it. If uploads of duplicates are really that much of an issue then Flickr2Commons just shouldn't be able to upload images until it's resolved. --Adamant1 (talk) 08:53, 12 October 2023 (UTC)Reply[reply]
  •  Oppose No ban or site ban. Per previous sockpuppetry, they have many methods for circumventing the rules. Lemonaka (talk) 09:19, 12 October 2023 (UTC)Reply[reply]
Sorry, but if they're a problem here, but they also sock to get round blocks, then we shouldn't bother to ban them? How does that work? Andy Dingley (talk) 10:15, 12 October 2023 (UTC)Reply[reply]
@Andy Dingley Banning a people sitewide meant that more eyes will be on them if they use socks to circumvent their ban, topic-banning is less noticed when circumventing by socks. Lemonaka (talk) 11:42, 12 October 2023 (UTC)Reply[reply]
 Oppose, the issue should be handled from the root, not from the leaf. I agree with @Adamant1: 's input. See also this discussion where I commented. I once imported a single file from Flickr, until the file description page begins to claim about an already-existing file on Commons, prompting me to add {{Duplicate}} immediately. Strangely it used to detect duplicates before, until at some point it failed to detect duplicates. At least all batch uploading using that tool should be disabled for all users, including me, until the tool developer fixes the technical issue. Yes the boilerplate notice on top insists users to direct technical concerns on the developer's website, yet I cannot immediately see a button or link on that website for messaging of concerns. I do not want to click any of the links there that appear to be technical in nature. JWilz12345 (Talk|Contrib's.) 09:25, 12 October 2023 (UTC)Reply[reply]
 Oppose topic ban for the reasons stated by Adamant1. I'd be inclined to support blocking access to the Flickr2Commons tool until the duplicates bug is dealt with. Abzeronow (talk) 16:29, 12 October 2023 (UTC)Reply[reply]
@Abzeronow: I may agree provided that Flickr2Commons is disabled for all users, including you and me, until the issue is resolved. Though Edelseider mentioned this discussion on the Flickr2Commons discussion page, and that discussion seemed to suggest a low probability of the tool being fixed. A possible suggestion is a semi-manual way of uploading using the regular UploadWizard, but it is not ideal for users who may have some erratic real life schedules or things to do like me, because descriptions as well as {{Flickrreview}} may need to be manually added. I agree to a possible replacement of Flickr2Commons that would be maintained by the community instead of a single user. I may have made an off-topic comment but this is one input that I wanted to say regarding this issue on widely-used Flickr2Commons. JWilz12345 (Talk|Contrib's.) 03:44, 13 October 2023 (UTC)Reply[reply]
I strongly oppose disabling Flickr2Commons. I use it quite a bit, and would find it very inconvenient not to have it. - Jmabel ! talk 04:03, 13 October 2023 (UTC)Reply[reply]
@JWilz12345: {{Flickrreview}} is added automatically when Using Upload Wizard, and yes, the descriptions have to be added manually with that toll where there is none, but you have the option to "copy all informations to the other files", i.e. it is enough to write the description, add the categories, supply any tag etc. once. --Edelseider (talk) 05:48, 13 October 2023 (UTC)Reply[reply]
  •  Support - please note that this is NOT a ban on A1Cafel uploading images from Flickr to Commons. Nor would it affect any other user from using the Flickr2Commons tool. Since the user has, despite warnings, failed to take due diligence in bulk uploading from Flickr, this would require them to use a different tool that makes upload of duplicates much less likely. I upload a good deal from Commons, regularly using Upload Wizard. Upload Wizard is still very easy and a convenient tool for uploading images from Flickr, and seems to much more reliably warn of duplicates. -- Infrogmation of New Orleans (talk) 21:11, 17 October 2023 (UTC)Reply[reply]
     Comment Since A1Cafel is not autoreviwer, he is limited to uploading 4 images at a time, using UploadWizard. Autoreviewers can upload 500 at once. RodRabelo7 (talk) 04:10, 18 October 2023 (UTC)Reply[reply]
    @RodRabelo7, do you mean autopatroller? -- Ooligan (talk) 20:14, 18 October 2023 (UTC)Reply[reply]
    @Ooligan, yes, sorry. In Portuguese it’s called autorrevisor. My bad. RodRabelo7 (talk) 02:41, 19 October 2023 (UTC)Reply[reply]
    @RodRabelo7, no problem. Thanks for your response. -- Ooligan (talk) 04:07, 19 October 2023 (UTC)Reply[reply]
of these two files; here (now here) and here
This could have been prevented by using Upload Wizard.
I use Upload Wizard, because Upload Wizard shows a warning for each individual file, if that exact same file already exists on Commons. When I see that warning, I do not upload that file. That is why I prefer to use it. Also, minutes ago I checked on this file on Flickr using the Upload Wizard. Upload Wizard shows both duplicate files by their different file names. --Ooligan (talk) 21:04, 18 October 2023 (UTC)Reply[reply]
 Comment - @Andy Dingley, @Abzeronow, @JWilz12345 and @Adamant1
See A1Cafel's talk page for a discussion started in late September about duplicates before this pages's discussion of a "topic ban": User talk:A1Cafel#More duplicates uploaded.
A1Cafel admitted on September 30 that he uploaded 31 duplicate files to Commmons from just one Flickr album. This is the diff
Please, note that is a rate of 36% of the 84 uploaded files from this one Flickr album were duplicates of already existing Commons files. --Ooligan (talk) 10:39, 19 October 2023 (UTC)Reply[reply]
Clearly both users need to be banned from using the tool instead of just blocking it /s --Adamant1 (talk) 12:08, 20 October 2023 (UTC)Reply[reply]
@Adamant1 Probably a bug caused by Magnus's unfair tool settings, see above for issues linked. Liuxinyu970226 (talk) 10:56, 31 October 2023 (UTC)Reply[reply]
@Liuxinyu970226: Thanks. Going by the issues it looks like this has been an on going problem for years and one that he is unwilling to fix. So all the more reason to just block it IMO. --Adamant1 (talk) 12:48, 31 October 2023 (UTC)Reply[reply]
Probably this is also a signal that whether we can still hope and trust Magnus to focus and resolve our concerns on using F2C tool, somewhat potentially, it might be a time that there should elect a new maintainer to take over the F2C source codes. Liuxinyu970226 (talk) 12:53, 31 October 2023 (UTC)Reply[reply]
 Question Does Flickr2Commons run a duplicates check before files are uploaded? If so, why isn't it catching these cases? — Red-tailed hawk (nest) 16:00, 20 October 2023 (UTC)Reply[reply]
@Red-tailed hawk: Flickr2Commons does run a duplicate check BUT it does not recognize files that have been uploaded with another tool (for instance the Upload Wizard), and it does not recognize files when their Flickr name has been modified by the Flickr user. This makes its duplicate check quite worthless. Edelseider (talk) 10:17, 23 October 2023 (UTC)Reply[reply]
That's odd. My understanding is that the upload wizard will give warnings broadly for if the file is on Commons already, regardless of how it was uploaded. Is there an API for this that could be easily incorporated into the Flickr2Commons codebase to improve the existing duplicate check? — Red-tailed hawk (nest) 00:59, 24 October 2023 (UTC)Reply[reply]
@Red-tailed hawk: Sadly, Flickr2Commons can only act on files it is used to upload, and I have come to the conclusion that @Magnus Manske doesn't care enough about the problem.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 01:10, 24 October 2023 (UTC)Reply[reply]
I just had to nominate 40 duplicate files for deletion that were uploaded using Flickr2Commons. I can understand where Jmabel is coming from, but the tool should clearly be blocked regardless of if it might inconvenience a few people. It's not like dealing with duplicate images isn't a massive hassle anyway. --Adamant1 (talk) 15:39, 24 October 2023 (UTC)Reply[reply]
@Red-tailed hawk: As I originally wrote, "Sadly, the Upload Wizard can only act on files it is used to upload".   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 01:11, 6 November 2023 (UTC)Reply[reply]
Sure, but there are bots that (used to) put out regular outputs of duplicate uploads. I'm not 100% on how resource-intensive this is, but I feel like a duplicate check against the database might be feasible in a way that doesn't restrict the scope to merely those files uploaded via the Upload Wizard (think of files uploaded with Special:Upload, for example). — Red-tailed hawk (nest) 01:17, 6 November 2023 (UTC)Reply[reply]
 Oppose From the above investigation comments, it looks like the initial poster of this thread does also have bad behaviors on Commons, so probably we need help from Growth team to seek if there's a way to teach both parties not to conflict eatch other anymore. --Liuxinyu970226 (talk) 07:51, 25 October 2023 (UTC)Reply[reply]
@Martin Urbanec: Perhaps? Liuxinyu970226 (talk) 07:53, 25 October 2023 (UTC)Reply[reply]
 Oppose Fix the tool - A1Cafel is the not the only person to upload duplicates Gbawden (talk) 11:48, 25 October 2023 (UTC)Reply[reply]
 Oppose If you dont like to clean up duplicates then push for the tool to be fixed--Trade (talk) 21:42, 31 October 2023 (UTC)Reply[reply]
 Support. if users had used f2c properly, that is, if they would add the proper categories, it's hard to miss that some files have been uploaded. they'd arrive at the categories to be added to the files while working on f2c, and see that some files are already in there.
it's possible to sometimes miss it, but long term behaviour and cases like uploading "a duplicate of his own upload on the same day just a few hours apart" shows this user is abusing this tool. RZuo (talk) 23:18, 31 October 2023 (UTC)Reply[reply]
@RZuoSo, you're guaranteeing that you won't do such behaviors by the current F2C settings? That said again and again, there are bugs within that tool, which may lead many users to easily make unwanted spam uploads, we need to fix it by pull requests, not fish someone by a bug. Liuxinyu970226 (talk) 00:07, 1 November 2023 (UTC)Reply[reply]
"long term behaviour" (misuse) including but not limited to Commons:Deletion requests/Files in Category:West Virginia government's COVID-19 press conference (2020-08-28) (10 700 photos like https://www.flickr.com/photos/govjustice/albums/72157715970584281 ). RZuo (talk) 07:48, 1 November 2023 (UTC)Reply[reply]
 Support +1 to what RZuo just said. I use this tool a lot. I believe the one or two times I've made this mistake I caught it myself within minutes and was able to correct the situation almost immediately. - Jmabel ! talk 23:47, 31 October 2023 (UTC)Reply[reply]
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Probably, it's the time to let someone to takeover source codes of Flickr2Commons tool?[edit]

As above opposition comments pointed, there are several bugs within that tool, that Magnus, probably read or not, has placed up for several years, even though some may lead Unbreak Now bugs (by our Phabricator's jargon), and by re-looking up that bitbucket, these are either unanswered, or answered by other bitbucket users who may probably not understand how to make pull requests to fix, thus, I'm currently in doubt on whether Magnus is still competent at maintaining its source codes, should there have a new programmers, that has JS professional, to takeover this tool and start a new working-able issue tracker? --Liuxinyu970226 (talk) 00:15, 1 November 2023 (UTC)Reply[reply]

 Support As Nom. Liuxinyu970226 (talk) 00:17, 1 November 2023 (UTC)Reply[reply]
  •  Support The ability to upload duplicates needs to be fixed regardless of the current issues with A1Cafel and I don't see that happening any other way then getting someone else to maintain Flickr2Commons given Magnus' lack of response in multiple issues having to do with it over the years. It's not like dealing with A1Cafel's chronic issues and fixing the tool are mutually exclusive either. --Adamant1 (talk) 00:39, 1 November 2023 (UTC)Reply[reply]
  • And that attitude towards tool developers is why no-one wants to work anywhere near the Wikimedia community. Andy Dingley (talk) 00:43, 1 November 2023 (UTC)Reply[reply]
And what's your solution? --Adamant1 (talk) 00:45, 1 November 2023 (UTC)Reply[reply]
Even in voluntary open source projects there are still an expectation for developers to reply to reports about major bugs within several years Trade (talk) 04:29, 1 November 2023 (UTC)Reply[reply]

{{Information}} This year the Flickr Foundation has adopted the f2c tool. This has been annonced at VP or HD or somewhere. The WMF people can surely give more info on that. --C.Suthorn (@[email protected] - p7.ee/p) (talk) 04:16, 2 November 2023 (UTC)Reply[reply]

@C.Suthorn Please fullfill the description, source and author fields for your templates provided, otherwise your comment will be itself problem. Liuxinyu970226 (talk) 04:40, 3 November 2023 (UTC)Reply[reply]
Oh, sorry , i mismatched informtation template for comment template. C.Suthorn (@[email protected] - p7.ee/p) (talk) 12:11, 3 November 2023 (UTC)Reply[reply]
Template disabled. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:08, 3 November 2023 (UTC)Reply[reply]
"This year the Flickr Foundation has adopted the f2c tool." This is not the case. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:08, 3 November 2023 (UTC)Reply[reply]
  • Support. The Flickr Foundation more or less appears to have decided to rewrite something from scratch. In the meantime, we need someone to maintain the legacy tool and to adapt it to more closely adhere to Commons's policies and guidelines. — Red-tailed hawk (nest) 22:11, 7 November 2023 (UTC)Reply[reply]
  • This isn't really something that needs (or is affected by) this discussion. Someone has to be willing to pick up the tool and maintain it. The source code is all at https://bitbucket.org/magnusmanske/flickr2commons/src/master/, GPLv2'd for anyone to do with it what they'd like. Because of the age and complexity of flickr2commons, finding a new maintainer will be difficult. --AntiCompositeNumber (talk) 02:29, 8 November 2023 (UTC)Reply[reply]

User:Raphael.concorde and Chris A. Hadfield Rocket Factory[edit]

"Chris A Hadfield Rocket Factory" appears to be a prank/hoax - supposed US facility named after living Canadian astronaut on the NASA Michoud Assembly Facility in New Orleans. Zero results for "Hadfield Rocket Factory" from any government websites. There is a facebook group for it [8], which seems part of the hoax, including clues that it is deliberately dubious like references to its "underground shopping center" (New Orleans is known for not having extensive underground structures due to high water table). See also recent en:w:Talk:Michoud Assembly Facility#"Chris Hadfield Rocket_Factory" does not exist. User:Raphael.concorde seems to be major promoter of the hoax on Commons and en:w. Some of the user's Commons uploads have already been deleted (note in particular Commons:Deletion requests/File:Chris Hadfield interview at CAHRF.jpg; clearly a manipulated photoshop (edit:) same photo seen on Flickr at [9]) but a number of others remain. I think this merits serious looking into. I suggest user's uploads without verifiable 3rd party sourcing be deleted (please note that at least 2 Flickr accounts seem to have promoted the hoax as well - "Daniel Molybdenum" (!) [10] and "Daniel Steelman" [11] {...edit, found a third: "John Chryslar" [12]}). Possibly further action is warranted. -- Infrogmation of New Orleans (talk) 22:18, 24 October 2023 (UTC)Reply[reply]

  • Update: User has been indef blocked on en:w by Tamzin [13] - "You have been blocked indefinitely from editing for long-term logged-out sockpuppetry (Special:Contributions/147.197.250.54, Special:Contributions/2A02:C7F:4872:8600:8DE2:2E64:110C:FFFA/64, https://w.wiki/7tZt—including at least one case of backing yourself up in an argument) and hoaxing (Talk:Michoud Assembly Facility § "Chris Hadfield Rocket Factory" does not exist)." I shall now block them here as well. -- Infrogmation of New Orleans (talk) 01:40, 25 October 2023 (UTC)Reply[reply]
I shall now block them here as well. Sounds like a good idea considering the circumstances. --Adamant1 (talk) 05:22, 26 October 2023 (UTC)Reply[reply]
  • Updates: Suspect the 3 Flickr accounts, since blacklisted here, are all socks of the same person as "Raphael.concorde" here. Note on other media goes by "Raphael Cryslar" and other variations. Most or all of the obvious hoaxes have either already been deleted or are currently listed for deletion. However there is more cleanup to do - probably the rest of the uploads from the Flickr accounts should be listed for deletion, even when there is no obvious problem, as unreliable users. Perhaps some users experienced with NASA image uploads can help further looking through some of the Commons user's uploads credited to NASA where links are dead? From context and metadata, I suspect many or most are legitimate NASA images - but in at 2 cases the Commons user created a false dead NASA link for a hoax image. Some that I *suspect* are OK I have not been able to find verifiable NASA links either via archive org nor reverse image searches, but people with more experience with NASA images may know better where to look. -- Infrogmation of New Orleans (talk) 19:54, 5 November 2023 (UTC)Reply[reply]

Joshbaumgartner’s cat renames[edit]

At Commons:Village_pump/Archive/2023/09#Bad category-renaming you can see how the user was called out about renaming categories in a way that’s not only terminologically subpar but also politically prurient. One full month later, Category:Brown women's eyes still exists, populated with more than 300 elements, let alone grandchild cats and other such cousin cats. This user seems to have stopped editing two weeks ago (last edit: 2023.10.17, 22:09:53), but apparently and against his promises in the ducussion, little was done to repair the acknowledged damage in the two weeks before that. -- Tuválkin ✉ ✇ 21:14, 30 October 2023 (UTC)Reply[reply]

    • @Tuvalkin: We can't really sanction someone for failing to edit, so I don't really see any possible useful action to take other than addressing him.
    • @Joshbaumgartner: I would certainly hope that if/when you return to Commons in any substantial, you make it your first order of business to clean up these categories. If I remember correctly, at our last interaction over this, you not only said you would do so, but seemed somewhat offended that I raised even the slightest doubt that you would. - Jmabel ! talk 01:20, 31 October 2023 (UTC)Reply[reply]
Meanwhile, crickets… And we keep unearthing further treasures in this vein, such as "Category:Gray girls' eyes". This is not just a bad case of Engrish (with a side serving of Ufology…): this is also a bad case of chutzpah, as Josh created this ridiculously inane catname by renaming/moving correctly named "Category:Girls with gray eyes"… -- Tuválkin ✉ ✇ 02:17, 5 November 2023 (UTC)Reply[reply]
@Tuvalkin: as you presumably know, this is AN/U. Can you explain what sanction you are seeking against Josh for complete inactivity? I have already addressed a comment to him above. Are you suggesting that we block him for not editing? That seems a bit perverse: "You haven't edited, so we won't let you edit." Or do you have some other administrative action in mind? Yes, these are bad category names. - Jmabel ! talk 06:05, 5 November 2023 (UTC)Reply[reply]
Josh should have his paycheque docked for not clocking in on time. Andy Dingley (talk) 11:12, 5 November 2023 (UTC)Reply[reply]
Alright, so we just gotta move the cats ours self Trade (talk) 12:02, 5 November 2023 (UTC)Reply[reply]
@Andy Dingley , indeed, I hereby surrender my entire year's salary for wasting time on a Mexican beach for the last few weeks instead of diligently fixing categories. But have no fear, I am back on the clock so I can make the big bucks again! Josh (talk) 07:42, 11 November 2023 (UTC)Reply[reply]
Sorry, didn’t mean to be annoying. Yes, this is AN/U, for user problems — not just for sanctions against users. Admins should be aware that this human eye color cat renamings done by Josh is even wider than it would seem and that admin action is needed:
  • Right now to revert said renamings: They all have renamed redirects, so an admin action will make reinstating the status quo much faster and simpler.
  • And futurely, as a caveat against Josh’s often seemingly good ideas which might later on fall apart due to his limitations and stubbornness.
(It’s easy to feel sorry for him over this kind of pile-on, true, but then one comes accoss yet another absurd catname…) -- Tuválkin ✉ ✇ 06:18, 6 November 2023 (UTC)Reply[reply]
Hmm, maybe you could ask Joshbaungartner to move (for instance) Brown adolescent girls' eyes to Category:Brown eyes of adolescent girls?
(How are those category names rendered in other languages, anyway?) Shāntián Tàiláng (talk) 21:40, 9 November 2023 (UTC)Reply[reply]
No need to overcomplicate — just revert this. -- Tuválkin ✉ ✇ 01:13, 10 November 2023 (UTC)Reply[reply]
I would be happy to make such a move (to Category:Brown eyes of adolescent girls), if there were a consensus that was the naming format we want to go to. I'm not saying there isn't, but a lot of the calls seem to be 'return to the status quo' but the 'status quo' was already a mess of inconsistent category names and structure, so that doesn't make much sense as a real consensus. I certainly think there could be a great discussion about what these really should be named, but that's not what's happening here (nor is this the forum for such a discussion). For now, I have fixed most of the categories already, and there are still a few left for me to get to. If there is a future CfD that settles on some consistent naming or structure, I'll help implement that consensus at that time. Josh (talk) 07:57, 11 November 2023 (UTC)Reply[reply]

User Meteum[edit]

Meteum (talk · contributions · Move log · block log · uploads · Abuse filter log)  Reinput the same screen capture of a copyrighted website after being warned. Furthermore, by the name, it seems a paid editor for https://meteum.ai/ Pierre cb (talk) 00:35, 2 November 2023 (UTC)Reply[reply]

✓ Done. User is warned against copyvios and advertising, all contributions deleted. Taivo (talk) 11:13, 5 November 2023 (UTC)Reply[reply]

Repeated insults and bludgeoning by User:Friniate[edit]

I recently nominated some images related to Italy for deletion, which User:Friniate decided to use as a platform to repeatedly insult me, lie about what I was saying, bludgeon the conversations, and otherwise derail them an unconstructive manner.

Just a few examples of the many insults

There's also more then a few examples of them repeatedly bludgeoning discussions, even after I asked them multiple times to drop. The conversation on the Village Pump being one example, but there are plenty more. As well as more examples of insults and patently false comments.

Adamant1 (talk) 19:10, 5 November 2023 (UTC)Reply[reply]

 Comment Your third link is broken. Yann (talk) 19:27, 5 November 2023 (UTC)Reply[reply]
Thanks. It should be fixed now. --Adamant1 (talk) 19:46, 5 November 2023 (UTC)Reply[reply]
The following on your part (User:Adamant1) were not the best either:
and possibly more but I haven't the patience to keep looking.
So, if you really want, I can give you both a topic ban and/or an interaction ban, but I don't see much else I can appropriately do here. I'd rather not do either. I'd rather you both try to focus on content, keep the personal issues out of the matter, and (I know this is probably too much to hope for) each make a clear statement of your case and let the other make a clear statement of their case, and after that confine yourself to good-faith questions about what the other has said/meant, rather than (1) insult each other, (2) impute motivations, and (3) both keep trying to have the last word, while often repeating yourself. - Jmabel ! talk 19:55, 5 November 2023 (UTC)Reply[reply]
I was going to provide a thorough answer with links and all, but I'm willing to let it down in order not to escalate further. I object an interaction ban since Adamant would clearly profit from it, not allowing me to comment on the multiple DRs that he is opening. Friniate (talk) 19:58, 5 November 2023 (UTC)Reply[reply]
@Jmabel: I said those things multiple days into him lying, insulting me, and derailing my DRs. In no way is me saying he was repeatedly derail the discussion, which was exactly what he was doing, comparable to him repeatedly lying about and insulting me for multiple weeks. You can read look at this back and forth from 11 September. I wasn't even the one who opened it. Nor had I interacted with Friniate or opened any DRs related to Italy at that point as far as I'm aware and he started calling me a troll right out of the gate. But sure, it's totally equal and I should be topic banned because I said he was hell bent on debating strawman 2 months into him bullying me. Whatever. The fact is that Friniate's been coming after me for months now and I'm not the one instigating things here. It's totally ridiculous to act like our behavior is at all equal or that I should be sanctioned just because I got a little defense months into it. --Adamant1 (talk) 20:07, 5 November 2023 (UTC)Reply[reply]
  •  Comment I think the behaviour of Adamant1 falls under the Commons:Disruptive editing guideline, more precisely the point 5 of the examples section: Creating multiple deletion requests. He is clearly abusing this privilege, and he's not new to this. He has already been blocked in Commons two times (first and second), both times regarding discussions about requests of deletions. And he was blocked precisely for trolling. I see complaints about his behaviour appear regularly and quite often on this noticeboard (1, 2, 3, 4, 5, 6, 7). He started since many weeks to target pictures from WLM Italy, causing a lot of damage to the website contents, damage that spread to sister projects. He do not have any knowledge of Italian law, and of Italian language either, but claims tha Wikimedia Italia, an official Chapter, contributed to upload tens of thousands of images in copyright infringement. Now I do not want to discuss the topic here, but if you think a Wikimedia Chapter is doing this massive law violation, the right way to address it is through general discussion, not opening deletion request about thousands of single pictures. Pictures which already had been authorized by copyright owners through WLM, with dozen of people working on those permissions. I can understand people losing their temper reacting to this massively disruption behaviour and trolling way of discussing. Relevant to this report is also the fact that Adamant1 was repeatedly blocked also on English Wikipedia, for disruptive editing and, how ironic: "badgering and bludgeoning". And no surprise, again, concerning deletion requests. Actually Adamant1 is indefinitely topic banned from all deletion discussions on English Wikipedia. This record is quite impressive, and as an administration myself on another Wikimedia project, I have to say I'm quite surprised such a user is left to continue freely with this behaviour. I think we need to protect Commons file from him, so a block or a topic ban it could be appropriate in my opinion. --Phyrexian ɸ 12:29, 6 November 2023 (UTC)Reply[reply]
  •  Comment, agree with Phyrexian above, this guy is here just to play at “Deletion discussion: The Game”. Once banned from deletion discussions on en.wikipedia he basically semi-retired from there and moved to play the same game here. He's currently doing a mass-deletion after another, nominating whole categories without checking the items in them (otherwise I should assume he considers pics like File:Bangkok Panorama (2287990977).jpg not in scope, which would be even worse), on the grounds that "I'm just never sure where the line is and some clearly aren't. So I thought it would be easier to nominate them as a batch". And, based on the links above, there is not a single case where he accepts a "keep" vote without bludgeoning the discussion. It's the same pattern which led to his en.wikipedia ban, and, while I wish everyone the best, I suspect at some point it will ends the same way. --Cavarrone (talk) 16:03, 8 November 2023 (UTC)Reply[reply]

User Tardjuli[edit]

Tardjuli (talk · contributions · Move log · block log · uploads · Abuse filter log)  uploads historical photos of Haiti presidents and other dignitaries, claiming they are his own work. The copyright is therefore doubtful and I signaled some already. Furthermore, some photos claiming to be of the same named person seem to be from different ones (e.g. File:President Joseph Lamothe Haiti.jpg and File:Joseph Lamothe President Haiti.png). Could and administrator checked those images and decide if they have to be deleted. Pierre cb (talk) 05:09, 6 November 2023 (UTC)Reply[reply]

With the exception of File:Portrait équestre de l'empereur d'Haïti, Jacques Dessalines.png and File:Jerry Tardieu, député de la République.png, all of their uploads appear to be too old for copyright to still apply. In Haiti that's 60 years after the death of the creator. The issue is that the uploader hasn't provided an actual source for most of these. The Squirrel Conspiracy (talk) 06:05, 6 November 2023 (UTC)Reply[reply]

User:SHB2000[edit]

The following discussion is archived. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
Please colleagues, this thread is closed as  Not done. Thanks --A.Savin 13:36, 9 November 2023 (UTC)Reply[reply]

Dear admins. I have a grievance against User:SHB2000 and their persistent and repetitive harassment on the wiki. After considering this for several days, I believe the moment is finally appropriate to end my silence. This user has consistently opposed me out of all three (123) of my rfrs; why me? You have no idea how unbearable and unwelcome it is; they have made me very angry, and as a result, I hardly update Commons anymore—I'm miserable and sad right now. In addition, I submitted a request for AWB on the Simple English Wikipedia. Since they don't even edit that wiki, they went there to inform the administrators of a recent RFR failure. Since then, they have been monitoring my edits in the hopes of discovering more ways to disqualify me [14]. For the entirety of my Wiki career, they are the only user who has done this to me, and I am devastated and angry about it. No, it highlights your extreme carelessness when using AWB was the response they gave me for an incorrect modification I made on the English Wikivoyage, which they properly restored. To begin with, I was unaware of the rule's existence, and if I had, I would have followed it. They also accused me of "background behavior". They went on to claim that because of the one modification I made incorrectly, all of my edits were painful, which is completely false and shows poor judgment (see Commons:Requests for rights/Denied/AutoWikiBrowser access/2023#20 upper 2). I was upset by those statements at first, and then I became angry. I'm not sure who grants them the authority to treat people in this manner. In addition, they disapproved of my proposal on FPC Talk simply because I proposed it and I should be disapproved of and silenced at all costs. Finally, the majority of the nominations I make on FPC, they almost always go against it. I rest my case. 20 upper 14:00, 6 November 2023 (UTC)Reply[reply]

Your lack of ability to follow even the very simple protocol of posting on this page kind of shows that SHB2000 was indeed correct in not trusting you with any additional permissions on Wikimedia Commons. TommyG (talk) 16:23, 6 November 2023 (UTC)Reply[reply]
@TommyG: What simple protocol? 20 upper 04:51, 7 November 2023 (UTC)Reply[reply]
Leaving me a message on my talk page notifying me of this discussion. I am only aware of it because of the ping. --SHB2000 (talk) 08:14, 7 November 2023 (UTC)Reply[reply]
@SHB2000: A ping is a perfectly good way to notify someone of something. I would certainly presume that any reasonably active user gets their pings. - Jmabel ! talk 15:39, 7 November 2023 (UTC)Reply[reply]
In the notes on top of the page: Notify the user(s) concerned via their user talk page(s). {{subst:Discussion-notice|noticeboard=COM:AN/U|thread=|reason=}} is available for this. A09 (talk) 17:44, 7 November 2023 (UTC)Reply[reply]
Fair enough – I only mentioned so because of the note at the top of this page, mentioned by A09. --SHB2000 (talk) 20:27, 7 November 2023 (UTC)Reply[reply]
  •  Oppose Any kind of action. The cross Wiki stuff is kind of silly, but you've been acting super demanding about getting the patroller right here on Commons and SHB2000 isn't the only one who thinks you shouldn't receive it. I was actually going to oppose the request myself. So I don't think there's anything to deal with or see here in that regard. Although there might be on another Wiki, but that's kind of out of Commons' remit. I will say though that you clearly need to learn some patience and how to not be so demanding. --Adamant1 (talk) 17:00, 6 November 2023 (UTC)Reply[reply]
@Adamant1: Why were you going to oppose? And what do you mean by I will say though that you clearly need to learn some patience and how to not be so demanding? Have I not waited 30+ days? And how am I being demanding? Please provide evidence before making such accusations. 20 upper 04:59, 7 November 2023 (UTC)Reply[reply]
Sorry, but in this sort of matter, 30 days is pretty much nothing. - Jmabel ! talk 15:42, 7 November 2023 (UTC)Reply[reply]
  •  Oppose Why am I not surprised with this ANU request the slightest? I don't think I need to defend myself for simply opposing your requests when you cannot be trusted right now with those perms. --SHB2000 (talk) 20:41, 6 November 2023 (UTC)Reply[reply]
    SHB, regarding your RFR behavior, can you please keep your comments to yourself. Please don't interfere in what doesn't concern you. What is so hard about leaving me alone? This is wiki hounding, and I won't take your behavior anymore. Why can't I be trusted with those permissions anyway? Can somebody please tell me what I did wrong. SHB, I got one last question for you and I need you to answer : Why are you targeting me? 20 upper 04:47, 7 November 2023 (UTC)Reply[reply]
    1. Anyone is allowed to comment in RFR; asking me to "leave [you] alone" on RFRs is a way to rack up one fewer oppose vote and does not constitute as wikihounding.
    2. For your second question, I am not targeting you, and never had the intention to, so I'm not sure what you're on about when you say "I'm not sure who grants them the authority to treat people in this manner. In addition, they disapproved of my proposal on FPC Talk simply because I proposed it and I should be disapproved of and silenced at all costs.". --SHB2000 (talk) 08:12, 7 November 2023 (UTC)Reply[reply]
  •  Oppose Telling us that your mental health is suffering because this community doesn't trust you with advanced permissions isn't the argument you think it is; you are in fact confirming our suspicion that you're badge collecting and can't be trusted with said permissions. Your continued failure to read and follow instructions also shows that you can't be trusted with said permissions. SHB2000 is not the common thread between all of your failed applications, you are. No action is needed here, at least against SHB2000. The Squirrel Conspiracy (talk) 05:23, 7 November 2023 (UTC)Reply[reply]
    @The Squirrel Conspiracy: What is badge collecting? And what instructions are you talking about? If there is anything I did to make you doubt my ability to use these permissions, I apologize and assure you that I will do all in my power to win your trust back. All I want is information to be clear and transparent. 20 upper 06:15, 7 November 2023 (UTC)Reply[reply]
    w:WP:HATCOLLECT is the relevant essay, if you want more info about what badge collecting is. --SHB2000 (talk) 08:13, 7 November 2023 (UTC)Reply[reply]
    Sorry for the offense SHB2000, I just want you to know how your behavior is affecting me, and I want us to understand each other and come up with a consensus. You see, I'm not here to collect hats; when I ask for rights, it's because I actually need them. According to the essay, there should be enough proof before accusing someone else of collecting hats. First of all, since I don't have any rights on any wiki, it seems reasonable that I would wish to acquire any when I need them for upkeep or, in this case, patroller permissions to reduce the backlog. Patrolling pages has always piqued my curiosity, and I've even grown rather passionate about it. I'm not lying; I'm telling the truth. Recently, the Squirrel Conspiracy has acted in a very unprofessional manner. They were really impolite to me, calling me a hat collector and said I had severe issues with maturity—a very nasty statement. Their behavior leaves me unsure of what to think. The thing that most irritates me is that, aside from the baseless charges of hat-collection, they don't seem to have any valid or reasonable explanation for refusing my request. 20 upper 09:33, 7 November 2023 (UTC)Reply[reply]
    Well, if multiple people are complaining about you, maybe it's not us [myself, The Squirrel Conspiracy, TommyG and Adamant1] who are the problem. SHB2000 (talk) 11:05, 7 November 2023 (UTC)Reply[reply]
    Then who is? 20 upper 11:09, 7 November 2023 (UTC)Reply[reply]
    You. --SHB2000 (talk) 07:21, 8 November 2023 (UTC)Reply[reply]
    Didn't do nothin wrong, but receiving so much hate for something I'm not. It's giving "You'll never receive any rights no matter how well behaved you are or how good your reasoning is, because you're a problem and nothing more than a hat-collector". Where's the evidence...that's right, there's none. Plus, Squirrel Conspiracy is so disrespectful, & u gon ignore that. I'm asking what I did wrong, but u guys keep runnin away from that question. I didn't follow the rules once, but u guys keep saying the word "repetitive", when it only occurred once, like what's that for?
    TL;DR — Why can't I receive permissions if I did nothin wrong? 20 upper 11:42, 7 November 2023 (UTC)Reply[reply]
    Permissions are not anyones rights - the community has to trust you to give them. Trust needs time to grow. If someone distrusts you, insisting that you should be given that trust will not bring the trust around. Try to step back for a bit and really think about what you could be doing to build trust. If you want to discuss this in more detail, feel free to message me via Wikimail. Kritzolina (talk) 09:47, 9 November 2023 (UTC)Reply[reply]

 Not done. There is nothing to be done about it. There is no "legal claim" or sth to receive a flag after a certain number of edits, after months of certain activity etc.pp... 20 upper, if some people continue to vote against you, harassment is seldom the reason. Reconsidering your own behaviour and waiting a while before re-nomination is probably the best way to go. --A.Savin 12:58, 7 November 2023 (UTC)Reply[reply]

Alright, as I would never want to interact with such persons, I kindly ask for at least an interaction ban between myself and them. This user is merely a waste of my time and energy; I wish to edit Wikimedia Commons in a calm manner. Many thanks. 20 upper 08:13, 9 November 2023 (UTC)Reply[reply]
I would  strongly oppose an IBAN – once again, it comes out as a snarky tactic to prevent someone who largely disagrees with you from commenting. --SHB2000 (talk) 11:36, 9 November 2023 (UTC)Reply[reply]
Your viewpoint is irrelevant in this case, in my opinion. I want you to quit communicating with me; this is not a tactic at all. I'm rejecting you. I genuinely don't understand your desire to communicate with someone who has explicitly rejected you. You are not entitled to interact with anyone, and interaction is never forced. You are not required to reply to this comment; it is for you to view. I don't like to argue, so I think it's best argumentative people like you stay away from me. I'm no longer interested in RFRs at this point; I just want a peace of mind. 20 upper 13:15, 9 November 2023 (UTC)Reply[reply]
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.


User:Prel1h[edit]

Prel1h (talk · contributions · Move log · block log · uploads · Abuse filter log)  is adding some odd strings of letters to various files. Why is he doing this? --トトト (talk) 17:16, 6 November 2023 (UTC)Reply[reply]

✓ Done Blocked for a week, all reverted. I wonder if this isn't a bug? Other edits need checking. Yann (talk) 18:15, 6 November 2023 (UTC)Reply[reply]

User Bergamota7826[edit]

Bergamota7826 (talk · contributions · Move log · block log · uploads · Abuse filter log)  uploads copyrighted website (https://b2b.meteum.ai/api). He is doing the same uploads as warned Meteum (talk · contributions · Move log · block log · uploads · Abuse filter log)  and therefore a likely sockpuppet. Both should be blocked indefinitely. Pierre cb (talk) 04:37, 8 November 2023 (UTC)Reply[reply]

✓ Done Both blocked as a precaution - they can request an unblock and explain their actions Gbawden (talk) 07:07, 8 November 2023 (UTC)Reply[reply]

User:Shrimpdick[edit]

As much as it pains me to report such a great username this is clearly a violation on account name rules as well as a pure COM:PORN user. If they want to contribute productively they can create a more appropriately named account. Dronebogus (talk) 12:07, 9 November 2023 (UTC)Reply[reply]

✓ Done Blocked indef Gbawden (talk) 12:45, 9 November 2023 (UTC)Reply[reply]

User:Pamulab[edit]

In January he received a warning on his talk page User_talk:Pamulab#You_may_be_blocked_soon, but he still uploaded photos that violate copyright. Special:ListFiles/Pamulab. Many of the photos have fake licenses, even though in many cases the copyright notice is clearly mentioned on the websites. 37.109.147.39 19:29, 9 November 2023 (UTC)Reply[reply]

✓ Done Blocked for a week. All files need checking. Yann (talk) 19:56, 9 November 2023 (UTC)Reply[reply]

User:Nordic9[edit]

Looks to be a Category:Sockpuppets of Oatsandcream, uploading blatant Beatles copyvios and possible hoax images of lost 1920s films again, same kind of material as earlier sock Sir Robert PerPaper (talk · contribs). SPI also opened on enwiki at en:Wikipedia:Sockpuppet_investigations/Oatsandcream. Belbury (talk) 19:01, 10 November 2023 (UTC)Reply[reply]

User:Noahbecksleftab[edit]

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

Persistently uploading of copyright COM:FU materials. — Paper9oll (🔔 • 📝) 06:59, 11 November 2023 (UTC)Reply[reply]

Warning given per COM:BP Gbawden (talk) 07:32, 11 November 2023 (UTC)Reply[reply]
✓ Done Marking as done because I don't remember if this is one of the channels where the archive bot looks for checkmarks or not. The Squirrel Conspiracy (talk) 09:24, 11 November 2023 (UTC)Reply[reply]

File:1930 Ford Model-A 2022-09-03.jpg[edit]

Hello,

because of personality-topics (numberplate) I ask, if you can remove the first version this file. Thank you very much. Regards Wikisympathisant (talk) 09:09, 11 November 2023 (UTC)Reply[reply]

✓ Done Wikisympathisant - I've also uploaded a version with the license plate pixelated out instead of being a fake number. If you prefer your solution you can revert my upload. The Squirrel Conspiracy (talk) 09:23, 11 November 2023 (UTC)Reply[reply]
thank you for your fast realization. I prefer the plate with the numbers, but really safe is your version. What do you think? KR Wikisympathisant (talk) 09:28, 11 November 2023 (UTC)Reply[reply]
Wikisympathisant I don't know how plates and plate laws work where you are. Is the fake plate a valid number (I know you just changed some things to 8s) that could belong to someone else? Does that actually matter, as long as it's not another Model-A? The Squirrel Conspiracy (talk) 09:34, 11 November 2023 (UTC)Reply[reply]
I had a discussion in German Wikipedia. Owners of such cars are afraid the pict is seen and people can ask for example at a insurance or authority and find such car and steal it. I can say, this idea is still strange for me, but it was told. In this case car may be very rare and if it appear in the market it would be easy give it back to the correct owner. Regards Wikisympathisant (talk) 09:39, 11 November 2023 (UTC)Reply[reply]

User Gaalkhalifah[edit]

Gaalkhalifah (talk · contributions · Move log · block log · uploads · Abuse filter log)  repeats uploading images of a Saudi scientific from copyrighted site. By the user name, it seems that it is self promotion. Pierre cb (talk) 12:46, 11 November 2023 (UTC)Reply[reply]

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Administrators%27_noticeboard/User_problems&oldid=820704160"