Use encryption for publicly available data as well
Summary
It would be good if there were support for encryption for publicly available data as well (websites, public datasets, etc.). If there is support for this eventually all data on the network could be encrypted.
Motivation
The motivation here is privacy, both for users of the network and also for storage providers. If there is unencrypted data on the network then the system is not zero-leak. Also this may put storage providers in a situation where they might host illegal data on their nodes and that can even be used by an attacker to craft certain chunks that end up in a neighbourhood of certain nodes.
Another issue is that the distribution of the data may not be uniform, therefore for certain datasets filling the postage stamps may be uneven and in those cases the batch would be overissued sooner than expected.
Having all data encrypted could solve both problems.
Implementation
The idea is that for public data the encryption key could be content-hash of the data, therefore uploading the same data twice would result in the same (encrypted) reference. There could be a new manifest type that could contain the encrypted reference of the data, which would not be encrypted, therefore it could be accessed through an unencrypted reference, making this work seamlessly with bzz.link as well.
related #4102