Handle renaming of users #1
Description
The idea
In some of the backends, it is possible for users to change their username. If this happens, many things in FALocalRepo may break, depending on how the backend service handles requests using the old name:
- Attempts to fetch the gallery / journals via the old username will likely fail.
- Attempts to fetch the gallery / journals via the new username will create a new Users object in the database, unrelated to the old one.
- New downloads will be linked to the new username.
Our ideal UI would look something like:
- Viewing a user profile displays all past usernames
- Submissions and user mentions link to the correct user, regardless of the username at the time that the submission was made. It matters less which name is displayed here, so long as it links to the same user in the database.
This will almost certainly require changes to the database in order to connect multiple usernames to a single User.
This will also require changes to FAAPI to detect when a username has been changed (most likely because a call to the user or gallery endpoint has unexpected results) and somehow encode that change in the response.
Implementation ideas
No response