David, thank you for opening up this discussion. My ideal Autosave improvement in Grasshopper 2.0 is as follows:
Mechanism 1 - Autosave files are always saved in the same folder where the original file is saved. The number of autosave files can be customized, and the oldest autosave file is deleted whenever the newer file is saved.
Mechanism 2 - Autosave files are stored in a separate folder like the current Grasshopper version, but users can customize the duration of those files are saved in the folder like several months.
There’s redundancy in this way, which gives more chances for users to recover lost Grasshopper files.