X.KOJIRA.IO
Timeline

Russell

[email protected]
npub1kg4sdvz3l4fr99n2jdz2vdxe2mpacva87hkdetv76ywacsfq5leqquw5te
Nostr enjoyer
Private aliases were never migrated to the new bridge architecture. Thank you for this precious information, it's now resolved.
You can find the nips on github or on nostrhub
https://github.com/nogringo/nostr-mail/tree/main/nostrhub
Pas forcement, avec nostrmail tu ajoutes un moyen supplémentaire de prouver que tu es le propriétaire de l'adresse. Si un bridge to censure/block, tes contacts ont toujours un moyen pour te recontacter. En plus 100% de test données sont sur tes relais donc il est presque impossible de perdre tes contacts ou emails.

La ou tu as raison, c'est que pour profiter du chiffrement de bout en bout il faut forcement etre entre utilisateurs nostr.
If you have encountered problems sending emails with the uid bridge uid.ovh, the problem should be solved, you can send again.
Why Cashu is a joke?
I agree, the secret should be deleted after "pairing" then the client keypair become the "API key"
If it didn't work, it's because zsp is not fully compliant with NIP-46. The secret is not even required, it's up to the bunker to enforce it or not. As for me, there is no need to update the NIP.
There is also privacy content
It look like npub1st430quxxz5ww… mint is down.
nprofile1qqstz2mr9… qu’est-ce que tu aimes dans Pubky ?
Nostr cannot do it but nostr apps can.

If Primal say you need 1000 nostr followers to enable this or that, then that is requirement they can put out.
On twitter if you lock down someone to see your notes, he can just create a new account and continue to see your notes
Even Youtube cannot show an accurate follower counts. Some people follow on unofficial Youtube client like Grayjay.
Can you name one app where you have the ability to lock down who has read access to your note ?
You can use server ip instead of DNS