Skip to content
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

Feature Requests #98

Open
Vig2OOO opened this issue Jun 23, 2023 · 1 comment
Open

Feature Requests #98

Vig2OOO opened this issue Jun 23, 2023 · 1 comment

Comments

@Vig2OOO
Copy link

Vig2OOO commented Jun 23, 2023

Would like to see the following feature requests:

  1. Ability to set an expiration date for a file OR number of downloads before file is deleted instead of it disappearing after one download. Example:
    2023-06-22 20_03_21-Transfer large files securely
  2. Show the exact date and time when the file expires (e.g., June 30, 2023 at 8:00pm EDT instead of 6 days, 23 hours, 59 minutes, 22 seconds)
  3. Create a link to manually delete file.
@stophecom
Copy link
Owner

Hi @Vig2OOO, thanks for the interest in this project and your suggestions. These would indeed be valuable improvements. If you need those things now, I suggest to have a look at https://send.vis.ee/ - it is a very similar service that offers what you are looking for (or at least partially).

If you want to see it on sharrr.com, feel free to add a PR - I have limited resources right now to further develop this project.

However, what I can do is adding some thoughts on how to achieve what you need:

  1. With the current design, there is no way to know what files (on S3) belong to an entity in the database. See https://www.sharrr.com/about for design reference. Which means, if you wanted to have "custom deletion settings" with the current design - it needed to be stored e.g. as part of the file name on S3. I see this working for e.g. a custom retention period, but becomes a bit more complicated for "amount of downloads" (Maybe with some meta data - not sure). Alternatively, one could store file references in the DB, but that would make the whole concept less secure. (I'd be happy for ideas on how others have solved that.)
  2. Should be easy to do
  3. This feature (only) made sense in combination with 1. In current setup you will always "soft" delete the file when you visit the link (and click download)

Hope that helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants