Replying to Avatar MichaelJ

How long before Nostr gets too big for lone wolf developers?

Most devs can hack together a relay or a simple client in a weekend...for now. As the number of NIPs increases—as does the userbase—the bar for quality Nostr software will just keep getting higher. Code quality and design will matter a lot more.

At that point, we'll need teams of developers and clear paths to monetization to make it worth their while.
Avatar
Low Information Voter 2y ago

Feature bloat kills so many projects.

Is there a process for de-authorising NIPs?

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 2y ago

NIP itself is pretty hackish, it's going to have to give way to something more organised and meritocratic at some point

being that I'm implementing a base set of parsers for them I can attest that the specifications have many missing stipulations that are assumed into existence by common JSON encoders that defy expectations from someone not experienced with JSON especially javascript JSON and the most popular encoders for C++, Rust, etc, and many of those are outside of the expectations of Go programers who are used to stringently static typing and no wibbly wobbly union and underspecified variadic structures

Avatar
MichaelJ 2y ago

Not that I'm aware of. I think NIP-04 has been deprecated, but not by any formal process. It fell out of use and clients started to replace it with a new standard.

But NIP support is entirely voluntary, and there's no guarantee all clients support them equally, or even correctly.