4 ms·

You're right! Luckily files have a maximum lifetime of 1 day, which helps with storage. Almost no computing needed. Expensive en/decrypting operations are done

You're right! Luckily files have a maximum lifetime of 1 day, which helps with storage. Almost no computing needed. Expensive en/decrypting operations are done on the client.

neolog 6y ago
Do you know what you'll do when people start sharing illegal content?
- bfuclusion 6y ago
  Not worry about it? It's not like he can see it anyways, it's encrypted on the client.
  - gilrain 6y ago
    That world certainly be the proper Silicon Valley approach: can this be used to harm people? shrug
    - eertami 6y ago
      I'm confused how much responsibility you want to put on a service provider. If someone sends an encrypted email containing illegal content, is email then considered harmful?
    - Spivak 6y ago
      I mean it's the dream, right? It's what we all wish we could build. You design a system that gives you (the hoster) zero ability to inspect, modify, block, censor, restrict any of your users' content and in doing so you're allowed to abdicate all responsibility for how the system is used because you're literally incapable of controlling it. Pure infrastructure with none of the messy real-world bits.
- timvisee 6y ago
  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.

You're right! Luckily files have a maximum lifetime of 1 day, which helps with storage. Almost no computing needed. Expensive en/decrypting operations are done on the client.

neolog 6y ago

Do you know what you'll do when people start sharing illegal content?

bfuclusion 6y ago
Not worry about it? It's not like he can see it anyways, it's encrypted on the client.
- gilrain 6y ago
  That world certainly be the proper Silicon Valley approach: can this be used to harm people? shrug
  - eertami 6y ago
    I'm confused how much responsibility you want to put on a service provider. If someone sends an encrypted email containing illegal content, is email then considered harmful?
  - Spivak 6y ago
    I mean it's the dream, right? It's what we all wish we could build. You design a system that gives you (the hoster) zero ability to inspect, modify, block, censor, restrict any of your users' content and in doing so you're allowed to abdicate all responsibility for how the system is used because you're literally incapable of controlling it. Pure infrastructure with none of the messy real-world bits.
timvisee 6y ago
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.