A Bitcoin node syncs blocks and queries locally.
Organic Maps pulls tiles and queries locally.
Why can't Zapstore pull release bundles and query locally?
At first this sounded crazy.
It turns out it's (almost) the holy grail of privacy and UX.
Initial prototype of v2 is insanely promising.
App written in Kotlin from scratch.
Browsing apps is instant. Search is orders of magnitude better.
For update checks, no need to reveal your installed app set to any remote server.
Tor by default.
And that's just the tip of the iceberg.
More soon.
Login to reply
Replies (5)
Yes, it's just that few are reproducible and we need providers. @AU9913 was on it.
the dream would be alerts on supply chain vulnerabilities for all apps
In this new design that wouldn't be hard to include! Where can we pull this data from?
I have pipelines setup to start trying to reproduce apps using @Arjen 's loom protocol as soon as the feature is live on zapstore. This way not only will the reproducibility attestation exist, there will be a link on that attestation to the actual pipeline run and its logs that produced it.
So far I think I have 7 done so far. And will probably prioritize nostr apps using ngit repos once the feature is built. Then I would like to continue collaborating with zapstore to make it so users can run the reproducibility pipelines on demand, just by paying an invoice (or loading up some cashu so we can refund if you over pay).
Its more something you'd have to compute from SBOM