"41e4abd836c79cf41a14c0ecc07cdd61af5f47b702bd0ec2f59cc1ef7c07037a85aa5c8f476bd9bb4d37ba729bd74204f8abf4657c89af964b68b6b26bb6e12c"

Last Notes

- reply

The issue with custodians is they tend to be centralized to only a few. But that is usually due to physical, legal, or informational constraints, which can be overcome with software and good design.
It would be good if there were more solutions with better designed information of lightning and ecash providers with automatic selecting of the custodians for the new people to balance the load to the less used ones or a more appropriate custodian for the user.

2026-05-24 02:40:04 CEST

- reply

The payment targets are really cool! Maybe if someone doesn't have zaps set up then the zap button can open their Payment target screen. And then the payment target screen can also open the wallet like @nprofile…n0es got working with cake wallet. Lots of people are trying out Monero for the first time with the payment targets and cake wallet swap.
I want to zap more but the nwc wallets feel too janky to trust with more value. The zaps seem to be working sometimes, but it always feels like a gamble if it's going to work or not. The Amethyst wallet display screen makes it feel especially janky where the wallets time out all the time. I've only seen the wallet screen load the wallet amount and transactions correctly like once or twice out of dozens of tries over the past few weeks, waiting for minutes each time. I have tried minibits and their mint and I have also tried with ecash app wallet and it has the same issues with different mints and relays. I have Tor on and I've tried with various configurations of internal, orbot, vpn mode.
Its also hard to find more nwc wallets. For example Minibits doesn't list nwc as a feature when searching on zap store. The whole ecosystem needs more work.

2026-04-04 21:49:16 CEST

- reply

You may not be interested in fighting tyranny, but tyranny is interested in fighting you.

2026-04-02 01:22:32 CEST

#nevent1q…tkck

2026-04-01 23:53:43 CEST

- reply

❤️🫂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 ).