# Manage pseudo renaming correctly

**URL:** <https://meta.discourse.org/t/manage-pseudo-renaming-correctly/17458>\
**Category:** Feature\
**Created:** [11.Июль.2014 09:28:49 UTC](https://meta.discourse.org/t/manage-pseudo-renaming-correctly/17458 "2014-07-11T09:28:49Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)\
**Post date:** [11.Июль.2014 20:30:56 UTC](https://meta.discourse.org/t/manage-pseudo-renaming-correctly/17458/10 "2014-07-11T20:30:56Z")

</div>

> [@codinghorror](#):
>
> But the point is, for the average user, changing your @username is a rare event

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.

---

_[View the full topic](https://meta.discourse.org/t/manage-pseudo-renaming-correctly/17458)._