That's a great advice. I have been reluctant to do that to date. It was probably the right decision when designing the architecture but now focus is shifting to creating user experiences it would be foolish to ignore tool and flow that has dominated the market.

I think trying to create a tool that would satisfies the expectations of git-over-email users and github users is a recipe for creating confusing experiences.

The great thing about nostr is that it is normal to have multiple clients to cater for different needs and preferences.

Reply to this note

Please Login to reply.

Discussion

I think in all Nostr projects we have to strike a good balance between the "just works" experience and highlighting the underlying technology. This is strongly related to the users target, of course; this is a quite technical tool, so we need to surface a lot of details, but in an clean and productive way. A sort of progressive disclosure pattern.

I am going to test ngit asap, shoot me a DM if you want to reason about some topics.

Thanks. what do you mean by 'reason about some topics'?

We can identify the most critical areas, and I can propose a design to improve them

Sure! Send me a DM

Damn, I just saw a DM of yours from a few days ago, it was stuck somewhere!

I will get back to you asap