drop the first-contact block on populated vault adoption: a second browser, tablet, or phone is now welcome to scan a QR and join an existing mesh as long as the vault id matches. The vault-id check in createVaultFromRootKey is the real security boundary; the prior known-peer gate prevented the intended N-device mesh and is removed (v2.7.10)
$ koh steal kepr.uk/peach-android@e8637519f572
·
parent: 892a8df66df6
discussion
log in to leave a comment.