Sounds like a bullshit excuse for not fixing things that matter to users.
Discussion
Iβve yet to use a nostr client with no features that break.. thatβs why Iβm forced to use 3, each serves a purpose the others canβt.
not saying this is optimal but since itβs the norm across all clients it forces me to use more than one
Same, and thatβs not ok. Broken app features arenβt cute and funny for users. No serious dev should try to rationalize them. Especially not a dev building for an app that wants users to pay for it.
i agree, this does leave room for anyone to create a solid one that doesnβt break n takes users from every client thatβs broken. Iβm really looking forward to this happening, i doubt fixing things broken for this long will get the bad taste out of the mouth of many..
IT will happen, #nostr still an amazing baby, and he will grow and become an adult with time. We still are in the development step, new features, possibilities...
You use Yakihonne?
I hadnβt used it in a long long time almost like a year, just opened it up n see a lot has changed, the thing thatβs peaking my curiosity the most is this gamification feature
breaking is OK. fixing is great. leaving it broken is useless.
You are absolutely correct! There is no excuse for not fixing things that are broken in your client that are within the scope of the client dev's control. There's a lot of "just ship it" and then move on to the next exciting new idea, leaving users with a bad experience and no expectation that it will ever improve. Then we wonder why user retention is so dismal...
That said, I also see a lot of complaints leveled at client devs that are not within their purview to fix.
"Zaps aren't working on Amethyst."
No... Your wallet provider's relay is down.
"Primal is really slow to load."
No... You're using a DVM feed that they have no control over how long it takes the DVM to send them notes to display to you.
"Jumble doesn't load this user's notes for some reason."
No... That user's outbox relays are all inaccessible via clearnet.
"Damus wiped my follower list somehow."
No... you used some other client that didn't load your existing follow list, so it created a new one and overwrote it on your relays. Damus is just displaying the most recent follow list created.
The list can go on and on and on. Users complaining to client devs about things broken in their client that have nothing to do with their client at all.
And when it comes to devs on an open protocol, you're always going to have a wide mixture of of those with focus, who want to build one or two quality projects, vs those with more ideas than time, who flit from one thing to the next, never really slowing down to make sure it's all in good working order. And now we have the advent of vibe-coding, and I am sure we will see a massive volume of "Look what I made, isn't it cool? What should I build next?" type of folks... As much as I can't stand that attitude, the protocol is permissionless, so they will exist, and they will be a drag on the quality of otherwise solid projects that they are interoperable with.
Just like the good work of one developer can improve all apps that interoperate with them, the bad work of one developer can be a drag on all apps that interoperate with them.