Stackedit: How I lost all my work with StackEdit

[dandv]

So I (re)discovered StackEdit yesterday and spent the whole day in its lovely interface importing Markdown files, updating them, writing new content etc. StackEdit stores all your files "in your browser", great.

This morning I was doing some debugging which messed up the cookies, so I did what I sometimes do in that case, Clear the cache/cookies/site data for the last hour:

I'm sure I'm not the only StackEdit user who's ever done this.

Here's the catch: I don't know if StackEdit autosaved something, but its IndexedDB (or wherever else it stores data), was also wiped out. Not just last hour (I didn't edit much during the last hour). Completely gone.

ALL MY WORK GOT WIPED OUT.

Now I fully understand the request for a desktop edition with real access to the filesystem (#323). I'm switching to Notable myself.

My last words: please consider adding a warning somewhere about Clearing browsing data. People do use that function not realizing its implications fully, and the loss potential is just too great.

[matrixik]

I'm not sure about longevity of any small service today so I'm using private GitHub repository as workspace for StackEdit. This way I also have history of edits to all files. But I don't know if this helps you with offline editing...

[WhyNotHugo]

StackEdit is a work editor, but I can't really figure out how to programatically export HTML or reliably save my work.

The whole markdown+github idea is very programmer-friendly, but then, saving/exporting is manual and has to be done via point-and-click?

I though it was just the online demo, but the dockerised version is the same. Looks like the whole "saving" idea is still missing.

[Yash-Singh1]

I don't think you should rely on StackEdit's cookies for storing your work. Either use the Sign in with Google or keep a backup on your computer.

[WhyNotHugo]

Yeah, not a fan of having to create a google account just to save stuff on StackEdit, sorry.