Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Username case fields #23

Closed
stuartpb opened this issue Apr 16, 2015 · 4 comments
Closed

Username case fields #23

stuartpb opened this issue Apr 16, 2015 · 4 comments
Labels
Milestone

Comments

@stuartpb
Copy link
Member

Things to list:

  • username.case.sensitivity: should be "insensitive", can be "sensitive" if the system is stupid (accepts "stuart" and "Stuart" as two different users).
  • username.case.display: Whether the system coerces usernames to "upper" or "lower", or keeps them "mixed".

As for passwords, if the password is case-insensitive, that is a HUGE red flag, and it belongs in redflags (since it's not common).

@stuartpb
Copy link
Member Author

stuartpb commented Jun 9, 2015

Putting this on future, even though it could feasibly be added before v0.1.0.

@stuartpb stuartpb added this to the future milestone Jun 9, 2015
@stuartpb
Copy link
Member Author

There's also the matter of how they're handled in URLs, and in what contexts they're corrected (ie. rewritten in mentions, redirected in links).

@stuartpb
Copy link
Member Author

stuartpb commented May 18, 2016

Right now, systems coercing usernames to (ie) lowercase in all instances can be represented as username.contents.whitelist.classes[0] = 'lowers', FWIW (though that's admittedly not a great way of representing all these nuances).

@stuartpb
Copy link
Member Author

Moving to opws/opws-schemata#25 (per #308).

@opws opws locked and limited conversation to collaborators Sep 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant