> you are handling it carelessly From the post: > Everything is local first, the input data is on your filesystem. If you're truly paranoid, you can even wra

> you are handling it carelessly From the post: > Everything is local first, the input data is on your filesystem. If you're truly paranoid, you can even wrap it in a Docker container. > There is still a question of whether you trust yourself at even keeping all the data on your disk, but it is out of the scope of this post. > If you'd rather keep some code private too, it's also trivial to achieve with a private subpackage. This seems as safe, if not safer, than the average service where a rogue employee can read/write to your data with little to no visibility. > You are just making it easier for some people siphon other's people data even more. The data is already being siphoned off of them -- usually through vague legal agreements and opaque security infrastructure they can't audit. At least with this model, a user can see the whole scope of data a service is collecting and act accordingly: whether by limiting the data collection as needed or by switching to another service.