ipwb currently encrypts content prior to pushing to IPFS with a key in anticipation that the same key will be used for decryption on replay, possibly by another user/party. As of version 0.4.7 (https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-284341649), IPFS has the ability to limit the swam to only users with a generated and shared key. Using this key in lieu of entering a string might be a good way to facilitate collaboration of archives. An idea is to use the generated key as the basis of encryption/decryption.
ipwb currently encrypts content prior to pushing to IPFS with a key in anticipation that the same key will be used for decryption on replay, possibly by another user/party. As of version 0.4.7 (https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-284341649), IPFS has the ability to limit the swam to only users with a generated and shared key. Using this key in lieu of entering a string might be a good way to facilitate collaboration of archives. An idea is to use the generated key as the basis of encryption/decryption.