Autosave and crash recovery fail very often.

[JapanYoshi]

• Provide a general summary of the issue in the Title above.
• Before you open an issue, please check if a similar issue already exists or has been closed before.

Important

Mark with [x] to select. Leave as [ ] to unselect.

When reporting a bug/issue:

• Screenshot
  

• The FontForge version and the operating system you're using
  20230101 a1dad3e81da03d5d5f3c4c1c1b9b5ca5ebcfcef

• The behavior you expect to see, and the actual behavior
  I was editing kerning on my font. Editing kerning in general is very prone to crashes, so I saved frequently. Unfortunately for me, FontForge saved a corrupted SFD file and lost the vast majority of my glyphs!
  xkcd-script.zip

I tried to recover my lost work by using the in-built "recovery" option (which I already had little faith in). Infuriatingly, it showed me the exact same damn font file, because as far as FontForge is concerned, I hadn't made any changes since the saved font file, and as such, the autosave folder was blank.

This miscreant of an autosave system also resulted in a corrupted kerning table in my previous project, Stampatello Faceto, leading to a problem that took over a year and non-FontForge tools to rectify,

Why can't FontForge be like a NORMAL program and autosave a full SFD file every few minutes, so that when it crashes, I can pick up where I left off?

And no, "just use your own version tracking" is not a workaround.

• Steps to reproduce the behavior
  I don't know what specifically crashes the program or corrupts the kerning data, but it has happened to me very often. Practically every other font project that I kern has had crashes and corruptions related to kerning.

• (optional) Possible solution/fix/workaround