[Feature request] Please add the option to use a Weblate ID for logging in or recovering an account.

[maksim2005UKR]

Describe the problem

Hello Weblate developers, I have some suggestions for you.

I don't have any problems at the moment, but I'm missing a login or recovery method, so I really wanted to add another one.

Solution brainstorm

You could add a new Weblate ID, which would allow you to log in using an identifier or to recover your account if you lose access. It would add a new login method and provide greater protection against account hijacking. It would be useful for me if you actually implemented this login or account recovery method.

So please support my ideas as they are useful to me, and thank you for your communication and support.

Describe alternatives you have considered

No response

Screenshots

No response

Additional context

No response

[nijel]

What do you mean by “Weblate ID”? I don't really see what this is about and what problem you are trying to solve.

[maksim2005UKR]

Hello! Thanks for asking for clarification.

By "Weblate ID", I mean a unique user identifier in a format similar to a WeChat ID, consisting of a prefix, a short numeric part, and a long alphanumeric token.

Proposed Format:
Weblate_Idx_[16 digits]_[64 characters]

Example:
Weblate_Idx_0638971593221863_9g56128933ke1465885has127xd99301274ks1v8s6641kes17088034adfhosa67

Breakdown:

• Weblate_Idx_ : System prefix
• 0638971593221863 : 16-digit unique user number
• 9g56128933ke1465... : 64-character secure token/hash for verification

Benefits of this approach:

1. Alternative Login Method: Users can log in using this ID instead of email.
2. Account Recovery: If access to the email is lost, the ID can be used to recover the account with the support team.
3. Enhanced Security: Two-factor structure (short number + long token) makes it harder to guess or steal.
4. Privacy: No need to expose email addresses for login purposes.
5. Versatility: Works for both login and account recovery scenarios.

Use Case Scenario:

• A user loses access to their registered email.
• They contact support with their Weblate ID.
• They prove ownership via the 64-character token.
• Access to the account is restored.

Is it technically feasible to implement such a system in Weblate? Are there any known limitations?

Additional questions:

1. Would users be able to change this ID after account creation?
2. Would it be public (like a GitHub username) or private?
3. Could it be used to generate public profile links?
4. Would it integrate with existing authentication methods (e.g., SSO, OAuth)?

Thank you for considering this feature request!