Trade-off query

[jjohare]

Thanks for this, it's an interesting an clearly define proposal, and a promising bridge between the principles of Solid and a more accessible decentralized web.

It seems at a glance that the vision is clear, but I'm curious about how Solid-Lite will balance between accessiblity vs ensuring security / privacy. I am unclear if the implication of simplifying demands any compromises. Is there anything you can point to that moves this on the risk curve that I can have a look into please?

[melvincarvalho]

The default strategy right now is that everyone can read and only the owner can write. After that different access conrol policies could be layered on top. Either for the whole space or individual files.

[jjohare]

Thanks for the quick response
I'm interested in how the protocol will evolve to support more nuanced access controls. Could you elaborate on the granularity of the permissions system? Is it capable of field-level permissions within a document, or is it confined to file-level access? How will the protocol ensure that more complex access control models can be integrated?

[melvincarvalho]

Sure the protocol can evolve to give everyone what they want, via the SLIPs repo.

A typical ACL would be WebACL which is similar to unix permissions and used in Big Solid. We have tests for that in the test suite and it can be a server module for those that want it.

Dont like ACL and prefer ACP (Access Control Policy) also used in Bit Solid. Just make a SLIP.

Solid Lite is a minimal viable core that can be extended as people see fit.