Good point, I wasn't clear about that and I don't have any examples, but it's a new "movement", spearheaded by nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac , I think, that says clients must hide Nostr from users at all costs.

And you always get these people saying that "normal internet users don't know about TCP" so it's a widespread belief.

I am not sure if this is @`fiatjaf's concern, but for me, what is utterly important is that users understand nostr like they understand email; and like they understand email providers and email clients.

We don't have to lecture people on how nostr works. What we need is to provide uniform identifiers like "Email" and "example@email.com".

I am not aware of any nostr clients that don't mention Nostr, but this was a bit of a dilemma for us when crafting the messaging and UX for new users. There's a cognitive overhead to dealing with two things: "What's this Primal thing? What's this Nostr thing?"

We decided the cost was worth it and leaned all the way into Nostr messaging.