We had someone register with a reserved username, getting around the restriction by the simple expedient of adding “1” to the end. I can’t tell if the system will accept a wildcard entry to prevent this, i.e., by declaring reservedusername* in the list. I’m a little hesitant to use the “just try it and see” method. Can anyone enlighten me?

[תמונה] DrBB: I can’t tell if the system will accept a wildcard entry to prevent this, i.e., by declaring reservedusername* It will, we mention it in the description below the setting Usernames for which signup is not allowed. Wildcard symbol * can be used to match any character zero or more times. reservedusername* should prevent reservedusername1 from being registered

[תמונה] awesomerobot: It will, we mention it in the description below the setting –Ha! I should look more closely at what’s in front of me. Thanks!

But people will be able to register reserved_username. Maybe it’s an idea to look at the Levenshtein distance instead of using a wildcard?

[תמונה] RGJ: Maybe it’s an idea to look at the Levenshtein distance instead of using a wildcard? Yow, that would probably be a lot more bulletproof, but I’m not sure it’s worth that degree of effort. Out of curiosity, would you use a reg ex test of some kind? Can you do that in the Discourse admin?

[תמונה] RGJ: Maybe it’s an idea to look at the Levenshtein distance instead of using a wildcard? This might be more effort than it’s worth… It would catch reserved_username1 but it probably wouldn’t catch official_reserved_username, right? this is the type of thing that a motivated person would always find a way around. [תמונה] DrBB: would you use a reg ex test of some kind? Can you do that in the Discourse admin? We have a regex setting for blocked/censored words, and that seems like a reasonable way to enhance reserved usernames (which only has the wildcard)… but does this problem come up often enough to justify prioritizing that? I don’t think it’s a complaint we’ve had often.

We only found the one instance when we searched our user names, so yeah, I don’t think it calls for anything too elaborate.

[תמונה] awesomerobot: this is the type of thing that a motivated person would always find a way around. Exactly, so why support wildcards then? :thinking:

Isn’t that just reason to separately block reserved and username?

Reserved usernames: wildcard?

תמיכה

RGJ (Richard - Communiteq) 7 במרץ,‏ 2019,‏ 11:11pm 8

Exactly, so why support wildcards then?

נושא		תגובות	צפיות
Reserved username name wildcards - didn't trigger Product Support	2	433	18 בדצמבר,‏ 2023
Reserved usernames wildcard Feature pr-welcome	17	3103	15 באוגוסט,‏ 2018
Feature Request: Making 'reserved usernames' check the censored and blocked words list Feature	6	1119	10 בנובמבר,‏ 2019
Regarding reserved "admin" user name Product Support	1	480	14 בספטמבר,‏ 2021
Can I restrict specific strings in usernames? Product Support	7	1244	22 בספטמבר,‏ 2017

Reserved usernames: wildcard?

נושאים קשורים