Everything that everyone has said here is incredibly crucial, and I know a lot of us 3rd party devs have built stuff on top of Steemit just for it to be usable for curation, etc.

I do have a suggestion about content saving, and sessions which I believe should be also incredibly important as far as reliability of service goes:

A much improved content saving cataloging system: Right now if a post does not go through (due to a transaction error / connection errors), sometimes it might save in the session so when you click back on post some/most of it might still be there, However if you click on post again (say from another browser tab) the content can disappear as a new post-session has been generated. So my suggestion would be to have an actual front-end 'pseudo-perma store' of posts, which can either be saved as a cookie or some other method of JS-storage, such that if you write a post and decide to leave it for a bit (or crashes/connection issues occur), it will/can saved as a 'draft', these drafts can be cataloged client-side and will allow the user to select from their drafts when they write a post again (hence saving the posts/comments and not being destroyed). This would obviously drastically reduce the impact of server instability / client issues in terms of people writing posts/comments.