Domain changed to archive.palanq.win . Feb 14-25 still awaits import.
[3 / 1 / 1]

Fake Filesystem

No.1477343 View ViewReplyOriginalReport
I am working on a phone app that has a kitsch, fake-filesystem-like interface for storing information. However, I have included the ability to copy folders, and a user determined to softlock themselves could theoretically 1. duplicate a folder 2. move both duplicates into a third folder 3. go back to step 1 until the app's fake-filesystem (stored in an sqlite database) stalls out, softlocks, and breaks.

How do I give the user relative freedom to copy folders without letting them do dumb things like deliberately softlocking themselves/filling the fake-filesystem with crap?

Plz gib ideas. Thanks.