Readit NewsGenuinely curious, fan of any tooling that makes writing MPC protocols easier.
All of which are just data storage/retrieval mechanics and custom types. This isn't adding some omnipotent AI agent to run/manage/optimize your DB or otherwise turn it into some blackbox gizmo.
Isn't this reason enough to not consider it an option?
Imagine an embedded system that only accepts firmware updates that are digitally signed and discoverable in a public append-only log. Such a proof would have to be attached to the firmware update just like the digital signature, with a size constraint on the order of kilobytes. To be fair I haven't kept up-to-date with blockchains, but I find it hard to believe that any existing blockchain could solve this. Transparency logs can.
I wonder when businesses that currently use blockchains as immutable logs will realise that there is a more cost-effective solution. One of the reasons it hasn't happened yet is because blockchains have magnitudes more mindshare than transparency logging. In fact, there doesn't seem to be that many people who deeply understand the design parameter space of transparency logs.
Shameless plug: My colleagues and I have spent a few years designing one - Sigsum. As Filippo mentions he has contributed to its design as well.
Any insight as to why you think blockchains can't handle this?
The only fundemental difference between blockchains and transparency logs is the trust assumptions and censorship resistence. Its fairly easy to reason about a transparency log as a permissioned blockchain. Conversely, a blockchain could be seen as a permissionless transparency log.
I also want to leverage the web platform (mainly because it's the right thing to do and partly because the web is the only one that offers a decent rich-editor environment without as much plumbing needed if I build natively). So basically a browser app that behaves fully like a desktop app without any needing internet connection.
And for that idea to become reality james long's absurd sql is basically the key. Without such persistent sql based db to work with, that ideas is never going to materialize :)
No affiliation, just interesting project that aligns with your description.
[0]: https://anytype.io/ [1]:https://news.ycombinator.com/item?id=38794733
Haven’t read the license but if it works as described I’d say it is open source. It has been irrevocably released to the open source ecosphere at a concrete future date. If someone handed you a post-dated cheque would you say “I didn’t get the money” or “they haven’t paid”? If his description is accurate it’s been released as Apache it’s just in public escrow.
I agree with your sentiment, its escrowed open source, which might be a turn-off for some I guess.
Because that is the definition of "Open Source"[0]. As was already said, "source available" is the correct term here.
[0] https://en.wikipedia.org/wiki/The_Open_Source_Definition
They are a single organization, that have done a tremendous job at trying to come up with a global and shared legal framework to which people can license code under. They have gone so far to come up with a pretty good definition of "open source", but not the definition.
This would be equivalent to saying that "Freedom" is defined by the US Constitution or the Canadian Charter of Rights & Freedoms. It is not, those are both examples of a legal definition of freedom, but neither are the sole authority for the global and cultural concept of "Freedom"
At Source, we aim to revolutionize developer data management for the open web. Our mission is to simplify data handling for edge devices, local-first software, and distributed infrastructures, allowing developers to unleash their creativity and build world-changing tools that realize the open web’s full potential.
Our suite of new technologies work together to make it easy for developers to ship edge and local-first software. We empower developers to create software and devices that seamlessly communicate, offer granular data control, and secure data cryptographically to ensure trust. Join us in shaping the future of data management and the open web.
We’re growing fast and are looking to fill the below positions:
ENGINEERING
-Protocol Engineer (Distributed Systems) - https://bit.ly/3WxBgRQ
-Software Engineer, Backend (Database) - https://bit.ly/4iiqOaZ
See all our open positions here: https://careers.source.network/