User talk:Reception123/Username RfC

Add topic
From Miraheze Meta, Miraheze's central coordination wiki
Latest comment: 4 years ago by Reception123

I support the general rule, in Proposal 1, that "Stewards have discretion," but it seems silly to say so, as the gist of the other Proposals is to codify common-sense rules by which to remove their discretion!

I recall that a "felony" is a crime punishable by a year or more of imprisonment. This may differ among jurisdictions, and there is no reason to use it as the standard for an invalid username. Any username that would be illegal should be against this rule, no matter the sentence!

Similarity of a proposed username to an existing username strikes me as misconduct, but requires Steward discretion. A username containing an email address or a phone number seems to be a subset of a problem, which is the attempt to use the act of creating a username to transmit a message and not simply create a name. User:GovernorSmithSucks! has the same problem though it doesn't "out" anyone.

Finally, "reasonable confusion" created by a username begs for Steward discretion. There is a conflict underlying this entire proposal between the need to rely on the common sense of the Stewards, and the implication that they don't have enough of it! Cheers Spıke (talk)03:54 27-Aug-2019 03:54, 27 August 2019 (UTC)Reply[reply]

@Spike: Thank you for your feedback! Proposal 1 is simply because that is the current status quo, that's the reason for me adding it to the RfC.
As for your felony comment that does make sense, and it should probably be bound directly by other policies rather than specifically the username one, so I will remove that one.
The existing username policy is really about people clearly impersonating other users, as we've seen that a lot around here. For instance, a user calling themselves Reception321 would be clearly impersonating me.
I understand your comments regarding discretion but anyway it usually is opposed, so there should be no issue there. Reception123 (talk) (C) 05:35, 27 August 2019 (UTC)Reply[reply]