mirror of
https://github.com/PR0M3TH3AN/bitvid.git
synced 2026-10-29 17:02:28 +00:00
Two root causes for "Blossom set as default but not showing / not usable": 1. SAVE required unlock. saveConnection throws "Storage is locked" without a master key — but Blossom has no secret. Added storageService.saveKeylessConnection() (writes plaintext meta, no encryption, no unlock) and the Blossom save branch now uses it. So a Blossom connection saves even if the user never unlocked storage. 2. UploadModal treated Blossom like a locked S3 connection: it only set activeCredentials when isStorageUnlocked, showed "Locked 🔒", blocked the file-pick behind an unlock prompt, and mislabeled it "S3 Compatible". Now: getProviderLabel → "Blossom"; loadFromStorage resolves servers from the plaintext meta (no unlock); the summary shows "N servers / Nostr-native"; the two upload gates and updateLockUi bypass unlock for Blossom (activeProviderIsBlossom). Uploads authorize with the Nostr signer instead. Bumped UploadModal size baseline (+gating code). Lint + build clean. Local only. Co-Authored-By: Claude Opus 4.8 <[email protected]>