> There is no notion of access restriction for now at least as this is something missing from ipfs itself, check out radicle’s faq. This isn't quite true. We a

> There is no notion of access restriction for now at least as this is something missing from ipfs itself, check out radicle’s faq. This isn't quite true. We already have an authentication and authorization mechanism on top of ipfs. So for instance, only admins/maintainers (of which there might be multiple ones) can accept patches. (Being an admin/maintainer is different than being a machine owner - currently there can be only one owner. Currently owner has to be online for any new inputs to be processed, though reading should work if your data is replicated, and we've already built some tooling around making that easy.)