Why Nostr? What is Njump?
2024-06-25 03:57:16

Karnage on Nostr: Kat’s 2 sats: I’m well aware of the nostr principles and various considerations a ...

Kat’s 2 sats:

I’m well aware of the nostr principles and various considerations a developer might make before integrating something that has potential to get rugged.

I’m also considerate of user desires and how they might fit into the overall product vision.

There are always trade offs with any decision. Do we make users happy? Or do we adhere to principles of rug-proofing?

I think it helps to look at the bigger picture and try to imagine what is more likely to happen - your brand new protocol dying because users were unhappy with the overall experience, or potentially having a part of your client not work if the centralized API is rugged.

Personally, I see former as a greater threat when considering that the features that might be rugged are not really core to the overall app experience. I’d much rather make users happy (and even charge them for it), then worry about media disappearing. Our words are the ultimate speech. We can continue communicating with words, even if media is gone.

For this reason, I see un-ruggable media is a nice to have, but not critical to success. If media dies, you still have time to replace it with another solution, but if the word dies, that’s it, most of your users will disappear (except the super hardcore ones who will wait for it to come back up).

The cool thing about nostr is that we have all these different clients who can do as they please and choose the path that works best for them and their own principles. We can’t really force anyone to do anything. Shouting at devs is defiantly not the way to get anything done. Ok to keep bringing it up, and even better if an issue is encouraged with some sats. I know that works because I have done it myself several times now. Those sats are not much, doesn’t really cover any real expense for developer, but it’s proof of work and very good signal.

As for “build it better yourself”, this is not a viable path. We already have very limited number of developers here, truth is that we can’t build it better ourselves. We all have different roles to play, all critical to success, but different. I would encourage developers to pay attention to user feedback, especially if it’s the same feedback over and over from multiple passionate and hardcore users - they are your signal and a good indicator if something is going right or wrong.

Anyway, love you all! 💜 Let there be peace!
Author Public Key
npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac