Yes, this idea would remain a separate function from cryptography overall (i.e. encrypted data). This would probid a. That a user selects an Algo out of maybe 14 or 15. That Algo then becomes a 'key' Algo. That Algo would have to be matched with a chechsum which would likely be a previous hash in a block somewhere upon that chain of a coont or token of that particular Algo. Each file would effectively be access protected and either encrypted or unencrypted (by separate process). In order to access 'that file' (or directory), the access clearance would have to match checksum with a hash of the previously selected Algo which would be formularically requirant inclusive of a timestamp already provided on that 'lock' (so to speak). Using bots or whatnot wouldn't acheive alot of success because not only does the key Algo have to be the correct Algo, but also, the match checksum has to include verification of the correct timestamp (with some element of temporal order ie. Time of day, day of month, month of year and year possibly). User would be able to specify from file lock as per file or directory as well as a specific scrutiny (i.e. how much accuracy specific to provided time stamp is required. The lock would simply exist 'upon' that file in such a way that access to any element of alteration of that file (read, write and/or move) could not become implemented without first providing a correct checksum from a previous hash on the key Algo (as well as matching the time stamp of that file).