This is an archive of past discussions about MediaWiki:Titleblacklist. 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.
Interestingly there is already an entry for this phone number. However the spammer has found a way around it using fullwidth characters. I'll try to adjust it now. If this practice becomes more widespread someone may have to adjust all the entries. BethNaught (talk) 12:34, 15 October 2016 (UTC)
Is there really a need for any page title to have a number with ten or more digits in it, obfuscated or not? This would catch essentially all phone numbers available to spammers. I can't see why any username should need such a long digit string in it, either. -- The Anome (talk) 12:45, 15 October 2016 (UTC)
@The Anome: As far as I know, there are no current such titles. I'd be inclined to add a autoconfirmed entry to disallow titles with long digit strings, yes. I wonder if an edit filter would also work but we'd need to know if there is a legit reason to add such a digit in particular namespaces. Jo-Jo Eumerus (talk, contributions) 13:36, 16 October 2016 (UTC)
Just be creative with your regex, as they will adapt quickly... 1-800 would become l--8__o__o for example...
That filter can debofuscate strings like "l--8__o__o". As for blocking strings of 10 digits: I don't know -- it's not something I can easily search for. The full-width numbers should have very little false positives though (but again, impossible to search for). MER-C00:35, 19 October 2016 (UTC)
(([0-9]|[oi\!]).*){10} should match any title with 10 digits in it (or common substitutes, add as needed) regardless of what else is in the title. So would match "0xxx1xxxxx2xx xxx3x456xxx xx7xxx xx8x9", for example. It would also match 10 occurrences of the "other" characters... CrowCaw22:58, 20 October 2016 (UTC)
Yep, rather dangerous in that form. Could be tweaked of course to lazy up the inter-character wildcard, and if applied to <autoconfirmed> for creation, should limit the disruption. The more open the regex becomes to catch the evil, the more good will get tied up, unfortunately. This may not be the best approach, I was just thinking out loud in response to the above questions. CrowCaw20:18, 21 October 2016 (UTC)
([\doi!]([ -_]{0,3})){7,10} should match: A digit or lookalike followed by between zero and 3 of space, hyphen, or underscore (to catch "1 - 2 _ 3...), repeated between 7 and 10 times. That returns "only" 909 existing titles (only a small number are in mainspace and some of which are not likely redirect titles, such as Gooooooooogle, so again, setting <autoconfirmed> should minimize legit disruption. CrowCaw18:05, 24 October 2016 (UTC)
I don't work over there so I have no idea whether it will be approved or not. Probably best to ask there, and if no we can locally blacklist just for the title (the global blacklist disallows both usernames and titles). Jo-Jo Eumerus (talk, contributions) 16:23, 21 November 2016 (UTC)
@Samtar: Thanks. It looks like you've put a leading space on there by accident - is there any danger that'll be taken as part of the regexp? --McGeddon (talk) 17:30, 9 December 2016 (UTC)
Hi - I saw this page and realised from the text that it should be "Van Mladen" - so I tried to move it. Turns out "Peer Van Mladen" is a blacklisted page so I tagged it for speedy. I thought I should mention it on here also, just in case someone removes the tag. Happy New Year MarkDask15:37, 29 December 2016 (UTC)
Request the addition of "Google Boys Arimalam" and combinations thereof
MSGJ, the nonsense was recreated this morning under 2 new variants of the title at :
09:32, 31 December 2016 Google Boys Arimalam (disambiguation) (hist) [38 bytes] Ayushmaan Bhava 24 (talk | contribs) (←Created page with '{{redirect}}') (Tag: very short new article)
09:31, 31 December 2016 Google Boys Arimalam Google Boys (hist) [59 bytes] Ayushmaan Bhava 24 (talk | contribs) (←Created page with '{{redirect|Google Boys Arimalam}}')
I would like to have the name Davide Anselmi and Anselmi Davide added to the title/word blacklist. Long story short, there's some sockpuppetry surrounding this and the guy's basic MO is to try to create pages that claim some pretty easily disproven stuff. The guy claims to have had Stephen Sondheim (who is known for his musical career) as a cinematographer on a film that gained zero coverage. Lately he's been trying to attach himself to various films, like claiming that he worked on the sound for the Maze Runner series, which again, didn't happen. The socks have been mildly creative with the various names, which have run the range from Davide Anselmi, Anselmi Davide, Davide Anselmi (composer), Davide Anselmi (composer), and Anselmi Davide (Drummer). Hopefully making it so he can't create an article will help deter him. If there's a way to prevent him from putting his name on Wikipedia at all, that might be good as well. Tokyogirl79 (｡◕‿◕｡)05:23, 20 October 2016 (UTC)
.*((david[e]*.*?anselmi)|(anselmi.*?david[e]*)).* should do the trick, at least until he starts adapting, then its easy enough to add more conditions. CrowCaw21:52, 20 October 2016 (UTC)
Christian/Christine Weston Chandler and other names
Hey, I was wondering if we could get the following names blacklisted from being added:
Christian Weston Chandler
Christian Chandler
Christine Chandler
Christine Weston Chandler
Sonichu
It isn't nearly as bad as it once was, but there are still periodically attempts to re-add this person and their family members to Wikipedia, done either as a joke or as a good faith attempt. This person is pretty infamous for their actions on the Internet, enough to where there are a group of people who have a wiki devoted entirely to their life and some of the trolling efforts done against them.
You can see some efforts that were clearly done as a joke here and there's a whole history of it at the Ruckersville, Virginia article, both good faith edits and joke edits. The talk page has a long section about him as well. There are also quite a few AfDs for articles about Chandler, their creation, and their brother. (2009 AfD, 2012 deletion review, 2010 AfD, 2010 AfD, 2016 AfD)
The attempts at this have greatly slowed over the years so this might be a bit late, but I figured that it'd be worth adding to the blacklist. Tokyogirl79 (｡◕‿◕｡)11:54, 19 January 2017 (UTC)
Looks to me like something which should be handled by WP:SALT. The expression Christi(an|ne) (W(\.|eston) )? Chandler should cover the first 4 you wrote on the list above, as well as the first 2010 AfD you mentioned; however, you could also SALT all 6 titles as they become problems (some already have been). עוד מישהוOd Mishehu12:01, 24 January 2017 (UTC)
Well... the issue here isn't so much that someone will try to create the articles as much as there are people who try to add this person and her creation into other articles like Ruckersville, Virginia or anything else that might be related to this person. Like I said, it's slowed over the years but it still happens. Most of the people that do this sort of thing are aware that any new page gets salted, so their game is to put her name into other articles. Tokyogirl79 (｡◕‿◕｡)07:08, 3 February 2017 (UTC)
Any way to create blacklisted redirect?
There is a constellation Boötes which obviously includes a diacritic. The stars in that constellation are named with green letters plus this constellation name (actually its genitive form Boötis). The titles of these articles are generally latinised, for example beta Boötis but a redirect is generally provided with the actual Greek letter. For most constellations this is not a problem, for example α Andromedae, but for α Boötis it is not allowed due to a blacklist entry here. As a result the redirects for this constellation are a mess, some exist without the diacritic, some with "oe" in place of it, and many are just missing.
I'm trying to tidy this up, so is there any way to bypass the regex and create these redirects, or am I stuck with the workarounds? There would be approximately 26 of them. No other constellation has this issue. Lithopsian (talk) 15:55, 10 February 2017 (UTC)
The title blacklist can be overridden with the right user rights. Ask an admin (preferably one who knows about astronomy) to do it for you. BethNaught (talk) 15:58, 10 February 2017 (UTC)
Thanks. I'll get together a list and do that. Turns out about half the stars in Boötes already have redirects with the diacritic so I'm even more keen to get it all consistent. Lithopsian (talk) 14:14, 12 February 2017 (UTC)
Because the name of the page is wrong, I tried to move the page User:WDCDECDCDC/userbox to User:WDCDECDCDC/My userbox, but I couldn't move it, and the table says:
"User:WDCDECDCDC/userbox" cannot be moved to "User:WDCDECDCDC/my userbox", because the title "User:WDCDECDCDC/my userbox" is on the title blacklist. If you feel that this move is valid, please consider requesting the move first."
Sorry I am not familiar with this page or the required syntax. You could ask MER-C as he/she seems most active in updating this page recently. — Martin (MSGJ · talk) 09:15, 3 March 2017 (UTC)
As Blocklogannotation never got off the ground, should we remove it from the titleblacklist? I see no reason to keep it any longer. – Train2104 (t • c) 03:28, 30 March 2017 (UTC)
The software for the title blacklist still displays the "Start the _______ page" even if it is blacklisted. It should say "This title matches an entry on the blacklist, so only administrators can create it. UpsandDowns1234 (🗨) (My Contribs) 19:35, 24 April 2017 (UTC)
Jonah Bryson
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Hi! I was wondering if someone could add Jonah Bryson and The Fight for Bala to the blacklist. Per the comments at this AfD, it looks like Bryson has been trying fairly hard to get himself added to Wikipedia and this is just the latest attempt. Tokyogirl79 (｡◕‿◕｡)14:05, 12 April 2017 (UTC)
Not done I'm not comfortable with this one, everything here if nominated for deletion is collateral damage. (Plus the given regex does not work.) MER-C04:48, 28 April 2017 (UTC)
I propose to add \D*1488\D* <newaccountonly>. "1488" has become a common code for identifying oneself as a neo-nazi on the internet and its use in usernames violates our policy against disruptive or offensive usernames. See [1] and Fourteen Words#14 and 88. There are over a dozen such blocked usernames on English Wikipedia, including User:1488Nate from just last month. The proposed regex looks for non-digit characters on either side of the 1488, so it would not block longer numbers that include 1488 by accident. Kaldari (talk) 17:33, 19 April 2017 (UTC)
@Xaosflux: I tried proposing it there and they said they wanted evidence that there was some consensus for it at the affected projects (mostly English and Russian Wikipedias). Any idea how I would show such consensus? Should I just start a discussion here rather than a request? Kaldari (talk) 02:36, 9 May 2017 (UTC)
Emoji that use variation selectors, emoji modifiers, regional indicator symbols, or (in the next version of Unicode) tags are also protected from creation. They too should be whitelisted. Gorobay (talk) 13:38, 23 March 2017 (UTC)
I'm curious to find out where the request for this blacklist entry was placed, or who added the respective blacklist entry to this page. I can't figure it out myself because I cannot comprehend almost any of the edit history of MediaWiki:Titleblacklist. (I mean, if this blacklist entry is removed, titles such as the following could be created, all of which are skintone and hair color variations of 🙎 present on at least Apple devices: 🙎🏻, 🙎🏼, 🙎🏽, 🙎🏾 and 🙎🏿.) Steel1943 (talk) 14:44, 23 March 2017 (UTC)
It was added in 2008. This was presumably because non-BMP characters are not used in English, so they are only useful as single-character redirects (allowed by the whitelist) or for vandalism. However, what appears to the user to be a single character may be encoded as multiple Unicode code points. This has been an issue for years, and not just for emoji, but emoji make the issue more prominent. Gorobay (talk) 15:23, 23 March 2017 (UTC)
Is anyone opposed to it? I figured the hold-up is because no one knows what such an entry would look like. --Tavix(talk)18:21, 30 March 2017 (UTC)
@Tavix: Per the above, it seems as though Gorobay already identified the line in the blacklist that is causing these title restrictions. I'd say that if Gorobay is 100% that is the line that is causing this restriction, you could probably make the change yourself. Steel1943 (talk) 18:36, 30 March 2017 (UTC)
A removal of that line might create other issues (I have no idea though, I've never looked into it). I figured it'd be a modification to the whitelist line that allows for single-character unicode redirects (or a new line completely?). --Tavix(talk)18:42, 30 March 2017 (UTC)
Yes, I’d say it’s safer to modify that line of the whitelist, something like ^(Talk:)?(.[\x{FE0E}\x{FE0F}\x{1F3FB}-\x{1F3FF}]?|[\x{1F1E6}-\x{1F1FF}]{2}|.[\x{FE0F}\x{1F3FB}-\x{1F3FF}]?((\x{200D}.[\x{FE0F}\x{1F3FB}-\x{1F3FF}]?)+|[\x{E0020}-\x{E007E}]+\x{E007F}))$. This overgenerates a lot to be forwards-compatible and easier to read. I didn’t test it. Gorobay (talk) 00:08, 31 March 2017 (UTC)
Why is this title blacklisted for a draft? It exists for an article, and I am trying to move the article to draft space because it is obviously incomplete. Robert McClenon (talk) 22:54, 27 May 2017 (UTC)
I've draftified it. I didn't see any warnings about the blacklist, though I'm a TE so I'm not sure what warnings, if any, I should've seen. – Train2104 (t • c) 01:27, 28 May 2017 (UTC)
Please allow move
Trying to move page SIGARCH to "ACM SIGARCH" to follow general convention on ACM special interest groups being prefaced with the "ACM" - and the associated conferences being named without the "ACM" prefix. I tried to move the page SIGARCH to ACM SIGARCH, but I couldn't move it, and the table says:
"SIGARCH" cannot be moved to "ACM SIGARCH", because the title "ACM SIGARCH" is on the title blacklist. If you feel that this move is valid, please consider requesting the move first."
Please see Association for Computing Machinery for more information - the large organization info box shows Special Interest Groups at the top and also includes links to conferences. All SIG groups should probably be moved en masse to "ACM SIGNAME".
That's odd, I don't see it on the blacklist, or the global blacklist, and in fact you yourself created ACM SIGARCH a few days ago, which wouldn't have been possible if it was blacklisted. I'm going to be bold and move the article; I am open to reverting and trouting as appropriate if this was circumventing anything. CrowCaw22:54, 6 June 2017 (UTC)
@Crow and Cypherquest: It appears to be this rule: .*\p{Lu}(\P{L}*\p{Lu}){9}.* <casesensitive | moveonly> # Disallows moves with more than nine consecutive capital letters – Train2104 (t • c) 22:59, 6 June 2017 (UTC)
Yep, thats the one. This appears to be otherwise uncontroversial so your best bet is to request the moves at WP:RM, describing the blacklist restriction preventing the move, so that only admins can move it. I'm unable to, even as a Page Mover. CrowCaw23:02, 6 June 2017 (UTC)
Will do - there are several pages like this that perhaps could/should be moved. We appreciate the help diagnosing the violation - and the help with moving this one. Cypherquest (talk) 00:14, 7 June 2017 (UTC)
On Wheels
In this line:
.*[OÓÒÔÖÕǑŌŎǪŐŒØƏΌΟΩῸὈὉὌὊὍὋОӨӦӪ0][N₦ŃÑŅŇṆΝ][ ]?[WŴẀẂẄẆẈ₩][HΉĤĦȞʰʱḢḤḦḨḪНҢӇӉΗἨἩἪἫἬἭἮἯῊᾘЋΗⱧԋњһh][ÉÈËEĘĚĔĖẺẸẾỀỄễỂểȨȩḜḝĒḖḗȄȅȆȇỆệḘḙḚḛ3عڠeēėèéëẽĕęəẻếềẹ][ÉÈËEĘĚĔĖẺẸẾỀỄễỂểȨȩḜḝĒḖḗȄȅȆȇỆệḘḙḚḛ3عڠeēėèéëẽĕęəẻếềẹ]+[L₤ĹĽḶŁĿΛЛЉ7][[S$ŚŜŞŠṢΣЅz5].* <moveonly> # Disallows moves with "on wheels" with 2 or more Es
The final character class appears to have too many opening square brackets, specifically [[S$ŚŜŞŠṢΣЅz5]. Julyo (talk) 19:44, 25 June 2017 (UTC)
Excessive Repetition, off by one
This line
.*([^0])\1{4}.* <moveonly> # Disallows four or more of the same character from page moves
should probably say "Disallows five or more" or "Disallows more than four"; alternatively, the {4} bit could be changed to {3}. Julyo (talk) 19:47, 25 June 2017 (UTC)
I'm an admin, so can over-ride the blacklist, but it seems that the list of expressions that are prohibiting this page (".*Hunter (The|Baker|Classic|Original|Mariner|Fan|Berkeley|2|3|4|5|Oasis|Eclipse|Beacon|Custom|Stratford|Low|Summer|Studio).*") includes far too many banal terms. Furthermore, it creates an annual problem for this important annual snooker tournament. "Classic" is a term used in many BrEng sporting tournaments, btw. --Dweller (talk) Become old fashioned!10:35, 20 June 2017 (UTC)
I feel comfortable removing it now, it's been a week. I just didn't want to remove it right away in case someone had a good reason not to. --Tavix(talk)13:57, 27 June 2017 (UTC)
The user Fouadadan (and socks) is creating and recreating lots of pages about himself (by now Hamoussin fouad, Fouad adan hamoussin, Fouad adan (anashed), Fouad hamoussin adan, Fouad adan Hamoussin, Fouad adan, Fouad adan anachid). For further info, see the SPI page, its archive, the SP category, and my request on meta:SRG (note: all socks are now globally locked). To prevent further vandalisms (hote that he created all this pages in few days, again and again), I request that the title Fouad Adan Hamoussin (of fouad adan, adan fouad... in any form, including l33t :-) ) should be listeD in the title/word blacklist. Due to the kind of self-promo vandalisms, that are user's only interest; removing the possibility to recreate this titles, the case should be quickly closed, once and for all (IMHO). And further socks should be avoided. -Dэя-Бøяg01:55, 25 July 2017 (UTC)
(?=.*\bfouad\b)(?=.*\b(adan|anashed|hammoussin|anachid)\b).* should match "fouad" and any of "adan,anashed,hammoussin,anachid" appearing in any order. If the TBL supports positive lookaheads that is. Otherwise a bunch of x|y comparisons could do it. CrowCaw00:29, 28 July 2017 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please add User:.*Fuck.* and User:.*fuck.* to the title blacklist to prevent further disruption with profanity. Ups and Downs (↕) 16:21, 30 July 2017 (UTC)
Please blacklist all pages here like John Abad, John Deguzman, Jon Abad, Jon de Guzman, John Ray Abad, John Ray Deguzman, John Ray De Guzman Abad, Jon Ray De Guzman Jon Ray De Guzman Abad Jon Ray Deguzman Jon Ray Deguzman Abad JR Deguzman JR De Guzman JR De Guzman Abad JD Productions Today Stars John DG. Abad Saturday Stars John Guzman Jon Guzman and JRD Primetastic Artist. per Wikipedia:Long-term abuse/Jr abad Thanks. 209.249.5.130 (talk) 23:28, 9 August 2017 (UTC)
A persistent troll has been creating a berage of sockpuppets mimicking my username, specifically to spam my notifications, and vandalise articles. This is far from being a first incident, because the seemingly same user spent several months from 2016 to 2017 trolling articles, spamming me and DangerousJXD (the user started targeting me after I assisted the latter), and creating multiple impersonation accounts of the both of us ([3], [4]). The user has also bragged about being "unstoppable" and being able to change IP ranges. The user's current wave of attacks consist of creating usernames based on Christopher Nolan's filomography (a pun on my username being "Darkknight") and following it up with "2149" or even "2419". Examples of these accounts include the socks Insomnia2149, Memento2149, Dunkirk2149, Memento2419, and Dunkirk2419. At this point, if someone is creating a username with "2149", chances are that it's either them or me. DarkKnight214917:35, 30 August 2017 (UTC)
The match is .*\\p{Lu}(\\P{L}*\\p{Lu}){9}.* <casesensitive | moveonly> # Disallows moves with more than nine consecutive capital letters. You can request these moves at WP:RM/TR. — JJMC89 (T·C) 19:30, 23 September 2017 (UTC)
I thought there was consensus to allow the creation of pages with emoji strings or color modifiers, but I recently noticed this message when attempting to create such a page (note I am a template editor):
@Gorobay: Looks like this blacklist entry affects any title that has a colon then an emoji (such as User:😎) or titles with consecutive emojis (such as 😶😶, though this one makes sense.) I triggered the blacklist entry when I was testing out creating pages in the "User:" namespace containing emoji in response to an ongoing WP:RFC regarding user names including emojis. Steel1943 (talk) 15:46, 17 October 2017 (UTC)
Pretty sure these were not exempted, and we didn't want these usernames being created - the recent RfC and contention has been about global names getting created elsewhere. — xaosfluxTalk16:05, 17 October 2017 (UTC)
There was consensus to allow single-emoji titles in the main namespace, but not to allow emoji in titles in general. The previous single-character whitelist regex was ^(Talk:)?.$. Its current version was only meant to expand it to allow emoji that appear as single characters but are encoded as multiple. It was not meant to affect non-main namespaces or to allow titles with multiple emoji. Allowing either of those would have required further discussion. Gorobay (talk) 18:23, 17 October 2017 (UTC)
@Xaosflux: Thanks. It seems to have stopped for now by itself. Maybe .*[①-⑨]{6}.* would catch future weird spam without too many false positives. Κσυπ Cyp18:52, 18 January 2018 (UTC)
I notice that there are a number of <newaccountonly> rules in the blacklist despite it now being supposedly being managed from Meta per phab:T38939. Is this incorrect, or can the local entries be removed and copied to Meta as appropriate? Jo-Jo Eumerus (talk, contributions) 16:53, 3 January 2018 (UTC)
My understanding is that their presence here will have no effect, and judging by some recent accounts I've seen, that is true. I'd say bring them up at meta, though in some recent discussions the folks there have been hesitant to blacklist names of interest to one project only. Kind of a catch-22, that... CrowCaw17:59, 3 January 2018 (UTC)
If a group of naughty accounts are being created from enwiki and editing only here, then an entry in the local blacklist makes sense. Just like how accounts aren't globally locked when they vandalize on one wiki. When just used on enwiki-specific vandalism, this won't have any negative effects on SUL finalization. -- Ajraddatz (talk) 03:57, 21 January 2018 (UTC)
If the account creation process is happening here, then the local blacklist should prevent them from being made. If the master tries to bypass the local blacklist by creating from another project, then that would be enough reason to add the name to the global blacklist. -- Ajraddatz (talk) 05:10, 21 January 2018 (UTC) Oh no, I just didn't read through the whole bug. I didn't realize that the functionality had been completely switched off at the local level. Obviously at Meta we should take any such reasonable requests then. -- Ajraddatz (talk) 05:20, 21 January 2018 (UTC)
You might need to do something around Daddy Hezekial as the author is running at as Prof and Prophet and will probably find other variants. KJP1 (talk) 16:50, 16 February 2018 (UTC)
I can work with that, but my question is: are there more drawbacks from this (apart from the fact that editing is limited)? I'd like to use the word "prefix", as in Ship prefix. Any advice? (move, continue, else)? FYI, when I moved a page into a "prefix:" pagename, I do not remember seeing that warning. Just to say: is there a leak? - DePiep (talk) 17:41, 15 March 2018 (UTC)
Others can edit the page. The limitation is only on creation. It only applies to "prefix:" with a colon. It's aimed at users who click a red "You may create the page ..." link after doing a prefix search with "prefix:" in the search. But the search software has actually improved to no longer offer silly creation links for such searches. We may not need the blacklist entry now but I guess it's safer to keep it. PrimeHunter (talk) 17:53, 15 March 2018 (UTC)
Not doneyet. Please provide diffs showing why those two strings should be added, I couldn't find any in the contributions of that person's socks, but I didn't go through every contribution. Fish+Karate11:27, 28 June 2018 (UTC)
IP talk pages blocked from moves
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Not done@Home Lander: you are referring to this right? That should have just been speedy deleted. As for your edit request, I assume you are referring to .*\p{Lu}(\P{L}*\p{Lu}){9}.* <casesensitive | moveonly> # Disallows moves with more than nine consecutive capital letters; however you did not provide a specific edit change that you would make so that this could be completed. This section can certainly be used to discuss this rule in general though. — xaosfluxTalk02:55, 8 August 2018 (UTC)
@Xaosflux: When I first came upon the page, I overlooked the extra stuff at the end of the title, so thinking I was just at the user's talk page already, I overwrote the content with a warning about it. It was after that I noticed that the title was incorrect, so I tried to move it. Yes, that is the line that I'm told prevented the page move. This line is potentially problematic, as shown here, because it prevents page moves to user talks of IP addresses that meet this rule. Home Lander (talk) 03:02, 8 August 2018 (UTC)
Bayer designations for stars in the constellation Boötes take the form of a Greek letter followed by the genitive form of the constellation name which is Boötis. Article titles consisting of a Greek letter in combination with non-latin characters are currently blacklisted. The star articles themselves are conventionally titled using the spelled-out form of the Green letter (eg. lambda for λ, lambda Boötis) but it is standard practice to provide a redirect from the name containing the Greek letter (eg. λ Boötis, especially useful for stars with proper names (eg. Arcturus). An exception would be helpful to allow this. If this could be general enough to allow derivations, for example λ Boötis star as a redirect to lambda Boötis star, that would be even better. Lithopsian —Preceding undated comment added 10:13, 24 August 2018
I'm guessing you hit the same blacklist entry I did - Latin + non-Latin. As a workaround, I believe admins can override the blacklist. Hairy Dude (talk) 02:17, 27 August 2018 (UTC)
There are potentially a whole bunch of redirects required, so it might be a bit much to ask of the admins. See Template:Stars of Boötes for a list of Bayer stars in that constellation (25 of them?), plus a handful of related classes. Lithopsian (talk) 13:18, 27 August 2018 (UTC)
If you provide a list of the 25 redirects (with targets) that you would like created, I will do it. — JJMC89 (T·C) 02:58, 28 August 2018 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Foreign language user pages need to be blacklisted.
For example, Luigi Catalani (talk·contribs) seems to be tring to create user pages for his students but is creating them in the Utente: namespace (which isn't a namespace on enwiki) so they end up as unwanted articles with silly names.
The following prefixes (out of many, I haven't figured out how to quickly create a complete list) ought to be blocked from creation:
Not done in addition to above, this is also not ready to add as if you could add it yourself. Of course this can still be discussed here, and when it is ready you can reactivate the request tag above. — xaosfluxTalk03:59, 26 January 2019 (UTC)
@Cabayi and Nyttend: In sanskrit, hindi, and Marathi (among few other languages) सदस्य of #15, and 18 means member, and प्रयोगकर्ता of #12, 16, an 17 means operator. —usernamekiran(talk)22:57, 1 February 2019 (UTC)
Användare:
Benutzer:
Bruker:
Gebruiker:
Pengguna:
sadasya:
Usuario:
Usuário(a):
Utente:
Utilisateur:
Utilizator:
प्रयोगकर्ता:
Χρήστης:
સભ્ય:
सदस्य:
ಸದಸ್ಯ:
ഉപയോക്താവ്:
பயனர்:
వాడుకరి:
Участник:
So here's our list. Assuming it's not hard to do the regex, is there any reason not to add them? I can't say there will never be a situation, but I can't currently imagine a situation in which we'd want to have an article begin with any of these phrases, and if there is such a situation, an ordinary "override the blacklist" request at WP:AN should work. Nyttend (talk) 23:04, 1 February 2019 (UTC)
Regexed list in syntaxhighlight block below (blank line ahead of section, leading space on each line, trailing wildcard .*). Explanatory comment added. Duplicates removed. Request reactivated.
syntaxhighlight is suppressing display of the leading blank line.
# Prevent creation of articles beginning with foreign language equivalents of
# User: as they aren't recognised on enwiki. (User: works on every wiki)
Användare:.*
Benutzer:.*
Bruker:.*
Gebruiker:.*
Pengguna:.*
sadasya:.*
Usuario:.*
Usuário(a):.*
Utente:.*
Utilisateur:.*
Utilizator:.*
प्रयोगकर्ता:.*
Χρήστης:.*
સભ્ય:.*
सदस्य:.*
ಸದಸ್ಯ:.*
ഉപയോക്താവ്:.*
பயனர்:.*
వాడుకరి:.*
Участник:.*
looks like I mistakenly removed from the regex when deduping - it looks very similar to Χρήστες which was caught. Regards, Cabayi (talk) 18:08, 5 February 2019 (UTC)
(?!(User|Wikipedia)( talk)?:|Talk:)\P{L}*\p{Latin}.*[^\p{Latin}\P{L}].* <moveonly> # Latin + non-Latin
If I'm reading this right, this bans titles that combine Latin and non-Latin script, but only when moving. This is bizarre - ʻokina is definitely part of the Latin script for Hawaiian. I note that this subject was brought up here previously (2012) but nothing was done. Hairy Dude (talk) 02:10, 27 August 2018 (UTC)
I encountered several okina moves last month. This is a problem because it required marking for administrator attention, but the moves were eventually completed. — Frayæ (Talk/Spjall) 22:14, 1 September 2018 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
I've reactivated this request. The text quoted by JJMC89 is not definitive enough ("generally") to justify an entry in the Titleblacklist. The Titleblacklist is a "never" list, not a "discourage" list. Jo-Jo Eumerus (talk, contributions) 10:15, 2 February 2019 (UTC)
Hi!
Why are some of the control character patterns (such as \x{00AD}) marked as casesensitive? For performance reasons? -- seth (talk) 21:10, 28 March 2019 (UTC)
Safety reasons. There have been some unexpected encounters with case-folding that prevented titles containing the letter "k", or a space, or other common things. Adding the "case sensitive" restriction means that people editing the list don't need to think about the arcana of Unicode case conversion rules. --Carnildo (talk) 02:21, 30 March 2019 (UTC)
Right now, new editor User:Love vashikaran specialist aghori baba can not edit their own user and user talk page because of a title blacklist for "*vashikaran.* # Indian astrology/magic advertising". Can I remove this element from the Titleblacklist, as long as this editor is active? It seems unfair that they can't make use of their own user pages and other editors can not leave messages for them. LizRead!Talk!02:40, 22 June 2019 (UTC)
Okay, now I'm confused as a regular editor has now left another message on this editor's user talk page. I don't think I understand how this title blacklist works as I'm sure I saw a pink message saying only admins and template editors could edit the page. LizRead!Talk!02:49, 22 June 2019 (UTC)
@Liz: you could add that specific user: page to the MediaWiki:Titlewhitelist instead of removing the entire pattern here. I haven't gone through all the logic to see if there is a bypass on user_talk for that right now, or if the namespace isn't working yet. — xaosfluxTalk03:21, 22 June 2019 (UTC)
@Liz: OK - so it looks like that pattern is only protected against creation, not editing (our local message is a bit wrong) - the talk page works because a sysop created it. I've created the userpage and usersandbox - so this will take care of the basic stuff. If they will need to create other subpages this will come up again, so you can go the whitelist route for the more specific pattern. — xaosfluxTalk03:29, 22 June 2019 (UTC)
That user is blocked as an LTA (and the reason the phrase appears in the TBL). Basically spamming for love sorcery cross-wiki... CrowCaw22:42, 22 June 2019 (UTC)
Well, I guess that takes care of that! "Love sorcery", huh? That is more interesting that our typical DJ & Marketing spammers.
At RfD, we came across a redirect containing a word joiner (U+2060). The redirect is Fernando Zor ending with four copies of the word joiner. Since this non-printing character isn't on the blacklist, I request that it be added under the "OTHER UNDESIRABLE CHARACTERS" section, along with the many other non-printing characters that are not yet on the blacklist; go through b:Unicode/Character reference to find them all. (Enter "%E2%81%A0" into your URL bar to go to a title with a word joiner; the same technique works with all non-printing characters, via their UTF-8 codepoint.) –LaundryPizza03 (dc̄) 03:52, 22 August 2019 (UTC)
Not done as to the immediate edit request, discussion can certainly continue below, including dealing with the need to build any custom messages in support. — xaosfluxTalk13:42, 8 September 2019 (UTC)
I started a discussion on when / how the Title Blacklist should be used; since the closest relevant policy is WP:SALT, and since the protection policy page's talk seems likely to be far more trafficked than this one, I put the discussion there even though it's obviously relevant here as well. Adding a notice here so people who actually use the Title Blacklist system can weigh in - I think we need at least a few sentences in WP:SALT (or somewhere) elaborating on what the title blacklist system is for, since currently I couldn't find anything. (Or, if there are instructions somewhere, it needs to link to them.) --Aquillion (talk) 07:32, 11 November 2019 (UTC)
