require a unique preferredUsername in the users model, for webfinger guarantees, or
figure out a way to use human-friendly webfinger without requiring preferredUsername uniqueness.
Our users are not tied to preferredUsername so theoretically it should be changeable, but the webfinger integration is the only point where that may not be true.
Either:
preferredUsername
in the users model, for webfinger guarantees, orpreferredUsername
uniqueness.Our users are not tied to
preferredUsername
so theoretically it should be changeable, but the webfinger integration is the only point where that may not be true.