After these important infrastructure improvements, our next big challenge is communities (next 4-6 weeks).
Anyone is able to run one, and discoverability will be first-class in the app and webapp. Instead of managing relays, Blossom servers, and tweaking a bunch of technical knobs, no: those are prepackaged in a community spec.
We are going to push the permissionlessness hard.
Stay tuned, it's going to be awesome.
Zapstore
_@zapstore.dev
npub10r8x...t2p8
The open app store powered by your social network
Download 1.0.0 for Android: https://zapstore.dev/
SHA-256 checksum: 37090571d00ca53ff1e4d21564a1b45e89feb09f47937d818156d48cf618e402
APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320
Tech support for developers: https://signal.group/#CjQKIC0VCHf6gGeeHKcIrKcaI-B5Kjvge2NKw2i4P55tMkCwEhBaOk9B80F3_MhMYVbgj7lL
Tech support for users: https://signal.group/#CjQKIK20nMOglqNT8KYw4ZeyChsvA14TTcjtjuC2VF6j6nB5EhDLZ7pQHvOeopr36jq431ow
Nostr DMs will be ignored, tag us instead.
Re: app updates.
On the indexer side, we deployed a demand-driven schedule meaning that your requested updates trigger a check - instead of being cadence driven (e.g. every day).
This means more efficient and faster updates across the board!
The indexer also now does takeovers, so if a developer stops publishing for whatever reason, the indexer acts as a safety net so you don't miss updates!
If the developer had cryptographically linked their APK certificate, then we can keep publishing on their behalf.
Attention developers. We're relentlessly lowering the bar for publishing.
If your npub is rejected (usually happens with new npubs) you no longer need to ask for whitelisting.
Simply add a 'pubkey' YAML property in your zapstore.yaml config file (must be at root of your repository, pushed) with your npub.
That's it!
(Malicious apps will swiftly get removed and the entire user from the forge, permanently blacklisted.)
โจ New feature (in alpha!)
Something that many asked for a long time.
You can now suggest apps to the Zapstore indexer. Simply search for the full repository URL like https://github.com/user/repo
If you get no results back, it will be queued for indexing in the background, and if it has valid APK in its releases, it should shortly be available.
Github only for now. Try it out!
๐ zsp publishing tool, just released 0.4.0
Lots of fixes and a publishing flow to link your APK certificates to your Nostr identity, implementing our new NIP-C1!
I encourage you to start signing these, it will strongly help improve trust signals.
It also works outside the flow, via: zsp identity --link-key

GitHub
GitHub - zapstore/zsp: Publish apps to relays
Publish apps to relays. Contribute to zapstore/zsp development by creating an account on GitHub.
Aurora Store release repository (auroraoss.com) has blocked Zapstore indexer IP, so no updates from them.
Github being more open than a FOSS project, who would've guessed.
"Nostr is only known by a very small number of people so I'll just stick to big tech" ๐
View quoted note โ
Friendly reminder:
View quoted note โ
Interesting thread on Linux app distribution.
Many answers, only one mention of verifying a package.
View quoted note โ