MediaWiki talk:Titleblacklist

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

This page consists of regular expressions, each on a separate line, for example:

Foo <autoconfirmed|noedit|errmsg=blacklisted-testpage> 
[Bb]ar #No one should create page about it

There is no need to use "^" at the beginning, and "$" at the end, these are added automatically.

Each entry may also contain optional attributes, enclosed in <> and divided by |

  • autoconfirmed — only non-autoconfirmed users are unable to create/upload/move such pages
  • casesensitive — don't ignore case when checking title for being blacklisted
  • errmsg — the name of the message that should be displayed instead of standard
  • moveonly — forbid moves but allow ordinary creation
  • noedit — users are also unable to edit this page
  • reupload — allow reuploads of existing blacklisted files

When the action is blocked, one of the following messages is displayed together with the filter row (as $1): titleblacklist-forbidden-edit, titleblacklist-forbidden-move, titleblacklist-forbidden-new-account or titleblacklist-forbidden-upload.

There is also MediaWiki:Titlewhitelist and a global title blacklist.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day. For the archive overview, see here.

File:(无|未|無)(标|標)(题|題).*[edit]

{{Edit request}} 未標題/未标题 is ungrammatical in Chinese. 未命名 (“unnamed”) is used instead. -- 11:51, 17 February 2022 (UTC)[reply]

 Support this makes sense. it's not about grammar but indeed computers/gadgets using chinese systems will name things with 未命名 instead of 未標題/未标题.--RZuo (talk) 14:31, 22 February 2023 (UTC)--RZuo (talk) 23:08, 10 June 2023 (UTC)[reply]
@沈澄心, @Mdaniels5757, @RZuo: I don’t understand this edit request yet; are you asking for the File:(无|未|無)(标|標)(题|題).* pattern to be removed / changed, or for another one to be added? What exactly should the new pattern be? (My understanding of Chinese is basically nonexistent; right now, all I can tell is that the initial message by @沈澄心 appears to contain nine Chinese characters, none of which seem to occur in the existing pattern as far as I can tell with Ctrl+F, so the connection between them is lost on me. But I’m sure I’m missing something.) Lucas Werkmeister (talk) 23:17, 3 November 2023 (UTC)[reply]
@Lucas Werkmeister:
original " File:(无|未|無)(标|標)(题|題) "
change to " File:(无|未|無)(标|標|命)(题|題|名) " RZuo (talk) 07:30, 4 November 2023 (UTC)[reply]
✓ Done, thanks for clarifying! --Lucas Werkmeister (talk) 10:19, 4 November 2023 (UTC)[reply]

Slavic letters[edit]

Filter seems to be blocking čšžđć. Don't know the specifics, but yesterday blocked filename Koroška Bela (river) and today Jernejčič (a familyname). As Commons is multilingual, we should tolerate such characters. A09090091 (talk) 14:20, 6 August 2022 (UTC)[reply]

@A09090091: Can you please post the exact filenames you tried? I’m pretty sure the problem is not the háčeks; I get no error or warning message when I try to create File:Koroška Bela.jpg. —Tacsipacsi (talk) 11:34, 7 August 2022 (UTC)[reply]
@Tacsipacsi: It was actually File:Koroska Bela - dolina in potok.jpg. While formulating rename template via RenameLink, the original name (Koroška Bela - dolina in potok.jpg) got rejected as it was on the titleblacklist. Same with File:Andreja Jernejcic.jpg, which I tried to rename to Andreja Jernejčič.jpg. Hope this helps, A09090091 (talk) 12:58, 7 August 2022 (UTC)[reply]
@A09: I don’t know what happened with the Koroška Bela, the API result states it’s allowed, and the gadget uses this API result (as far as I understand its code). File:Andreja Jernejčič.jpg is indeed not an allowed target name, but not because it would be blacklisted, instead because it already exists. —Tacsipacsi (talk) 22:53, 20 August 2022 (UTC)[reply]

KakaoTalk[edit]

please add one to block titles like File:KakaoTalk 20200702 111529628.jpg.--RZuo (talk) 11:59, 22 September 2022 (UTC)--RZuo (talk) 23:08, 10 June 2023 (UTC)[reply]

Captura de ecrã[edit]

portuguese for screenshot. please add it to line 97. RZuo (talk) 10:44, 10 March 2023 (UTC)--RZuo (talk) 23:08, 10 June 2023 (UTC)[reply]

Allow character 䐑[edit]

I want to move Category:鯖小紀 to Category:䐑鯖小紀. 䐑 is blacklisted. Can anyone help? 維基小霸王 (talk) 12:08, 23 March 2023 (UTC)[reply]

Request to add a new file type to Wikimedia Commons[edit]

I would like to request that Wikimedia Commons include the m4a file type. the reason is that many people in Burma do not have enough money to buy a computer, so they mainly work on Wikimedia by phone. therefore, when recording audio with the phone, only one type of m4a is available, we encountered various difficulties in uploading the audio files with our recorded audio to Wikimedia Commons and Our actions are also delayed. as explained above, we would like to have access to the m4a file type on Wikimedia Commons, thanks.--𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 08:58, 13 October 2023 (UTC)[reply]

M4A is not a free format, so it can't be used on Wikimedia projects. Yann (talk) 09:41, 13 October 2023 (UTC)[reply]
@咽頭べさ i think, you can use com:v2c to convert audio files as well. you dont need a computer to use v2c. browser the website on your phone, select the file you want to upload, then select only "keep audio", then follow instruction to the end. RZuo (talk) 09:43, 13 October 2023 (UTC)[reply]
thank you very much 𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 10:09, 13 October 2023 (UTC)[reply]
Hi @RZuo, I tried following the link you gave me, but it doesn't work at all, but I need m4a to wav for the audio file, but now it is not available for audio files at all, only for video, see Reference by Intobesa.webm, I'm not very tech savvy, so if there are any other easy ways, please share, thanks 𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 11:21, 13 October 2023 (UTC)[reply]
Video na Wikimedia Commons, video2commons tutorial
@咽頭べさ after picking the file, unselect "keep video" and "import subtitles", then click green button, then is the place to edit filenames etc. dont edit the "uploads:..." string! RZuo (talk) 12:27, 13 October 2023 (UTC)[reply]
Thank you very much, but the content displayed in your video is not related to the audio file, Please show me m4a to wav. see my difficulties with audio files on Wikimedia Commons in File:Reference by Intobesa 2.webm and I still need help from you, thanks. 𝓓𝓻.𝓘𝓷𝓽𝓸𝓫𝓮𝓼𝓪|𝒯𝒶𝓁𝓀 06:42, 14 October 2023 (UTC)[reply]
why did you not click submit at 7m5s after filling up the form?? RZuo (talk) 08:15, 14 October 2023 (UTC)[reply]

Improving the filename blacklist[edit]

Change (Untitled|No[-_]?name|Unbenannt|Picture|Pict?|Image[mn]?|Img|Immagine|Clip|Photo|Foto|Bild|Scan[\W\d_]|Panorama|Sin_título|Capture)_?\P{L}*\.\w+ to \P{L}*(Untitled|No[-_]?name|Unbenannt|Picture|Pict?|Image[mn]?|Img|Immagine|Clip|Media|Photo|Foto|Bild|Scan[\W\d_]|Panorama|Sin_t[ií]tulo|Capture)_?\P{L}*\.\w+ to tackle filenames like "15 sin titulo27 20220826233348.png" and "Media 230915 080936.gif". JsfasdF252 (talk) 00:31, 12 January 2024 (UTC)[reply]

Non-BMP characters[edit]

See also phab:T297351

{{Edit request}} I think the following line should be removed:

.*[^\0-\x{FFFF}\p{Han}\p{Ahom}].* <casesensitive|errmsg=titleblacklist-custom-hidden-char> # Very few characters outside the Basic Multilingual Plane and CJK Unified Ideographs are useful in titles

and the following line

.*[\x{E000}-\x{F8FF}\x{FFF0}-\x{FFFF}].* <casesensitive|errmsg=titleblacklist-custom-hidden-char> # Surrogates, Private Use Area and Specials, including the Replacement Character U+FFFD

replaced with:

.*[\x{E000}-\x{F8FF}\x{FFF0}-\x{FFFF}\x{40000}-\x{10FFFF}].* <casesensitive|errmsg=titleblacklist-custom-hidden-char> # Surrogates, Private Use Area, Specials (including the Replacement Character U+FFFD) and unused planes

"Very few characters outside the Basic Multilingual Plane are useful in titles" may have been true in 2009 when this was added, but it is not at all true today. There are now over 100 scripts with characters outside the BMP (more than are encoded in the BMP), including scripts like Latin and Cyrillic. As well as Han (added in 2019) and Ahom (added last year), I'm aware of people reporting not being able to upload files using Warang Citi, Chakma and Brahmi.

I don't think it's sensible to continue adding scripts one-by-one, so I propose that non-BMP characters are handled the same way as BMP characters: allow them by default and exclude the ones we explicitly don't want, instead of the other way round. Non-BMP characters are well-supported these days and we already allow some non-BMP characters in filenames, so applications will already have problems if they don't support them.

The planes 4 to 13 (U+40000 to U+DFFFF) are still completely unused (not even any tentative assignments of blocks), so there's no reason for those characters to be in filenames any time in the foreseeable future. Plane 14 (U+E0000 to U+EFFFF) is for special purpose characters and planes 15 and 16 (U+F0000 to U+10FFFF) are private use characters, their BMP-equivalents are already explicitly excluded.

Here's an example in the API sandbox that can be used to test whether it works.

- Nikki (talk) 06:02, 16 January 2024 (UTC)[reply]

 Support Psubhashish (talk) 03:32, 17 January 2024 (UTC)[reply]
 Support. Some minorities reported to be unable to record their language on Wikimedia Lingualibre due to Wikimedia Commons restriction rejecting their script. Hugo en résidence (talk) 09:38, 17 January 2024 (UTC)[reply]
✓ Done – it’s a big change, but it sounds reasonable and this has been open for long enough with no objections --Lucas Werkmeister (talk) 18:51, 26 January 2024 (UTC)[reply]