Just two short questions:
- Are images saved in a safe way? I remember that Roam’s is not perfect here and it has been one of the reasons why I haven’t used it as much as possible. I am working with a lot of image data that I am not allowed to share.
- What happens with an image when I delete a card that contains it? Will the image be deleted from the cloud? If not, can it be deleted from the cloud in another way?
By this definition, not really: if you know the card id and the file name, you can derive the url of a card’s image.
- only someone who can already see the space will know the card id and file name. So moot in a private space
- the id generator has billions of permutations
When developing the image serving system, balancing speed and security, I noted that trello and other used-in-enterprise tools do this. (It’s the best balance between perf and irl security)
It’s currently not deleted, I might be wrong tho I’ll need to double check. I can change it to deleting the file , but only if the card is permanently removed from the Removed menu
I think this is a good policy. It’s important to give the user the ability to expunge all of their data from the server. Maybe it was sensitive information that they did not intend to upload. Or they just want to leave the service and make sure there is none of their personal data lingering.
Maybe it’s worth mentioning the underlying storage service is Linode (at least currently). So there is some trust in that system: Linode Object Storage | Linode. And I think they are highly trustworthy and reputable.
It would be great if it was possible to delete the data, e.g., when the card is completely removed.
Just want to +1 this, especially if it’s a small scope—I think if the image upload feature had existed when I was first evaluating Kinopio, I would have had this question, and it would have been important to me that I knew I could expunge my data in case I didn’t end up using the service. I feel like this is good all around—it recovers some storage space and reduces Kinopio’s “liability” of having sensitive/unwanted assets.
Amazing! Looking forward to it!
turned out to be v non-trivial, involving lots of internal server changes that affect bunch of stuff:
verified in db and transmit
x remove space soft
x delete space
x delete all spaces
x restore space
x restore card
x remove card from cardDetails
x remove card from multiActionsSelect
x delete card
x delete card w asset
x click/unclick empty card to delete (low perf impact)
x delete all cards
in the final review phases, will release this tonight or tmrw morning
ok this is now live, give the app a refresh and let me know how it goes . i’ll market it tmrw
Amazing :). Thank you very much for your hard work!
Maybe worth adding something about this in the help? https://help.kinopio.club/posts/privacy-policy/
will do , thanks for the reminder