Feel free to create a workable non-zap option in NIP 69. We can implement if there is one.
Discussion
No.
““No one can serve two masters; for either he will hate the one and love the other, or he will be devoted to one and despise the other. You cannot serve God and wealth.”
Matthew 6:24 LSB
I didn’t realise it was a nip. I don’t understand why that would be part of nostr, I think crypto stuff should be a completely separate thing.
Funny thing about Nostr is that anyone can do what they want. There is no way to block things from "being part of Nostr". The NIP process is barely a guidance for implementers and a place for consensus in the use of event kinds. But one can always create their own kinds by themselves or break away from NIPs.
Is a new kind how you would distinguish data stored for a specific application? Let’s say I have an arbitrary json spec let’s just say a structure for a food recipe, would I then create a kind so people could share recipes? Or is there a better way to accomplish this? Just curious.
Yep, you would sign in the way relays can verify, but inside your JSON, you can add whatever you want.
Do an NIP if you want support from other clients.