Nostr Web Client

One of the things i feel the most is the separation of nostr and lightning. (Which imo ZBD has solved).

That integration should be the default, with advanced options available. Every client should become by default a lightning custodian.

Every client should use nostr, but build as if they are one stop shop solution. This reaches more people.

At the moment, you either are not a techie, and will be getting half of the experience. Or need someone to walk you through onboarding, or a techie and know what you are doing to enjoy the full experience.

Derek Ross 2y ago

The Current client was the first Nostr client with integrated wallet. It's a good model. However, not client wants to manage people's funds for them.

I do agree that on-boarding is a major issue as it's essentially non-existent across most apps and is an afterthought. I am hopeful that this comes. This will being in the non technical people when we're ready for them. This is acting as a barrier now, protecting Nostr while devs build.

Reply to this note

Please Login to reply.

Discussion

TKay 2y ago

Agreed, and thats a good strategy, use is as a way to gain more time and build.

But imo, its the barrier for the real value proposition.

I understand that many believe the nostr value proposition is the decentralization and resilience. For the average joe, its not.

The real value proposition is V4V. which is implemented and carried by lightning. And hopefully this keeps away the ads and bots.

florian 2y ago

When we have zaps based on ecash it would make it a lot easier to build a wallet directly into nostr clients. It’s less complex than integrating a lightning wallet and might help to create this smooth integration. Of cause it would also introduce security concerns when storing funds in a plain text token somewhere in a browser. I’m excited to see how this will be solved.