Commons:Village pump/Proposals/Archive/2019/09

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

Increase the move rate limit for autopatrolled from 8 to 32 moves per minute

ACCEPTED:

The move rate limit will increase for all users with 'autopatrol' and without 'noratelimit' user-right (i.e. 'autopatrollers', 'patrollers', and 'image reviewers', but not 'administrators' and 'bots') on Commons from 8 to 32 moves per minute per unanimous consensus below. 4nn1l2 (talk) 22:34, 11 September 2019 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Tracked in Phabricator
Task T232657

These are users who actually spoke up. (and that I was able to find) Many who encounter the error likely ignore it. I propose increasing the move limit for users with autopatrol flag from 8 to 32 per minute.

Increase the move rate limit for users with autopatrol flag to 32 moves per minute: votes

Increase the move rate limit for users with autopatrol flag to 32 moves per minute: discussion

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 22:34, 11 September 2019 (UTC)

The picture of the location of temperate rainforest File:Temperate rainforest map.svg have the mistake。 温带雨林地点图片有事实性错误

The picture of the location of temperate rainforest (File:Temperate_rainforest_map.svg) have a mistake. The location of the temperate rainforest means most of this mostly in oceanic moist regions, and in the temperate zone. As a result, the location in P.R.China is not the temperate rainforest. The right picture (my evidence) is : DellaSala, D.A., 2011. Temperate and Boreal Rainforests of the World: Ecology and Conservation. Island Press


温带雨林地点图片有事实性错误。 （File:Temperate_rainforest_map.svg) 中国云南的那一块不是温带雨林。 证据（正确的图片）在： DellaSala, D.A., 2011. Temperate and Boreal Rainforests of the World: Ecology and Conservation. Island Press — Preceding unsigned comment added by Tangmingxyz (talk • contribs) 12:37, 9 September 2019 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 09:13, 11 October 2019 (UTC)

Make Autopatrol automatically given once the user hits the 30/500 mark

As a user that just hit the 30/500 mark, I believe that Autopatrol should be automatically given when someone hits the 30/500 mark, much like how the same 30/500 rule gives the extendedconfirmed right in Wikipedia. Calvinkulit (talk) 09:13, 16 September 2019 (UTC)

  • Strong  Oppose - Autopatrolled right isn't like the extended confirmed user right. Autopatrolled allows users to batch upload files upto 500. Only trusted should be given this right. Also it marked one's edits automatically patrolled, inexperienced users can seriously abuse this right. Masum Reza📞 09:26, 16 September 2019 (UTC)
(Edit conflict)  Oppose Autopatrolled and extended confirmed is totally different. Extended confirm only gives the user an extra right which allows them to edit "extended confirmed protected" pages. The autopatrol flag should only be given if the user is fit/trusted for it such as recommendation by patrollers, etc. 大诺史 (Talk/留言/토론/Discussion) 09:28, 16 September 2019 (UTC)
  • However, I won't oppose if someone recreates the extendeduploader right. It may automatically be given to an user when they reach about 1000 uploads. IMO, upload by url isn't sensitive. Masum Reza📞 09:37, 16 September 2019 (UTC)
@Masumrezarock100: a proposal is in the works. (but waiting for technical details) - Alexis Jazz ping plz 13:39, 16 September 2019 (UTC)
 Oppose Autopatrolled should not be given away by any automated process. I suppose we could create the extendedconfirmed group here, but we'd need a clear view of what we'd use that for. - Alexis Jazz ping plz 13:39, 16 September 2019 (UTC)
@Alexis Jazz: Possibly QIs, FPs & other images that have a usage of more than 5? 大诺史 (Talk/留言/토론/Discussion) 13:44, 16 September 2019 (UTC)
@大诺史: You mean protecting those so you need extendedconfirmed to edit/overwrite them? That's possible. Perhaps extendedconfirmed could also be given the increased move rate limit and be allowed to upload more than 50 files (but how many?) with UploadWizard. For upload_by_url I'm working on another proposal. Extendedconfirmed should probably not be allowed to bypass the abusefilter to upload Mp3 files. - Alexis Jazz ping plz 13:55, 16 September 2019 (UTC)
@Alexis Jazz: Maybe 100 or so? The upload wizard (for me) is pretty slow sometimes, so being able to upload more files at once does not neccessarily mean that it's a good thing for all. 大诺史 (Talk/留言/토론/Discussion) 14:00, 16 September 2019 (UTC)
@大诺史: Yeah, probably. Don't want to go too high as a proposal may be rejected for that. - Alexis Jazz ping plz 14:06, 16 September 2019 (UTC)
Maybe add Import offline translations (translate-import) rights to extendedconfirmed? This right is currently only available to Translation administrators. Note that there is an user group named "Offline translators" on translatewiki where this right is included. I do not think this right is much sensitive. It is very useful when translating. Masum Reza📞 14:07, 16 September 2019 (UTC)
  •  Oppose No. It's about autopatrol, only trusted users can have it. Yes, some users show great talent, they are familiar with copyright rules etc. so they become autopatrolled once they are around 30/500; but it isn't true about all users. Such users may request for this right and they are very likely to get it, but making it automatic? No, this right is more sensitive than that; and extendedconfirmed isn't as sensitive as this (it's only useful when you want to edit an extendedconfirmed protected page). Ahmadtalk 18:51, 18 September 2019 (UTC)
No, not good at all.--Roy17 (talk) 15:51, 19 September 2019 (UTC)
Would someone just WP:SNOW close it? Masum Reza📞 15:45, 30 September 2019 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 06:43, 11 October 2019 (UTC)

Make the Confirmed right automatically revoked after the account is 4 days old

Tracked in Phabricator
Task T232756

The Autoconfirmed right will get applied after the account is 4 days old on this wiki, so Confirmed would be redundant. With this change, there will be a new filter that automatically revokes the Confirmed right if the user is 4 (or more) days old. Calvinkulit (talk) 02:36, 12 September 2019 (UTC)

 Support but I am not sure filters can do such things. Masum Reza📞 04:49, 12 September 2019 (UTC)
 Comment This only concerns 5 users, they can easily be dealt with by hand. - Alexis Jazz ping plz 10:41, 12 September 2019 (UTC)
@Alexis Jazz: So a request to a moderator to have this taken care of should be sufficient? --oSeveno (User talk) 11:42, 12 September 2019 (UTC)
@OSeveno: I think so. - Alexis Jazz ping plz 14:17, 12 September 2019 (UTC)
@Alexis Jazz: Already done at COM:RFR. Calvinkulit (talk) 15:52, 12 September 2019 (UTC)
 Question Why do users with confirmed rights get the autoconfirmend rights? Would it not be possible to say that users with confirmed rights do not get the autoconfirmend rights and stay with that confirmed rights till they get other rights? --GPSLeo (talk) 11:46, 12 September 2019 (UTC)
@GPSLeo: Before, when a confirmed user gets autoconfirmed, the confirmed right would be revoked. And that practice is still here today. Also, the autoconfirmed right is permanent compared to the confirmed right as special rights like the Confirmed right get revoked when the person gets blocked from editing. But, revoking the Confirmed rank from a person that is already autoconfirmed is like trying to battle with your own shadow. Calvinkulit (talk) 11:57, 12 September 2019 (UTC)
 Comment Made a task for it: Automatically remove confirmed user right when eligible for autoconfirmed. This isn't specific to Commons. - Alexis Jazz ping plz 16:24, 12 September 2019 (UTC)
@Alexis Jazz: Thank you. Calvinkulit (talk) 02:49, 13 September 2019 (UTC)

Proposal to replace Template:Indefblocked-global with Template:Indefblocked-global-WPstyle

RESOLVED:
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

As the creator of Template:Indefblocked-global-WPstyle, I vow to replace the legacy {{Indefblocked-global}} with {{Indefblocked-global-WPstyle}}. After the legacy template gets replaced, the WPstyle template will be renamed to "Template:Indefblocked-global". Calvinkulit (talk) 14:07, 6 September 2019 (UTC)

@Calvinkulit: The lack of extra information is one of the reasons that Commons/Wikipedia has such a steep learning curve for newcomers. I'd like us all to help do something about that. It only requires a little extra effort. --oSeveno (User talk) 10:30, 10 September 2019 (UTC)
@OSeveno: Fixed, check it out. Calvinkulit (talk) 11:17, 10 September 2019 (UTC)
 Support Thanks! It's really well done. I now fully support your proposal. Regards, --oSeveno (User talk) 11:49, 10 September 2019 (UTC)

@Masumrezarock100: I tried to make a French translation, but it failed. Calvinkulit (talk) 01:51, 11 September 2019 (UTC)

@Calvinkulit: To translate a page, first it needs to be marked for translation by a translation admin. Masum Reza📞 04:20, 11 September 2019 (UTC)
@Calvinkulit: marked for translation. MorganKevinJ(talk) 04:55, 11 September 2019 (UTC)
@Calvinkulit: I have made a translation into the Dutch (Netherlands) language. --oSeveno (User talk) 11:38, 12 September 2019 (UTC)
@Morgankevinj: I think there's a problem with the <translate> tag, see User:Achim55555's userpage for example. Ahmadtalk 09:16, 21 September 2019 (UTC)
fixed MorganKevinJ(talk) 15:52, 24 September 2019 (UTC)
I added bn (Bengali) translations. Masum Reza📞 15:20, 16 September 2019 (UTC)
This section was archived on a request by: MorganKevinJ(talk) 02:11, 19 October 2019 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

More Of This ⬅️, Less Of That ➡️

I'm curious if there is a section on Wikimedia Commons or Wikipedia where users can specify images that they need more of or a specific image that is needed to fill an article?

For instance, it would be great to have a picture of an Icosahedrite (I'm a geologist and recently read this article) to go on this page:

Not sure if that exists somewhere but it would be helpful to find photos that need to be taken to fill in gaps on Wikimedia/Wikipedia.--Tenace10 (talk) 14:50, 9 September 2019 (UTC)

@Tenace10: , technically there is "Commons:Picture requests/Requests", but in reality these requests are rarely answered. Personally I'd rather see some sort of category which uses either local Wikimedia websites or Wikidata that creates a list of topics needing images and that this category can be sub-divided into multiple subjects which people can patrol. It might be wise to devise a better system, I do know that the English language Wikipedia has a "Picture needed" template, but I am not aware of any active photographers trying to tackle these huge backlogs. --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 20:19, 10 September 2019 (UTC)
Thanks Donald, this is really helpful. I'd imagine there is a constant and large backlog of images that would be great to have on the platform. But this gives me a good place to start looking!--Tenace10 (talk) 15:17, 11 September 2019 (UTC)
@Tenace10: The template is at en:Template:Photo requested; I added it to the Icosahedrite article's talk page in this edit Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:51, 20 September 2019 (UTC)

A DR noticeboard for language/country-specific issues

How about a noticeboard, on which users could transclude controversial DRs that need help from miniority linguistic/national groups? Its structure would be something like 

== Arabic (1) ==
{{Commons:Deletion_requests/File:ABCD.jpg}}

== Chinese (1) ==
{{Commons:Deletion_requests/File:XYZ.webm}}

== Japanese (2) ==
{{Commons:Deletion_requests/File:ABCDEF.webm}}
{{Commons:Deletion_requests/File:ABCDEFGH.png}}

...

Anyone can list a discussion manually. A bot would remove archived DRs and update the number. This might help decision making in cases that involve minority languages/lesser-known countries' laws.--Roy17 (talk) 16:36, 19 September 2019 (UTC)

 Support I am unsure how effective this will be, but it can't hurt to try. If it doesn't work, no harm done. If it works, awesome. - Alexis Jazz ping plz 18:47, 19 September 2019 (UTC)
  •  Support: Interesting idea. Needs development and maintenance, though. -- Tuválkin ✉ ✇ 19:21, 19 September 2019 (UTC)
  •  Support: There is indeed a potential need for this. From the technical side (and as a maintain member of the DR script) I've no idea how to solve this, it should be relatively hard to develop (if it should be user friendly). -- User: Perhelion 21:37, 19 September 2019 (UTC)
    No, I said discussions were to be listed manually. Whoever thinks a discussion might merit specific communities' help could add it to the proposed page manually, but not every discussion has to be listed (automatically as you and Jeff G seem to suggest). (So it could include CfD too.) Krdbot removes closed DRs. SteinsplitterBot removes closed CfDs. We'll just need an automatic counter that counts how many lines starting with { exist under a section. Actually, the page could be created right now and the bots could be configured to check the page. Only the counter is missing. The counter is helpful to quickly check whether a language has something pending, because if this were implemented, tens of languages are expected on the page.
    This would hopefully be a better venue to seek help rather than visiting the graveyards {{Lang-VP}} or going to the individual wikis.--Roy17 (talk) 22:11, 21 September 2019 (UTC)
    So... about the counter, I know we can simply set it using a bot, but I also think that, with a bit change of plans, we can create it using {{Count on page}}. Now, the thing is that this template doesn't check a page's source, but checks its visible content (basically, what you can actually see in a page is what it counts). So for example, in Special:PermaLink/367876566, it returns 516 occurrences of "File" or "Files" in Commons:Deletion requests/2019/09/20. Now, if a bot is going to set the counter(s), the idea can be just as above, but using this template needs a bit of change in that structure, because this template needs a page to search in it, and we need the counter(s) to be language-specific. So to use this template to set the counter, we'll need a subpage for each language (and we'll just transclude that subpage in the main DR page, it can also help keeping its source clean). Is this idea helpful? Ahmadtalk 18:09, 23 September 2019 (UTC)
    Oh, I found a better template: {{String count}}. This one searches the source of a page, we can simply set it to count occurrences of "Commons:Deletion requests/" in a page; but the subpage problem is still there. You can see an example in Special:PermaLink/367994721, it's just like counting the number of DRs transcluded in a page. Ahmadtalk 14:49, 24 September 2019 (UTC)
    ...Maybe something like {{DR counter box}}; you can see the result in Special:PermaLink/368007075. Please feel free to edit the template! Ahmadtalk 16:32, 24 September 2019 (UTC)
  •  Support, perhaps with cats automatically determined by the encoding of the pagename.   — Jeff G. ツ please ping or talk to me 16:53, 20 September 2019 (UTC)
  •  Comment Sounds like a good idea, but maybe it would be better to have separate (sub-) pages for the different languages. That way, you can add the couple of languages you know well enough to your watchlist and won't be bothered by the rest. The single language subpages could still be transcluded to the main page. --El Grafo (talk) 14:06, 24 September 2019 (UTC)
  •  Support but with specific subpage for each language (and we will eventually transclude those subpages in main page). In addition to technical reasons I've mentioned above, what El Grafo mentioned is another benefit it'll cause. Ahmadtalk 18:43, 24 September 2019 (UTC)
  •  Support, I've actually wanted to propose more tools that bring deletion requests more to the attention of more users. In the current system they basically only get seen by a handful of users and often don't get as much community input unless they're massive. --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 10:29, 2 October 2019 (UTC)
  • Support El Grafo idea. Subpage per language means I am only notified when there is an edit on the language I am interested in, and nothing else. — regards, Revi 01:42, 1 November 2019 (UTC)

Implementation

I suggest the page be titled Discussions by language. Each language would have a subpage Discussions by language/xx using its langcode as in Category:Commons by language. What do you think?--Roy17 (talk) 21:28, 10 October 2019 (UTC)

Isn't "Discussions" a bit too general? Since this proposal is focusing on "Deletion requests", I suggest something like "Commons:Deletion requests by language". Creating subpages using langcodes is a good idea in my opinion. Ahmadtalk 13:51, 24 October 2019 (UTC)
I'm still working on it, but User:Ahmad252/Deletion requests by language is an example of what it might look like. I can create a specific subpage for each language using my bot, but we need to discuss on titles first. Ahmadtalk 11:30, 25 October 2019 (UTC)
@Ahmad252: I made Commons:Discussions by language. A subpage is called Commons:Discussions by language/Boards/pl for example. I have to add the extra layer 'coz if the main page should be made translatable so my original idea would clash the the translation pages. I dont think we should mass create subpages. We can wait for discussions that need help emerge and let users create the subpages.--Roy17 (talk) 15:37, 27 October 2019 (UTC)
@Roy17: Good idea, But I've always been a bit worried about the crowdedness that might happen in the future. I think we'd better create a collapsable template for this page and limit the TOC to level 2 headings. This way, anyone will simply uncollapse the venue they want to check, and other languages won't distract them. We can set the collapsable template to auto-hide when there is no DR for the specified language.
And I think creating an editnotice would be a good idea. The editnotice (Template:Editnotices/Page/Commons:Discussions by language) can explain how users should create and transclude each venue on the main page. Ahmadtalk 15:52, 27 October 2019 (UTC)
@Roy17: I edited the /pl subpage in Special:Diff/372722393 and made it collapsible, just as an example of what that might look like in the future. Ahmadtalk 18:32, 31 October 2019 (UTC)

Well, we have to find and transclude the DRs manually. Transcluding them hand by hand would be really tedious. I think we have to find the way to automate the process. – Kwj2772 (talk) 20:35, 23 November 2019 (UTC)

Commons:Discussions by language has been set up. If you wanna discuss, please continue on its talk page.--Roy17 (talk) 21:19, 23 November 2019 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Roy17 (talk) 21:19, 23 November 2019 (UTC)
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump/Proposals/Archive/2019/09&oldid=377760778"