Many asked for it: bitchat is on @Zapstore Signed by me

Released zapstore CLI 0.2.2 Fixes an issue with the `--overwrite-app` flag As usual, I recommend all developers self-signing to upgrade to the latest. Publishing no longer prompts for installing locally - download and run `./zapstore publish` right away

Best trust model the Microsoft corporation could come up with We are not the same

🚀 Zapstore CLI 0.2.1 is out with a ton of fixes - Now allows running `zapstore publish` without having to install it - Fetches highest quality images from Play Store - Much faster release version checks and lots of other safeguards - Prepares for new NIP format And... it's now powering the new indexer that is LIVE and working to get you the latest releases for Github, Gitlab and the web. You'll notice much higher quality image galleries in the app already. Developers I highly recommend updating: - zapstore install zapstore - Or get from https://zapstore.dev/download What a long day... enjoy! #devstr

Indexer migration ongoing ⚠️ Some apps are not being updated but that should be resolved throughout the day. Since the new zapstore CLI is used for indexing and there have been many fixes there: developers expect a new 0.2.1 release (also today hopefully)

Zapstore documentation could be better, that's for sure. In the meantime, if you're a developer wanting to publish, here's a #protip Provide https://zapstore.dev/docs/cli/publish/ and ask your favorite LLM to help you produce a zapstore.yaml config file (as well as the command to run) according to your situation. Place it in your project's folder and publish.

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

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.