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

"Destruct after the first download" not working with messenger apps #365

Open
paulkitt opened this issue Aug 4, 2021 · 6 comments
Open

Comments

@paulkitt
Copy link
Contributor

paulkitt commented Aug 4, 2021

When using the "Destruct after the first download" option and sharing the link via Slack, Mattermost or Signal the download gets destroyed. The messenger apps try to render a preview which counts as a successful download in plik.
My guess is that its the same with Telegram, Whatsapp, etc

It would be very great that the download gets deleted after the whole file is transferred successfully. A quick fix would be to have small site for each download with a start download/stream button.

We also had users surprised that the download was gone after they clicked the Cancel button in the download box in their browser. Changing/Fixing this would solve both problems :)

@paulkitt
Copy link
Contributor Author

paulkitt commented Aug 4, 2021

The streaming option has the same problem. When sharing the file link with a messenger the preview is starting the stream download.

@camathieu
Copy link
Member

camathieu commented Aug 4, 2021 via email

@paulkitt
Copy link
Contributor Author

Thanks for the quick reply. Sadly I am not a go developer and cant contribute to the project in this way 😞

@camathieu
Copy link
Member

See also : #281

@tvelvet
Copy link

tvelvet commented Oct 5, 2022

same here. :( i really love plik tho. :) make my life easier.

is it not possible to change how many times a streamed file can be downloaded? i can't really send the link via messenger, webex, team and others. Or have to obscure it somehow. :)
it works on fibridge and drop-it.
https://github.com/Orange-OpenSource/just-drop-it
https://github.com/anderspitman/fibridge-proxy-rs

@acuteaangle
Copy link

acuteaangle commented Nov 6, 2023

For anyone else finding this, here are two workarounds (that have made this a non-issue for my use case at least, and hopefully yours as well):

For direct links (plik.domain.tld/file/<pasteID>/<filename>), you can enable the password option and send the credentials along with the link. It will only burn your stream/autodestruct with the correct credentials, so application previews, email tracker protection, etc. won't interfere with it.

For indirect links (plik.domain.tld/?id=<pasteID>), every application I've tested worked fine – nothing crawled through to the direct links for the file(s).

Perhaps some information could be added to an FAQ/docs/tooltip somewhere?

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

No branches or pull requests

4 participants