-
Notifications
You must be signed in to change notification settings - Fork 49
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
Change @ to another qualifier - Suggestion #32
Comments
I agree, and have struggled with this for awhile. Out of the following, is '#' your preference? username~server.tld |
I like # because it's known and easy to type, but might also get other interpretation by people that use social media. Lot's of pros and cons. I think personally I like the / the most, since it's easy, makes some amount of sense, and the con is more for advanced users that will want to find a solution for the escaping problem anyway. |
On a 'qwerty' keyboard the '~' is similar to the '@', it requires the shift key. I agree with your pros and cons, and will go with '/'. I'll include this in the next couple of weeks. Thank you for the feedback! |
XMPP uses [email protected] as well, I suggest keeping it how it is |
The current mobile app allows you to login with either '@' or '/' as a separator, but within the app it displays the '/'. Were you referring to this latest version, or should I avoid using '/' everywhere? |
Right now the users are recognized as "[email protected]"
If wide spread adoption is the goal, this will be confused with Email addresses very easily.
I suggest the use of another qualifier. Discord is getting rid of it's #, maybe that would be an idea?
The text was updated successfully, but these errors were encountered: