Nostr is not a giant shit show. I was frustrated and that was an over the top thing for me to say.

The point was a good one though, and people writing PRs for NIPs need to keep it in mind.

What actually gets merged turns out to have a lot less breaking changes than I thought (now that I've gone through the git trying to count them). I may have overestimated.

Reply to this note

Please Login to reply.

Discussion

We know… πŸ«‚

secp256k1 is a dumb curve!

I'm sorry. I'm sorry.

I don’t get it πŸ˜†

You said I could vent and still be welcomed with open arms, so I just humorously decided to test it a little bit.

Actually agree, too much NSA involvement with NIST curves, we should use Curve25519 or Ed25519 as appropriate, but as per your last rant it is difficult to change without breaking shit at this point πŸ˜…

Crypto algos are broken from time to time. When Quantum computing comes nostr will have to change to a new algo.

I hope nostr is flexible enough for this

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

are you proposing a nip to change it? πŸ‘€ πŸ˜‚

I was entertained and learned something.

Boo! Bring back the angry Mike!

hahahahhaa

Respect for cooling down and posting this, most people double down on shit.

This is a good community ❀️

That didn’t sound to me like a bad criticism! It was good to hear, and to remember that we can always do better! πŸΆπŸΎπŸ«‚πŸ«‚πŸ«‚

nah. you were right.

But somehow it still works, and its beautiful

My beef with the nips is the unnecessary consolidation of 9, 20, and 16 into NIP-01. Those were fine separate. It made liars out of NIP-11 implementations that said they supported those now defunct others.