Developers: If you want to keep publishing releases (with uploadable assets) you must use the latest Zapstore CLI.
Older versions do not produce the right Blossom authorizations.
#devstr
Zapstore
_@zapstore.dev
npub10r8x...t2p8
The open app store powered by your social network
Download 1.1.0 for Android: https://zapstore.dev/
SHA-256 checksum: 25bc797d64b8a6c5a9bfd4224598f3875e5c0b07beed985e9e29bc94899c0164
APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320
Support: https://zapstore.dev/community/forum
Nostr DMs will be ignored, tag us instead.
Once it becomes more stable, I will be using @White Noise for Zapstore support. Hopefully other apps use the MLS libraries too.
Regular DMs will get no answer.
Server disk is at 99.8% capacity, it sounds like a good moment to migrate to our new Blossom server.
Updating DNS records for cdn.zapstore.dev now.
🤞
Github and web indexing are paused until widespread propagation. It will be resumed by the new indexing software, probably tomorrow.
Love to see this
GM!
If you built an Android app and don't know how to publish to Zapstore, let me know.
It's easy and I can help you.
Issues with the relay have been fixed. It should all be back to normal now.