It should be possible to create temporary shares, ones with an expiration timestamp. After the timestamp, the share will no longer be accessible and its DB entry for it will be garbage collected. Temporary shares should not have a separate table, but should be listed in a separate page on the client UI.
It should be possible to mark shares as unlisted. If unlisted, a share will only be accessible via a direct path.
It should be possible to share a single file.
It should be possible to filter shares (in the client gRPC) based on the following criteria: is temporary, is unlisted, is single file.
All of these features combined with #22 would make it possible to generate and share temporary links for files and folders on a user's computer, which will be an incredibly useful feature when augmented with external tools that interface with the client.
It should be possible to create temporary shares, ones with an expiration timestamp. After the timestamp, the share will no longer be accessible and its DB entry for it will be garbage collected. Temporary shares should not have a separate table, but should be listed in a separate page on the client UI.
It should be possible to mark shares as unlisted. If unlisted, a share will only be accessible via a direct path.
It should be possible to share a single file.
It should be possible to filter shares (in the client gRPC) based on the following criteria: is temporary, is unlisted, is single file.
All of these features combined with #22 would make it possible to generate and share temporary links for files and folders on a user's computer, which will be an incredibly useful feature when augmented with external tools that interface with the client.