Jump to content

Wikipedia talk:Username policy

Page contents not supported in other languages.
Page semi-protected
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia talk:UAA)

Wikipedia Talk:Usernames for administrator attention and Wikipedia talk:Requests for comment/User names now redirect here. Click "show" for archive links and other relevant information on those pages.

WT:UAA archives:

Wikipedia talk:Requests for comment/User names archives and deletion notices:

Bot needed to monitor and readd instructions for user-reported usernames

At the top of the "User-reported" section of WP:UAA, there is an HTML comment with a brief set of instructions for editors:

REPORTING A USERNAME: Add * {{user-uaa|Example user}} How this username violates the username policy. ~~~~

This text is often deleted by editors when they report someone. Can we please task a bot with monitoring for that and restoring the text when it's deleted? Thanks! ElKevbo (talk) 10:29, 25 September 2024 (UTC)[reply]

I don't think we need an extra bot, just get HBC AIV helperbot14 updated to make sure it's part of its check. Mdann52, what do you think? Primefac (talk) 11:51, 25 September 2024 (UTC)[reply]
Currently this is in my dev code, will finish testing and push to live when I get some time (hopefully over the weekend). Mdann52 (talk) 19:57, 26 September 2024 (UTC)[reply]

The redirect Username policy has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 October 12 § Username policy until a consensus is reached. C F A 💬 20:38, 12 October 2024 (UTC)[reply]

AGF message for semi-"well-known" people

WP:IMPERSONATE says that editors whose username matches that of a well-known person "may" be blocked, and that verifying identity must be done "in some cases", and the standard practice seems to be not to block someone who is only marginally well-known and an unlikely target for impersonation, especially if their edits don't seem problematic.

Prompted by this discussion on UAA with Just Step Sideways and Secretlondon, I was wondering if there any consensus to include more detail on cases in which we shouldn't block, or if that would that be WP:BEANS?

Even if we don't include extra detail here, I created {{Uw-agf-wellknown}} as an alternative to {{Uw-ublock-wellknown}}. Is there any objection to proposing this this template for inclusion in our standard list of warning templates and/or incorporating it into Twinkle? --Ahecht (TALK
PAGE
)
16:17, 7 November 2024 (UTC)[reply]

I don't think "block first and let VRT sort it out" is the best way forward. I do agree that asking them to verify their identity is probably a good idea (regardless of how notable they are). I'm not opposed to the nicer message, especially since it is in a similar vein to {{Uw-coi-username}}. Primefac (talk) 17:05, 7 November 2024 (UTC)[reply]
The idea, for me, is that we don't want people editing their article with the authority of claiming to be the subject. Most of the COI-not-username cases are of people who are non-notable. It really doesn't matter if they are the real person or not if they are not anyone in particular. I push back against people wanting to block COI spammers as a username violation - there really is no doubt they are John Doe (rapper), and asking them to prove they are doesn't make any difference. If they become notable it is different. If John Doe is being irritating we block them for what they done (link spam etc) not pretending that we are worried they are impersonating themselves. Secretlondon (talk) 17:06, 7 November 2024 (UTC)[reply]
To follow on from that - we get a lot of stage names/online handles of YouTubers. We'd never ask them to prove they are who they claim to be. These are just COI. We just don't vet randoms like this. Secretlondon (talk) 17:27, 7 November 2024 (UTC)[reply]
Obviously if User: Mr Beast starts editing his article then we'd block as impersonation until proved otherwise. Secretlondon (talk) 17:28, 7 November 2024 (UTC)[reply]
I think the line for blocking is/should be at "famous" as opposed to just well-known. If someone is claiming to be Beyonce, they are probably lying. Just Step Sideways from this world ..... today 20:31, 7 November 2024 (UTC)[reply]
Noting for the record that, Orangemike (talk · contribs) went ahead and blocked the account that prompted this discussion, despite the fact that the account had made no edits since I dropped a note on their talk page about the name. Just Step Sideways from this world ..... today 16:39, 8 November 2024 (UTC)[reply]
Yes I saw.. Secretlondon (talk) 17:35, 8 November 2024 (UTC)[reply]
ticket:2024110610009272 feels like confirmation enough for me (see the return email address) so I've unblocked. Primefac (talk) 22:05, 8 November 2024 (UTC)[reply]
I don't have access to VRT but there was never really any doubt. Secretlondon (talk) 08:07, 12 November 2024 (UTC)[reply]

Illegible usernames

I recently encountered a sig which I was unable to read because of the color patterns, and left this message on their Talk page. I found nothing in the policy that seems to cover this, so it seems permissible currently. I would assume that styling one's sig, say, in white-on-white font (not the case here) would be unacceptable, but there isn't really anything about that, afaict. It seems to me we should add something to the policy about illegible signatures, but I don't think we have to enumerate all the ways someone could obscure their sig, because someone will always find some other way; it would be sufficient to have a catch-all saying that signatures styled in such a way that an editor could not easily determine the username, should be forbidden. I am not overly concerned with the case of the individual editor I messaged; my main concern is having something in the policy I can link or quote to a user when an illegible sig is at issue. Mathglot (talk) 04:43, 12 November 2024 (UTC)[reply]

This sounds like a WP:SIGAPP issue. Nobody (talk) 06:54, 12 November 2024 (UTC)[reply]
Agreed; signature customisation is allowed until someone finds issue with it; nothing wrong with saying to someone "I can't read your sig", goodness knows I've done plenty of that over the years. Primefac (talk) 12:40, 12 November 2024 (UTC)[reply]

Old revisions show newer reports

Like say the 8 November version, it is showing the reports bots made at 15 November. ExclusiveEditor Notify Me! 05:43, 16 November 2024 (UTC)[reply]

If you want old bot-reported data, you'll need to check the history of Wikipedia:Usernames for administrator attention/Bot. Primefac (talk) 14:03, 16 November 2024 (UTC)[reply]
Ah, so it is transcluded, ok, thanks. ExclusiveEditor Notify Me! 14:19, 16 November 2024 (UTC)[reply]

Declined and stale reports

Should we run a bot to remove declined and stale reports from UAA? Currently, HBC AIV helperbot14 only removes processed reports, so we have to manually remove declined and stale ones. I suggest removing declined reports that haven't received any comments within an hour, and stale reports with no comments in the past 24 hours. If HBC AIV helperbot14 can add this functionality, that would be great. Otherwise, I can assist with my bot. – DreamRimmer (talk) 12:12, 9 December 2024 (UTC)[reply]

Huh, I thought that was already part of the functionality. Courtesy ping to Mdann52. Primefac (talk) 13:02, 9 December 2024 (UTC)[reply]

RFC relating to enforcement of this policy

See Wikipedia:Username policy/ORGNAME/G11 in sandboxes RFC. El Beeblerino if you're not into the whole brevity thing 21:18, 16 December 2024 (UTC)[reply]