Design draft: fixing deletes and server side copy

[jammerdan]

Massive reads on startup

This should absolutely not be hard-coded and rather run when it is appropriate over the course of a day. As I have suggested, if the files that get moved into trash get stored in a database with their modification times, any future deletion day can be calculated from that and then it is only a query to the database once a day which files to delete which can be put into a low priority background task for final deletion over the course of a day. This hard-coded sounds also weird. My gut feeling…