Writing that has not been saved

Every Markdown box in Go Scribi keeps what you type in your own browser until the server has it. Close the tab on half a sentence, lose the laptop's battery, press "leave anyway" on the warning — the writing is still there when you come back.

What it is not

It is not a save, and it never says it is. The word "Saved" belongs to the server: when writing is kept in your browser and nowhere else, the line under the box says Kept on this device — not saved yet, and it labours the difference on purpose. Somebody who reads "Saved" is somebody who closes the laptop.

It is one browser on one device. Writing kept on your laptop is not on your phone, is not in another browser on the same laptop, and does not survive clearing your site data. It is not a backup and it is not synchronisation — it is the gap between your last save and now, somewhere safer than nowhere.

Getting it back

Nothing is ever put back into a box on its own. Open a note with unsaved writing in it and the page says so, above the note and again inside the editor, with three things you can do:

ButtonWhat it does
Put it back in the box Drops the writing into the editor, where you can read it, change it and save it in the ordinary way.
See what is different Shows the saved note against the writing on your device, as the same kind of difference the note's own history draws.
Discard it Throws the kept writing away. It asks first, because there is no other copy of it and no undo.

Why it is not put back automatically. A box refilled behind your back is how somebody else's work gets overwritten: the text comes back but the note's version number does not, so a save looks current and quietly replaces whatever was saved in the meantime. Putting writing back is therefore something you do, on a page whose version number is the one the server just gave it.

When it stops being kept

By itself, and without being asked to. The moment what is kept matches what the server has — because you saved it, because you typed it back, or because somebody else saved the same thing — it goes. There is no housekeeping to do and nothing accumulates behind you.

Signing out, or signing in as somebody else, removes everything that is not the current account's. Writing done through a share link is kept under that link and never under an account, in either direction — a public link cannot leave anything in your own store, and your own writing is never offered to a visitor.

The same note open twice

A draft belongs to the writing, not to the window — so two tabs open on one note share one kept copy, and the last thing typed is what is kept. Both tabs still hold their own words on screen, and saving from either is refused in the usual way if the other got there first, with both texts shown.

A tab that is still holding unsaved writing keeps it, even after another tab saves and clears what they shared. Discarding deliberately — from the list, or from another window — is left alone: that was a decision about that writing, and it is not undone behind you.

Finding what you have forgotten

Not yet saved appears in the sidebar when there is unsaved writing on this device, with the number of pieces. It lists each one, where it was written, when, and enough of it to recognise — and links back to the page it belongs to. The entry is not there at all on the days when everything you have written has reached the server.

When there is no room

A browser gives each site a few megabytes, and it is possible — if unlikely — to fill it. When that happens the page says so plainly: this writing is NOT being kept. Nothing older is deleted to make space, because that would be throwing away writing you cannot see to keep writing you can. Clear what you no longer need from Not yet saved, and there will be room again.