0.0.31: settings reads as two networks, and a retry stops failing on itself
Two sections asked for "a bridge key" and only one named its network, so pasting
the Bluesky key into the fediverse form was the obvious move — and then the retry
failed with "duplicate channel", because connectBridge built a second ProtomuxRPC
over the still-open connection.
Settings is now one section per network, numbered in dependency order, each step
saying what the one below it still needs. The carry offer no longer hides behind a
local `submitted` flag that only exists for identities minted after that flag did.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
9e80dd839b2a10eaeed79025c54f33f79e6101a1
by plankatron <fleeky@gmail.com> · 2026-09-11T19:59:37.000Z