Even I wake up to a “this is broken” message every day so I can’t imagine what it’s like for the big client developers.
The worst part is it’s almost never broken so it makes you doubt people too. Takes a lot of patience and I appreciate the devs who handle this so well. I am not always so graceful.
It can be hard too when we’re still so early. Writing FAQs or Knowledge Base articles to refer people can help.. but they take time and often go outdated as things are improved or addressed quickly.
Support is a key reason why I haven’t opened up more public Nostr services. I can’t do what I enjoy if 70% of my time becomes support work.
Yup, it’s part of why we are hesitating to release some of what we’ve written. We absolutely have no time to support others trying to use it on their own.
Community helps a lot here but doesn’t solve it unfortunately.
Just an opinion but we're at the stages where users should be contributing beyond callouts.
Instead of noting that a FAQ/README is outdated, open a PR to have it updated.
We should all be working together.
I think we have a huge community of all kinds of contributors, which is awesome.
The biggest challenge is the subset lazy persona who literally makes no effort and takes 10 seconds to blindly complain, which cascades out to dozens of minutes or even hours in support to try verify, review and respond.
They are eternal.
Absolutely this. And for some reason they tend to be the ones to spread misinformation far and wide too. Adds additional fires you need to put out.
A lot of it is breaking assumptions that people have about how this new technology works.
The simplicity of the Nostr protocol doesn’t automatically translate into seamless enjoyable experiences for users.
Absolutely! The same magic that makes nostr special makes it hard to setup for a new user.
Onboarding still needs lot of work and we need to change the way people think about social media. Luckily we have an amazing community that takes time out of their day to educate new users for no personal gain 💜
Creating an experience in an open ecosystem for an open protocol means you can’t control everything end-to-end like you can on a closed ecosystem. It’s like driving in traffic during rush hour in Cairo. Total chaos. Your roadmap is controlled as much by what others are doing as what you want to do.
It’s a classic two foot carbon based error,, two feet from the screen consuming oxygen causing issues. They happen with all apps, unavoidable.
Hahaha I like this term
Your post is attracting a lot of attention.
Added to the https://member.cash/hot feed
