3 ms·
I also don't want to be responsible for processing other people's data. For example, let's say you upload a song that hasn't been released yet. If it goes to m
by 999900000999 2y ago
I also don't want to be responsible for processing other people's data.
For example, let's say you upload a song that hasn't been released yet. If it goes to my-server.com and then something strange happens and it leaks it's my fault.
If instead it goes to localhost, that risk isn't there.
- codingdave 2y agoAnd then their local system gets coffee spilled on it and is friend, and they call you asking where their data went... I totally understand not wanting to be responsible for their data, but you'd better be really sure that they understand how things work. Uploading to a web app makes people think their data is in the cloud. If you want their data saved locally, use a native UI that makes it clear they are saving a file to their system.
- JSDevOps 2y agoAh I see what you want to do. Maybe have a look at something like ZipApp https://docs.python.org/3/library/zipapp.html https://docs.python.org/3/library/zipapp.html