Make usernames truly feel like unique

(#3614) Feature Open: Under consideration

Current problem

Rather than hardcoding a specific username format, instance owners could define their own regex for username validation. This would allow each instance to decide which characters and formats are appropriate for its community, while keeping usernames distinct from display names.

Proposed change

Rather than hardcoding a specific username format, instance owners could define their own regex for username validation. This would allow each instance to decide which characters and formats are appropriate for its community, while keeping usernames distinct from display names. For example, an instance could choose to allow only lowercase letters (a-z), numbers (0-9), etc... (., _), while another instance could use a different format if desired.

Platform

API, Self-hosting

Additional information

Many platforms distinguish usernames from display names by placing stricter restrictions on the characters that can be used in usernames. For example, instead of having a username like Revenant alongside a display name like Revenant, an instance could require usernames to follow a stricter format, such as @rev. This makes the distinction between a username and a display name more apparent.

3 comments

Sign in with Fluxer to comment and vote.
Comment by sodiboo
sodiboo 2 votes 1 reply
consider why the character set is limited: if you allow too many exotic things, you can get "unmentionable names" which are a pain to moderate. this was kind of a problem on discord in it's early days, because although allowing arbitrary Unicode usernames was really cool (your username could be in any language! how very internationalization of them!), it also made it hell for English speaking moderators to consistently refer to accounts. not to mention, it allows for homoglyph attacks (i.e. identical looking usernames). there's very good reason why the username charset is so limited on Discord and Fluxer today and just about every other platform in existence. and, a critical technical restriction for this suggestion is that third party bots and integrations and sites will need to parse and display Fluxer usernames. we're not seriously considering having the server send them a regex and make "you Need a regex parser" part of the API contract? it's very valuable to have a single, relatively consistent way that usernames are formatted, because it simplifies all code regarding them. but that being said, i agree the current charset is limited. at most, maybe we can have the characterset be customizable per instance. but really, i think it would be better to just expand the character set for everyone, potentially to exactly what polyproto allows and nothing more, nothing less. if you want to further enact a policy limiting username choice (rather than expanding it), i think that's already doable via SSO? (surely SSO providers will forcibly override the username?) with polyproto-allowed characters (the maximal set we should ever reasonably allow), it might be worth considering which symbols should be reserved for system use, though. for example, i've seen talks that # (to denote a discriminator) becomes . in a federated name. so maybe we don't allow dots? maybe some other symbol is reserved for webhooks? bots?
Comment by sodiboo
i think that if the point of usernames is not to have a "consistently formatted name" referring to a user, then there is no point to usernames at all. Steam doesn't really have usernames (it has a login name, which is private, and it has a URL slug, which is only used on the profile page). users do not have a consistently formatted name that they can be identified by. it's just a user ID and their freeform display name. if you want to add someone as a friend, you need to already be looking at their profile by having interacted in a game or on the forums, or by directly lining to their profile (which generally contrains a full steam id) if someone wants an internationalizable Fluxer without ascii usernames (the only real reason i can think of to go beyond polyproto chars), i think it would be compelling to have an instance without usernames at all (like Steam), rather than an instance with very weird usernames.