#216 closed enhancement (fixed)
Block @ in WPORG usernames
Reported by: | Ipstenu | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Support Forums | Keywords: | has-patch |
Cc: |
Description
We should filter @'s (and email addresses) from WPORG usernames so people can stop signing up as ipstenu@… and so on (like I just did, you can nuke that).
Change History (8)
#2
@
11 years ago
Because people rarely (if ever) actually WANT a public username to be their email address. It causes spam, and also a high number of people kvetching to us because we can't change the usernames.
tl;dr - Protect people from being silly.
#3
@
11 years ago
Another solution would be to detect (via JS) an email address in the username field and pop-up a message saying something along the lines of "Your username is public. Are you sure you want it to be your email address? We recommend a username different from your email address."
#4
@
11 years ago
If we did that, we may as well add it 'Your username is public and cannot be changed....'
Not that I think people actually read, though, Sams. They'll just click and then complain later.
#5
@
11 years ago
We need to make our usernames more restrictive. Spaces, @ signs, and such cause a lot of inconsistency, grief, and general issues across WP.org.
#6
@
11 years ago
- Resolution set to fixed
- Status changed from new to closed
The @ signs have given us grief in other ways too. They're blocked now. Existing usernames can still have them, but new accounts cannot.
This ticket was mentioned in PR #217 on WordPress/wporg-mu-plugins by adamwoodnz.
3 years ago
#7
- Keywords has-patch added; needs-patch removed
StevenDufresne commented on PR #217:
3 years ago
#8
I took this change and added one more in: https://github.com/WordPress/wporg-mu-plugins/commit/abc02533432fb1987ea9b96d5a7fef28c0c51d73.
Thanks for the head start!
Why?
(I'm not objecting, just curious, because I don't see any inherent harm in it.)