lee on Nostr: Every social media company today does #2. They remove content async. The law seems ...
Every social media company today does #2. They remove content async. The law seems happy with that.
If you wanted more assurances you could do something fancy where you save the file locally for those 14 seconds. If the file is requested while CV is running, return a placeholder loading image. Then after CV completes, you start seeding the file as a torrent (if passes checks) or delete it from local disk (if fails checks).
It's not materially different than hosting images and scanning them with CV in a traditional way without torrenting involved.
At the end of the day, it's your code controlling the ingress/egress of bytes from your machine. Torrents or not. You can control the flow of that however you'd like.
If you wanted more assurances you could do something fancy where you save the file locally for those 14 seconds. If the file is requested while CV is running, return a placeholder loading image. Then after CV completes, you start seeding the file as a torrent (if passes checks) or delete it from local disk (if fails checks).
It's not materially different than hosting images and scanning them with CV in a traditional way without torrenting involved.
At the end of the day, it's your code controlling the ingress/egress of bytes from your machine. Torrents or not. You can control the flow of that however you'd like.