Show a comment field below a discussion, with rich text and link functionality, to inspire people to craft a detailed answer.

Maybe they will forget to type Ctrl+A, Ctrl+C before hitting send.

So when they do, show a message that "you must be logged in to comment". Use a JS SPA to make sure that there is no way for users to restore their drafted comment. Don't show it after they logged in. When they use their browser's back button, they surely want to exit the application, so make sure to discard any transient data in that case.

Seen on WordPress.org using their infamous Gutenberg block editor.

We're all transient bytes in a big application 😵

I hate the feeling when the processes maxing out all my cpu cores are processes I thought were long since terminated. I guess even when I rm -f I don't really let go and still have the tar.gz in the back of my mind somewhere, and somehow zcat pipes those seemingly tidy archives all over my cwd at the worst possible times like some systemd transient timer that I can't recall the syntax to check... This is when the shell becomes unresponsive and I can't cd away, or even ps aux | grep -i 'the bad thoughts' to get their pid to figure out why this is happening again. Is it really time to hold down the power button? I'm so afraid of loosing unsynced data, I'll wait a little longer...