For those trying to install @Fountain via Zapstore: The issue is that the APK has been removed from its original location https://storage.googleapis.com/fountain-fm-builds/android/fountain-1.3.2-1531.apk @Oscar Merry are you aware? Could you get this fixed? View quoted note →

@Max shilling Nostr to a packed room. Great talk and thanks for bringing up Zapstore!

New Zapstore web! Every app now has its own page (available at https://zapstore.dev/apps) and deep links are working in Zapstore 1.0 so sharing apps will become much easier. Still unfinished but overall improved copywriting and aesthetic of the site.

Permissionless publishing update: I received harsh criticism about the publishing experience lately, interestingly by some who genuflected before the centralized stores, but the feedback is valuable and made me rethink the whole process. Publishing will have less friction, here's the medium-term plan: 1) Remove the relay.zapstore.dev whitelist. Pubkeys will be passed through a web-of-trust filter which should work for most profiles without asking for permission 2) Add relay management (will ship in Zapstore 1.1) such that app events can be hosted on any relay - now that a stable NIP has been defined 3) Create a tool to cryptographically link Android keystores with nostr pubkeys (NIP-39 PR). In this way, developers will only need to sign their kind 0, once. The Zapstore indexer will take care of pulling their app updates. (Downside: updates are not immediate as publishing directly)

Zapstore 1.0 update: Reached feature parity with latest 0.2.7 (remember this is a complete rewrite). Issue of apps not refreshing latest version should be fixed now. There are new features, notably comments on releases and silent updates (phase 1). Still fixing the mess introduced by the AI, despite being strongly guided by the #purplestack context file and underlying libraries. I won't ship until the technical debt is low enough. I just reorganized the milestones, here if you want to follow:

GitHub

zapstore/zapstore

The social permissionless app store. Contribute to zapstore/zapstore development by creating an account on GitHub.

Zapstore 1.0 is ~90% there. I hope the infamous last 10% is not the hardest. Most of the remaining work is fixing various weird patterns introduced by the AI, and manually review all critical parts of the code.