-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revolving Link in blindsend: Enable many-to-one, and multiple-time upload use-case #12
Comments
This becomes the request use-case then, we ditch the current one? In this case, R gets 2 links - one to share with A B C and one for her to download files. If users concurrently upload multiple files in a span of few days, download files page can seem very disorganized (R doesn't know who uploaded which file). |
We need to work on the exact workflow, as I think we might in fact need a similar thing for PrivateForm that we are building now, with the difference that in Private form, each of the users A, B, C must be able to invoke their GDPR rights on the specific files they uploaded. R must still have a revolving link. |
I have encountered the need for this same feature once again. The scenario is the following: what do you think @m4rk055 ? |
I think having 2 links (one for the client and one for the lawyer) is less confusing - lawyer may wonder why is there the "add files button" and client may see the password field and completely overlook the possibility to upload additional file. If multiple users are uploading, it gets even more complicated. |
You are right. Would it be possible to have the two links be in some sort of correspondance (we can derive one link from the other)? Maybe this can be solved by just appending "s" or "r" letter to the link. I think people get that the link is a reference to their exchange of files, and that they (both sender and receiver) will deal with the same sort of box where files reside (that is identified by the link) and that there are two context (send and receive). |
Sure, it can be done. |
The receiving user (R) creates a link to request files. She shares this link with mutiple sending users (A,B and C), and request each one to send her a few files.
The goal of this feature is to anable the following behavior sequence:
User A goes to the link, uploads a file 1.
User B goes to the same link (can't see priviousely uploaded files by A), uploads his file 2.
Receiving user R can download and decrypt the files 1 and 2 submitted by A and B. Without creating a new link, the user R writes to user C to remind him to submit his file, and also tells A that more files are needed from him.
Users A and C, independently go to the same link, sumbit new files 3 and 4 (without the ability to see files 1 and 2).
Receiving user R downloads and decrypts filles 1,2,3,4.
The receiving user R can therefore have a permanent link to which anyone can send him files at any time.
The text was updated successfully, but these errors were encountered: