Damus
Zapstore profile picture
Zapstore
@Zapstore

The open app store powered by your social network

Download 1.0.0 for Android: https://zapstore.dev/

SHA-256 checksum: 37090571d00ca53ff1e4d21564a1b45e89feb09f47937d818156d48cf618e402

APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320

Tech support for developers: https://signal.group/#CjQKIC0VCHf6gGeeHKcIrKcaI-B5Kjvge2NKw2i4P55tMkCwEhBaOk9B80F3_MhMYVbgj7lL

Tech support for users: https://signal.group/#CjQKIK20nMOglqNT8KYw4ZeyChsvA14TTcjtjuC2VF6j6nB5EhDLZ7pQHvOeopr36jq431ow

Nostr DMs will be ignored, tag us instead.

Relays (3)
  • wss://relay.damus.io/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://nos.lol/ – read & write

Recent Notes

TravelTelly · 15h
And keep up the good work. Nostr and The zapstore made me buy a pixel phone as hard core apple user. I call it now my #Nostr phone :)
Zapstore profile picture
That's great.

So, the bug is related to your app using different identifiers in metadata (`com.traveltelly.app`) than in the APK manifest (`com.traveltelly.twa`)

We should be catching this in Zapstore but if you want to resolve it faster, fix that.

What are you using to publish it? zsp definitely extracts the correct metadata for me.
2❤️2
TravelTelly · 6h
Ok yeah shakespeare told me abit about this issue. I use the back-end of my traveltelly.com website where shakespear.diy (from nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7lsdlz6 ) build me a ste...
TravelTelly · 3h
Got it working with the help of shakespear.diy nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7gzayh9 https://blossom.primal.net/a1a2c0ade87b1d5f9b0c903ce11a481fa732e515da276b4a102317bb35917...
TravelTelly · 15h
Yeah shakespeare Ai from nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgkwaehxw309aex2mrp0yhxg6t5w3hjuur4vghsjg6xpt told me that it was this bug but I did not believe him😅 Keep in mind I am just using shakespeare and don’t...
TravelTelly · 15h
And keep up the good work. Nostr and The zapstore made me buy a pixel phone as hard core apple user. I call it now my #Nostr phone :)
MikeMonty · 1d
lol I saw it in passing and was just like https://blossom.primal.net/97cb0c616884c03bd32be79967755a139f616b88af608724c8d29756fdf80f3e.gif
CanopyKev · 1d
Last time I published I used zapstore-cli but now it appears that functionality has moved to zsp. But when I try zsp it says it needs a github release, which I dont have.
CanopyKev · 1d
it says uploading to cdn.zapstore.dev and responds with error 400
Zapstore profile picture
Zapstore will remain usable by anyone around the world without requiring personal information, identification or an account. Zapstore and our services will remain available internationally. If Zapstore can't be used in a region due to their regulations, so be it.

714❤️35🚀5🧡5♥️3❤️3🤙3
MikeMonty · 1d
Ah nice, so this was just a joke nostr:nevent1qqs99kccfcf8e43v9ngrs5nnulrhzxzsyuv598uhru802xdwglhxdtcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhg3340pv
Neo ⚡️ · 1d
https://cdn.nostr.build/p/nb5594.gif
Oskar · 21h
If Zapstore and GrapheneOS can't be used in my region, I move.
Nate · 13h
I *think* (assuming courts don't strike the laws down, which I hope they do) the laws mostly focus on companies. If Zapstore and GrapheneOS are outside jurisdictions that require it, and somebody in a restricted jurisdiction get their hands on it one way or another, nobody's going to jail. Which is...
GummiGum · 1d
you are right I have zapstore installed on more than one profile. Thanks for reaching back 🤗
elsat · 2d
3063? Is it this one: https://github.com/nostr-protocol/nips/blob/9d959cd9e238b6ccb11cd7feeb066567860181d0/82.md