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.
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.
You should notice because the interface is pretty broken already.
If in doubt ๐ Download at 
Zapstore
Zapstore
Discover apps on Nostr. Open source, decentralized app store.
Try making your agent autonomously publish an app to Google Play or F-Droid
Bro blindly pushing to Zapstore ๐
So cool. It works!
View quoted note โ
Designing a NIP for age verification so you can use Zapstore in California.
๐๐


I didn't know Stockholm syndrome existed for mobile devices ๐
View quoted note โ
PSA if you see duplicated apps in Zapstore, or apps signed by Zapstore that shouldn't, please go to profile screen > Clear local storage
View quoted note โ
Zapstore relay is back up again!
Post-mortem:
A bug in the indexer background process replaced 8 self-published apps with indexed ones (signed by Zapstore indexer). Main symptom for users was seeing duplicates of these apps.
Backups were there but faulty so the recovery was difficult and partial. 5 were successfully recovered and 3 were not (Primal by @Primal Developers and Amber and Citrine by @greenart7c3 ).
Users please go to your profile screen > "Clear local storage" if you see double entries of some apps! We are working on a feature in the next release to repair these issues without you having to delete the cache.
Backups, as well as the original indexer bug, were fixed.
View quoted note โ
I'll explain:
- I'm switching off the relay to prevent bad data from spreading to clients which will cache it
- We are working on ways to bust these cache entries in the mobile app but that's not ready yet (next release though)
- If I leave the relay on, I will get an avalanche of support requests I can't handle by myself
- I'm also the only guy doing devops, which really is a full-time job in itself, and I have an appointment now so I'll take care of it when that's done. At least 2-3 more hours
tl;dr: making sure all apps are always up to date is hard.
View quoted note โ
We just had a data issue in our indexer, it's possible I have to turn the relay off for a few hours. Investigating. Apologize in advance.