Y’all are trying to do everything on Nostr at once, sometimes “just for the sake of being on Nostr” (aka LNURL over Nostr / NIP47 adding tons of specific keys/events/etc). I see the value in these, but it’s going to lead to tons of segmentation / fragmentation of users, clients, and relays. One of the main reasons Nostr has been so “quick to pick up is due to its simplicity” 🤷‍♀️

(Who cares what I say though, this is a decentralized protocol, do whatever you want 😆)

Reply to this note

Please Login to reply.

Discussion

I agree and can’t keep up. It’s also not a bad time to move fast and break things - so much trial and error is needed to mature our approaches.

It's way better than coding a different API to each wallet service out there.

isn't adding more event kinds the thing that keeps it simple?

As I understand it, NIPs are essentially “if you want your client to do this use case, here’s the standardized way that the official repo recommends.”

If you’re not interested in your client handling that use case, you could just ignore that NIP, no?

NIPs seem like they’re an opt in thing, whereas we’re conditioning to view these things from the lens of 3rd party APIs that require calls have certain info, and regularly change those rules so that the API call has to change.

The most boring part of nostr is the social media part. A lot of things can be done without nostr using some alternative complex magic but the beauty of a unified generic protocol that everyone can pickup easily is priceless.