Why is Primal not interoperable with nostr?
Login to reply
Replies (33)
Come to poster.place primal sucks
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.
Broken by design
Never worked ever
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 think it’s the caching server.
To clarify, this is a technical fact. All notes are decrypted before they reach your device on Primal. Let alone that their caching server is a filter for content.
I could see it, if it was this one.
😂
Relay issue? I see this frequently as well, not sure why.
PosterChan · Nostr
It’s displaying now, I assume it is the caching server.
or tell me how do you avoid being seen on primal?
Come to Wisp
I use wisp all the time.
Interesting. So, what’s a proper Nostr client on iOS?
Nostur, Damus, and a few PWAs using a browser app.
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.
Oh jk I thought this was like an unsupported kind thing.
Sure it’s not a mute?
Zap Cooking is Wisp based
Looks fine to me. Maybe there was a delay to render
View quoted note →
Ya
Notes on relays, keys in users hands.
All good my friend. Sorry for the misunderstanding 🫂
It’s so bad
No, it was a delay in rendering. It displays fine now.