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.
>>1477343Why not use real folders under the hood instead of a database?
>>1477399A good suggestion actually, andprobably what I *should* do.Since no one replied to this threadfor about a day, I ended up disablingfolder copying at 1GB, with a popup explaining that it's to prevent the user from softlocking themselves easily (fortunately most people will never encounter this, and those who do will likely be trying to softlock deliberately).So, a user *could* still break it by copying something like 20,000 files but it'd bereally hard and take 20 hours or so.If I ever update the app to store morecomplex/large stuff I'll probably go with this. But thankfully the file sizes of the db files are really small so it's not an issue.
