If there is one thing as a user you would pay for in Zapstore...
What would that be?
How much would you pay?
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.
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
You can now drop Obtainium!
View quoted note →
And junk apps.
This is why we are building everything around communities.
View quoted note →
It's cool to see AltStore folks recently connecting the dots between app distribution and the social layer for discovery.
It has been the vision for Zapstore since the beginning, and I think our primitives are better. They are all in the fediverse.
Looking forward to attempting Zapstore iOS later this year.
systemd added birth date storage in order to comply with California, Colorado and Brazil age verification laws.
Slippery slope.


Our relay was getting overloaded since last night, and that resulted in a degraded experience in the mobile app and webapp, that a lot of you noticed. Fixes were applied and it should work better now. We are monitoring the situation.
It's likely we were getting spammed. Already planning longer-term solutions for this.