Losing draft posts client-side in browser even though code shows local storage is being used

[ltfschoen]

📚 Context

Problem:

I still keep losing draft posts that I've written but haven't published yet.

Relevance:

It is unbearable, especially when you've spent a considerable amount of time preparing a post, only to have it just disappear.

What are the possible solutions?

Here's my explanation of the issues and proposed solutions https://polkaverse.com/12864/how-to-avoid-losing-your-draft-posts-on-polka-verse-74158

If there is only one draft Post being stored in Local Storage, and the post modal disappears, then show an "Edit" button in the header so they may restore that draft Post and continue editing.

If there are multiple draft Posts from the same or different Spaces then store the values in Local Storage under Space + Post key, and if in one of the browser windows or tabs they lose the popup modal of one of the draft posts, provide a "Restore" drop-down or similar, that allows try restoring any of the draft Posts from Local Storage until they find the one they thought they lost

📈 Subtasks

• Store draft posts in browser client-side so it works with VPN

🎯 Definition of Done

• User is able to use a VPN service to protect their privacy even whilst having a poor connection and even if they lose their Websocket connection to the Subsocial node and their draft post disappears, there's an "Edit" or "Restore" button to restore it, rather than just the risk of clicking the wrong thing and finding it gets permanently removed from local storage.