Oddbean new post about login | logout Is it a feature of Nostr that replies from one client don’t appear in other clients? So fucking tired of absolute basic shit like this being broken.
Can you link an example?
This reply of mine to one of Lyn Alden’s posts just now. I replied in Damus, but it doesn’t show in Primal. I had a similar situation a few days ago with a few replies by different people to a post not showing up in Primal but showing up elsewhere. https://image.nostr.build/8c8aaa1871bc2f65cc6bc1a65249de6312a04f134a2a77105fbf1d4f7962e511.jpg https://image.nostr.build/fb01ab8969e23191f4b71289235cdbfc27118ed51a5575041885e4ed3cd755cf.jpg
It's a client issue. I've noticed some clients only fetch a few relays, typically the fastest ones, even if you have more than 20 configured. For instance, the #noStrudel client by default only checks the 4 fastest ones. Sometimes, your note may not be included in any of these selected relays and will result in it not being displayed in that specific case. I assume #Primal functions similarly. I tested on #Snort and your note appeared correctly, but on noStrudel didn't (unless I configured it to fetch all relay).
It’s a fucking nightmare for users. Something as basic as a reply should work and it’s unacceptable that it doesn’t.
Absolutely agree. New #Nostr users might not have this knowledge. Clients should stop worrying about new features and focus on fixing core functionality. If they only check 4 relays for performance reasons or whatever, that's a terrible implementation. I prefer if it loads slowly rather than it missing some notes.
💯 if you have relays configured, it should use all those relays. There’s a reason you added them in the first place. And from there the client can make suggestions for how a user can change their settings.
afaik primal loads its main feed from a “caching relay”. that means content will be stale to some degree. tradeoffs for faster page loads
here’s this thread for me on primal https://image.nostr.build/6ac6fefc6b30c09a7243d4d7cf93facf18ee64e0aa7fb8ea639a7e9e600caac2.jpg
but if i view my profile on primal, it actually fetches my notes relays and not the cache https://image.nostr.build/1fb0438dcde94bf199fe897156372dacc45e51ad71597138a06e9e65c52c75b6.jpg
This is because primal doesn’t support the deprecated form of nip10 which damus still uses. Choosing to not implement deprecated stuff (index mentions, old-style nip10) is a valid choice, but it’s choosing to be broken in some situations and for historical notes.
Do you already have an idea? I think backwards compatibility is important for a protocol
Thanks. It’s helpful to know why it’s happening. It’s frustrating from a user standpoint because it destroys Nostr’s “post once, see it everywhere” appeal that got so many of us excited when we joined and there were just a couple of clients. I understand differentiation in features and style, supported content, etc. Clients don’t need to be all things in every case. But basic activities such as replies and reposts and zaps, etc., just seem like they ought to work seamlessly everywhere. Otherwise each client becomes a bit of an island to itself. Just thinking out loud. Not pointing fingers at any particular client.
You have to GM @fiatjaf 21 days in a row to resolve this issue.
It’s as if the note was only sent to one specific relay that’s not available on the other client. Very annoying. Happens often
I have over 20 relays including Blastr. It’s not an issue of being only on a few relays unless Damus isn’t using all my relays.
I don’t get it either. I use the mutiny blaster and it still happens
It has to be clients fucking things up and either having bugs or not following NIPs the same way. Either way it’s annoying af and for something as basic as a reply it shouldn’t be an issue.
Question d'articulation qu'ils doivent de résoudre au plus vite, en concertation pour rendre aisée l'utilisation de nostr, cela éviterait toute cette pollution d'informations chaotiques sur les notes ( utilisateurs, clients, mises à jour, événements etc.. 🙏💜
Yeah you can go back and forth between Primal and Amethyst and have totally different conversations. Whenever I occasionally log into Primal I notice there's people trying to interact with me who probably think I just ignore them because I don't see them in Amethyst. Connected to the same 22 relays in both clients but they obviously don't pull everything from all 22 relays and one gets some comments and the other gets other comments.
“To participate in this thread we recommend you use Nostr Explorer or Nostrscape Navigator.”
Yes, it is a feature. It can also be a bug, of course, but it depends.
Maybe we need to create some “Designed for Primal” or “Designed for Amethyst” etc stickers to attach to all posts. Like it used to be with internet browsers. Who needs interoperability and compatibility anyway? Let’s be sure to establish some user lock-in here with different clients.
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.
I love that he’s doing that 💜🔥
I was trying to reply to this but Yana wasn't showing the replies so I couldn't find it.
🥲
Maybe we should all just agree on a relay URL and all clients use that to fetch replies.
