Replies (18)
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.
You use Yakihonne?
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...
Yup it has come a long way. Honestly, probably one of the best Nostr clients that's also cross-platform. Suggest keep giving it a try and rack up some points ππ€

this sounds like desperate jargon meant to help with coping rather than looking at the situation and fixing broken apps.
- if the app can't perform its basic function, it is DoA
- if the app is DoA it has no reason to exist
- if the dev won't admit to the problems or fix the app, the app will fail
- people won't use broken slop
breaking is OK. fixing is great. leaving it broken is useless.
breaking is ok when fixing happens
some things are never broken n never fixed
are broken n never fixed***
is the points something I can see on others profiles or is it personal?
sure
but they suck just the same
I don't care about perfection but broken ass vibecoded apps that are cobbled together and abandoned are slop
It is βhappeningβ already, just not on Damus. lol
damn thatβs an interesting concept, gonna have to lock on in on this
What am I missing?
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.
And apparently in the future the XP will be redeemable for in-app purchases or converting to sats
Itβs nostr, who can say? Depends which client youβre using π