Status icon (aka. badge) for vaults shared but not yet granted access

[chenkins]

Story

• Persona: cipherduck user
• Need: feedback on which vaults can/cannot be opened
• Purpose: not being confused

Acceptance Criteria

Open Questions

• same in hub?
• which icon or filter out?

Context/Notes

[overheadhunter]

Can you elaborate this? Might be something that needs to go upstream

[chenkins]

@overheadhunter status icon aka. badge see https://docs.mountainduck.io/mountainduck/sync/#status-of-files.

Alternative: we do not show these vaults at all, we filter out those requiring access grant in the client.

TODO need to check how these vaults are displayed in the hub.

cryptomator/cryptomator@develop...feature/new-hub-keyloading -> "URI constructed from params known to be valid". If I understand correctly, users need to add vaults themselves to cryptomator client (there is no open all vaults under this folder to my knowledge, is there?), so here less of a problem.

[overheadhunter]

Oh I see, so this is a client-side feature. There is no such thing in Cryptomator: You can add any vault to its list and will only know whether you can unlock it (or why you can't) when attempting to do so.

I have mistaken this for a Hub (i.e. web app) feature, but I guess you use this repo to track issues for both sides?

[chenkins]

@overheadhunter yes, the idea is to track everything cipherduck-specific here (hub upstream issues go to cryptomator/hub directly) and to use the issue labels client and hub. Let me know if that does not work well for you.

[chenkins]

Current implementation filters them out, see 403 -> continue in HubSession.sync() -> we could display the bookmarks in the menu greyed out, but never connect.