Talk:Title blacklist/Archives/2012

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Proposed additions

Modify an entry

Please replace plays?\s*with <newaccountonly> with [pṕ]lays?\s*with <newaccountonly>, because there are new entries with this name in the global account log. Thanks. Francisco (talk) 17:11, 24 May 2012 (UTC)

Yes check.svg Done. Trijnsteltalk 17:46, 24 May 2012 (UTC)

Proposed removals

spambots, checkuser-l

this is too broad, for it can block a lot of (too much) reasonable names. The regexp should be more precise, if possible. -- seth (talk) 21:35, 14 June 2012 (UTC)

Already removed. mabdul 10:11, 15 June 2012 (UTC)


.*Rschen7754.* <newaccountonly> I would like my name removed from the global title blacklist; I think the troll that hit in 2009-2010 has moved on. I am unable to create new accounts on non-SUL-enabled wikis. --Rschen7754 10:34, 9 November 2012 (UTC)

Yes check.svg Donebillinghurst sDrewth 04:21, 10 November 2012 (UTC)
Thank you! --Rschen7754 07:57, 10 November 2012 (UTC)


.*Spacebirdy.* <newaccountonly> Please remove, I can't log in to new accounts on e.g. wikivoyage, etc. thanks, --birdy geimfyglið (:> )=| 21:08, 14 November 2012 (UTC)

Yes check.svg Done [1]. Please tell us if you want to be re-added again. Un abrazo :) -- MarcoAurelio (talk) 14:34, 15 November 2012 (UTC)

Troubleshooting and problems

(?: syntax

What does (?: mean? I have read this but can't see how it is relevant to the Title blacklist. 19:38, 15 October 2011 (UTC)

If I remember correctly, the edit summary says it was done to improve performance a little. I guess backreferences come at a cost. Nemo 23:12, 2 January 2012 (UTC)
In the past there was a slight performance difference. Nowadays in most of the big regexp engines there won't be a big difference. However, "(?:)" should be used for normal grouping. "()" should be used only, if there's need to capture the grouped pattern and back-reference to it lateron. If one doesn't use names for capturing, then he always has to count the number of capturing parentheses. Programmers a lazy, they don't want to count a lot. Apart from that it's just easier to count, the lesser the number of elements is. ;-) -- seth (talk) 18:46, 29 May 2012 (UTC)

Broken entry

The entry "*(?:a(cl|d)min|sysop).*" is broken (see for example [2]). It appears the leading '.' was lost in this edit. Anomie 16:52, 7 January 2012 (UTC)

It has been almost two months now. Please change the mentioned entry to .*(?:a(cl|d)min|sysop).*, i.e. add a period character before the first * to make the regex non-broken. Or just delete the entry, if you'd rather, since it hasn't been effective since August 2010. Anomie (talk) 18:24, 4 March 2012 (UTC)
Done. Sorry to say, unlike the spam blacklist, this one needs the edit protected template to draw attention, it seems. Courcelles (talk) 19:48, 4 March 2012 (UTC)

.*Dri\.?n+i.* <newaccountonly>

A user on commons wanted to choose the user name WoderTeedrinis. The request was refused with some error message like unwanted user name. I think this was caused by the rule
.*Dri\.?n+i.* <newaccountonly>
here on meta. But I might be totally wrong. Would it be possible to allow this rather harmless name? I really don't have an idea what names should be refused by that rule. regards --Herzi Pinki 20:18, 4 February 2012 (UTC)

The regex is there to catch look-alikes for a steward's user account. Vandals think it clever to create narrative user names that encapsulate stewards' names. Is it possible to get another username, as modifying the regex for the suggested name will be difficult. It might be possible to go to Steward requests/Username changes and ask, though I still think that it is going to be problematic every time the user moves to another wiki as it will hit the title block. billinghurst sDrewth 23:29, 4 February 2012 (UTC)
Thanks for the answer, that's how I understood it anyhow (it is commented that way), but I didn't find the name of the steward who is afraid of this kind of name similarity vandalism. But I think that WoderTeedrinis will be quite different from the name of the steward, so my opinion is, that the regex is much too prohibitive. That's why I was asking. The user already has chosen another name, so the problem is not really a problem. Maybe it still would be possible to relax the strength of the regex, e.g. by just making it case sensitive? I will clarify with the user who wanted that name. cheers --Herzi Pinki 07:35, 6 February 2012 (UTC)
Steward's username is Drini, so no, at this stage it is not too restrictive. There is an election process about to occur, so it is probably worth flagging this set of titles for review following that process. billinghurst sDrewth 12:24, 6 February 2012 (UTC)
I agree to Herzi Pinki, that the regexp is a bit too general. (If one day there will be a steward called "A", this would not be a sufficent reason for blocking all user names containing "A".) I suggest an alternative:
.*(?:\bd|D)ri\.?n+i.*      <newaccountonly|casesensitive>
-- seth (talk) 18:37, 29 May 2012 (UTC)
The steward in question has long changed name and is virtually inactive anyway, so it doesnt seem that likely to be a target of attack usernames. Snowolf How can I help? 18:43, 29 May 2012 (UTC)
Then we can remove that complete entry anyway or are there any objections to this? -- seth (talk) 18:49, 29 May 2012 (UTC)
I've pointed him towards this discussion, if he has any comments. I would suggest that yes, it could probably be removed, given he's been renamed for 2 years now and the rule is causing issues for legitimate users. Snowolf How can I help? 19:05, 29 May 2012 (UTC)
Removed Removed -- seth (talk) 21:11, 28 June 2012 (UTC)

Put this website on global spam list. --Kolega2357 (talk) 08:04, 10 November 2012 (UTC)

This is the title list, check Spam blacklist; from memory I saw it added, but you may wish to check. If it isn't there, then make the suggestion at Talk:Spam blacklistbillinghurst sDrewth 10:19, 10 November 2012 (UTC)

False positive

Recently my bot commons:User:DcoetzeeBot on Commons triggered the blacklist while uploading a file with title "Unidentified Artist - Mathew Brady, Juliet Brady and Mrs. Haggerty - Google Art Project.jpg". This appears to be due to the entry ".*hagg[ae]r.* <newaccountonly>". I'm not sure why it was triggered since my bot account is not a new account. Dcoetzee (talk) 12:12, 23 December 2012 (UTC)

It shouldn't have been the case, as the <newaccountonly> is meant to only apply the filter to matches of new accounts, not to file names. — billinghurst sDrewth 13:49, 16 January 2013 (UTC)