MediaWiki talk:Titleblacklist

Welcome to the title blacklist noticeboard

The following instructions were copied from mw:Extension:Title Blacklist.

The disallowed titles list is maintained as a system message MediaWiki:Titleblacklist.

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

Foo <autoconfirmed|noedit|errmsg=blacklisted-testpage> 
Bar #No one should create article 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
• noedit — users are also unable to edit this page
• casesensitive — don't ignore case when checking title for being disallowed
• errmsg — the name of the message that should be displayed instead of standard

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. Generic filenames have their own custom error message, MediaWiki:Titleblacklist-custom-imagename.

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

Only administrators, page movers and template editors can override this list on all actions. When they override this list when creating or editing a page, MediaWiki:Titleblacklist-warning is displayed. Account creators can override this list on account creations only.

The disallowed usernames list is handled at meta:Title blacklist by adding entries with the <newaccountonly> parameter.

unblacklist request

Hi, i would like to get the word "object show" unblacklisted because this word has been unknownly blacklisted with "bfb", "bfdi", "battle for dream island", cary, micheal and others. I was trying to create my user page Threeobjectshow! (talk) 18:27, 28 January 2025 (UTC)

No. * Pppery * _{it has begun...} 18:33, 28 January 2025 (UTC)

why not? Threeobjectshow! (talk) 18:37, 28 January 2025 (UTC)

Because we aren't interested in letting more BFDI/object show/whatever nonsense in here. See WP:BFDI. * Pppery * _{it has begun...} 18:41, 28 January 2025 (UTC)

And we're not going to risk harm to the encyclopedia so that we can accommodate your choice of username. Pick another. —Cryptic 19:05, 28 January 2025 (UTC)

(See WP:Changing username for how to change your username). * Pppery * _{it has begun...} 19:11, 28 January 2025 (UTC)

I have a solution! Perhaps an administrator/page mover/template editor can create your user page (maybe even your user talk page) for you, @Threeobjectshow! They can maybe create a completely blank page, which you then may fill with (almost) anything you want! You should ask someone to create it for you. This would make everyone happy. You would get your user page, and Wikipedia would not get spammed with BFDI stuff. This is simply my suggestion to you, @Threeobjectshow! Crocusfleur (talk) 16:52, 26 June 2025 (UTC)

I am unfortunately not any of these things (yet), thus I sadly can't create your user page for you, @Threeobjectshow! Sorry. I would if I could. Crocusfleur (talk) 16:58, 26 June 2025 (UTC)

This doesn't work in the medium- or long-term - it would need admin(/pm/te) intervention for every page in that userspace, and in particular for talk page archives. —Cryptic 09:37, 1 July 2025 (UTC)

Protected edit request on 3 June 2025

Please add the phrase "kill all" to the blacklist, as this could be used to create attack pages with "kill all (insert ethnic, religious, demographic, or other group here)" in its title. RaschenTechner (talk) 17:29, 3 June 2025 (UTC)

 Not done TB rules are not added preemptively. And there are several legitimate pages with "kill all" in the title: kill all humans (a redirect from a catchphrase); Kill all men -> androcide (admittedly I might support deleting this at RfD); the songs "Kill All the Things", "Kill All Hippies", "Kill All Your Friends", the book Kill All Normies, the TV episodes "Kill All Others" and "First Thing We Do, Let's Kill All the Lawyers", the catchphrase Let's kill all the lawyers, an album and an EP titled Love Will Kill All, etc. On the contrary this seems to have only been used twice for vandalism in the history of Wikipedia: Kill all gays, Kill all niggers (as well as Kill allison which is only included by accident and Kill all the fags which seems to have been an NN song rather than an attack), in addition to a few inappropriate usernames which the modern-day title blacklist wouldn't stop. * Pppery * _{it has begun...} 19:43, 3 June 2025 (UTC)

"Bad user subpages (ending in /)"

Hi @JJMC89: I'm a little confused about the addition of User( talk)?:.+\/$, labeled as # Bad user subpages (ending in /).[1]
As a template editor, I'm actually not affected by that, but as a common editor I always found that ending very handy when testing templates and subtemplates in userspace. For example, when testing User:Est. 2021/Template/Example, I used to simply name the subtemplate User:Est. 2021/Template/Example/ and invoke it via {{/|parameter}}, instead of writing-out or copy-pasting countless times the longer forms {{/subtemplate|parameter}} and {{User:Est. 2021/Template/Example/subtemplate|parameter}} at every occurrence. I mean, you can test hundreds of {{/|parameter}} in a row in few seconds, while writing-out or copy-pasting the longer form at every row definitely slows down things a lot, and I don't see any positive side, nor any self-explanatory need for that. Is there any? Thanks in advance. — Est. 2021 (talk · contribs) 19:48, 21 June 2025 (UTC)

Hits here. —Cryptic 20:17, 21 June 2025 (UTC)

@Cryptic: Thanks for the link. I can see there are thousands of occurrences as well, as you brought up first (talk). I just made an example of how I used to exploit that at User:Est. 2021/sandbox/CURRENT [2] (subtemplate User:Est. 2021/sandbox/CURRENT/). It is very handy and fast, so I don't get why it is not allowed to common editors. That's a useful feature. Est. 2021 (talk · contribs) 22:01, 21 June 2025 (UTC)

Update: as another month passed, I'm inclined to remove that from the blacklist, but I'm gonna consult Wikipedia:Village pump (technical) first. Est. 2021 (talk · contribs) 15:25, 22 July 2025 (UTC)

I am inclined to remove this (and add a narrower rule specifically targeting ClueBot III badly subnested archives) unless JJMC89 provides a good explanation for the purpose of this rule. I personally think creating subpages without a name is dumb, but the purpose of the blacklist isn't to keep people from doing things I think are dumb in their userspace - if you think otherwise then more power to you.

JJMC89 hasn't edited since Cryptic poked this thread on his talk page; I'll give him a chance to respond first. * Pppery * _{it has begun...} 01:46, 29 July 2025 (UTC)

 Removed That rule since I still haven't heard from JJMC89. * Pppery * _{it has begun...} 18:08, 31 July 2025 (UTC)

Quaderni d’Italianistica

Apologies if this is the wrong place but maybe you can point me to the right one. This page is on the title blacklist. I want it to redirect to Italian_studies#Quaderni_d'Italianistica. What do? Thanks, Prezbo (talk) 18:11, 25 June 2025 (UTC)

Use a straight quote not a curly quote per MOS:CURLY: Quaderni d'Italianistica. * Pppery * _{it has begun...} 18:14, 25 June 2025 (UTC)

Thanks. Prezbo (talk) 18:17, 25 June 2025 (UTC)

Edit request 28 June 2025

Description of suggested change: Multipart request to cleanup multiple entries in the "Spam or salt evasion titles" section.

Diffs of requests:

Collapsed list of requested changes

1. −

   .*\+ *91[ -]*[0-9].*

   +

   .*\+ *91[ -]*\d.*

   Shorthand.

2. −

   .*l[o\x{043E}]v[i\x{0456}]f[m\x{043C}].* <antispoof>

   +

   .*lovifm.* <antispoof>

   <antispoof> already matches the \x{characters}, antispoof uses equivset and equivset's list can be seen here to verify this.

3. −

   .*[p\x{0420}\x{0440}][e\x{0435}][c\x{0441}][h\x{043D}][k\x{043A}]?u[r\x{0433}][o\x{043E}][uvw].* <antispoof>

   +

   .*pechk?uro[uvw].* <antispoof>

   <antispoof> already matches the \x{characters}, see #2.

4. −

   .*ale(x|kse[ijy]|xe[iy]).*?pech?k?uro[uv].*

   +

   .*ale(x|kse[ijy]).*?pech?k?uro[uv].*

   |xe[iy]) is never matched as (x| will always be lazy matched first. If this pattern used [uvw] like #3 above instead of [uv] then h? could be removed from this pattern as #3 would trigger regardless.

5. −

   .*pech?k?uro[uv].*?ale(x|kse[ijy]|xe[iy]).*

   +

   .*pech?k?uro[uv].*?ale(x|kse[ijy]).*

   Same as #4 above.

6. −

   .*ale(x|kse[ijy]|xe[iy]).*?bugatti.*

   +

   .*ale(x|kse[ijy]).*?bugatti.*

   |xe[iy] removed for the same reason as #4 and #5.

7. −

   .*((sachin.*?tomar)|(tomar.*?sachin)).*

   +

   .*(sachin.*?tomar|tomar.*?sachin).*

   Unnecessary groups.

8. −

   .*[Jj]ohn.*[Gg]alea.*

   +

   .*john.*galea.*

   Unnecessary character classes, matching is case-insensitive.

9. −

   .*((davide?.*?anselmi)|(anselmi.*?davide?)).*

   +

   .*(davide?.*?anselmi|anselmi.*?davide?).*

   Unnecessary groups.

10. −

    .*over.+the.+top.+(?:digital|agency|marketing|SEO|organi[sz]ation|search|company|business).*

    +

    .*over.+the.+top.+(digital|agency|marketing|SEO|organi[sz]ation|search|company|business).*

    No need to specify a group as non-capturing.

11. −

    .*amsu(d|dd)in.*atel.*

    +

    .*amsudd?in.*atel.*

    No need to use a group.

12. −

    .*((C\.R\..*?enkatesh|enkatesh.*?C\.R\.)).*

    +

    .*(C\.R\..*?enkatesh|enkatesh.*?C\.R\.).*

    Unnecessary group.

13. −

    .*[Jj]im.*eiss.*

    +

    .*jim.*eiss.*

    Matching is case-insensitive.
14. .*((.ilesh)|(.rabhat)).*(.aurya).* and .*((.ilesh)|(.rabhat)).*(.ricket).* can be combined and simplified into .+(ilesh|rabhat).+(aurya|ricket).* which will match exactly the same as the other two patterns.

15. −

    .*(Jay Silver).*((Music)|(music)|(Artist)).*

    +

    .*jay silver.*(music|artist).*

    Unnecessary groups, matching is case-insensitive. Intention of the original pattern is unclear, if the parenthesis around [Mm]usic and Artist were intended to be literal then .*jay silver.*\((music|artist)\).* is correct.
16. Category:M[o0]+[Ww][o0]+\d* and Category:W[o0]+[Mm][o0]+\d* can be combined and simplified into Category:(m[o0]+w|w[o0]+m)[o0]+\d* since matching is case-insensitive.

17. −

    .*(yassin|yasser).*ennassiri.*

    +

    .*yass(in|er).*ennassiri.*

    More targeted group.

18. −

    .*((?<!:))(chanda+n).*(mada+n).*

    +

    .*(?<!:)(chanda+n).*(mada+n).*

    Unnecessary group.

19. −

    .*Abhilash *Pillai.*

    +

    .*Abhilash[ ]*Pillai.*

    Unnecessary character class.

fifteen thousand two hundred twenty four (talk) 08:17, 28 June 2025 (UTC)

 Done All except the antispoof ones, since antispoof doesn't seem to work the way you think; antоny gordon (using the +436 character) is not blacklisted, for example * Pppery * _{it has begun...} 21:05, 28 June 2025 (UTC)

I'm slightly confused then, m:Extension:TitleBlacklist says that antispoof normalizes titles before matching, and the equivset antispoof uses here has all the characters in the above suggested changes as equivalent to the accompanying latin text. Using .*l[o\x{043E}]v[i\x{0456}]f[m\x{043C}].* for example: Line 41 here contains both U+006F "o - Latin Small Letter O" and U+043E "о - Cyrillic Small Letter O", line 35 both U+0069 "i" and U+0456 "і", and line 39 "m" and U+043C "м".

"antоny gordon (using the +436 character) is not blacklisted" – I'd expect it wouldn't be since U+0436 "ж" doesn't match any of those latin letters in equivset, but I'd expect that "αɳｔ0ռӯ ｇɵᴙðσՈ" would be, since all those characters are listed as equivalent.

I'd appreciate if you could help me understand where I've gone wrong here, I don't have a local mediawiki instance to test on so I've tried to follow what the docs appear to say. fifteen thousand two hundred twenty four (talk) 03:24, 29 June 2025 (UTC)

Sorry, I meant 43E, not 436 (which you could have confirmed from the actual link I used). αɳｔ0ռӯ ｇɵᴙðσՈ triggers a completely different blacklist rule higher up on the list ("Fullwidth Latin letters"), which makes it impossible for me to determine whether it triggers the lower rule because rules are evaluated top to bottom. If I try to munge that as little as possible to avoid other rules, I get Talk:Αɳt0ռӯ gɵᴙðσՈ, which isn't blacklisted - indeed even αntony gordon isn't blacklisted,

And I do have a local MediaWiki instance set up, but I didn't rely on it here; I actually made the changes, observed they caused things to be unblacklisted that shouldn't have been, and self-reverted; I'm just as confused as you are; maybe file a bug on Phabricator. * Pppery * _{it has begun...} 03:55, 29 June 2025 (UTC)

Its possible that antispoof is working the same as it does with usernames, it only triggers if a given name already exists. So if antony gordon existed only then would it match αntony gordon or Αɳt0ռӯ gɵᴙðσՈ. I'd assumed otherwise given m:Extension:TitleBlacklist (and common sense), but it might not be a bug at all. fifteen thousand two hundred twenty four (talk) 04:03, 29 June 2025 (UTC)

It's not that because Antony Gordön is blacklisted. * Pppery * _{it has begun...} 04:22, 29 June 2025 (UTC)

I've now found this open issue on phabricator that seems to be the root of the problem (and it seems you've found it too).

For those following along: antispoof rejects mixed-alphabet strings and won't normalize them, but titleblacklist ignores this rejection. αntony gordon mixes greek and latin characters, so antispoof rejects it and titleblacklist ignores that rejection. Antony Gordön only contains latin characters, so antispoof doesn't reject it and normalizes it to "antony gordon" as expected.

Thank you for your help and patience, hopefully its something that'll be fixed soon. fifteen thousand two hundred twenty four (talk) 04:41, 29 June 2025 (UTC)

Yeah, that's it. I had apparently found that once, but had forgotten about it. * Pppery * _{it has begun...} 04:46, 29 June 2025 (UTC)

I still think encouraging this kind of makework is a bad idea, and the above is kind of why. It's good and all that the accidentally-unlisted title is one of the ones you verified afterward; next time it may well not be. If there's am actual, functional change being proposed or a measurably poorly-performing regex being remediated, by all means do it. But if all you're doing is reformatting so that the rule looks prettier, then it's not worth the risk or your time. —Cryptic 09:46, 1 July 2025 (UTC)

I don't feel like I wasted my time reviewing this request; it inspired me to submit a patch to fix a longstanding software bug relating to antispoof rules that I'm sure would have bitten someone else in the future instead. * Pppery * _{it has begun...} 15:45, 1 July 2025 (UTC)

Inconsistent redirects

Wikipedia:TBL, Wikipedia:Titleblacklist, Wikipedia:TITLEBLACKLIST, and Wikipedia:TITLE BLACKLIST redirect to MediaWiki:Titleblacklist, whereas Wikipedia:Title blacklist and Wikipedia:TitleBlacklist redirect to Wikipedia:Title blacklisting. Should all of them redirect to the local title blacklist (the former) or the essay page (the latter)? AlphaBeta135talk 18:38, 28 June 2025 (UTC)

I would point them all to the essay. * Pppery * _{it has begun...} 21:05, 28 June 2025 (UTC)

 Done without objections AlphaBeta135talk 23:47, 1 July 2025 (UTC)

Edit request 1 July 2025

Description of suggested changes:

Thirteen requests which reduce line count in a straightforward manner. Five additional potential makework and higher-risk requests have been listed in a separate section to address raised concerns.

Suggestions:

Reduce linecount

# INVERTED QUESTION MARK WITH NON-LATIN TEXT

• .*¿.*[^\p{Latin}\P{L}].*
.*[^\p{Latin}\P{L}].*¿.*
  can be replaced with:
  (?=.*¿).*[^\p{Latin}\P{L}].*

# EXCESSIVE PUNCTUATION OR REPETITION

• .*‽‽.* <moveonly>
.*¿¿.* <moveonly>
  are already matched by:
  .*[!?‽¿]{2}(?<!!!).* <moveonly>

# ATTACK TITLES AND/OR PAGE MOVE VANDALISM TARGETS

• .*chaos.{0,7}apper.*
.*chaos.{0,7}usic.*
.*chaos.{0,7}ntert.*
.*chaos.{0,5}ashington.*
.*chaos.{0,5}iscography.*
.*chao\$.*
  can be replaced with:
  .*chao(\$|s.{0,7}(apper|usic|ntert)|s.{0,5}(ashington|iscography)).*
• .*customer support (phone|number).*
.*tech support (phone|number).*
  can be replaced with:
  .*(customer|tech) support (phone|number).*
• .*on wh33ls.*
.*on whiels.*
.*on wiels.*
  can be replaced with:
  .*on w(h33|h?ie)ls.*
• .*on rails.* <moveonly>
.*on treads.* <moveonly>
  can be replaced with:
  .*on (rail|tread)s.* <moveonly>
• .*[cċĉ¢сćĉçč][óòôöõǒōŏǫőøόδοσоʘǿọơờởỡớợồổỗốộ][cċĉ¢сćĉçč][kķкќқҝҡҟӄ].*
.*[ċĉ¢сćĉçč][oóòôöõǒōŏǫőøόδοσоʘǿọơờởỡớợồổỗốộ][cċĉ¢сćĉçč][kķкќқҝҡҟӄ].*
.*[cċĉ¢сćĉçč][oóòôöõǒōŏǫőøόδοσоʘǿọơờởỡớợồổỗốộ][ċĉ¢сćĉçč][kķкќқҝҡҟӄ].*
.*[cċĉ¢сćĉçč][oóòôöõǒōŏǫőøόδοσоʘǿọơờởỡớợồổỗốộ][cċĉ¢сćĉçč][ķкќқҝҡҟӄ].*
  can be replaced with:
  .*[cċĉ¢сćĉçč][oóòôöõǒōŏǫőøόδοσоʘǿọơờởỡớợồổỗốộ][cċĉ¢сćĉçč][kķкќқҝҡҟӄ](?<!cock).*
• .*giant penis.*
.*huge penis.*
  can be replaced with:
  .*(giant|huge) penis.*
• .*\bnimp\.org.* is already matched by .*nimp.org.*

# Prevent accidental creation of pages with some double namespace prefixes

• User( talk)?:User( talk)?:.*
User( talk)?:Template( talk)?:.*
User( talk)?:Draft( talk)?:.*
  can be replaced with:
  User( talk)?:(User|Template|Draft)( talk)?:.*
• Wikipedia( talk)?:User( talk)?:.*
Wikipedia( talk)?:Wikipedia( talk)?:.*
Wikipedia( talk)?:Help( talk)?:.*
Wikipedia( talk)?:Draft( talk)?:.*
  can be replaced with:
  Wikipedia( talk)?:(User|Wikipedia|Help|Draft)( talk)?:.*
• Template( talk)?:Template( talk)?:.*
Template( talk)?:Portal( talk)?:.*
  can be replaced with:
  Template( talk)?:(Template|Portal)( talk)?:.*
• Draft( talk)?:User( talk)?:.*
Draft( talk)?:Category( talk)?:.*
Draft( talk)?:Draft( talk)?:.*
  can be replaced with:
  Draft( talk)?:(User|Category|Draft)( talk)?:.*

Potential makework and higher-risk suggestions, feel free to ignore

• −

  .*[\p{Z}]{2}.*

  +

  .*\{p}Z{2}.*

  Makework – Unnecessary character class.

• −

  .*Rap(e|es|ing) (babies|children|kids).*

  +

  .*Rap(es?|ing) (babies|children|kids).*

  Makework – Less alternation.

• −

  .*[Gg]oogle[A-Za-z0-9]*\.html*

  +

  .*google[a-z0-9]*\.html*

  Makework – Matching is case-insensitive. Is the ending * intentional or would a ? or .* be more appropriate?

• −

  Wikipedia:Today's[ _]featured[ _]article\/[a-zA-Z]+[ _][0-9]+,[ _][0-9]{4}.*

  +

  Wikipedia:Today's featured article\/[a-z]+ [0-9]+, [0-9]{4}.*

  Higher-risk, makework – Matching is case-insensitive, underscores are converted to spaces according to mw:Extension:TitleBlacklist#:~:text=Underscores and the code on phabricator. This pattern has not been tested on a mediawiki instance.
• File:.*(\,|\.)(png|gif|jpe?g|tiff?|xcf|pdf|mid|ogg|ogv|svg|djvu|oga|flac|opus|wav|webm|webp)(\ |\,)?\.(png|gif|jpe?g|tiff?|xcf|pdf|mid|ogg|ogv|svg|djvu|oga|flac|opus|wav|webm|webp)
File:.*(\ |\,)\.(png|gif|jpe?g|tiff?|xcf|pdf|mid|ogg|ogv|svg|djvu|oga|flac|opus|wav|webm|webp)
  can be combined into:
  File:(?(DEFINE)(?'ext'(png|gif|jpe?g|tiff?|xcf|pdf|mid|og[gva]|svg|djvu|flac|opus|wav|web[mp]))).*([ ,]\.(?&ext)|[,.](?&ext)\.(?&ext))
  Higher-risk.
  • Converted extension list into a named capture group for easy reuse and maintenance ((?'ext' ... )).
  • Converted alternations in the extensions group into character classes where applicable (og[gva] and web[mp]).
  • Converted groups into character classes ((\ |\,) into [ ,], (\,|\.) into [,.]).
  • Removed duplicated functionality ((\ |\,)? from pattern 1).
  • Merged patterns.

Test cases at regex101: pattern 1 "double extension", pattern 2 "unconventional spacing", and new pattern. This pattern has not been tested on a mediawiki instance.

fifteen thousand two hundred twenty four (talk) 11:39, 1 July 2025 (UTC)

I have done a few of the straightforward changes. I haven't done: INVERTED QUESTION MARK WITH NON-LATIN TEXT, Chaos rules, cock rules, since I feel like rewriting several relatively straightforward cases into one using advanced regex features may not be worth it and I'm kind of coming around to Cryptic's position above there. I haven't done double namespace prefixes since I feel that listing the explicit namespaces disallowed each is clearer despite being longer. And finally the first "makework" change doesn't seem to make sense; you don't seem to realize what the /p modifier does (or maybe you made a typo) * Pppery * _{it has begun...} 15:58, 1 July 2025 (UTC)

Typo .*\p{Z}{2}.* is the intended version, I had mused about suggesting .*\pZ{2}.* but decided to cut any cosmetic changes, must have re-added the brackets around the wrong character. Those are all the changes I'll be suggesting. Thank you. fifteen thousand two hundred twenty four (talk) 16:12, 1 July 2025 (UTC)

Edit request 9 September 2025

Description of suggested change: Hello. I can't create the page "Tɕʼ" because it's on the blacklist. Please remove it from the blacklist. I think the thing that is blacklisted is the symbol ɕ, and it's weird an IPA symbol and other symbols in the entry ".*[ℂ℃℄ɕƌʥℇ℈℉ℊℋℌℍℎℏℐ‼ℑℒℕ℗℘ℙℚℛℜℝ℞℟℣ℤℨ℩ℬℭ℮ℯℰℱℲℳℴℹ℺⅁⅂⅃⅄ⅅⅆⅇⅈⅉⅎ].* <casesensitive> # Select Unicode Letterlike Symbols (excluding Kelvin, Angstrom and Ohm signs, see talk)" are on the blacklist.

Diff:

−

.*[ℂ℃℄ɕƌʥℇ℈℉ℊℋℌℍℎℏℐ‼ℑℒℕ℗℘ℙℚℛℜℝ℞℟℣ℤℨ℩ℬℭ℮ℯℰℱℲℳℴℹ℺⅁⅂⅃⅄ⅅⅆⅇⅈⅉⅎ].* <casesensitive> # Select Unicode [[Letterlike Symbols]] (excluding Kelvin, Angstrom and Ohm signs, see talk)

+

BodhiHarp 20:11, 9 September 2025 (UTC)

@BodhiHarp Is there a reason why you can't just ask a administrator (like me to create the page for you?) I see this as a one-off exception and not a reason to remove the rule from the titleblacklist ? Sohom (talk) 00:04, 1 October 2025 (UTC)

See this and search for "unilateral". BodhiHarp 01:02, 1 October 2025 (UTC)

I've created it. —Cryptic 01:42, 1 October 2025 (UTC)

Protected edit request on 9 October 2025

Add the words "Holocaust", "Nazi" and "Hitler" to the title blacklist. I'm surprised HoIocaust (a misspelling) is on the list but not the correctly spelled word. Make both case insensitive.

It is a sensitive subject and I have a feeling many vandals will try to make pages with either word in the title as a joke, and I don't like that. DetectiveClarinet15 (talk) 04:07, 9 October 2025 (UTC)

 Not done, no proof this is necessary and would likely prevent creation of proper articles. CoconutOctopus talk 14:33, 9 October 2025 (UTC)

Yeah. There's almost 9000 existing mainspace pages matching this pattern, including bunches of false positives particularly for "nazi" ("Internazionale", "Ashkenazi", and "Nazim" repeatedly jumped out at me while the results were scrolling by). Blacklisting would interfere with talk page creation and archiving, nominations for deletion, peer and good article reviews, you name it for all of these. About 8000 deleted titles too, granted, with more than their share of G5s among the deletion reasons; but comparatively few saltings (about 50). —Cryptic 15:01, 9 October 2025 (UTC)

Why do we blacklist characters

Why do we blacklist characters? - BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 05:33, 21 October 2025 (UTC)

We blacklist titles that have a history of being disruptive here on our English language project. — xaosflux ^Talk 09:41, 21 October 2025 (UTC)

Mis-using certain characters can be used to obfuscate names in unhelpful ways. Others may be used abusively, such as the swastika character, or have no reasonable purpose for ever including in a user or page name, or may be used to disrupt page layout at a technical level. Note that in the rare cases one of these characters does need to be used (as see above) an administrator can override the blacklist. — The Anome (talk) 09:53, 21 October 2025 (UTC)

Delist BFDI (and unsalt)

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.

---

Publication of a new source has caused the topic of Battle for Dream Island to cross the notability threshold.

• See discussion at: Wikipedia talk:Why is BFDI not on Wikipedia?#New source

Work on the BFDI draft by experienced editors has led to the creation of content which shows that a policy-compliant encyclopedia article is possible. As an NPP who reviews AfC submissions, I consider the draft as passing my review.

• See Draft:Battle for Dream Island

Two requests, based on the above:

1. To administrators processing the titleblacklist: Please remove Battle for Dream Island-related rules.
2. (Separately, to keep this concentrated) To the salting admin User:Ritchie333: Please unsalt Battle for Dream Island.

—Alalch E. 09:56, 22 October 2025 (UTC)

Just for the record, I only salted the article because I found a consensus to do so at Wikipedia:Articles for deletion/Battle for Dream Island as an uninvolved admin; furthermore the consensus to salt was endorsed at deletion review here. (I have no interest in Battle for Dream Island and I'm not even sure what it is) Consequently I am happy to unsalt if consensus has been found that the topic is now notable (ie: nobody's going to want to AfD it again). Ritchie333 ^{(talk) (cont)} 10:03, 22 October 2025 (UTC)

Thanks. Then, a deletion review should be started. I might start one later. —Alalch E. 10:10, 22 October 2025 (UTC)

Deletion review is the correct option here. Per WP:SALT "Editors wishing to re-create a salted title with appropriate content should either contact an administrator (preferably the protecting administrator), file a request for reduction in protection level, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.". To be clear, if consensus at such a review is found to be "allow recreation" or something similar, then any administrator is free to unsalt the title without needing to consult me. Ritchie333 ^{(talk) (cont)} 10:17, 22 October 2025 (UTC)

I've been monitoring this (I'm the admin who recreated the draft). I still think we need a consensus on one source before this is mainspaced, but if that is passed then I'm OK to do the necessary un-salting etc. to achieve this. I don't think a DRV is necessary because ultimately we are not recreating the article originally deleted, and if the second source we are looking at passes the discussion at RSN because in that case we would have two instances of IRS SIGCOV, and thus a reasonably-arguable WP:GNG pass. Whether or not anyone's going to try to AFD it at that point is impossible to say - someone tried to MFD the draft shortly after creation but was prevented from doing so by the title-block - but there wouldnt be a very strong chance of a successful AFD against it. FOARP (talk) 10:37, 22 October 2025 (UTC)

@Ritchie333: Above, FOARP, who is an administrator, has announced that he will create the article through your creation protection, based on a supposedly pending conclusion about a source at RSN. Namely, it is supposed that editors at RSN should decide whether a source that is obviously a reliable source (and no one has said that it is not) contains significant coverage, which immediately predicates the determination of notability. But RSN is not a notability forum, it is concerned with reliability of sources, not whether they confer notability, and there shouldn't have been such an RSN filing absent a concrete worry that a source is not reliable for a certain claim — there is no such worry. I think it's great that FOARP apparently wants to create the article, but this RSN business is just an excess of process and will not give any special authority to FOARP to create the article through your protection over any other editor. He would be following his editorial judgement ultimately, just like I am following my editorial judgement in wanting to create the article.

Do you have any comment on this disagreement between FOARP and me about starting a deletion review? —Alalch E. 12:57, 22 October 2025 (UTC)

I think an RSN discussion is a low-drama way of short-cutting the inevitable litigation which is going to happen over this source. It's also a perfectly good place to get feedback on how people would characterise a source, including whether or not they think it's notability-sustaining. There are concrete reasons why this might be seen as not IRS SIGCOV, including it being something that some people would describe as a blog, and it potentially being something that some people would describe as an interview. So let's get feedback on that from people who aren't involved closely with the issue (EDIT: indeed, we're already getting that feedback).

Let me also say that jumping around and trying to force the process like this is why this article got blocked in the first place. Let's take the time to get this right. FOARP (talk) 13:39, 22 October 2025 (UTC)

DRV (not necessarly now) seems to be part of doing it right like Ritchie333 said. Skipping it and going straight to mainspace with this mega-salted thing seems likely to increase drama. Gråbergs Gråa Sång (talk) 13:50, 22 October 2025 (UTC)

Exactly this. Since the article's notability has been so fought-over in the past few years to the point it generated an essay, we need to make sure a consensus to reverse that is watertight and looked at by as many people as possible. Otherwise I can predict an ANI thread complaining about "unilateral overriding" of something. Ritchie333 ^{(talk) (cont)} 10:41, 23 October 2025 (UTC)

RSN is not a good place and nothing will happen there, and DRV is a good place and is a low-drama forum. The salting admin said "go to DRV", citing a policy saying "go to DRV". You are wrong to characterize anything I have done as "forcing the process". Instead, the RSN idea is an unnecessary procedural improvisation and an excess of process. At DRV, there is a widely accepted view that DRV is not necessary when the salting admin can be asked to unsalt, removing the need to involve other editors. That request can be granted or declined. Here, it was declined, which is just fine. That is a best practice and not forcing the process. I asked Ritchie, he wouldn't unsalt—escalate to DRV. That is the process. —Alalch E. 13:52, 22 October 2025 (UTC)

Btw, if a DRV is started, please note at Draft talk:Battle for Dream Island that it's going on. Gråbergs Gråa Sång (talk) 14:02, 22 October 2025 (UTC)

OK, well, good luck with that. FOARP (talk) 14:07, 22 October 2025 (UTC)

Now at DRV: Wikipedia:Deletion review/Log/2025 October 25#Battle for Dream Island. ObserveOwl (talk) 13:51, 25 October 2025 (UTC)

DRV closed as recreation allowed. Can an admin now remove it from the blacklist? (Also maybe other related terms like ".*object.*show.*" should be removed so that redirects can be created.) ObserveOwl (talk) 15:32, 1 November 2025 (UTC)

 Done by Toadspike in Special:Diff/1319897249. SuperPianoMan9167 (talk) 16:55, 1 November 2025 (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.

ʖ works?

Why can you create pages with this character despite being on the title blacklist? I tested it and it works. Non-admins, test combinations like ʖ̼ or ʖʼ and it will work, though ʖɕ for example won't work because ɕ in on the titleblacklist. - BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 20:42, 26 October 2025 (UTC)

The only entry where this character (explicitly) appears is marked <moveonly>, so you can create titles containing it but not move other pages to titles containing it. —Cryptic 20:54, 26 October 2025 (UTC)

ɕ

Can someone show me examples of abuse from this character that is on the titleblacklist. - BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 21:57, 26 October 2025 (UTC)

There aren't any non-revdeleted/oversighted pages that abused this character in their title, either currently-existing or -deleted. However, in most such cases, I would expect most such abuses to be revdeleted or oversighted, and the only practical way to find them can't see through that. There are numerous other similar characters in the same rule that have been abused in this way; about the tamest they get is User:R℮dwolf24.

Even lacking such specific examples, though, I'd rather not unblacklist this. If there are other redirects you want created that contain this character like tɕʼtɕʼ, I'm willing to do that, or you can ask at WP:AFC/R. —Cryptic 23:16, 28 October 2025 (UTC)

Pyccᴋᴎᴎ̆

What about creating this? It's a Latin approximation for Русский, a Russian word. - BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 04:47, 10 November 2025 (UTC)

No, neither are Russian words. Русский is, and it already exists. —Cryptic 05:35, 10 November 2025 (UTC)

I accidentally misspelled Русский with a Greek kappa. - BᴏᴅʜıHᴀᴙᴩ (talk, contributions) 05:56, 10 November 2025 (UTC)

Protected edit request on 25 November 2025

Per Wikipedia:Miscellany for deletion/Draft:Joey Primiani (courtesy ping Salvio giuliano as closer), please add

.*\bj.*\bprimiani.*      # Wikipedia:Miscellany for deletion/Draft:Joey Primiani

to the "# Spam or salt evasion titles" section. Hits are at quarry:query/99297. I am involved. —Cryptic 11:40, 25 November 2025 (UTC)

 Done I actually was close to adding that rule sua sponte after having seem your nomination at the MfD (but I happened to check the edit request queue before I noticed the discussion was closed). * Pppery * _{it has begun...} 16:55, 25 November 2025 (UTC)

Trying to update club badge

Trying to add our new club badge to relate the old badge. Nahnuk (talk) 13:02, 2 December 2025 (UTC)