Anyone else having issues zapping via NWC in Zapstore?
View quoted note โ
Zapstore
_@zapstore.dev
npub10r8x...t2p8
The open app store powered by your social network
Download 1.0.6 for Android: https://zapstore.dev/
SHA-256 checksum: 8619dabc77c84b7ba5621f1b707153460e0dd643ec65bd814d4e6f32560be66b
APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320
Support: https://zapstore.dev/community/forum
Nostr DMs will be ignored, tag us instead.
๐ Zapstore 1.0.2 just released!
- Faster loading
- More reliable updates check
- Curated stacks
- A handful of annoying bugs fixed
- Under the hood changes getting ready for communities
Swipe on the stacks to "See More" and make sure you migrate yours to the new format!
Update from Zapstore itself or 

Zapstore
Zapstore
Discover apps on Nostr. Open source, decentralized app store.
Heads up nekogram users!
View quoted note โ
If there is one thing as a user you would pay for in Zapstore...
What would that be?
How much would you pay?
After today's drama there's a clear takeaway:
Apps are not shitposts, even if both are carried over the same protocol.
Catalogs are responsible for the apps they publish, and the well-functioning web-of-trust check and warning was not as useful. People just don't pay that much attention and that's a data point, not a complaint on my side.
Architecting Zapstore around communities, who own these catalogs, is the way forward for software distribution. I am more sure than ever.
The Zapstore software:
- provides a great default community
- surfaces communities/catalogs people in their WoT are using, and allows easy community management
- provides credible exit rather (permissionless at the catalog level, not the app level)
@Niel Liesmons has a lot of credit for this one
Zapstore working as intended, despite the bug
๐ฏ
View quoted note โ