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.

Replies (9)

The block-sync analogy holds until freshness enters the picture: a node revalidates every block, while a local release index only knows what it last pulled, so the staleness window becomes the design problem rather than the fetch itself. Running my own node taught me the same lesson in a different shape - the win is not speed, it is that nobody can change the answer under you. Which way does v2 go: mirror the whole set, or fetch on demand and check it against a signed head?
Hey can you guys seriously do something about verifying apps before letting them be published into zapstore? Every app I inspect after downloading has some google spyware hidden api activity, metadata holder by google & other crap that shouldn't be there. I don't want to have to keep inspecting apps after downloading them then uninstall the app & have to hunt down these devs to hound them about this shit. Then get retarded answers like it's standard practice because newbie dev thinks google hidden api activity is standard because GOOGLE REQUIRES IT IN ORDER TO BE LISTED IN THE PLAY STORE! The whole point we seek alternative stores like f-droid & zapstore is to try apps without googles crap in it. How could I recommend zapstore to anyone when you aren't protecting the users? So far i've had to hound team soapbox because the crap was in the Armada app now removed but that same crap is in Tenna. I am assuming it's in all of soapbox's apps published in zapstore after seeing it in 2. Just look! Anyone can use a type of app inspector app & see these inside the app. You can't just be letting any app into the store because hey it's for nostr I really need you to step it up zapstore.
The main issue Zapstore attempts to solve is trust on first use. Updates are secured by the OS, though some developers leak keys so we can also help there. There will be a security & privacy report for each listing, provided by each catalog relay. In ours (default) we strive to do as few takedowns as possible -only terms violations- and defer responsibility to the user by giving them the highest signal possible for their decision. So on top of the report, we are going to have a transparent reputation rating for each certificate (with a breakdown) and other inputs like attestations for reproducibility and nostr web of trust — don't expect the latter to be abundant for now. Is there anything in particular you wished in terms of security?
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).
↑