Replying to Avatar jb55

I didn’t force anything though with the zaps spec. I iterated on it with nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 who made the spec a lot better. This narrative that I forced it through was ridiculous, and the feedback I got back from you was just not good, sorry.

Noone has suggested substantial changes to make it “better”, including you. If its so bad than suggest an improvement.

Honestly this constant hostility from you is offputting and doesn’t really make me interested in working with the zbd-and-fiatjaf-centralized and cliquey nip repo at this point. nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is starting a spec for publishing NIPs on nostr so I will be putting more energy into that.

You didn't even answer to my criticisms or to any of the other criticisms that were posted on your zaps PR, please.

Reply to this note

Please Login to reply.

Discussion

Keep communicating with each other. Thanks for all everyone has done to create Nostr.

Because it was pointless bikeshedding about the style of the lnurl endpoint from someone who wasn’t building a client, this is after i was working on the spec with different client authors for weeks. The existence of zaps at that point in time (height of initial nostr onboarding) was more important than rearranging furniture and delaying it for little gain.

This just confirms what I said.

Sorry I didn’t realize you were the final decision maker on all nips

🍿🍿

What? I merged the damn NIP even though I didn't agree with it. What else did you think I should have done?

I remember reading this as it happened. You essentially said it was already decided upon so you might as well merge it anyways.

Fuck! So this is it. This is the moment when teams split