Damn, I have so much opinion about this.
1. I am not sure knowing about why clients do what they do will speak louder than good experience. I mean, hack, google photos and drive still working quite decent together, compared to a nextcloud. Mine works also, but it is constant tuning, and effort. Aint nobody got time for that. But Google makes a lot of money on the data people feed it. Many people know it, but few act against it. It has a good experience, shitty on morals, but people use it.
2. I am not sure what percentage care about how the program/service works that they use. Either it works decently, so they use it, or it is too shitty, and dont bother.
3. I think people either are the victim of censorship, so they care, or they dont care at all about nostr uniqueness on this manner. And who cares about that will know their client. For these people, we definitely need to share these things. But a dev posting about this might not be enough.
4. Maybe we need to create an easily available table of features of clients. This would include note verification, usage of only a caching relay, storing search results connected to pubkey. Hmm, I will do this if it is not available already.
Couldn't have said it better.
Users care about their experience with an app, not about how it works under the hood. That is, until how it works under the hood encroaches on their experience.
Unfortunately, users don't often find out about this until they get burned. They choose the short-term, convenient experience, and find out later why choosing something that was a bit less convenient would have saved them a lot of pain.
For instance, just pasting in your nsec to log into a client is the most convenient way to use it. You only find out why you should have gone the less convenient route of using a browser extension or remote signer when your private key is leaked, either unintentionally or maliciously, by one of those clients and someone else starts posting as you. Never have that experience? Well, then you might never understand the importance of protecting your nsec unless you hear from someone else who tells you what can happen if you don't.
So, maybe the devs aren't the best folks for that job, but there need to be people who understand the protocol well enough to help other users understand why they should follow best practices. Otherwise, everyone is just going to gravitate toward the apps and services that are most convenient in the short term, without considering the tradeoffs that they aren't aware even exist.
Thread collapsed
