still no-go, i am on latest grapheneos, apk installed from zapstore
nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 seems to be the only one i am unable to zap
That's weird. By the way, the Primal you see on Zapstore is actually downloaded from Github. So that's the APK source
I don't understand. Minibits 0.1.10 is the latest on the relay. Pull to refresh the app?
Also nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p07xr4s5 would you like to self publish your app?
Each update *is* a nostr event
Ok so this works but clients don't parse it. We're working on an https handler that will work thru the website eventually
The FUTO keyboard works really well now. It does autocorrection, swipe typing, and it no longer fights with #Amethyst anymore. 😁
Will be using it as my daily driver from now.
Available on nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0, is it possible to get a sharable link or nostr id for it that brings you to zapstore?
Testing zapstore://org.futo.inputmethod.latin
trying to zap any note from nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 fails
I just auto zapped myself and it worked. Or is Alby still with other issues?
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 how is it that I'm getting a HTTP 500 error for my WoT? Aren't you calculating it locally? 
Nope, it was always calculated on our server! It's next to impossible to do web of trust with good UX locally, that said it can (and should) be verified locally which I definitely will be doing.
This is what I run: https://github.com/zapstore/trustgraph
Also, with nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4auspz4mhxue69uhkzat5dqhxummnw3erztnrdaksz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgxmpqkh we are working on something. To be announced soon.
Yeah, it's planned for a while now. https://github.com/zapstore/zapstore/issues/72
Remember how Apple bullied Hey.com ?
That triggered DHH (and 37signals) to completely move away from the Apple ecosystem. I believe they only use Linux there now.
Heads up, when you "Zap this release" you are really zapping the latest release that your Zapstore is aware of.
So if you are on 3.9.2 and there is a 4.0.0 update available the zap will go to 4.0.0
I need to fix this, but in any case the zaps all go to the app 👊
I don't know what to say. This is very weird. I checked and don't find anyone with the same issue. Hopefully in the future some upgrade will resolve it
Maybe, I don't know yet
Earned the “zap” in zapstore 👏 nostr:note1cvfyzlzdtzh2xf5vcv4h8zv5awqsf9lxjhusqn8pcwwqgep3tdjsu740a6
Long due 😅
⚡ Zaps finally got to Zapstore!
0.2.0 is out with support for sign in with Amber (NIP-55) and zaps via Nostr Wallet Connect.
Big shout out to nostr:nprofile1qqsrq7p2sv3m0jvtzuk952hhyp4ms2puv4d7dhwwzyfnvydq8403zacppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgdwaehxw309ahx7uewd3hkc598d06 for implementing an important chunk of it. All zaps in this note go to him!
Update right from Zapstore or check out the link in this nostr profile
Do y'all realize that we literally have our own freaking APP STORE straight from freaking GitHub????
For those who don't know it's called nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 and it's only for crazy anarchists
Lol not only for crazy anarchists.
Some releases come from Github, others not.
Hmmm doesn't seem my nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 is functioning right. The search bar is not finding Olas. It's kinda sitting and just thinking.
Sometimes it hangs. Need to fix that! Try killing the app and trying again
what's the diff between zap.store and Zapstore -- because I now have **both** on my device...? 😬
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 #asknostr
Explained on our profile!
The brainchild of Amber and Honeypot? nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5
Each brand will solve this UX in their own way, though we'll see some patterns emerge
It's not a problem, it's to be expected if this is a decentralized network
One day, you'll be able to input this into Zapstore (or it will pick it up from kind 1 notes?) and get an offer in sats.
Zap back, app produced, checked (builder reputation, build reproducibility, privacy, malware, etc) and ready to install without leaving the UI
I have a problem on GrapheneOS (latest version) and nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0. When I download and install the .apk again and open it for the first time, everything works fine. The flash icon turns and the app loads. However, after I close the app or restart the mobile phone and try to open zapStore again, the flash icon spins indefinitely and the app won't load.
How can I provide more debugging information or is this bug already known?
Dang.
This only happens with the latest version? I tried on Graphene, reinstalled and it works.
How many times have you tried? Maybe it was an issue with the relay and it hanged at that point
Sure where are the APKs?
Zeus can now publish to Zapstore, without having to wait for any further approval or delays.
Publishing apps as fast as a nostr note!
Notice that in the meantime, I have removed the Zapstore-signed Zeus from our relay to give way to their version.
Done!
Also removed Zeus signed by Zapstore, so yours is the official one
Let me know how that goes
99% of users haven’t downloaded Zapstore yet. It would be easier to onboard users if an app vendor could put a single link on the website that gives instructions to:
1. Install Zapstore
2. Download the app (with deeplink to the zapstore listing)
Similar to how TestFlight does it. They assume most users don’t have it installed yet. For example see: https://testflight.apple.com/join/HcmDhGAA
Thankful for nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 for their nostr-centric web of trust app store on Android and nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc for his Powertools app list. The nostr protocol continues to amaze.
Thank you!
How to verify integrity of the Zapstore APK:
Most convenient on desktop:
- Download the package from Github, or from cdn.zapstore.dev
- Run shasum -a 256
- Result should match the *artifact hash* in Zapstore's nostr profile
Most convenient on mobile:
- Download the package from Github, or from cdn.zapstore.dev
- Open file with the AppVerifier app (get via any other app store, or download directly!)
- Result should match the *APK certificate hash* listed in Zapstore's nostr profile
Not sure, what are you talking about?
Yes! Only happens with Themed icons enabled
So true, and exactly the challenge we seek to solve
nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 what does the rest of the text say in this toast? "To fix, remove the..."
It says To fix, remove the app.
But there's another bug if you decide to uninstall, so in that case Delete local cache from Settings
Hi nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8, your logo is bugged in adaptive icon mode.
Thank you for reporting!
