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  

 so in summary, this is confusing ux by primal because of the tradeoff they make with caching 

 yeah lately I have this as well, on front page i see there is a reply to a post, a click on it and then there is nothing (primal) 

 for example
https://m.primal.net/HZPP.jpg 

 Thanks for reporting. We received a few similar reports and are investigating the issue.  

 notes are visible from the profile “replies” tab, but not on timeline. I assume it’s related to caching based on my understanding of your architecture. 

 Thanks! 🙏 🙌 

 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.