client conflict will be an issue if NIPs aren't accepted by the community

Reply to this note

Please Login to reply.

Discussion

I think the problem is that these NIPs are coming so quickly that developers with limited time, resources, and established sprints or cycles don’t have time to properly review them. Then when they are implemented by individual clients, the user experience is broken for a large number of people. Does this proposal improve Nostr for the majority? If so, shouldn’t it go through a more rigorous process where developers of similar apps for different platforms can discuss how to best roll out these features to cause the least disruption? Why isn’t backward compatibility, at least for a given period of time considered?

as clients and products are created, it'll become harder to achieve unison with all developers

clients will have to adapt to others, unfortunately

backwards compatibility would be lovely, but I can see that being a headache in some cases

I get that it’s messy and we have to live in the sausage factory, but I really think this process needs to be improved. Because right now, my experience as a user is broken by an app that isn’t available for my platform. When new users join and see things like this happening, what makes anyone think they’ll want to return?

completely agree, this is awful any way you slice it