22
33Native macOS, Windows and Linux without the live development broker open on a
44welcome screen when no human key exists on this device: ** Buzz** — "Your people,
5- your agents, your projects — all in one place." — with ** Sign in with email **
5+ your agents, your projects — all in one place." — with ** Sign in with Builderlab **
66(the label the Buzz mobile client uses; first-run copy never names the sign-in
77provider) and a live ** Community URL** field with ** Continue** beside it (the
88same field and normalisation as Join a community below). Sign in runs the
@@ -17,7 +17,7 @@ heading unless the page focuses a field itself, and **Back** returns focus to
1717the choice that opened the page.
1818
1919Federated-identity builds (` BUZZ_BUILD_FEDERATED_IDENTITY_CONFIG ` ) do not yet
20- support this flow. ** Sign in with email ** runs under the bundled Builderlab
20+ support this flow. ** Sign in with Builderlab ** runs under the bundled Builderlab
2121plugin's own network grant, which an FI build does not have (its Builderlab
2222calls go through the native FI session; #1461 ), so sign-in fails with
2323* Couldn’t sign in* after the browser step. FI builds need their own first-run
@@ -45,7 +45,7 @@ another Builderlab deployment, and every community in a build whose
4545` BUZZ_BUILDERLAB_URL ` is another origin or empty, pauses on ** Connect to
4646{host}** : nothing a relay publishes names its sign-in portal, so the user
4747chooses. The page says only that Buzz relies on a key for the user's identity; its choices are
48- ** Sign in with email ** , which signs in at ` BUZZ_BUILDERLAB_URL ` and
48+ ** Sign in with Builderlab ** , which signs in at ` BUZZ_BUILDERLAB_URL ` and
4949continues exactly as the welcome screen's own button does (the landing shows
5050the sign-in pending with the address held; the key it creates is linked to that
5151account and backed up there), and setup then lands on ** Join Community** for
@@ -85,30 +85,30 @@ where the backup step can run (see
8585[ automatic backup] ( #automatic-backup-and-optional-recovery ) ); kgoose answers
8686` 404 ` wherever backups are not configured. Not sent, a ` 404 ` or any failure
8787leaves the lookup unavailable rather than empty, and never fails setup: it only
88- decides whether Welcome back offers a restore and whether an import needs the
89- backup offer .
88+ decides whether Welcome back offers a restore and whether an import needs
89+ automatic backup .
9090
9191** Not linked** pauses on ** Get started with Buzz** . ** Create my key** creates
9292and links a key; ** Use an existing key** opens ** Enter your private key** . ** Use a different
9393account** signs out the first-run session and returns to the welcome screen.
9494The browser may retain its portal session. This choice page shows the signed-in
9595email so the account can be checked before linking a key.
9696
97- Creation does not authorize backup. After creating and linking, Buzz asks
98- ** Back up your key? ** , with the disclosure that Block can restore the encrypted
99- copy, including anywhere else the key is used. ** Back it up ** enables automatic
100- backup and waits for the uploader. ** Not now ** persists automatic backup as off
101- when the build supports backup, then continues. A failed upload can also be
102- skipped with automatic backup disabled. First run never reveals a newly created
103- key; Settings → Identity can reveal it later.
97+ Builderlab setup automatically backs up the created key after linking it to the
98+ signed-in account and waits for the uploader. The create/import screens disclose
99+ this behavior. A failed backup stays in setup with ** Try again ** , preserving the
100+ key on this device; it cannot be bypassed by disabling backup. If the session
101+ has expired, retry signs in again and must return to the original account before
102+ uploading. A canceled sign-in or different account leaves setup and the key intact. First run never
103+ reveals a newly created key; Settings → Identity can reveal it later.
104104
105105** Enter your private key** accepts a plain-text ` nsec1… ` key or a text file up to 1 KiB.
106106The input stays masked until ** Reveal private key** is selected using the eye
107107inside the field; ** Hide private key** masks it again. The public identity preview uses npub. NIP-49 encrypted backups are not supported;
108108invalid input stays on the form. ** I lost my key** sits under the input. ** Back**
109- discards the draft. A successful account-backed import links the key and offers
110- backup unless that key already has a backup. An import without Builderlab
111- sign-in skips linking and backup. Importing alone never authorizes an upload .
109+ discards the draft. A successful account-backed import links the key and automatically backs it up
110+ unless that key already has a backup. An import without Builderlab
111+ sign-in skips linking and backup. Importing without a Builderlab account never uploads the key .
112112
113113** Linked** pauses on ** Welcome back** : the account is already linked to a Buzz
114114identity — the key on the user's other device — shown as the full npub under
@@ -125,13 +125,15 @@ stack, **Use a different account** is the same exit as on Get started with Buzz:
125125signs the session out and returns to the welcome screen without importing,
126126restoring or replacing the linked key. The imported
127127key is already the account's, so nothing is linked. Unless the lookup already
128- lists it, a successful import then pauses on ** Back up your key? ** as on a new
129- account; a listed key continues without the offer .
128+ lists it, a successful import automatically backs up the key as on a new
129+ account; a listed key continues without another upload .
130130
131131** Restore your key** opens native recovery in a separate browser sign-in.
132132Only the account’s linked key can be installed. While waiting, ** Cancel** cancels
133133the attempt; during installation, navigation is disabled. A successful install
134- continues without a backup offer. Failure shows ** Couldn’t restore your key** ,
134+ continues directly to community restoration and the next required step, without
135+ another Welcome back confirmation. One status screen shows ** Restoring your key…**
136+ throughout recovery, with a browser sign-in hint while waiting. Failure shows ** Couldn’t restore your key** ,
135137with ** Enter my private key** , ** I lost my key** , optional ** Try again** , then Back.
136138Retry is available for transient errors and partially retrieved backups, but not
137139for unavailable/refused recovery, a complete empty result or complete mismatch.
@@ -143,7 +145,7 @@ signed-in device or a usable backup. Starting over replaces the linked key;
143145old messages and profiles are not deleted, but access does not carry over.
144146Owned community hostnames appear only when present; a failed lookup still shows
145147its error. ** Go back** returns to the prior screen. ** Start over with a new key**
146- creates a key, unlinks the old key, links the new one, then offers optional backup .
148+ creates a key, unlinks the old key, links the new one, then automatically backs it up .
147149The old key stays linked until the new one is on the device,
148150and binding never overwrites, so the unlink comes after creation and before
149151the link. The unlink checks the bound key first: it sends nothing more when
@@ -169,20 +171,13 @@ which stays on the error and is logged in development builds. Once a key is on
169171the device, the page also says what is undone: * Your key is saved on this
170172device, but it isn’t linked to your account or backed up yet.* when
171173the unlink or link failed (a key that isn't linked can't be backed up),
172- otherwise * Your key is saved on this device, but it isn’t backed up yet.* A
173- failure that may clear offers ** Try again** (primary), which repeats the failed
174- step and the rest of the lane, never creating a second key: for the account
175- check, unlink or link, no answer, too many requests (HTTP 429) or a server
176- error (HTTP 5xx), and for the link also a link request that expired, was
177- already used or could not be found, since Try again asks for a new one; for a
178- backup, Builderlab being unreachable or slow to confirm. A lapsed sign-in is
179- never retried, since Try again would send the same sign-in. A failed unlink or
180- link with a key on the device blocks: nothing links the key later, so the page
181- offers only ** Try again** , whatever the failure, and no way past it. A failed
182- backup also offers ** Continue without backup** , which writes nothing and skips
183- the remaining steps for the end of the lane below (Finding communities on a
184- linked account, then the restore); a later sign-in runs the backup again.
185- Before a key exists, the page offers ** Back** to the welcome screen instead.
174+ otherwise * Your key is saved on this device, but setup isn’t complete yet.
175+ Retry to continue.* ** Try again** repeats the failed step and the rest of the
176+ lane without creating another key. An expired backup session prompts sign-in
177+ again and verifies the original account subject before uploading. Canceled or
178+ wrong-account sign-in leaves setup and the key intact. Unsupported backup builds
179+ show configuration guidance. Failed linking and backup cannot be bypassed.
180+ Before a key exists, the page also offers ** Back** to the welcome screen.
186181
187182Within one first-run session the Join page exits only through a join or a
188183restored community; there is no skip. That holds only while the app stays
@@ -518,12 +513,12 @@ hands the sign-in back, whatever the outcome; an earlier pass's result never
518513answers it. A pass that stops to wait for consent, a session or a key binding
519514fails the step, since nothing would wake it again before first run ends. The
520515failed page names the reason without any service response. The automatic choice
521- stays on after a failure, Continue without backup included, so a later
516+ stays on after a failure, so a later
522517Builderlab sign-in may still finish the backup the user asked for. The step
523518hands a sign-in over only when this build's uploader can back up to Builderlab.
524519Anywhere else (a build without backup configured) the step fails at once as
525- * Key backup isn ’t available in this version of Buzz .* without saving the
526- choice, and the user continues without backup .
520+ * Couldn ’t back up your key. This build needs Builderlab backup support to finish setup .* without saving
521+ the choice. First-run failures offer retry and preserve the saved key .
527522
528523When secure storage confirms absence, native recovery commands support explicit
529524browser sign-in. The session and recovered keys remain native; the renderer sees
@@ -783,9 +778,10 @@ The native identity service exposes `getBackupChoice()` and
783778` setBackupChoice(pubkey, automatic) ` . These APIs expose public metadata and do not
784779change identity readiness. Reading a choice does not contact a server; saving
785780automatic backup wakes the existing native uploader if a session is connected.
786- First run's backup consent is ** Back it up** , after creating, replacing or
787- importing a key. Creating or linking the key does not authorize an upload.
788- ** Not now** persists automatic backup as disabled when backup is available.
781+ Builderlab first run discloses automatic backup before creating, replacing or
782+ importing a key, then enables it after linking. There is no separate backup-choice
783+ screen or failure bypass. Independent imports without Builderlab sign-in do not
784+ enable backup. Settings retains control over future automatic uploads.
789785
790786The choice is bound to the current public key and trusted build-configured backup
791787service and namespace. Missing or mismatched metadata returns no choice;
0 commit comments