Yes, but in the quote instance clicking on the username/psuedo doesnât attempt to take you to their profile, so it isnât something that would break. Whereas, mentions do break because that is the intent.
This is kind of irrelevant since you can only change username by default for the first 2-3 days after creating your account.
Admins/Moderators can do it any time, of course.
But the point is, for the average user, changing your @username is a rare event â not sure we need to spend any time optimizing for it at the moment.
This is true for the user, but for very large organizations, since many @usernames are based on real names (2 out of 6 in this topic so far, and especially in corporate settings), it can be rather common for admins of large instances since a significant % of the population changes names at least once in their life, usually in the time frame where they use online tools.
Atlassian decided to use usernames as primary keys in their products, and hundreds of admins have been complaining about it for 10+ years, because changing usernames has been impossible/broken that entire time. Granted, with Discourse it isnât quite that bad because the usernames can actually be changed but it still leaves broken trails of damage around the app.
To be clear, the long username field â that can be changed as many times as you want, any time.
Weâre talking about @username here which may not be tied to your first and last name at all. @username, by default on every Discourse instance, can only be changed for the first few days after the user creates their account.
@jane_smith renamed to @jane_jones after she marries. It would suck to force her to keep her surname forever due to this.
Long term I would like to support correction of quotes and mentions on rename but its definitely not in scope for v1. Not even as a community built feature, way too complex.
I was glad when I could change a username from testacct1
Banging an existing inconsistent username to Discourseâs defination might have high effect during migration i.e. old names in to pseudo names
By this I mean ânot real but as similar as possibleâ, a fake. (so maybe faux-code, meh)
IMHO making changes to have a looser definition is not a wise decision.
giving affected members due time and sufficient Notice is a must do.