How is that not the case today? It's extremely clear, or am I crazy
❤️🫂zap store!
At first I didn't even remember if there was a warning, but then I do remember there is actually the warning! But people have been *conditioned* that warnings are not optional, that they just have to accept the warning anyway, so they just forget it and click yes anyway! But with the Zapstore warning about the app being untrusted, there is actually a path to trust the signer! No one is conditioned to expect this, so they SEE the warning but they don't even NOTICE it!
Just like the psychological study of people asked to watch a video and count the number of times people pall basket balls and they DON'T EVEN SEE the GORILLA walking between everyone on the video and they DON'T EVEN BELIEVE IT until they're told about it and they see the video again!
But this is a great opportunity to improve!
You can't force the users to read, but you can make the warning bigger and bolder, and give them more explanation about what the trust means, and how to build your web of trust to configure your nsec and examine the profile of the person that signed the app.
Current Zapstore: "Trust this app? (App) is published by (npub)" ( you cannot click the npub to check them first, you have to go back first)
Normal user: "Yeah, I guess... it's not like I have ever had a choice in my life... Yes, just trust the app and install..." 😔
Future Zapstore: "Trust this app? (App) is published by (npub) You haven't trusted this profile yet! Check out their profile to determine if you trust them." (Make sure it's not a scam!) Or something like that. And you can click the profile to go straight there. Also the profile page could show the npub reports (like Amethyst has) of scam/etc reports ( global if you don't have a nsec set up, or trusted reports if you do, like Amethyst ).
At first I didn't even remember if there was a warning, but then I do remember there is actually the warning! But people have been *conditioned* that warnings are not optional, that they just have to accept the warning anyway, so they just forget it and click yes anyway! But with the Zapstore warning about the app being untrusted, there is actually a path to trust the signer! No one is conditioned to expect this, so they SEE the warning but they don't even NOTICE it!
Just like the psychological study of people asked to watch a video and count the number of times people pall basket balls and they DON'T EVEN SEE the GORILLA walking between everyone on the video and they DON'T EVEN BELIEVE IT until they're told about it and they see the video again!
But this is a great opportunity to improve!
You can't force the users to read, but you can make the warning bigger and bolder, and give them more explanation about what the trust means, and how to build your web of trust to configure your nsec and examine the profile of the person that signed the app.
Current Zapstore: "Trust this app? (App) is published by (npub)" ( you cannot click the npub to check them first, you have to go back first)
Normal user: "Yeah, I guess... it's not like I have ever had a choice in my life... Yes, just trust the app and install..." 😔
Future Zapstore: "Trust this app? (App) is published by (npub) You haven't trusted this profile yet! Check out their profile to determine if you trust them." (Make sure it's not a scam!) Or something like that. And you can click the profile to go straight there. Also the profile page could show the npub reports (like Amethyst has) of scam/etc reports ( global if you don't have a nsec set up, or trusted reports if you do, like Amethyst ).