Oddbean

As someone whose donated well over 1M sats to your project, I find this to be a poor response to legitimate user feedback. Are you building for yourself or for your users? For better or worse, this is why clients like @primal that put the user experience first will continue to be the most popular.

Maybe it’s because you are not aware of our core principles which determines how we build things? We are very skeptical of adding centralized integrations such as google apis, as well as KYC wallets. If we didn’t care about these things than we might as well just be another big tech app. It’s also why damus will remain functional when your ux-friendly app goes down. Damus’s core philosophy is that we can do the same things but better in a more decentralized way, even if it’s harder and will take more time.

“It’s also why damus will remain functional when your ux-friendly app goes down.” Sorry man, this is why I stopped using Damus months ago and I’m sure I’m not the only one. The bugs and crashes made it completely unusable. To top it off, user feedback was brushed off and new features completely disappeared. I’m sure the Damus core principles are excellent and heavily weighted towards censorship resistance, decentralization, sovereignty and the like. It’s just pretty clear that user feedback is not one of them.

I use damus every day and do not have crashes. If there are crashes they are quickly fixed. What feedback did you give which was not received? Dev has indeed slowed because I am working on a multiplatform client as you rightly criticized. In the meantime i have hired @danieldaquino to work on ios part time. They have implemented: - new threads - damus purple - push notifications (soon) - many bug fixes - first aid (contact recovery) - onboarding (first post, suggestions) And much more. Also we are much more conservative in adding features. People depend on that for reliability. Pushing new things and breaking things is something we try to avoid.

Oh we accept feedback, but we are not obliged to implement all feedback, especially if it goes against our core principles. Luckily there are clients who might implement everything you ask them! Thats a pretty cool feature of nostr. Personalized clients.

I wish you the best of luck Will, but I find the way you speak to your active users and people who have supported you financially to be condescending and smug. I’ll be taking your advice and will move on to clients that can balance the whims of their core devs with legitimate user feedback.

Core principles are great but you could just integrate it as temporary solution and then replace whenever you guys will have a time to come up with better idea. Everyone whom I onboarded from the normie land said that they stopped using it because there is a luck of basic things that needed. If we will wait for years to come up with the “better solutions” by sacrificing users then this place will be dead !

I’m not against that reasoning, I wouldn’t reject a PR for it. Im also not going to spend a lot of time implementing that if I could spend that time working on a better way. There is a reason I built damus, it was to build decentralized tech. I personally spend very little time thinking about api integrations. If I lose marketshare then so be it. Yes I am very ideological, and am willing to have less users, but at least they will be users who care about decentralization and understand why we are here. If thats damus’ niche then so be it. nostr enables this diverse landscapes of clients and views. If users are happy with centralized integrations that are tracking all of their activity then great! All the power to them.

we had multiple integrations but one of them broke (proving my point of my original concern), so now we have one. I was very much against it and would still prefer a better way. I did not personally implement it. I always saw nostr build as a temporary thing like you mentioned.

See, the core principle was sacrificed. I don’t want to go into arguing mode and being sofa expert. And we aren’t just dunking on you. The basic stuff was requested for months to all of the devs.

i think a nostr.build integration is not as bad as a google api integration, since the latter would require us to implement something on a server. The nostr.build integration was the least bad infraction of these principles since we could do everything client side and it’s run by nostr folks, and we had multiple backends.