When Jami launched, I think many of us (including me) didn’t know how Jami works and that too the about nature of usernames. May be because of that, people (including me) uninstalled Jami thinking they could relogin using the username.
Many try to maintain consistency in usernames across platforms to indicate their identity/persona. Losing usernames in Jami, accidentally, is sad.
IIUC, the Username-JamiID mapping exists separately (ns.jami.net) from the records of JamiIDs. Can it be reset for just once? Then, include a banner/mention in the signup page/window about the nature of username and how it can’t be recovered once its lost, to prevent the accidents from happening again?
Possible ways:
[1] Remove Username-JamiID mapping that’re inactive for more than year.
[2] Remove all the Username-JamiIDs and re-record the Username-JamiID mapping from the current Jami sessions.
I agree with @pmetras. I would not be in favour of changing this. It’s unfortunate to lose a username through not having read the instructions, but security is paramount.
Still learning here, if this is obviously answered in docs my apologies…
Not sure I understand this issue…is the constraint there are no additional fields/data associated with JamiID besides the username? And there is no provisioning for multi-factor auth of any type (hardware key, email/phone signalling, etc)?
This is difficult because Jami’s server doesn’t save the password for the account, it just binds the username to a randomly generated id.
If you lose your id, that’s unfortunate, but there’s nothing to be done about it because everything is stored on your personal device, which is safe because no one, including Jami’s official staff, can gain access to your account from the server level. But this also results in the server not being able to do anything with your account.
So it’s a problem where you can’t have it both ways.
so
(1) all account authentication is located/executed by the JAMI client on the personal device?
(2) then the JAMI client connects (to the openDHT server) using only the fingerprint / randomly generated id?
I note that the backup of the user account on the personal device results in a 16kB binary file which contains my contacts. This is a very nice feature if I have to rebuild my pc or move between operating systems. However I am confused between Link and Backup/Restore function result:
When I used backup from one personal device to install a new one, the fingerprint is the same.
Is there functional difference between “Link Device” and Initializing a new client with a backup from from the first personal device? For the purpose of the question please assume that both personal devices are operating and connected to the internet.
For the same account to have different fingerprints when logging in on different devices, they shouldn’t be functionally different at this point, but it depends on the network and how good the software is.
