From d0d055839ab378f91f52b40e7e1ef88a6490139c Mon Sep 17 00:00:00 2001 From: Scott Reimers Date: Wed, 22 Apr 2026 00:05:53 -0400 Subject: [PATCH] Download page: keep v0.5.3 links as upgrade bridge for v0.5.0-and-older users The v0.5 export format matured in v0.5.1; exports from 0.5.0 or earlier won't import cleanly into v0.6. Add a secondary warning pointing those users to a two-hop upgrade via v0.5.3, with direct links to the archived 0.5.3 artifacts that remain on the server. Co-Authored-By: Claude Opus 4.7 (1M context) --- website/download.html | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/website/download.html b/website/download.html index 03349c0..fc7e6da 100644 --- a/website/download.html +++ b/website/download.html @@ -27,7 +27,7 @@

Available for Android, Linux, and Windows. Free and open source.

- Upgrading from v0.5? v0.6 is a hard network fork — older versions can no longer reach the network. Bring your account over in three steps: + Upgrading from v0.5.1 or newer? v0.6 is a hard network fork — older versions can no longer reach the network. Bring your account over in three steps:
  1. On your current v0.5 install, go to Settings → Export, tick “Posts + media + identity key”, and save the .zip somewhere safe.
  2. Download v0.6 below (APK, AppImage, or Windows installer).
  3. @@ -36,6 +36,16 @@

    Your posts, media, follows, and identity key all come across. Encrypted posts stay decryptable under the same key.

+
+ Upgrading from v0.5.0 or older? The v0.5 export format matured in v0.5.1, so a direct export from 0.5.0 won't import cleanly into v0.6. Do a two-hop upgrade: +
    +
  1. Install v0.5.3 Linux AppImage / Android APK / Windows installer and open it. It reads your existing data in place.
  2. +
  3. In v0.5.3, go to Settings → Export and save the bundle.
  4. +
  5. Install v0.6.0 below and import that bundle on first launch.
  6. +
+

v0.5.3 is kept online only as an upgrade bridge — it no longer connects to the live network.

+
+

v0.6.0 — April 21, 2026

The privacy architecture overhaul. Network identity is decoupled from posting identity — peers cannot correlate network traffic to a posting identity, and users can hold multiple simultaneous posting identities (personas) on one device.