Talk:Title blacklist
For more information on what the title blacklist is for, and the processes used here, please see Title blacklist/About.
Please post comments to the appropriate section below: Proposed additions, Proposed removals, or Troubleshooting and problems, read the messageboxes at the top of each section for an explanation.
Also, please check back some time after submitting, there could be questions regarding your request. In addition to that, please sign your posts with ~~~~ after your comment.
Completed requests are archived, additions and removal are logged.
- Information
- List of all projects
- Overviews
- Reports
- Wikimedia Embassy
- Project portals
- Country portals
- Tools
- Spam blacklist
- Title blacklist
- Email blacklist
- Rename blacklist
- Closure of wikis
- Interwiki map
- Requests
- Permissions
- Bot flags
- New languages
- New projects
- Username changes
- Translations
- Speedy deletions
 |
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day.
|
snippet for logging: {{tbl-log|27853222#{{subst:anchorencode:SectionNameHere}}}}
Proposed additions
[edit]
|
This section is for proposing that a page title be blacklisted; add new entries at the bottom of the section. Provide links demonstrating widespread creation by multiple users or IP's. Completed requests will be marked as done or denied and archived.
|
Proposed removals
[edit]|
|
This section is for proposing that a title be unlisted; please add new entries at the bottom of the section. Remember to provide the specific title or regex blacklisted, links to the articles they are used in or useful to, and arguments in favour of unlisting. Completed requests will be marked as done or denied and archived. The addition or removal of a title is not a vote, please do not bold the first words in statements. |
Krimpet
[edit]I propose removing .*Kr[i1l]mpet.*. This user Fran Rogers (talk · contribs), previously known as Krimpet (talk · contribs) has been inactive for almost 10 years. 181.79.234.90 22:51, 22 November 2024 (UTC)
- Is the pattern causing issues? XXBlackburnXx (talk) 03:14, 24 November 2024 (UTC)
- I would assume 181.79.234.90 ended up here because they wanted to create an account that matched that rule. * Pppery * it has begun 05:34, 24 November 2024 (UTC)
Troubleshooting and problems
[edit]|
|
This section is for comments related to problems with the blacklist (such as incorrect syntax or entries not being blocked), or problems saving a page because of a blacklisted title. This is not the section to request that an entry be unlisted (see Proposed removals above). |
Lose x pounds
[edit]The rule \blose \d\d pounds <autoconfirmed> has "\b" at the start, which has no effect, because the whole page title has to match, and the beginning of the page title counts as a word boundary. I'm guessing that the intention here was to have it match anywhere within the page title, and that whoever added this rule didn't realise that the blacklist doesn't do partial matches by default, because it would be weird to have "\b" in there for no reason. In that case, let's replace this rule with .*\blose \d\d pounds.* <autoconfirmed>. Unfortunately, the addition of this rule has not been properly logged—it does appear in the log page for September 2018, but that log page doesn't have a link to the diff where this rule was added, so we'd have to do a lot of manual crawling to find the diff. TTWIDEE (talk) 11:50, 23 November 2024 (UTC)
Fuerdai
[edit]The rule .* fu[a-z]{1,5}?rdai. * ends in " *", so it will check for zero or more spaces at the end of the page title, which has no effect, because the MediaWiki software automatically strips trailing spaces anyway. I think the space before the final "*" is probably a typo, so let's replace this rule with .* fu[a-z]{1,5}?rdai.*. TTWIDEE (talk) 20:03, 23 November 2024 (UTC)
Apostrophe weirdness
[edit]There's a rule which is given in the source code as .*''.* <newaccountonly> # ''This rule blocks new usernames with two consecutive apostrophes in a row - the apostrophes are interpreted as wikitext in the render (extraneous spaces removed for brevity), and the combination of the two pairs of apostrophes causes the text between them to render in italics if you're not using the source view, which is confusing. We should probably remove the second pair of apostrophes to fix this.
However, that would cause a potentially much bigger italics issue if there are ever any subsequent rules or comments that contain ''. I don't think there'd be a huge need for pairs of apostrophes in other rules, but it's worth keeping in mind. Maybe we could add a comment at the top warning about this issue, and just not use '' in any subsequent rules or comments. Obviously, using '' would cause a pair of apostrophes to render when viewing the blacklist, but (correct me if I'm wrong) I don't think the title blacklist extension would process the HTML entities, so that would cause rules using this approach to match page titles/usernames containing '' instead of ones containing '', which is obviously not desirable. TTWIDEE (talk) 20:44, 24 November 2024 (UTC)
- I intentionally added the second pair of apostrophes there - previously it was rendering as
.*.* <newaccountonly>, which looked like it was blocking all accounts. * Pppery * it has begun 23:28, 24 November 2024 (UTC)