| ▲ | 7bit 2 days ago |
| > it depends on how users choose to use it. Protect yourself as best as you can. The worst that could happen is if this is used for CSAM, and then it's over. |
|
| ▲ | Rayid 2 days ago | parent [-] |
| Well, since all files are encrypted on the client side, I can’t actually read or access the contents of the files being uploaded. That means I can't know what’s being shared. However, I’ll be adding clear policies that will allow me to delete any files that appear to be used unethically or in violation of the guidelines. |
| |
| ▲ | rad_gruchalski 2 days ago | parent [-] | | Since you have access to raw data as it is being encrypted, you can know what material is being uploaded. You could in theory maybe claim that data is encrypted on the client but it is your client served from your domain. | | |
| ▲ | Rayid 2 days ago | parent [-] | | Right, since the client is served from my domain, trust in the code is essential. Encryption happens in-browser, and nothing is logged or intercepted, but to back that up, I’m planning to open-source the website in the future so anyone can verify exactly what’s going on. |
|
|
