You are describe a search result issue not a Nostr client issue (except with gossip). Client devs can’t fix what a searcher sees. We need to know which website they come across to know what they see. Then we can approach that website to try to recommend better clients.
Login to reply
Replies (2)
If Gossip has remained broken on Mac all for years and the dev is completely unwilling to make his app conform to the normal unsigned app security exception workflow of MacOS, demanding users read a README file they have no indication they should read and execute a terminal command, that means that glaring usability issues are considered no big deal for user onboarding. There is zero effort to make an onboarding experience that makes sense from someone doing a web search for “Nostr” or “Nostr client”.
This screenshot is the first DDG result for Nostr clients, nostr.com — it specifically recommends Gossip of one of only 5 clients to Mac web browsers. Gossip is glaringly broken for any normal Mac user. The most usable client for Mac users, @Nostur, is the fifth result, right after the client that throws an error on execution with no hint of solving it. This is normal in the Nostr ecosystem.
I understand that a dev can’t solve this, but “follow me on Nostr” always leads to a massive, multi page long chatlog of people saying “this client doesn’t work, this client doesn’t work, I can’t figure out how to follow you on this client”.


It has a terrible onboarding flow I got a feed first time I tried but have no patience for the unclear ui. I know from experience native apps are a huge pain and radically different between platforms.
My suggestion is consider organizing to donate an old but current enough MacBook or Mac mini. I'm open to that too. Building for windows can be done on Linux, but neither macos or iOS. You must have a Mac to test and build properly. I'm pretty sure Mike doesn't have one. Neither do I but I have less options for ui libraries as I refuse to use c/rust