At the moment Datagram requires you to have the right user credentials. If these are not provided, it won't initialize. And if it would initialize, it wouldn't open any data because the data would fail verification due to the missing user id. This is fine for the use cases where the user sends data between their own devices, but it prohibits sharing datagram with others.
To make multi-user work, verification needs to made optional, and datagram needs to have a built-in user registry where the user can save read keys from other users for data verification.
Deliverables
[ ] Implement user registry
[ ] Refactor data fetch code to optionalize verification & decryption
At the moment Datagram requires you to have the right user credentials. If these are not provided, it won't initialize. And if it would initialize, it wouldn't open any data because the data would fail verification due to the missing user id. This is fine for the use cases where the user sends data between their own devices, but it prohibits sharing datagram with others.
To make multi-user work, verification needs to made optional, and datagram needs to have a built-in user registry where the user can save read keys from other users for data verification.
Deliverables
addUser({ name, read_key, encryption_password })method