This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
No idea why this is in "Proposals" rather than "Copyright", but as I understand it UPI images were distributed widely to newspapers etc., which itself constituted publication. At that point I would think copyright was lost, and it certainly could not be regained if some (or even all) of those newspapers chose to add a copyright notice when publishing. Alternatively, if I'm wrong about that: if any significant number of papers routinely published without copyright notice and were not enjoined, that would also probably place that published content in the public domain. - Jmabel ! talk04:33, 10 September 2024 (UTC)
@Clindberg: do you have any thoughts on this before someone creates a template? In particular, do you think my reasoning above is flawed? Anyone else you think we should bring in for their opinion? - Jmabel ! talk15:49, 11 September 2024 (UTC)
The reasoning there is somewhat correct, in that virtually all photos published by UPI before 1989 are public domain for lack of copyright notice. But the key word is published. Getty acquired the UPI archive, which doubtless includes many photos that had never been published before. So we can't make a blanket statement that photos from the UPI archive are public domain. Any photo on Commons should include some evidence that the specific photo was published without copyright notice, to satisfy COM:PRP. If there were to be any template for photos that don't have such evidence, it should be a cautionary disclaimer template to warn potential re-users that the photo's PD status hasn't really been established. (That's just my opinion; the Commons community would probably lean more towards deletion rather than disclaimers.) Toohool (talk) 17:27, 14 September 2024 (UTC)
Strickt overwriting rule for adding or removing transparency
With the darkmode being added to Wikipedia the fact if a graphic has an white background or a transparent background is getting very important. I think we can expect many users overwriting or requesting to overwrite files with a transparent background to add an white background as the graphic is not readable with dark mode without a background added though other ways. To avoid trouble on this I propose the following clarification to the Commons:Overwriting existing files guideline:
Adding or removing a transparent background is always considered a substantial change requiring upload as a new file.
Oppose I support the spirit of the proposal but I think that changing an image to remove the white background should not require upload as a new file in many cases. I would support it if it was only about removing transparent backgrounds. I think transparent backgrounds are better for many reasons, mainly one can readily use them in other images using the existing background or giving it the background one wishes it to have. It can be a real hassle or not worth it to add some image with a white background into an image like an infographic with another background. It's similar to why SVG is preferred over jpg files. Concerning dark mode, I think technical changes are needed so that transparent background images are readable on it. Is there any issue for that? One shouldn't have to resort to changing the background to be able to view images with transparent background in dark mode – it could set a greyish white as the background or inverse the font color if dark mode is enabled. Prototyperspective (talk) 11:17, 15 September 2024 (UTC)
If you make the background of a graphic transparent every page where the graphic is used needs to be adapted to make the file readable in dark mode. This is possible but if someone overwrites a file no one on a Wiki where the file is used will get notified. They have to switch to dark mode and look on the page to see that something changed. With upload as new file and then using universal replace there is an edit on the page that notifies the users that something changed. GPSLeo (talk) 11:51, 15 September 2024 (UTC)
I think the software needs to be so that pages don't need to be adapted. However, maybe it's only made so that people can specify whether the background is transparent and the text black manually such as specifying it where it's used e.g. [[File:..|thumb|transparent]] so that's a good point – I would support if this was changed so that one can upload as a new version with transparent background if the file is either not used in any Wikimedia project or one adjusts all of these uses to be dark mode compatible. By the way one can check for used transparent background images here (may be dysfunctional). Prototyperspective (talk) 12:09, 15 September 2024 (UTC)
Comment presumably if the original was created and uploaded by a still-active Commons user, they can consent to a change, no?
Support. If the readability of transparent images on a dark background is an issue, this should be addressed at a technical level, e.g. through a MediaWiki feature request to allow images to be displayed with a solid background (e.g. [[File:Transparent image.png|thumb|background=white]]). Replacing transparent images to work around the lack of this feature is not appropriate. Omphalographer (talk) 21:29, 19 September 2024 (UTC)
Do not add a white background to this symbol. Make a new file with a different foreground.
Oppose The background should not be a part of the illustration. For example, if a symbol happens to have a white background, then it should be OK to overwrite the image with a transparent background. I do not see that as a substantial change. If a flag is supposed to have a white background but happens to have a transparent one, then it should be OK to overwrite the file with a white background. That would be a correction rather than a substantial change. If a file's black marks disappear into the background in dark mode, that is not a reason to rewrite a transparent background to white. In that situation, there should be a new file, but that new file should not have a white background (the background is not part of the image); instead it should change the foreground color to contrast with the dark mode. Glrx (talk) 03:28, 20 September 2024 (UTC)
Not sure I see the logic in allowing one way, but not the other. Either way can break a particular current usage, and leaves no choice for other people to go back to the one they were using. Carl Lindberg (talk) 03:41, 20 September 2024 (UTC)
Oppose - the general idea is okay and reasonable, but I'm unhappy with the word "always", when the main concern is that a black-on-transparent graphic becomes invisible in dark mode. But let's suppose a typical yellow/orange emoji-graphic on white background. Switching the white to a transparent background would be better to support both modes, to no detriment for the readers. Ergo, this is a case of "it depends". A lot of graphics may even have to be tweaked to support dark mode as well; so allowing adding/removing backgrounds would be beneficial. The rule should be that adding/removing backgrounds in graphics is a substantial change that needs to be carefully done with both bright and dark modes in mind. --Enyavar (talk) 04:24, 20 September 2024 (UTC)
Support I think. If recently uploaded, it's fine to change, particularly by the uploader. But in general, adding or removing a transparent background always has the potential to break existing usages, and we'd prefer both options be available. Even an emoji which would work in light or dark mode may not work if it happened to be on a yellowish background for some reason (with a white background). It may make sense to have a default background color in image boxes, which remains light even in dark mode -- for non-transparent images it would make no difference, but a default of a lighter color (unless changed intentionally) probably would preserve most image usages in dark mode just fine. Carl Lindberg (talk) 05:08, 20 September 2024 (UTC)
Here I'm proposing a way to sometimes specify to which parts of a video a category applies. Often categories only apply for a specific part of the video and it's just dumped into a category of files that are only about that or have that category as a main characteristic / subject throughout the video. For example a video containing a time-lapse clip may be in Category:Time-lapse videos even when 90% of it aren't in time-lapse. This can cause issues and there currently is no way to specify the metadata of which parts a category refers to.
This contains a high-quality clip of a person using a smartphone normal for the early 2010s
This belongs into many subcats of Category:Drone videos by country even if it's appropriate to keep in the parent cat or in a cat like "Drone videos from many country"
This contains videos showing explanatory demonstrations of many different exercises (e.g. Category:Bench press)
Here @Kai Burghardt: added cat Videos from Rothenburg ob der Tauber with comment <!-- at 1:51 -->
This could be implemented like sortkeys are implemented (which is [[Category:CatName|sortkey]]).
For example, one could specify which parts a category refers to like so (these are details that can be worked out): [[Category:Time-lapse videos|1:51]] or (better) [[Category:Time-lapse videos|1:51-2:23]]. One could also specify multiple segments e.g. like so: [[Category:Time-lapse videos|1:51-2:23,3:04-5:01]].
Files can also be sorted using the sortkeys but it's barely used and there's the risk people sort files in unexpected ways so people can't find stuff when looking through a cat alphabetically due to which replacing the sortkey functionality is something worth considering. However, one could also simply use another syntax instead of the well-known pipe for the segment-qualifier, e.g. [[Category:Time-lapse videos/1:51-2:23]] and in the very rare case that a sortkey is specified as well e.g. [[Category:Time-lapse videos/1:51-2:23|sortkey]].
Then of course there's multiple things that could be done with this valuable new data. I suggest that something is displayed next to these categories like a small timestamp and when clicking on it, it jumps to the video section of that timestamp using the neat temporal media fragment functionality (only instead of a link with ?start=1:12:30 it would need to be #start=1:12:30 so it doesn't reload the page but only jumps to that part of the video which is useful and needed and already possible on YouTube with its video chapter links).
One could also make the files show differently in the respective cat or get subcategorized automatically into e.g. 'Videos containing xyz' cats like "Videos containing time-lapse videos" so one can always see full time-lapse videos and videos only containing such separately or distinguish between these. Not right from start but at a later point one could maybe even make it so that video starts at the specified timestamp when opening the video from that category.
Note that people can also extract relevant parts into a new file, such as a clip or animated GIF about a particular fitness exercise for the category about that exercise from a long video about many exercises so setting the cats even when a file is not fully about something is usually useful. At a current discussion about Photographs of flags there was discussion about photographs where flags are only a minor subject. Trying to keep it short I think would solve multiple problems, be very useful, and substantially increase the data quality of WMC. What do you think? Prototyperspective (talk) 18:12, 30 September 2024 (UTC)
Interesting but even if that was the case, this is about adding this functionality to the categories. So if it was a widely used structured data property then this proposal would be about copying it from the structured data to the categories and adding this functionality at the category level in addition to the SD functionality. However, in contrast to categories (sortkey-like specifications thereof) I don't think the SD for that will ever be widely used (read, maintained, or written). Prototyperspective (talk) 17:41, 6 October 2024 (UTC)
Yes; I know that your point is "about adding this functionality to the categories". My point is that a tool to record the relevant metadata already exists, so investing the effort into creating a duplicate tool - especially given the limited developer resources we have - is probably redundant. Your suggestion that SD "will [n]ever be widely used" is bizarre. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits18:55, 6 October 2024 (UTC)
It's not duplicate. For example, you can't see see items in a category which only partially include the subject of the category.
SD are barely used and most users don't use them. Vandalized SD stays as is even for some of the most popular media files included in several large WP article because barely anybody watches changes to them or looks them up. Moreover, many files have false SD and nearly/virtually all of them have not nearly as much in metadata in the file as there is in the categories which are well-maintained and easily navigable and that even for new users.
The suggestion that people could instead go to the structured data enter some depicts statement and then set some qualifier for it where nearly all contributors never set any qualifier for some structured data property for a media file is bizarre in the sense of ignoring reality and wishful thinking. Even if people (ie readers and contributors) knew about structured data and actually used it (and I have enough items on my Watchlist to know contributors don't), then they still wouldn't know about or use the "time index" qualifier. I hypothesize that there's less than 40 files where this qualifier has been used out of the many millions of files on Commons and that for these items less than 5% of viewers of each file (not even considering the category) have actually benefited in any way (e.g. read the qualifier or have come across the file in contextualized way) from that SD being set.
If you think about this in terms of technical hypothetical possibility then I suggest you reconsider it in terms of this being about making functionality useful and used.
I've been thinking about this for a while now and can't for the life of me figure out how it would actually be implemented. Except for maybe creating subcategories of main sujects that have time stamps in their names. Like "videos of horses (1 minute into video)" or something but that seems less then optimal to say the least. I'm really strapped as to how else it could done besides through structured data though, which I agree isn't great at this point. But realistically how else would you do it aside from creating specific categories containing time stamps? --Adamant1 (talk) 21:36, 6 October 2024 (UTC)
how it would actually be implemented ... how else it could done besides through structured data though Well what do you think of what is proposed here? I've been thinking about this for a while as well.
how else would you do it aside from creating specific categories containing time stamps? if you're talking about specifically how it could be made available to the end user, then please see: there's multiple things that could be done with this valuable new data. I suggest that something is displayed next to these categories like a small timestamp and when clicking on it, it jumps to the video section of that timestamp using the neat temporal media fragment functionality (only instead of a link with ?start=1:12:30 it would need to be #start=1:12:30 so it doesn't reload the page but only jumps to that part of the video which is useful and needed and already possible on YouTube with its video chapter links). One could also make the files show differently in the respective cat or get subcategorized automatically into e.g. 'Videos containing xyz' cats like "Videos containing time-lapse videos".
I mean, you mentioned using sortkey with times. I'm not really clear on how it would work or fix the problem though. I don't think the idea of putting small timestamp would work either. I assume whatever solution you want to go with would have to be something that can actually be done with the current software. Otherwise your just proposing theoretical solutions that have little, if any, chance of being implemented. Not to say that's anything with developers, but from what I've seen the back end software running this seems to be pretty limited and there aren't even people maintaining exiting third party things like the crop tool at this point. So it seems like the only semi-workable options are doing it through structured data or categories. --Adamant1 (talk) 00:03, 7 October 2024 (UTC)
I am proposing a technical feature – a change to the software, apparently you misunderstood what this thread is about. Yes, there's too few developers and many of them work on niche products or subjects and I made a list of suggestions on how to change that which I think is the responsibility of the WMF and 'step 1' imo. Volunteer devs may also pick it up and there's also people who currently develop gadgets – this page is open for everybody to read. Here I made the case for it and described the technical concepts, sadly the chances of it getting implemented any time soon may be low nevertheless. Prototyperspective (talk) 23:04, 7 October 2024 (UTC)
I understand perfectly fine. I just don't think it can or will be done through a technical feature by changing the software. That's all. Although I do think it's possible to implement something similar with exiting features, but you clearly don't agree and that's fine. At the end of the day there isn't one single best way to fix things and probably a lot of it can or should be done through incremental steps on our end while we wait for the developers to change the software.
Either that or you could just say screw it and write a long winded essay about something that has almost zero chance of ever happening, at least not any time soon. Whichever. It's your choice since it's your idea to begin with. I'm just saying I think there's other ways to go about it besides a backend change to the software. Why don't you a open Phabricator ticket for this and see what kind of reception it gets though? Who knows maybe it would be a quick, easy thing to implement. --Adamant1 (talk) 01:17, 8 October 2024 (UTC)
Yes exactly, maybe it could something that is relatively quick and easy to implement (e.g. since the sortkey functionality is already there). I'll open a phabricator issue at some point but thought it would be a good idea to discuss these here and explain why it would be useful and how I think it could work – for example maybe somebody had an idea on technicalities of how the added metadata could be made available to the user such as e.g. adding a tooltip saying partial relevance to items to the respective file-titles in the respective category. This is not an essay but a technical specification of an idea/proposal with info on how it could be implemented as well as why it would be useful. Prototyperspective (talk) 08:54, 8 October 2024 (UTC)
@Prototyperspective: Fair enough. I didn't think about it working with the exiting sortkey functionality. And I'm not trying to say there's anything wrong with discussing it or laying out the details of how it would work. It's easy to lose people in the details though and I suspect the length of your original message is one of the reasons it's gotten so few responses. Which is to bad, because it's a good idea in general even if I disagree with some parts of it. I probably could have just worded the message better. I am interested to see if it's something the developers would want, or be able, to implement though. --Adamant1 (talk) 22:35, 8 October 2024 (UTC)
@Prototyperspective: This is a use case for structured data. Categories are the wrong tool for that. At the moment, however, COM:DEPICTS documents a conservative, restrained tagging policy. When subtitling I recognized the street scene and I’ve added a categoryjust not to lose that piece of information, not because categories were a particularly good tool for that. (Also I did not know which qualifier the depicts statement to pair with.) Andy’s tagging approach seems legit, though. ‑‑ Kays (T | C) 07:35, 8 October 2024 (UTC)
This is a use case for categories. Structured data are the wrong tool for that. I didn't say you added any category or find them to be a good tool. That you used them despite thinking without giving any reasons that SD is a better tool is just a perfect illustration that they're better. Prototyperspective (talk) 08:44, 8 October 2024 (UTC)
You have expressed the use-case as "a way to sometimes specify to which parts of a video a category applies". That is bad practice, because it focusses on a particular technology, rather than what the user wants to achieve. The correct way to express the underlying use-case would be "a way to specify which parts of a video show a particular subject". Categories are not the right way to do that, and SDC is. But you don't like SDC, so we have this waste of electrons and screen space instead of a rational discussion to progress the matter. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits11:37, 8 October 2024 (UTC)
Categories are the right way to do that and you have given zero reason why that wouldn't be the case. I think SDC are largely redundant due to categories and a huge time sink that is not well maintained and misses most data that is already in the categories. A rational discussion would be good – that I think consists of making points and addressing points. I don't think you have done so here. The explanation of how it could theoretically but not in practice be achieved to a small extent (e.g. not seen and used by readers) using SDC was constructive but that's about it. Prototyperspective (talk) 12:40, 8 October 2024 (UTC)
It's kind off topic, but at least IMO they aren't mutually exclusive and will probably coexist with each other for a while until structured data is more ubiquitous and user friendly. At the end of the day something like this probably can and should be done with both though. --Adamant1 (talk) 22:39, 8 October 2024 (UTC)
It seems to me like this should be possible to model with structured data more easily than with categories, because structured data allows qualifiers. - Jmabel ! talk16:11, 12 October 2024 (UTC)
That is not the case because you apply a narrow shortsighted view that is only about the technical theoretical possibility of adding this data while this concept is about something broader that includes actual use, ease of use, and availability/accessibility/usefulness to real-world users. Prototyperspective (talk) 16:14, 12 October 2024 (UTC)
I gather that you can make a template that draws on the structured data. But saying that structured data in general is not a reasonable way to model anything? I think that train long since left the station. There is a lot I don't like about how they did it, but it's part of Commons now. - Jmabel ! talk16:27, 12 October 2024 (UTC)
That would be more constructive things to add to this thread and then we'd be discussing the actual subject at hand: 1. why would creating such a template for SD be easier to implement by simply extending the sortkey functionality of categories to enable specifying which part(s) a cat apply to? 2. That doesn't change that categories with sortkeys are easier and quicker to use as well as used far more.
And I did not say that. However, that something is a technical part of Commons doesn't mean it's not largely redundant while being a time-sink or used a lot. Nevertheless, this was never meant to be a discussion about SD and don't know why it was made so so I don't intend to discuss SD here insofar as it doesn't directly relate to the proposed feature. Prototyperspective (talk) 16:34, 12 October 2024 (UTC)
Not that it solves this more general question, but I think it's useful to add thumbnails in the file description (using "thumbtime=") to highlight segments of a video, especially the ones that are categorized. ∞∞ Enhancing999 (talk) 12:53, 13 October 2024 (UTC)
This would be an interesting thing to consider in the two requests for enabling video chapters: in V2C, in WMC (audio & video). I've never seen thumbtime used in the file description – how would this look like? It may also be useful to make it possible to specify a thumbtime for a video that gets displayed whenever it is shown (including on cat pages and by default when no thumbtime is specified on WP). Prototyperspective (talk) 19:51, 13 October 2024 (UTC)
Currently we are only slightly backlogged, with 1087 DRs that are >1 month old as of speaking and who-knows-how-many CFDs. We also don't have that many active administrators (10-20). Here's why I think having eliminators would be useful.
Most of the backlogged DRs and CFDs (especially CFDs) are uncontroversial. These can be closed by most semi-experienced users. By having an eliminator role, we can reduce these backlogs without the extensive trust required for users to become admins. I have drafted a policy page, and have made the requirement per Commons:Eliminators#Rules for usage that eliminator actions must be accompanied by a speedy deletion tag set by another user or an uncontroversial/supported by consensus deletion request by another user to avoid the chances of false deletions.
Oppose despite the work overload for administrators, I think that anything that increases the risk of deletion of legitimate content should be avoided. I remember that the first (and to date, the last) time that I tagged files (uploaded by me) for deletion, due to a change of format, I thought: "Why is this so complex? I uploaded them myself only a few weeks ago, why can't I just delete them?". But I quickly realized that, however unfriendly it was for novices, it was necessary for it to be so. Once a file is uploaded, it can be used by anyone, it doesn't belong to you as uploader. I uploaded those images, among other things, to contribute in preserving them, so it makes full sense that it isn't so easy to delete them. MGeog2022 (talk) 21:08, 26 September 2024 (UTC)
Support Anything to lighten the load on admins is a good thing, but there should be a limit to how long discussions can run before closing, in addition to a minimum length(2 days at least) to avoid someone slipping under the radar. If this gets approved, I volunteer to be the test user for the whole process. All the Best -- ChuckTalk16:53, 27 September 2024 (UTC)
@MGeog2022, Undeletes are cheap, and if we have a seprate log for eleminiators, its easy to patrol edits. I only ever see there being 5-10 eliminators at any given time, as most people who would be eliminators are already admins. We @Matrix, what are your thoughts on requiring LR before getting eliminator, and allowing these users to grant autopatrol? All the Best -- ChuckTalk16:56, 27 September 2024 (UTC)
I think it's best not to tie this right to license reviewers. There are Commons users that are familiar with copyright, but have no interest in reviewing files from Flickr. Furthermore, the implied journey of normal user -> autopatroller -> patroller -> LR -> eliminator is simply too long. A user's ability to interpret deletion policy and requests can be judged by previous DR history and questions from other users during the process. As for allowing these users to grant (but not remove) autopatrol, I think this is an all right idea in theory, considering license reviewers can grant (but not remove) license review status for other users, but in practice we don't really have that big of a backlog at COM:RFR so it would be quite redundant.
I was referring to requests for the right, not for DRs. The autopatrol granting is because some editors (who are fantasic!) don't have autopatrol, but their (perfectly fine and above board) edits clog up RTRC, and dealing with that problem is where I see the utility (or just allow LRs to grant autopatrol.) Please let me know if I missed somthing. All the Best -- ChuckTalk17:52, 27 September 2024 (UTC)
@Alachuckthebuck, OK, if eliminators are few and very trustable, Support. I do know that deletions can be undone, but the problem with deletions, unless other editions, is that deleted files can't be viewed any more (except for very few privileged users), so a wrongly deleted file would not be so easy to detect (also, even if undeleted, most of its previous wiki uses wouldn't be restored, so some damage would already be done). MGeog2022 (talk) 19:22, 27 September 2024 (UTC)
@MGeog2022, If an image is in use on a wiki, than the deletion threshold is a lot higher, and In-Use images can only be deleted as copyvios, vandalism, or advertisements. That's it. As to undoing deletions, "deleting" a file on commons just hides it from the majority of users, and undeletion just unhides the file. Currently, I can think of about 4 users who would be given this right by the community, and never expect it to go above 20 unless commons becomes bigger than en-wiki. All the Best -- ChuckTalk21:09, 27 September 2024 (UTC)
@Alachuckthebuck, false positives in copyvio could take place if people without enough knowledge could delete files. But, from what you say, it's about having less than 10 (very trusted) people as eliminators, to reduce workload to administrators. So, certainly, I Support, then. MGeog2022 (talk) 12:45, 28 September 2024 (UTC)
No least: If the potential eliminators would just use the same time for commenting on deletion request, the problem was also resolved. More rights don't help to solve resources issues, but more active users do. Krd06:35, 28 September 2024 (UTC)
@Krd, How do comments help make closing DRs easier? If its an open and shut case, an eliminator can close the DR, rather than commenting "Delete as (Generic reason here), Could have been CSD", and wait for an admin to come along and close. If its more complex, then they can comment as community members. But the majority of DRs don't need 5 community members, they need someone who has the technical ablity to delete the file to close the DR, and delete the file. If community members can close DRs as speedy keeps (and only a few even do this due to the effort involved in manually closing a DR as keep), why can't they close 7 day old DRs that should have been CSD tagged? That's the role of Eliminators: allowing admins to focus on the DRs that tend to stay open for weeks, rather than the 50 Open and Shut cases. All the Best -- ChuckTalk23:57, 28 September 2024 (UTC)
Thats why eliminators should exist, allow the admins to not worry about the simple stuff and just focus on the Difficult DRs. And also allow a path to increasing the size of the admin corps. Its a win-win All the Best -- ChuckTalk05:58, 29 September 2024 (UTC)
Chuck, we admins can always close more open and shut cases, those are not the biggest issue in our backlog, the difficult ones are often open the longest because we need specialized information or it's not clear-cut on whether or not it fits a copyright exemption. We definitely want more non-admins to be active in DRs. Some of our most trusted users are not admins. Abzeronow (talk) 18:38, 29 September 2024 (UTC)
Neutral :- @Matrix, In my opinion, unbundling the toolkit is not a solution. I would suggest that the community should take initiative and pitch potential candidates for RFA. That way it will ease the task for the community to decrease the backlog. Thanks --C1K98V(💬✒️📂)04:32, 28 September 2024 (UTC)
I was talking to someone about doing that a few months ago but it seems like there just isn't any users on here would qualify, maybe some users from Wikipedia but I don't think anyone would vote for someone who isn't active on here even if they would be fine otherwise. --Adamant1 (talk) 11:45, 28 September 2024 (UTC)
some users from Wikipedia: I think this is a very good idea. If there are copyvio images in Commons and they are used in Wikipedia, this is is also a problem for Wikipedia, so it's of interest even for Wikipedia-only community members. MGeog2022 (talk) 12:50, 28 September 2024 (UTC)
Then I assume you're looking for potential candidates at the wrong place. Without RFA you're reaching to conclusions is not fair (community views might differ). Thanks C1K98V(💬✒️📂)13:04, 28 September 2024 (UTC)
@C1K98V: I'm more then happy to look over a list and give my opinion on the candidates if you want to email me one. I spent a good amount of time a few months ago researching users on here to see if any of them wanted to apply for adminship though and couldn't find anyone who would qualify. That's not to say their isn't anyone, there were two users I thought might be able to pass an RFA at the time, but the pool of potential candidates is clearly extremely low. I don't even think there's that many active users on here to begin with. Let alone anyone who's untarnished enough to be an admin. --Adamant1 (talk) 17:27, 28 September 2024 (UTC)
Oppose. I do not like such unbundling / fine divisions of labor. In addition, an eliminator could not undo her own mistakes. Glrx (talk) 13:12, 28 September 2024 (UTC)
Oppose Deleting as important to the administrator's toolkit as blocking and protecting. I can only think of two people whom I wouldn't trust with the block button but with the rest of the tools. Basically, if they're trusted enough to delete and undelete, they are trusted enough to be administrators. Also, I'll note there really is not a RFR backlog, at least one request is being kept open so the requestor can get more edits. I'm also aware of a future RfA from a trusted user whom I would support. Abzeronow (talk) 21:03, 28 September 2024 (UTC)
Even if we only get two more people helping with the backlogs, thats two more people helping close DRs. Adminship is supposed to be Not a Big deal. This "admins are gods" mindset is everywhere on commons, and anything we can do to reduce that mindset is a plus. All the Best -- ChuckTalk23:45, 28 September 2024 (UTC)
I would definitely encourage more people to become admins. I don't agree with "admins are gods" mindset, and as stated, backlogs exist for reasons other than number of admins. I've got at least three DRs that I can't close yet because I need information on the ToO of Serbia. Abzeronow (talk) 18:38, 29 September 2024 (UTC)
Here's a paradox: many users are too humble to consider applying to be sysop, whereas those who do often have big ego and cannot restrain themselves. (same is true for politics and management in real life, but there are more checks and balances. here users are often anonymous; positions are for life; participation is voluntary = bad money drives out good.)
so i have 2 suggestions:
for the 1st part of the paradox: let's hold a "nomination call" once a year. users list names that they trust to be sysops.
hope is that a listed user seeing the support they have will have confidence to apply.
The whole bad admin part doesn't exist right now, but the first part made sense. Would you be willing to be bold and be the first person to make such a list in userspace? All the Best -- ChuckTalk15:33, 2 October 2024 (UTC)
Totally a side thing, but realistically how many new admins do either one of you think there needs to be for the backlogs to get dealt with? --Adamant1 (talk) 23:40, 4 October 2024 (UTC)
I think at least 20 more. I'd take part in a "nomination call" as I can think of a few users that I'd like to see as sysops. Abzeronow (talk) 17:34, 5 October 2024 (UTC)
That sounds about right. I have a list of 5 or 6 people I've been sitting on for a while now. Maybe we could create a special page or something for finding people and nominating them for adminship where we can list everyone. Although I'm hesitant to name people publicly or nominate them for the role if they don't want to be admins in the first place. But there's certainly people out there who would clearly qualify. There just needs to be a more organized, intentional effort to find them and make them administrators. --Adamant1 (talk) 17:46, 5 October 2024 (UTC)
@Adamant1, 20-50 depending on what backlogs you are talking about. And about 100 LRs working full time on the Flickr backlog All the Best -- ChuckTalk23:25, 5 October 2024 (UTC)
Comment Why cant we just try to recruit admins from other Wiki projects? I'm sure ENWP will survive a few less of them--Trade (talk) 00:32, 16 October 2024 (UTC)
Because they don't have the trust of the commons comunity, and don't know our policys and/or tools. Commons has a lot of tools that aren't needed elsewhere, and most en-wiki tools don't work here. Can someone please fix auditor, it's kinda half broken, as is the commons fork of twinkle. I know you come from enwiki, and its a interesting place with a lot of history and traditions (trout in particular). It's a completely diffrent set of skills, and com:MELLOW sums it up pretty well. I'm thinking about writing a supplementary essay about how com:an is not en-wiki's ANI (and we like it that way), or any of the "drama boards" that are so often timesinks of enwiki. Commons doesn't have 55 active notice boards. We have 8 main, with about 15 supporting and occasional activity. And commons admins do a lot more deletion than en-wiki admins. All the Best -- ChuckTalk03:42, 16 October 2024 (UTC)
@Trade, We don't have admins who just do admin things (I.E, UAA) we have admins who work on copyright, image upload, VRT, RTRC, or doing other tasks. En-wiki's admins aren't known for being mellow. All the Best -- ChuckTalk20:59, 16 October 2024 (UTC)
Redirect undermaintained Species Galleries to Category pages
Hey all, I have been thinking about this for a while so wanted to put it out there.
I have been watching a lot of the Taxon galleries and have been noticing a pattern:
the vast majority of them have less than 10-15 pageviews a month, some as few as 0 or 1, and have barely any information -- nearly 90% of the time, it has less Taxonomic information than Wikidata, which in turns means that the gallery page is far less informative or easy to translate than the Category Wikidata Infoboxes, which include all of the identifiers currently used in special templates on the gallery pages.
Moreover, almost all of the gallery pages haven't had any images updated since ~2013-14. This means that most of the time, images are low quality or don't represent the biodiversity very accurately. Especially on taxons, there has been a lot of subsequent work to partner with Natural History organizations, Flickr or INaturalist to add additional photography and media, and the editors working on taxon categories have been far more active.
Additionally, by both having a Commons Category and a Gallery page, it targets navigation from Wikipedias and other sources using interwiki links towards the less useful set of media files.
I propose that we redirect the Gallery pages to their corresponding taxonomic category, if:
The page contains less than 500 bytes
Hasn't been edited since 2016 (or hasn't had more than 2 edits since 2016)
and has less than 15 pageviews a month
I have a sample query with Petscan of the kinds of taxons pages this would include. And based on massviews for the first 20000 or so of these gallery pages, I estimate that we would probably be redirecting ~ 80% of the pages if we only used the pageview criteria, the other two will reduce it substantially but make it easier to evaluate the quality of the remaining ones.
Once this step is done, we could look at the remaining taxon Gallery pages to evaluate if they are providing sufficient value to users or are worth trying to maintain. I get the impression that there would be a second tranche of redirects if we are thinking about reader value and maintainability, Sadads (talk) 13:55, 19 September 2024 (UTC)
Support Agree 100%; the gallery pages no longer have any useful value, and most of them should be redirected to the relevant category, or deleted. I'd also widen the criteria for inclusion somewhat, to say 'Hasn't been edited more than 2 times in the last 8 years', so subsequent small maintenance edits (e.g. for replacement or removal of deleted or misidentified files) doesn't prevent redirection. - MPF (talk) 14:15, 19 September 2024 (UTC)
I would endorse that switching from "Hasn't been edited since 2016" to "'Hasn't been edited more than 2 times in the last 8 years'" -- that would definitely be a better scope for getting rid of unmaintained stuff, Sadads (talk) 14:33, 19 September 2024 (UTC)
Another major issue here not mentioned so far is that in the MediaSearch under "Categories and Pages" by default galleries are also shown. Depending on the search phrase, there's often many of them. Especially in such cases but also in general, this means category and help pages are buried underneath so people, especially people not yet very familiar with WMC, won't find them. Gallery pages seem to show up there near the top and most of them are not useful and even when they are I think it's rather unlikely people using that search searched for galleries there. When I search for categories (less often also help pages or prior discussions) I usually go there and then click Namespaces and then select Custom and unselect Gallery. New users and unregistered people casually browsing the site shouldn't be expected to find that. As a solution I'd propose moving galleries a bit down in these search results and what's proposed here would probably also substantially contribute to making that search much more useful. Prototyperspective (talk) 23:03, 24 September 2024 (UTC)
That's certainly a problem. Right now if you look for "roses" it's impossible to ever to any categories in the search results because there's 2,000 galleries for every minor sub-species. I'm not sure if making galleries show up lower in the results would work though. Since there's probably always going to be more categories having to do with a particular subject then galleries. Meaning galleries will just end up being hidden at the bottom. The better solution is having standards about it and not letting people create galleries in mass for every minor subject. Admittedly I haven't looked into these galleries that much, but at least the ones for roses seem to have been created in a semi-automated way as part of paid editing campaign or something. So I doubt there's much chance of it being duplicated. Probably the same applies here. There's almost zero chance of someone creating 40,000 or however many it is unless their using a bot or something. So there just needs to be better standards and regular review of new galleries once the current crop is cleaned up. --Adamant1 (talk) 00:38, 25 September 2024 (UTC)
That's a good example. It doesn't even show the category of the exact same name, Category:Roses, near the top but only underneath a pile of likely irrelevant galleries. To clarify: I didn't mean that all categories come first and then all galleries below them – just that their relative relevance is decreased and I don't know if the Wikimedia search algorithm is transparent/open. So galleries would still show high up if they are very relevant such as having a name that matches the search term 1:1, just not so many at the top and maybe only below a few most-relevant cats. One could also consider things like reserving the top 3 search results for category and help pages and several other things like that. Standards and what has been proposed here would help a lot and may be more helpful in that regard compared to improving the search engine algorithm but both things can be done and if the latter is implemented that may take quite a while until it's applied. Prototyperspective (talk) 10:34, 25 September 2024 (UTC)
@Prototyperspective: Maybe it would be worth just disabling galleries in the search results by default like they do with talk pages and the like. I doubt anyone uses the search to specifically look for a gallery right off the bat and they show up in the drop menu anyway. So it doesn't seem like it's necessary to even show them in list of results to begin with. At least not by default. --Adamant1 (talk) 17:56, 25 September 2024 (UTC)
I think it would be useful to have some data how much of the traffic for Galleries is from Search vs Interwiki Links vs Google + referrals -- my bet is the later two are a much higher driver of traffic than the search, but it would be good to know if a decision like that would reinforce evidence of galleries in Decline-- this should be part of a followup set of discussions related to galleries, Sadads (talk) 18:35, 25 September 2024 (UTC)
Disagree
So problems are that a lot of Taxon galleries are less useful because they have old images, are small, have not enough information and have less than 15 pageviews a month. Is that the case? Why is it a problem that:
old images are used? Do organisms change overtime? Do the images not show good enough what an organism looks like? I always thought that organisms do not change a lot within a century.
they are small? The number of 500kb also means that even a gallery page with eight images, like Penstemon gracilis, would be emptied. Up to now we have used a limit of one image (a gallery page with one image may be deleted, one with two or more should be kept).
offer not enough information? Add a Wikidata infobox and you have access to all the information that you may wish for within the Wikimedia family. For me a gallery page is also useful for a quick view: a visual answer to the question what is the subject about (and not having to click on many subcategories within a category), and then maybe click through for more information.
they have less than 15 pageviews a month? Commons is not a commercial organization where only images or gallery pages may stay that have a minimum use or pageviews. Gallery pages in the end of the long tail can also be useful and valuable.
And I totally disagree with MPF that gallery pages have no longer any useful value and most of them should be deleted. I use them often and in general I find them useful. JopkeB (talk) 16:25, 19 September 2024 (UTC)
When it comes to your example, the gallery is not more useful than the category page. It's less useful and has several other issues such as newly uploaded images added to the category not showing up in it. Prototyperspective (talk) 16:32, 19 September 2024 (UTC)
It is not about this example, it is about gallery pages with eight images that might be deleted when these criteria are used. JopkeB (talk) 16:41, 19 September 2024 (UTC)
@JopkeB The example you share of Penstemon_gracilis is a perfect example of where the gallery has less information that the Category (exact same pictures, less information). And a good example of where we have already 8 different other pages where you could get the same data (5 Wikipedia articles, A Commons category, a WikiSpecies page, and a Wikidata item). The page has been used 185 times since 2016, whereas the category has been used 103 times. We have basically split the audience, but created twice the work for the volunteer editors maintaining the page. Moreover, the Gallery would require an editor to actively maintain the page to include new novel information, such as images in Category:Penstemon_gracilis_-_botanical_illustrations, Sadads (talk) 18:06, 19 September 2024 (UTC)
Ditto to @Sadads, the Penstemon_gracilis page @JopkeB cites is a perfect example of why the galleries are useless; that gallery includes no information at all that is not in the category, and omits several things that are in the category, like filenames and file sizes.
Also well worth mentioning (which it hasn't been yet), is the complexity of renaming when a taxon is renamed (e.g. a change in the genus a species is in, or a former subspecies changed to a species): the presence of a gallery double the amount of work to do. This is a major problem with the massive backlog of taxonomic updates needed on Commons. - MPF (talk) 19:28, 19 September 2024 (UTC)
Weak oppose
Yesterday and today, I checked roughly 430 of those pages. Most of them are not real gems of our project. That brings me to my main point: Commons is a project just like the Wikipedias. Some day, a colleage fills out one page and another time, someone else populates another one. Readers can jump to the main category anytime. A solution would be a contest "who illustrates / populates" poor taxon gallery pages - or a focus on taxon pages for a month (the 3 best users get a virtual ribbon). At the German Wikipedia, we have writing contests (e.g. Asia) but at Commons, there are only a very few (image contributions of a certain topic, or QI, etc.). I wonder what happened to the peoplz who created this mass of pages ... -- Did they all drop out? --Mateus2019 (talk) 16:58, 19 September 2024 (UTC) ← has no biology background beyond school education back in the 1970s to 1990s.
They may no know of categories and it takes an extra click that many won't do if the first page doesn't show already useful media. It could be that many of these have been created by bots but I haven't checked. In any case they hide the media in the categories. Prototyperspective (talk) 17:07, 19 September 2024 (UTC)
Yeah the problem is that the Categories and Infoboxes on the categories are much easier to maintain, higher value information resources -- and there is not a lot of editors working on the Galleries for the taxons (40k of them) and there is not a really compelling case to be made to work on them, when the categories and infoboxes do most of the work. Sadads (talk) 17:56, 19 September 2024 (UTC)
In my opinion the function of a gallery page is NOT to be complete nor to show all the available information about a subject, but to show a fine selection of all the media in relevant categories. Many categories show media of low quality, or media that look a lot alike, or have many subcategories where gems are hidden. In a good gallery a selection of the best media is shown, including the hidden gems of the subcategories, all to see at a glance. And they may have other funcions, see my list at Commons talk:Galleries#Add "criteria for creation of galleries" section to guideline. Categories and galleries are complementary to each other. In the case of toxan galleries they might give a quick glance of different aspects of a species.
To start with almost all of the ones I am encountering, have super low quality images, that could be better represented by new media that are higher resolution or a featured image. However, I also keep finding galleries with 1-3 images, that exactly replicate the category -- sometimes featuring quality images -- also not helpful if they don't help the reader get oriented to the topic. This is part of the reason I am suggesting a criteria of 500 bytes: larger than that, and there is usually some kind of meaningful description or "orientation to the topic" that would be lost -- usually its superficial, but at least there are captions, sections and some kind of filtering going on. Wheras the smaller ones (especially those without edits or pageviews), basically don't show the best of commons -- leading to the kinds of confusion of unfamiliar readers/editors/community members suggested above, and also to the neglect of maintenance of things like translation. 10:00, 20 September 2024 (UTC) Sadads (talk) 10:00, 20 September 2024 (UTC)
Support I've been going through and adding categories to species galleries the last couple of days. Most of them totally pointless and have no way of being expanded because there isn't enough files on here having to do with the species to begin with. One thing that I think should be done with a lot of these small, unmaintained galleries is that they get up-merged to ones for the broader topic. A good example of that is the galleries in Category:Gallery pages of roses, most (or all) of which only contain a couple of images and have zero way of being improved. There's just always a tendency to take everything down to the lowest possible point on here for some reason though.
Regardless, there's no reason most (or all) of those galleries couldn't just be gotten rid or up-merged into one for roses in general, instead of us having to deal with, improve on, and maintain 2309 galleries for every single minor sub-species. Realistically we just don't have enough people who are interested in the area to improve the galleries. Let alone enough images to make it worth putting the work into to begin with. So I'd totally support just redirecting or deletion them in absence of a better alternative. I don't think they be kept as is indefinitely just because though. At the end of the day there should either be a clear, reasonable way to improve them or they should be gotten rid of however it's done. --Adamant1 (talk) 07:25, 20 September 2024 (UTC)
I agree completely. Small, specialized categories rarely deserve a gallery page of their own. Upmerge galleries to form a decent gallery corresponding to a parent category. I think Romanian Orthodox churches in Bucharest is a good example of doing this at the right level. Yes, many of these churches have categories of their own, but few deserve galleries of their own. - Jmabel ! talk15:10, 20 September 2024 (UTC)
Anywhere there is an analogous situation. One of the best features of galleries is that they allow us to juxtapose images from subcategories and help people identify what they are looking at without having to dig into a bunch of separate categories. Tiny, sparse gallery pages don't help with that. - Jmabel ! talk20:02, 20 September 2024 (UTC)
Support. Galleries make sense where there are enough images related to a broad topic that it becomes helpful to call out a few really good examples, or where there's some structure to a set of images which is difficult to show in a category. A great example of both is gallery pages for cities, where the page will often be organized around points of interest in the city, and will pick high-quality images from subcategories to illustrate each one. Creating galleries for species categories which only have a few images to begin with is a waste of time; there's no additional curation or organization that can be offered. Omphalographer (talk) 16:38, 20 September 2024 (UTC)
Comment @Sadads commissioned me to write a Quarry query for this project ^^ https://quarry.wmcloud.org/query/86509 should implement the first two conditions, i.e. list small pages (for taxon galleries) with few edits since 2016. (I slightly tweaked the second condition to avoid including pages that were created post-2016 but had ≤2 edits.) The third condition, pageviews, isn’t available in Quarry, so someone™ will have to do that externally. But I hope this helps :) Lucas Werkmeister (talk) 17:27, 24 September 2024 (UTC)
All the galleries I've checked barely had any views. So I doubt it matters. The most important things are the size of the galleries and number of edits. --Adamant1 (talk) 17:32, 24 September 2024 (UTC)
The main issue is figuring out what makes a gallery qualify as "small" or not. It seems there's some resistance when it comes to galleries containing more then one image being deleted, but that seems like an extremely myopic and arbitrary place to draw the line. I've certainly seen plenty of galleries that weren't any more valuable just because there was one or two extra images. --Adamant1 (talk) 00:48, 25 September 2024 (UTC)
@Adamant1 @Omphalographer I think the byte count is really telling, the more I look into this (I ran @Lucas Werkmeister Quarry, without the limit to the Taxon Galleries: https://quarry.wmcloud.org/query/86513 -- and sampling from other generes/themes, low byte count = no captions, sections or sufficient contextual data to be useful in a way that is more helpful than a category page, right around 600 bytes you start getting sufficient description or complexity (i.e. multiple images in multiple sections). Sadads (talk) 00:52, 25 September 2024 (UTC)
That being said, I think the consensus in this discussion is on the taxon content, if we want to do the other topics I think we should start another discussion (once the taxons are gone, it will be easier to see what is being neglected here, Sadads (talk) 00:56, 25 September 2024 (UTC)
That sounds reasonable. I think around 600 bytes is a good place to deal with it at and then we can review and clarify where the final line should be from there as needed and/or with other topics. --Adamant1 (talk) 00:58, 25 September 2024 (UTC)
To Summarize:
Sort criteria for the purge are:
that the gallery is less than 550 bytes. I'm splitting the difference here between the 2 most popular proposals.
Less than 2 2 or less (see Adamant1's comment below) edits in the last 8 years.
Wikidata infoboxes for all the subspeices should be on the catagory pages.
The gallery policy should be updated and possibly changed to increase the quality expected of gallerys, and to require RFC (or equivalent, i.e. Village pump/propsals) before any form of mass gallery creation starts.
Organise and editathon (or similar) to perform all the taxanomic updates needed.
Make a method for editors/permission holders to help conribute.
That sounds fine except I'd change the edit count to "two or less" since from what I've seen a lot of galleries get superficially edited by a bot at some point and I don't see why it should matter. --Adamant1 (talk) 01:59, 25 September 2024 (UTC)
@Alachuckthebuck I think the Wikidata Infobox is not a firm requirement before the redirects -- there are already several hundred that need to be fixed in Category:Redirects_connected_to_a_Wikidata_item -- I think the requirement is something we can fix afterwards, because we are going to need to fix the interwiki link mapping, and subsequently the addition of Infoboxes to some of those pages (it also simplifies the bot or AWB run to do it). I think the more important requirement is that the gallery is in a category that has the same name, Sadads (talk) 02:02, 25 September 2024 (UTC)
Makes sense, that was more summarizing the discussion, less about updating policy.
someone (probably me in a few hours) adds a new section summarizing the discussion into a set of suggestions under a new heading, then let that run its course. Then an uninvolved admin closes, and we start implementing the changes technically, probably will need someone on the WMF side to help with this, @Sannita (WMF), Who would be the right person to talk to for somthing of this scale server side? All the Best -- ChuckTalk20:55, 25 September 2024 (UTC)
@Alachuckthebuck A summary of the discussion would be most welcomed, so that I can try to help you with the request. Please ping me when you are (or who will do the summary is) done with the summary. Sannita (WMF) (talk) 11:14, 26 September 2024 (UTC)
Interesting @Alachuckthebuck & @Jeff G., why would redirects by a bot effect CVN? My understanding from bots on other wikis is that you can have their actions either autopatrolled, or clearly labeled with the bot label.
All deletions go into the CVN-bot logs. those logs were the only indication that something was off when we had the whole Vietnamese artist mass no permission tag fiasco. All the Best -- ChuckTalk14:41, 30 September 2024 (UTC)
I support that, assuming cat edits only include Hotcat and Cat-A-lot/other cat tools with edit tags (for technical reasons, makes sorting automatically possible without regex) To paraphrase into policy/technical speak:
Edits made by flagged bots, those marked as minor, and edits tagged with Hotcat,Cat-A-Lot or another catagory tool do not count toward the 2 edits or less threshold for inclusion.
Support, these add no value to the project, only maintenance burden, let's get rid of them. I would like to see this extended to all galleries, though, not just taxon ones. Thanks. Mike Peel (talk) 10:10, 30 September 2024 (UTC)
Summary Proposal by Alachuckthebuck
(After purge and renames are complete) Add Wikidata infoboxes for all the subspecies should be on the category pages.
The gallery policy will be updated and changed to increase the quality expected of galleries, and to require an RFC (or equivalent) before any form of mass gallery creation. This needs proposal on the gallery talk page.
Organize a Backlog Drive after purge to perform all the taxonomic updates needed.
Make a method for editors/permission holders to help contribute to the drive who are not familiar with this topic area.
The first paragraph of the gallery policy has the sentance: Galleries must have a valid reason for creation, and not just be simple copies of categories, A selection of media from a large category, or a collection of categories, is acceptable. added to the end.
The first paragraph of the section When to create a gallery in the the commons' gallery policy has the sentence" The Bar for the creation of galleries is higher than categories, and a valid reason for creation is required for mainspace galleries. to the end of the paragraph.
Purge the Taxon Galleries with the following criteria:
The gallery is less than 550 bytes
2 or less edits in the last 8 years (must be created before 2020 to apply). Edits by Flagged bots, Marked as minor, Cat-A-Lot, or HotCat do not count towards this limit.
Can someone close this? There appears to be a consensus to implement at least some of the proposals. All the Best -- ChuckTalk17:17, 8 October 2024 (UTC)
I think more feedback would make contributing much more fun and keep people engaged and facilitate them to contribute more, have a positive experience and remain motivated. There are several kinds of interactivity / feedback here, some already are implemented, some would be difficult to implement well, and some are probably not overly complex to implement with nearly no downsides but many advantages and high usefulness. I think is of the latter kind.
On Wikipedia, one can already get notified when pages wikilink to an article one has started. This is simply interesting to the person who created the article and encouraging.
Could similar notifications be enabled for when files one has uploaded get used on another Wikimedia project? It could show a This file {filename link} is now in use notification for either all file-uses or the first use per file.
One could enable/disable these notifications in the preferences, like on can for when a WP article is linked (and maybe at some point one could also exclude a select subset of one's uploaded files where one would like to not be notified). Inexperienced contributors don't learn when or whether their files are being used which must be pretty discouraging and boring; it also does not provide feedback which of their files is what is probably among their most useful (encouraging more of these). One can currently see which of the files one has uploaded are used by putting them all in one category and then using a tool like GLAMorgan but I don't think there's a way if one's files are not in a category and that sends a notification when (best shortly after) a file gets used. Prototyperspective (talk) 22:49, 4 September 2024 (UTC) --El Grafo (talk) 08:50, 17 October 2024 (UTC)
Support Although weakly. It's an interesting idea but I'm not to sure how useful it would actually be in motivating people to contribute to the project more. There's also already enough issues with ownership on here that I feel like this exacerbate. There's no practical reason why someone needs to be notified if one of their images is used or not somewhere. They don't really "own" or have any control over the images after uploading them anyway. Or at least they shouldn't. --Adamant1 (talk) 00:06, 5 September 2024 (UTC)
Yes, they don't need to be notified but it's encouraging further contributions and making contributing more engaging. I don't think this would exacerbate problems but there could be some issues when people feel like the media they uploaded (or created and then uploaded) is used in a 'wrong' way. However I don't think it would be a significant/big problem (very rare and then solved on the article talk page / by other editors changing it) and the advantage that they could also spot mistakes in the file caption for example could easily offset that potential problem. People can already see when their files are used and I haven't heard this caused many problems, this would just make file-uses more widely and quicker known. Prototyperspective (talk) 00:18, 5 September 2024 (UTC)
I think Jmabel asked on the Village Pump awhile ago if there was a way to search for files that are in use by a particular uploader. I feel like that would probably be a better way to do this. As I think there's a general interest in knowing who's files are being used where. All a notification does is let the person who uploaded the files know though. I don't think your whole that it would help for files that are being used "in a 'wrong' way" is really that valid either since uploaders have a tendency to be control freaks who think their contributions are being used wrongly regardless if they are or not. I could really care less if an uploader on Commons thinks a particular usage is "wrong." What matters if the person on Wikipedia's end who added it to the article and has prior experience in the area thinks it's correct. --Adamant1 (talk) 00:28, 5 September 2024 (UTC)
When it comes to complex scientific illustrations and so on people can easily get things slightly wrong. It may be rare that some correction/adjustment is due and that the uploader checks the caption and implements such but I think minor talk page drama will be even rarer as I don't think uploaders have a tendency to be control freaks and haven't seen much or even anything supporting that (and that despite that people can already bulk check which of their files are in use). I think it would probably be best if there were two checkboxes in the Preferences – one about all notifications when a file is used and one for the first use of a file – with only the latter being the default. Probably half of the time if not more often, the uploader doesn't even see the notification because they stopped using the site and uploaded the files 5+ years ago. Prototyperspective (talk) 23:14, 5 September 2024 (UTC)
I don't necessarily have an issue with it in that case and a few others, which I do ultimately support the proposal. But I still think the potential for something like this leading to more drama due to some uploaders having control issues is a problem even if that hasn't been your experience. I've certainly seem myself. Although admittedly not that frequently but it still happens. --Adamant1 (talk) 23:19, 5 September 2024 (UTC)
Two remarks:
See Glamtool GLAMorous for the use of your (or anyone else's) uploads: fill in the user name, click on Show details and Do it! So you do not need to put them all in one category for this reason.
I think this should not be done through notifications but through the Growth dashboard that on Wikipedia already shows how often the edited articles are viewed. GPSLeo (talk) 05:53, 5 September 2024 (UTC)
@JopkeB Great, thanks – seems like I used to miss clicking on Show details with that tool. Don't know if it's a good idea to have that not be the default without any info about it on that page because "Show details" is not self-explanatory. Maybe I'll propose it in the Wishlist.
@GPSLeo I don't see a growth dashboard on Wikipedia so I don't know if that is still upcoming or only for some subset of new users. It seems to be on Wikipedia only but this is about and specific to WMC (and I would support having a similar dashboard here). Having both would be best imo where the user could choose which one to enable/use. Prototyperspective (talk) 23:26, 5 September 2024 (UTC)
Wikipedia can notify a user when an article they created is linked from somewhere.
supposedly settings can be tweaked by wmf to let the same kind of notification happen for files on commons? RZuo (talk) 14:24, 6 September 2024 (UTC)
Support I would like to know if my uploads are being independently used without periodically checking individual files or relying on external gadgets. Dronebogus (talk) 15:02, 9 September 2024 (UTC)
Oppose I would like to get notified about disuse as well. Otherwise this proposal sounds like unnecessary “gamification”. Good files get used. And, more importantly, remain in use. ‑‑ Kays (T | C) 07:35, 8 October 2024 (UTC)
I wouldn't be concerned about the potential issue of uploaders trying to keep their files in use or trying to control how they're being contextualized / captioned but I would be to some extent if they get notified about disuses of their files – this just invites them to change it back. On Wikipedia one also only gets notified once an article one has created is wikilinked from another one, not once the use is removed. Use-notifications could already be nearly too many for many users without adding depressing disuse-notifications on top. Prototyperspective (talk) 11:52, 26 October 2024 (UTC)
Support --Adamant1 (talk) 08:31, 15 September 2024 (UTC)
Oppose I support the spirit of the proposal but I think that changing an image to remove the white background should not require upload as a new file in many cases. I would support it if it was only about removing transparent backgrounds. I think transparent backgrounds are better for many reasons, mainly one can readily use them in other images using the existing background or giving it the background one wishes it to have. It can be a real hassle or not worth it to add some image with a white background into an image like an infographic with another background. It's similar to why SVG is preferred over jpg files. Concerning dark mode, I think technical changes are needed so that transparent background images are readable on it. Is there any issue for that? One shouldn't have to resort to changing the background to be able to view images with transparent background in dark mode – it could set a greyish white as the background or inverse the font color if dark mode is enabled. Prototyperspective (talk) 11:17, 15 September 2024 (UTC)
Comment presumably if the original was created and uploaded by a still-active Commons user, they can consent to a change, no?
Neutral :- @Matrix, In my opinion, unbundling the toolkit is not a solution. I would suggest that the community should take initiative and pitch potential candidates for RFA. That way it will ease the task for the community to decrease the backlog. Thanks --C1K98V (💬 ✒️ 📂) 04:32, 28 September 2024 (UTC)
Disagree
Weak oppose