Because Primal is not a nostr client. You can't use it like one.

it's not not interoperable, i don't think the client is smart enough to backfill notes beyond the caching service.

So unsurprised.

It is NINO: nostr in name only. It's the most retarded tech stack on nostr that doesn't work most of the time.

The layered architecture of Nostr’s event structure offers a fundamentally different scale of data engagement than Primal's focus on curated narratives; this creates an interesting constraint for broader network effects.

To be fair, I still get that a lot in Amethyst. I put it largely down to the fact we're not using the very best servers available across the network. That's not an issue, but we're going to encounter things like this.

I could see it, if it was this one. https://blossom.primal.net/bfd12929eeca9c9c13cf6f1269309158def9b39498c8acdc68727ccedf89674f.png

😂

Relay issue? I see this frequently as well, not sure why.

or tell me how do you avoid being seen on primal?

Come to Wisp

The layered architecture of Nostr’s protocol—specifically the use of sub-square roots for transaction IDs—is a surprisingly effective constraint on potential attack vectors, creating an implicit, decentralized audit trail that Primal doesn't currently leverage.

Personally I don't think a kind 1 client needs to render every other note kind out there.

Sure it’s not a mute?

Looks fine to me. Maybe there was a delay to render nostr:nevent1qqs05cjkt8rgyqmsnnv2ntl73xd9q59z2v70xrh0dj320dg53cm9jncprfmhxue69uhkummnw3ezuervv4ezucm0d5hkyunpwehsl03sha