Replying to Avatar Charlie Fish

NIP-17 is awful. I can’t even get it to work. Obviously I’m doing something really dumb, but spent a few days before giving up.

This is exactly where #nostr could fail. The NIP process is long and tedious, yet incomplete. Is anyone thinking about the scalability and long term impacts of these proposals? More time should be spent on that as opposed to all these dumb little proposals that have almost no usage. Let’s get the foundation right first.
Avatar
Siphiwe 1y ago

Yeah, I've found that documentation is really a big thing in open source projects. And I have a deep appreciation for people who contribute to open source. But I definitely think that especially with nostr NIPs, we could do with better documentation. I think just having examples would go a long way when you're implementing the NIPs.

Reply to this note

Please Login to reply.

Discussion

Avatar
Charlie Fish 1y ago

This. Documentation is tough. It’s the boring part of software engineering. But if you’re gonna build software that you expect others to use, it’s critical. Even more so for a protocol like this. You have to brute force it to be a priority.