Nothing you save waits for a signal.

A bookmark, a tag or a delete is written on the phone and appears in the list immediately — no spinner, no failed save to retry. A small dot marks the ones the server has not seen yet.

Those are uploaded on the next sync: when you open the app, come back to it, pull to refresh, save something new, or in the background every six hours. One that is still waiting while you read it is not lost; it is just early.

1. Uploads what you changed. Oldest first, so the order you tapped in is the order the server sees.
2. Fetches what is new. It stops as soon as a page is entirely familiar, so a quiet library costs one short request instead of a full download.
3. Checks everything every twelve hours. All pages are read and any bookmark the server no longer has is removed from the phone. This is how edits made in the web UI reach you: within twelve hours, or immediately if you pull to refresh.
4. Keeps your edit. When a bookmark changed on both sides, the most recent edit wins — and yours is uploaded before anything is read back, so a stale copy cannot overwrite it.

The bookmark sync finishes first, so the library is usable the moment it is done. Then the text streams in behind it: every bookmark Shiori has a copy of, newest first, in batches of twenty, with a running count next to the sync status.

It all comes from your Shiori instance, never from the sites themselves. A failure stops quietly and resumes on the next sync, and the whole download can be switched off in settings.

Your session lasts thirty days. After that the sign-in screen comes back with your server address and username already filled in — one password, and everything resumes where it was.

No analytics, no telemetry, no crash reporting, no account with anyone else. The only network traffic is to the Shiori instance you configured, and everything you read is already on the phone.