Chapter 4 · Where Your Work Lives
Connecting Dropbox
Connecting Dropbox gives your manuscript a home outside Storskarvia. This chapter covers the handoff itself, the folder Storskarvia is sandboxed into, how paths translate, and every way the connection can go wrong.
What connecting does
Once Dropbox is connected, any document you point at it is written into your own Dropbox as real files while you work:
- the full document, as
.skarvia.json; - a plain-text copy, as
.txt; - for a novel with two or more chapters, a
.chaptersfolder holding one.txtper chapter; - a
.versions/folder for the versions you save by name.
Chapter 3 covers what each of those files is for and when one is skipped. This chapter is about the connection underneath them.
The connection belongs to your account, not to one document. You authorise Dropbox once and then choose it per document from the storage dialog.
Connecting it
There are two doors to the same place:
- From your Account page, under Connected storage: Connect Dropbox.
- From inside the editor, when you pick Dropbox in the storage dialog before you have connected. The dialog says Connect Dropbox first: with a Connect Dropbox button beside it.
Either way you are sent to Dropbox to approve the connection, then returned to where you started. From the Account page, you land back there with Storage connected. ✓ at the top of the storage section. From the editor, you land back in the same document. If it has no home yet, the storage dialog opens again by itself; otherwise click the storage chip in the status bar. Pick Dropbox, and this time the path field is there instead of the Connect button.
Finish the approval in one go. The token that carries you through the handoff expires after ten minutes. If you wander off mid-approval, you come back to your Account page reading That connection didn't complete. Please try again. There is nothing to repair: click Connect Dropbox again and go straight through.
The same message appears if you finish the approval in a browser where a different Storskarvia account is signed in. The approval must come back to the browser and account that started it. If your Storskarvia session has lapsed, you are sent to sign in before the handoff starts.
What Storskarvia can see
The connection is App-folder scoped. Dropbox gives Storskarvia one folder of its
own, at Apps/Storskarvia, and nothing outside it exists as far as the application is
concerned. It cannot read your tax returns, your photos, or another app's folder. Dropbox enforces
that boundary, so it holds whatever Storskarvia's own code does.
The access token is encrypted where it is stored. Storskarvia asks for offline access so it can refresh that token quietly instead of asking you to reconnect every few hours.
Where your files land
Because of the app-folder sandbox, every path you type is relative to
Apps/Storskarvia. This is the detail that confuses people, so concretely:
| You type | It lands at |
|---|---|
/My Novel/Chapter 1 | Apps/Storskarvia/My Novel/Chapter
1.skarvia.json and Chapter 1.txt, with named versions in
Apps/Storskarvia/My Novel/.versions/ |
/Scripts/Pilot/Act One | Apps/Storskarvia/Scripts/Pilot/Act
One.skarvia.json and Act One.txt |
The field is labelled Folder & file name, and the line under it previews
the result: Saved as /My Novel/Chapter 1.skarvia.json + .txt · versions in .versions/.
Storskarvia fills the field in for you, built from your project title, the folder the document sits
in, and the document title, so the common case needs no typing. Do not add a "Storskarvia" folder of
your own to the front: you would end up with Apps/Storskarvia/Storskarvia/….
Rules the path follows:
- It must start with
/and must not end with one. You are naming the document; the file extensions are added for you. Break this and Save here answers Give a full folder path like /My Novel/Chapter 1. - Characters Dropbox cannot store in a name (
\ : * ? " < > |) are stripped out of project and document titles when the suggestion is built, so a document called What Now? becomesWhat Nowon disk. - If something already sits at the suggested name, Storskarvia adds a number and offers the
next free one, so a second Untitled is offered as
/My Novel/Untitled 2.
Type a path by hand where a .skarvia.json, a .txt or a
.chapters folder already exists, and Storskarvia refuses to write over a file it did not
write. The status-bar chip reads ⚠ name already taken in Dropbox › Apps/Storskarvia/….
Click it and choose a different name.
When it syncs
Storskarvia pushes to Dropbox as you write, on save, at most once every ten seconds for any one document. There is no sync button to remember. If you want the cloud copy written this moment, press Ctrl+S (Cmd+S on a Mac), which saves and pushes straight away.
Choosing or changing a document's storage destination also pushes at once, and so does reconnecting an account that had fallen out of touch.
The chip in the editor's status bar tells you whether your words have reached Dropbox:
| The chip reads | What it means |
|---|---|
| ✓ saved to Dropbox › … | The last push landed. |
| … saving to Dropbox › … | A push is waiting or under way. |
| ✗ retrying: Dropbox › … | Dropbox refused or failed a write. The next save tries again. |
| ✗ reconnect: Dropbox › … | Storskarvia has no working connection. See below. |
| ⚠ name already taken in Dropbox › … | Another file holds this name. Pick a different one. |
When the connection breaks
Tokens expire, people revoke apps, and Dropbox occasionally says no. Storskarvia refreshes the token automatically when it can. When it cannot, or when Dropbox keeps failing writes, a bar appears across the top of the editor: Dropbox stopped saving your work. Your recent changes are safe on Storskarvia, but they aren't reaching Dropbox until you reconnect.
The bar has two buttons. Reconnect Dropbox takes you through the approval and brings you back to the same document. Save somewhere else opens the storage dialog if you would rather move the document to Google Drive or a folder on this computer.
Reconnecting does more than restore the token: every document of yours that was stuck at reconnect or retrying is pushed again straight away, so a day of writing that never reached the cloud catches up by itself. You do not have to visit each document.
The Account page shows the same trouble under Connected storage: ⚠ Dropbox stopped saving. Your work is safe on Storskarvia, but it isn't reaching your Dropbox until you reconnect. Its Reconnect Dropbox button does the same job as the editor's and returns you to the Account page. The warning is hidden on the page you land on while the catch-up push runs, so reload a minute later to check. If it is still there, reconnecting was not the fix: open the document, and if its chip reads ✗ retrying, Dropbox itself is refusing the write. A full Dropbox or a name Dropbox will not accept are the usual causes.
Nothing is lost while the connection is down. Storskarvia keeps your working copy, and an unsynced change stays on Storskarvia until it lands in Dropbox. One exception: with zero retention on, Storskarvia holds no copy of a document it has already synced and sends its automatic checkpoints only to Dropbox. While the connection is down, such a document may refuse to open (Storskarvia couldn't load this document from Dropbox, so editing is paused), and its checkpoints go nowhere. Reconnect before you write. Chapter 7 covers what zero retention trades away.
Disconnecting
Account page, then Disconnect Dropbox. What that does:
- Storskarvia forgets the token. Mirroring stops immediately.
- Every file already written to your Dropbox stays exactly where it is. Disconnecting never deletes your manuscripts.
- Documents that live in Dropbox switch to
✗ reconnect:at once, and open with the Dropbox stopped saving your work bar until you connect again or use Save somewhere else. Connecting again pushes them all.
The same holds at the far end: deleting your Storskarvia account removes what Storskarvia stores and leaves the files in your own Dropbox untouched. That is the point of the whole arrangement. Google Drive works the same way with a few differences, covered in Chapter 5.
Updated 2026-10-13 · Full contents · Something wrong or missing?