Damus
Open in Damus
Vitor Pamplona · 1w
Nostr-tools has a lot of bloatware nobody needs in a library architecture (everything in one repo) that doesn't make any sense. Of all the libraries, that one needs to die first. On the NIPs, we alre...
 SondreB profile picture
SondreB @sondreb
There is no problem having all the NIPs implemented in the same repo, why is that a problem? The opposite is a disaster, I know how horrible it is when developers goes nuts with "microservice" repos.

Any app that needs NIP-19 encoding in their web app, will only load a minimal set of code into their build output. Three-shaking ensures only what is used, is included.

The library is battle-tested, existed for years, used by many. Telling AI to implement the same based upon NIP markdown files will end in disaster, because the NIPs are not all well written.

I will follow my own advice and fork it!
1
Vitor Pamplona · 1w
Yep, what I am saying is that the chaos of AI not implementing things correctly, and us having to fix it, is preferred than having one maintainer dictating (or a government pressuring said project) how nostr should be. The reason we have events in lots of relays is to avoid single point of failure...
mleku · 1w
what is a bigger problem is that npm is such rubbish that separating these things into separate package would be even more of a nightmare. what you want to do is just reorganise it. in fact, i didn't even think about whether it was badly architected, i'm gonna take a guess that it is a dog's breakf...