2 ms·

Good question. Simple answer: no. I've thought about it though, but haven't settled on anything yet. I can't inspect files. I'll add an abuse report notice soo

Good question. Simple answer: no. I've thought about it though, but haven't settled on anything yet. I can't inspect files. I'll add an abuse report notice soon, abuse@ is already live. I'll attempt to manually review cases. That doesn't prevent illegal sharing, but I think that's the best I can do. If things get out of hand, I might take the instance down. I don't want to support hosting illegal stuff. A newer Send version (yet to deploy) also shows a clear warning, and requires users to tick a confirmation box, when downloading through the webpage. I hope that helps preventing malware installations.

Reelin 6y ago
Earlier you said the max file TTL is 1 day. That's brief enough that it seems the only meaningful action you could take much of the time would be to log the incident and report it to the proper authorities. Between the short TTL and E2E encryption, I'm struggling to think of any legal obligations you would have in most western jurisdictions. Perhaps logging in some places? Even the DMCA permits more than 24 hours to respond to a takedown notice.