3 ms·
A niche cloud that only runs public auditable source code, built on top of ObservableHQ so the user has the power to read and fork the serverside implementation
by tlarkworthy 6y ago
A niche cloud that only runs public auditable source code, built on top of ObservableHQ so the user has the power to read and fork the serverside implementation if they wish
https://observablehq.com/@tomlarkworthy/serverside-cells https://observablehq.com/@tomlarkworthy/serverside-cells
The idea is if we shine a light on server side implementation, and give more power to the end user to see what is happening, we can build trust. Personally I want an AI to hoover up my data and act based on anticipate my needs. However, in the current climate its just too risky letting my data leave my control.
So the problem is not privacy per se, but trust that my data is used in my best interests. This is my attempt at fixing the internet services trust issue: Make sure the production code that runs on the data is verifiable at all times.
It's very half baked at the moment as the serverside runtime is not open sources, nor is there a billing system. I am acutely aware of the hypocrisy and will fix it in due time :p
- ramoz 6y agoLike smart contracts? I also see relevance with compliance-heavy stacks, maybe integrating something like https://github.com/usnistgov/OSCAL https://github.com/usnistgov/OSCAL
- tlarkworthy 6y agoNo just javascript. Crypto and protocols are one way of solving this issue, but I wanted something any developer could adopt. So there are no "proof" of security, but you can always inspect the source code, so services no longer behave like a market-for-lemons. It adds a buying signal. Which although not watertight, does change the market dynamics I think for the better. Thanks for the links, it could well be relevant.