i dunno, if its not then great
Discussion
There was a time when my understanding was that Zapstore worked on only a singular specific relay. Not sure if that was true or if so, if that has changed since then. It’s a great idea regardless as the decentralized aspect of it unlocks so much. Would it make sense to combine it with Blossom if it’s not yet doing that?
Where does Zapstore keep apk files?
Oh looks like the docs mention Blossom support already, so the answer is anywhere you want. Great! I think it can read from GitHub or other arbitrary internet sources too. nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 can correct me if I’m wrong. I’m several months out of date on his project.
Yes! With the latest zapstore-cli you can choose any amount of Blossom servers to push your assets to, in addition to the default cdn.zapstore.dev.
For Github releases (which will soon be living in a separate relay) the APKs are fetched from Github first, and we keep a copy as backup.
Zapstore is decentralized.
You can use it with any relay as long as it follows the Software Application NIP I proposed. To change the relay, at the moment you need to fork the app because it's hardcoded.
I will of course make that much more convenient, relay management is coming to the next major version for which I'm working my ass off.
Every piece of the stack is open source and I will encourage people to run other relays instances with software releases.
I don't know who said it was centralized but why would it be, when it's built on nostr and supported by OpenSats? Makes no sense.
I might have accidentally embellished it in one of my conversations with some other folks, around the fact that there’s only one client and one relay at the moment. Wasn’t meant to be a dig at the project, just sharing the state of affairs. But there’s no reason why there can’t be more clients and relays. Keep at it!
Thankyou for your service 🫡