Yes this is OK and expected behaviour. What happens in the network is that this datamap forms part of another structure (you will see in clients as the posix api happens). The holder of the datamaps is a
Directory type. These directories are like dirs on your drive, but stored. So the whole datamap (which you can consider file password really) is held along with file metadata (size, access time etc.).
Directory type is again encrypted and stored on the network as a type of structured data. Hence we don’t encrypt the very small files as we consider the datamap holder has the file regardless. It is the secure storage of the datamap that then is the issue that had to be solved.
On the network there are several StructuredData types (I have an rfc to improve this actually). So some are directories. All structured data has an owner (so signed) and it may be many owners (multisig (escrow capable) data more later on this). Main point is only owner can update this data.
So for private data, you encrypt and do not disclose the id of the directory (you don’t see it anyway, but you could figure it out by altering the source code to print it etc.). This way nobody see’s what you have, can recognise the data or be able to find or read it.
So for public data (websites, new internet of all data types (not only html) etc.) all we do is don’t encrypt the
Directory type, but it’s still signed. So becomes
Read Only data on the network. Again you can create multiple Public (throw away if you wish) id’s and publish safely data that will never be removed or able to be updated. For a large whistleblower disclosure say, create a public ID, publish, delete public id and no coercion can remove the data or publication etc.
Anyhow, just some background on why you see this, very cool now people are really digging. We are all Jock Tamson’s Bairns as I have said before, but this community seem to be proving that point.