Same URL repository ID for write, blind and readonly repositories

[trymeouteh]

Please have the "URL" for a repository be the same weather the repository is write, bind or readonly. For example...

Read Only
https://ouisync.net/n4qgdki2xvw370y07aivvr3xzzvvzu99/SoeRXwD2hyPe3R3gYFdI1LQDjHPU8cH0rHBF8uLoThO6RVdTCsr4Y61HOvwId7z1

Blind
https://ouisync.net/n4qgdki2xvw370y07aivvr3xzzvvzu99/

Write
https://ouisync.net/n4qgdki2xvw370y07aivvr3xzzvvzu99/QqE9sVxUsPbbQ7XO1z08grKLSxf2UnsjKBXlapzwCv6dmK4md170NJKtjtBAvgB4

The repository ID is n4qgdki2xvw370y07aivvr3xzzvvzu99 and there is a different key depending on the permissions access to the repository.

• If you have write access, you can always get any of the three URLs (readonly, blind and write)
• If you have blind access, you can only get the bind URL
• If you have readonly access, you can only get the readonly URL

Use Case
The usecase to this URL structure is to allow a user to use an untrusted blind node as a node to backup the repository and if the user devices get lost or break, as long as the user has kept the write URL, or the repository ID and the write key/password, the user can recover their repository and its contents by installing Ouisync on a new device and syncing to the blind repository.

Currently the URL is different for the write URL, readonly URL and the blind URL, making it hard to manage the keys of a repository. When creating a repository you do not want to ever lose access to, you will need to backup all three URLs for the repository. It would be nice if instead all you needed to backup was the URL with the write key and with this key, you can regenerate the readonly key and blind key.

[IvanaBlzvc]

https://redmine.equalit.ie/issues/31244

[inetic]

Hi @trymeouteh , thanks for taking time to create the issue and I apologize it takes a long time for us to reply.

What you proposed makes sense for, as you wrote, managing keys manually. But unless I'm misunderstanding something the rest of the use cases are already covered. That is, if you have write token, you can use it to generate a read or blind token, and if you have a read token, you can use it to generate a blind token.

I think right now to do that you'd need to import the repository into the CLI or the GUI app and then ask it for the particular token. It might be useful if the CLI app could do the conversion without doing the importing first.

The one disadvantage of the way you proposed the tokens should look is that it would make the tokens longer than they already are by adding redundant information.

[trymeouteh]

If the tokens in the URL are longer I do not see that being an issue, they are already quite long and to backup, one needs to copy and paste them.

Currently the URL is different for the write URL, readonly URL and the blind URL, making it hard to manage the keys of a repository. When creating a repository you do not want to ever lose access to, you will need to backup all three URLs for the repository. It would be nice if instead all you needed to backup was the URL with the write key and with this key, you can regenerate the readonly key and blind key.

Currently when you only backup the write key and import it into another device and generate a readonly key and blind key from the write key, the readonly key and blind key are different from what they were before.