Currently, the only access mode is read-write? So as soon as you move beyond the use-case of private, single-client data (eg: browser storage) everyone involved can read and write data?
I'm not sure where you are getting the idea that the only access mode is read-write.
> You can specify the peers that have write-access to a database. You can define a set of peers that can write to a database or allow anyone write to a database. By default and if not specified otherwise, only the creator of the database will be given write-access.
It would appear that the database is read-only for all other peers.
"OrbitDB currently supports only write-access and the keys of the writers need to be known when creating a database. That is, the access rights can't be changed after a database has been created. In the future we'll support read access control and dynamic access control in a way that access rights can be added and removed to a database at any point in time without changing the database address. At the moment, if access rights need to be changed, the address of the database will change."
That sounds like data is either private, or world read-writable.
Ed: but I take it, data is World-readable in general? So private data would need encryption?
https://github.com/orbitdb/orbit-db/blob/master/GUIDE.md#acc...
Currently, the only access mode is read-write? So as soon as you move beyond the use-case of private, single-client data (eg: browser storage) everyone involved can read and write data?