mirror of
https://github.com/PR0M3TH3AN/bitvid.git
synced 2026-10-31 18:02:27 +00:00
The keyless Blossom save returned early without triggering storageSyncService.push (the S3 path does it after saving), so changing Blossom servers never updated the synced copy — it looked like the settings didn't sync. Blossom servers already live in the account record's plaintext meta (which exportAccountRecord ships), so the same push the S3 branch uses now runs after a keyless save: the record is re-encrypted to self and published, and it roams like S3. NOTE: sync export/import needs the account's encryptedMasterKey, which exists once any secret-bearing (S3) connection has been unlocked/saved. A Blossom-ONLY account (no S3 ever) has no master key envelope yet — encrypted sync for that case is a follow-up. Lint + build clean. Local only. Co-Authored-By: Claude Opus 4.8 <[email protected]>