@dhimmel and myself have recently gone through the traumatic experience of losing two hours worth of pristine, beautiful brain juice.
Poor habits, forged in a world where auto-saving is the norm (Evernote, Gmail, BS Word...), led us to blissfully write long comments and start discussions but without actively using the "Save as Draft" feature - mainly because the piece was intended to be posted. Of course, the wonders of modern technology sometimes result in random crashes and reboots, or wild logging out (by Thinklab systems, with irrefutable legitimacy). No drawing is needed - catastrophes ensued.
The proposition here is to mitigate these issues by automatically 'saving the draft' at regular intervals, whatever option is finally chosen. Like normal drafts, these 'background drafts' will either be deleted over posting or overwritten if saved again. The only foreseeable problem with this strategy is automatic overwriting of an existing 'voluntary' draft, but use-cases that would be affected by such a behavior are hard to think of.
Thanks to @jspauld for giving us an open space to Think.
Auto-save could be helpful. There are three situations to consider here:
When Thinklab eats the content (posting while logged out or before having a verified account).
Client-side crashes or user errors that lead to an open composition getting lost.
Accidental deletion where a use removes all text from a composition. In this case, autosave could lead to content loss.
Poor habits, forged in a world where auto-saving is the norm (Evernote, Gmail, BS Word...), led us to blissfully write long comments and start discussions but without actively using the "Save as Draft"
My issue is that I only save when I have writer's block. When I'm on a writing spurt, I don't to deviate from content creation.