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. 

 Damus still has a centralized image upload serves… 

 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. 

 It’s easy to add and difficult to take away. Slow and steady wins the race 🏁🐢