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 (3)
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.

Tenna — Postimages
the dream would be alerts on supply chain vulnerabilities for all apps
Its more something you'd have to compute from SBOM