I'll be lazy and comment instead of reading the whitepapers, but as somebody who loses internet connectivity near constantly, the Steemit site should adopt Github's or Trello's approach to ensure local edits don't get blown away on reload. I've always assumed Github used localstorage in the browser, but never dug in. Depending on how long the content is, hitting submit only to find our your connection died and your content is gone… not a fun thing :)
(A quick test shows it doesn't fail so spectacularly, thankfully. Since the submit is ajaxy, the page doesn't reload. Hooray for that, at least. Accidentally closing the browser tab though would still be a bad time. Restoring the tab doesn't restore the content.)
Oooh… Interesting. Looks like unsubmitted comments persist on page reloads. Posts don't though, as far as I can tell.
I've also noticed if you hit "Reply" but don't reply, it remembers you were going to reply and the box will still be open later. So there is some saving going on. As for the white paper, it doesn't discussion user interface details. ;)
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit