Replies (41)

JackTheMimic's avatar
JackTheMimic 7 months ago
I checked, if you try to download it as an update Zapstore will flash a big red banner and say: "THIS IS NOT SIGNED BY THE SAME DEVELOPER, FORCE UPDATE ANYWAY?" I said no, found yours and updated. New Downloads need to look for " @utxo the webmaster πŸ§‘β€πŸ’»πŸ " as the signer of the code.
This raises an interesting question. My understanding is that zapstore only shows me curated apps from @Zapstore team and apps from my WoT. So how did this get in there?
I'm thinking that's it. I forked Wisp for testing purposes and did the search so Zapstore would index my version, but I didn't intend for anyone else to see it in Zapstore!
capybara's avatar
capybara 7 months ago
Still not used to the keyboard on GrapheneOS πŸ˜€
Yep this i think could be checked like "only display updates if from the same source" if an app has different forks or publishers you only get if updated your fork
Almost fell for it.. i double checked the github acc and it was leading nowhere .. glad i didnt directly download it
I see both and both are indicated as installed, but I actually only installed the correct one because the other showed the signature mismatch I reported earlier, but @Zapstore offered it as ready for update. This is definitely unfortunate and needs to be resolved.
capybara's avatar
capybara 7 months ago
Coming from Android. It's just that I haven't setup the FUTO keyboard properly in different users
Correct. If you choose to install an app for the first time, you will get an "are you sure?" type of message that shows whether anyone in your web of trust follows the publisher of the app, but that doesn't show up at all for updating. It would be nice if @Zapstore showed WoT on the app information page prior to tapping "install."
No, the need for seeing WoT before updating is resolved by the fix you made today, assuming that was a general fix and didn't only apply to Wisp. I'm talking about having WoT visible on the app info page simply because people viewing that page may find the information useful. If they have never installed the app before, they might use it as part of their decision-making process, or they may just want to see if the publisher is reputable before adding the app to one of their stacks, since others might view that as their endorsement. Only having that information visible when a user hits "Install" means that users have mostly already made the decision that they're going to install the app before information that may have changed their mind is presented, and it means the information isn't visible at all for users who already have the app installed, but still may find WoT details useful for other reasons. "Oh, my buddy Derek follows this dev? He probably uses this app too so I'll reach out to see how he likes it compared to X similar app."
It's clearly one of the two issues: Naming Caching Off by one error
#2 image 1. A lady Nostrich suffering from war 😞 View quoted note β†’ 2. Congratulations Buddies! πŸ₯³ View quoted note β†’ 3. This indicates why we should be on Nostr 😍 View quoted note β†’ 4. This would be really helpful for Nostr users 😍 View quoted note β†’ 5. This is the way to be successful πŸ‘‡πŸ» View quoted note β†’ 6. Be cautious from the fake wisp ⚠️ View quoted note β†’ 7. Miljan replies about the user base on Nostr πŸ‘¨πŸ»β€πŸ’» View quoted note β†’ 8. Life is meant to be experienced, not to be endured πŸ‘ˆπŸ» View quoted note β†’ 9. We need more onboardings like this 🀩 View quoted note β†’ 10. This is an awesome trick that everyone should aware 😍 View quoted note β†’ 11. But Nostr won’t ban this small family β™₯️ View quoted note β†’ 12. This is so cool 🫢🏻 View quoted note β†’ 13. He really tries to opt-out from Big tech 😍 View quoted note β†’ 14. A New wallet from Primal? πŸ‘‡πŸ» View quoted note β†’ 15. The last several live days of the Custodial Primal Wallet 😱 View article β†’ 16. He enjoys the growth of Nostr 😊 View quoted note β†’ #community_nostr_recap
↑