Skip to content Reserve your Writality username. Reserve yours

Online

Writality is an offline app, I hope that is hammered in now. Your projects live on your computer, and nothing you write needs a server to work. Online is an optional module for some incoming features. Right now that's connecting the username you reserved on the website. Sharing and writing groups are coming in v2.

Online is off by default. With it off, Writality only goes online to check for updates, load a preview of a link you add, or download music and language packs. To make matters easier, I have added an indicator on the top. Whenever it's bright, it means activity is happening in the network.

Turn Online on

Open Settings, go to Modules, and turn on Online under integrations. Turning it off again cancels anything in progress and hides your username. The connection is kept though, so turning Online back on brings your username back without signing in again.

Connect your username

Usernames are reserved on writality.com. Reserve one there first, then connect it from Profile in settings:

  1. Choose the globe button next to your name.
  2. Choose Connect your username.
  3. Enter the email address you reserved with, then choose Email me a code.
  4. Enter the six-digit code from your email and choose Connect.

To disconnect, open the same menu and choose Disconnect.

Codes expire after 10 minutes and allow five guesses. If a code doesn't work, request a new one. Writality should only accept the latest ✨ code you asked for.

What Writality sends

Connecting a username sends your email address, the code, and later a session token. Your email is encrypted and saved in the server.

Every Online request goes to www.writality.com and nowhere else. The address is fixed in the app and can't be changed by a setting or a redirect. Requests carry no cookies, aren't cached, and give up after ten seconds. Opening Profile reads your saved username from this computer so it doesn't really connect to the internet after that, except to validate occasionally if something has changed.

To deliver the code, your email address passes through Resend, the email service I use. The full details are in the privacy policy.

What's stored, and where

On the server. Your email is stored as a keyed hash. The code is hashed too. A successful connection creates a session that lasts 30 days. The server keeps only a digest of the session token, so a copy of its database can't be used to sign in as you. Expired codes and sessions are removed in batches.

On your computer. Writality keeps your username, the session's expiry, and when it was last verified in its app settings. These are stored with the app on your computer, outside your workspace, so they aren't part of your projects or their backups. The session token is encrypted by your operating system before it's saved:

SystemWhere the key lives
macOSYour login Keychain
WindowsYour Windows account (DPAPI)
LinuxYour desktop keyring (GNOME Keyring or KWallet)

On macOS you may be asked whether Writality can use the Keychain the first time you connect. Allow it if you want to avoid having to reconnect every time.

When the token can't be protected

Some setups have no secure place to keep the token. This is most common on people running Linux without keyring. It also happens if you deny the Keychain prompt on macOS. Can't say for sure about windows. I am sure there are occasions.

In those cases Writality keeps the connection in memory only. The default would save it in plain text, but that could be problematic. This method means that for those cases, you would have to login again after the app quits every time. The globe's menu says so beneath your username, so it won't be a surprise. Linux can also fall back to storing secrets with a fixed, built-in key; Writality treats that as unprotected and won't use it.

If you'd like the connection to persist on Linux, install and unlock GNOME Keyring or KWallet, then connect again.

Signing out

Disconnect clears the connection on your computer first, then asks the server to end the session. If the server can't be reached, you're still signed out on your machine. The server session simply runs out at its expiry.

Occasionally the saved token can no longer be decrypted. This can happen after moving your settings to another computer or changing keyring. Writality discards it and asks you to sign in again. Since the token is unreadable, the server session can't be ended from here. Writality tells you so, and the session expires on its own within 30 days.

What this means for you

The token is protected from other people's accounts and from copies of your files. It isn't protected from someone using your unlocked account, the same as a browser's saved logins. But honestly, at that point you're cooked anyways and your writing is there. If someone else uses your computer as you, they can act as your username until you disconnect.

Now I know this is a bit overkill for an offline writing app, but there have been so many security problems recently thanks to AI, that its best to err on the side of caution.