3 ms·
I find "burn after reading" downloads for a number of reasons, but generally, they often don't work as intended. For example, modern email services (Google, MS
by redm 9y ago
I find "burn after reading" downloads for a number of reasons, but generally, they often don't work as intended.
For example, modern email services (Google, MS, etc.) accessing links in emails and download the content and check it for malware. They probably mitigated this but its caveats like this that cause messages to be burned before the intended reading.
- sterex 9y agoTrue! Also like one commenter said on the original article, if I have to share a file with 3 users, I will have to upload it 3 times and also there's the case of failed downloads. Not sure if this is viable.
- saimiam 9y agoWhy are jumping from imagining a specific use case (1:N file share) failing (with little evidence that the product doesn't/can never recover from failures seamlessly) to calling into question the entire product? Give the product a chance, imho.
- wongarsu 9y agoAccording to yesterday's discussion they do have problems with handling failed downloads, they might want to fix that. But if they would handle 1:N file sharing, they would risk being attractive to a lot of users they don't want (mostly those distributing in a copyright-infringing way)
- qqg3 9y agoIf you were sending a 3 file to 3 people, just use WeTransfer
- gvx 9y agoSince downloading the file has side effects, I assume Mozilla would require the user to push a button that initiates a POST request. And I don't think any modern email service would initiate a POST request, because that would be a massive vulnerability in that service.
- floatingatoll 9y agoThe URL shared to the recipient is /download/, but the actual one-time trigger is bound to /assets/download/.