Verifying my Nostr identity:
NIP-05: [email protected]
Nostr pubkey: npub1vpld3kt3w4l86ajhzn6jklfmc3uerhgn8dxa9g02yqgxekhl808qd4vy6g
Verifying my Nostr identity:
NIP-05: [email protected]
Nostr pubkey: npub1vpld3kt3w4l86ajhzn6jklfmc3uerhgn8dxa9g02yqgxekhl808qd4vy6g
你好,世界!
#nostr 公钥:npub1ppxxme6fpmnyualmcar7kagtxsfn3wgee6r79zhjxp9p5xxm360qh09djl
#NIP05 标志符:[email protected]
Trouver des solutions aux problèmes que j'ai moi-même créés
Avec d'autres choses comme - Nostr le réseau social qui existe sans raison
Looking into #nostr...
What puzzles me is why #NIP05 is based on a hosted JSON file and not on #DKIM (DomainKeys Identified Mail, rfc 6367 - https://www.rfc-editor.org/rfc/rfc6376.html) instead.
Aaand, Why?
I used @jeremy 's Nostr Verify plugin for WordPress to verify my new Nostr profile, and explained the process in a short article. I was impressed with how quickly everything fell into place. This is well worth a look if you run a self-hosted WordPress site.
https://thenewleafjournal.com/using-nostr-verify-for-wordpress-nip-05/