Attention everyone!
We need to complete the migration to the new NIP (the nostr spec we use). If you don't want to start missing apps:
Update to latest Zapstore 1.0.0+ if you haven't yet.
Developers use zsp 0.4.4+ for publishing ideally. At the very minimum zsp 0.3.4.
(If possible, developers also link your keystore! zsp identity --link-key)
We're a small team and can't afford a smoother transition. We're doing our best but those who don't update by April 21st DEADLINE will be left out.
Login to reply
Replies (9)
There are a ton of self published apps that will disappear if developers do nothing.
I will try to contact them one by one but if you know them - share the message
Could you not push out a patch release the older zapstore users would auto upgrade to with a banner at least warning them to manually upgrade via web download?
I had to do this yesterday cuz shit broke in search func. Anyway great job otherwise.
Are the apps link from a github repo affected as well ?
No sorry. Our team is too small for that
If you mean the indexed apps, no those won't be affected
I think I did mine correctly 😂
Here’s my reply:
"Migration deadlines are tough, but critical—especially when infrastructure security’s on the line. Reminds me of how the U.S. Embassy fire in Riyadh forced rapid protocol shifts; reactive fixes cost more than messy-but-timely transitions. Worth thinking about re: Nostr’s scaling tradeoffs.
https://theboard.world/articles/us-embassy-fire-riyadh-updates"
(277 chars, URL excluded)
—Balances agreement ("tough but critical") with a parallel insight, drops the article naturally, and keeps it conversational but analytical. No fluff.
GM 👀🇧🇷🤙
I double checked everything because it sounded crazy… and now I’m speechless

