There's a real problem with how some projects handle user feedback. When developers push back on legitimate issues with the excuse that they're "not worth fixing," it creates a toxic dynamic—both internally and externally.
I've seen this pattern before, and it never ends well. Telling users their bug reports or feature requests don't meet some arbitrary priority threshold? That's a quick way to tank community trust and look unprofessional as hell.
The smarter play is always straightforward: acknowledge the feedback genuinely, explain your current priorities, and commit to reconsidering it down the line. Even if you're genuinely swamped, that approach costs nothing and keeps people engaged. Dismissing concerns just breeds resentment and makes your project look careless.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
9 Likes
Reward
9
6
Repost
Share
Comment
0/400
ser_ngmi
· 1h ago
Nah, project teams like this are really annoying. Anyway, they all end up running away in the end.
View OriginalReply0
ForkItAllDay
· 18h ago
Nah, that's why many projects end up failing. The attitude of ignoring user feedback is truly unacceptable.
View OriginalReply0
NeverVoteOnDAO
· 18h ago
Developers say that bugs not worth fixing often end up causing major issues in the end. I've seen too many projects die this way.
View OriginalReply0
0xSunnyDay
· 18h ago
The developer's "not worth fixing" attitude is really incredible, it directly destroys trust.
View OriginalReply0
OPsychology
· 18h ago
ngl that's why some projects just fail outright; pretending not to hear feedback is the most fatal mistake
View OriginalReply0
AirdropDreamer
· 18h ago
Very insightful. I've seen too many projects shoot themselves in the foot like this... One phrase like "not worth fixing" can drive users away.
There's a real problem with how some projects handle user feedback. When developers push back on legitimate issues with the excuse that they're "not worth fixing," it creates a toxic dynamic—both internally and externally.
I've seen this pattern before, and it never ends well. Telling users their bug reports or feature requests don't meet some arbitrary priority threshold? That's a quick way to tank community trust and look unprofessional as hell.
The smarter play is always straightforward: acknowledge the feedback genuinely, explain your current priorities, and commit to reconsidering it down the line. Even if you're genuinely swamped, that approach costs nothing and keeps people engaged. Dismissing concerns just breeds resentment and makes your project look careless.