Oddbean

If a client uses an approach to load replies that ends up showing you spam notes and another one doesn't would you consider it a bug? What if a client uses some trick to fetch replies only from people in your extended network, whatever they publish to, and another client loads everything from a fixed set of relays -- would that also be a bug?

If it’s advertised to work in that way, and I as a user know that, then I don’t consider it a bug. Like a text-only web browser, for example. I know what to expect because of what it’s obviously designed to do and not do. But if a nostr client is supposed to be a general purpose social networking app, and the only way to have a consistent/reliable experience is to only communicate with people who also use that app, then it doesn’t need to be nostr. Either that, or people need to stop touting nostr as place where you can login anywhere and see your content and social connections. Right now there is either a mismatch in development, or in messaging.

Maybe it would be helpful to have categories of nostr clients, and recommended NIPs for those clients to support and adhere to. It doesn’t make sense for certain clients to show certain things, I understand that. But it does make sense for different clients with a similar purpose to reliably show the same thing if they support the type content.

I’m not a dev so that could be a terrible suggestion. But I do create content and engage with people and at the moment I can’t reliably use nostr to do so because of the little things that get broken between clients, and those little things have big effects.

nostr:nprofile1qyw8wumn8ghj7cmgwf5hxarsd9kxctnwdaehgu339e3k7mf0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprpmhxue69uhhyetvv9ujuum9dej8xarj9e3k7mf0qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03q7ajndq is working on the compatibility issue. You're right, it's pretty bad, and getting worse.