Verifying my Nostr identity:

NIP-05: [email protected]
Nostr pubkey: npub1vpld3kt3w4l86ajhzn6jklfmc3uerhgn8dxa9g02yqgxekhl808qd4vy6g

#nostr #npub #nip05 #web3

你好,世界!

#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

https://blog.sus.fr/~/Techfr/Trouver%20des%20solutions%20aux%20problèmes%20que%20j'ai%20moi-même%20créés/

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?

RFC 6376: DomainKeys Identified Mail (DKIM) Signatures

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/

#wordpress #wordpressplugin #nostr #nip05 #socialmedia

Using Nostr Verify for WordPress NIP-05

I explain how to use the Nostr Verify plugin on WordPress to use a profile on a self-hosted WordPress install to verify a Nostr keypair in a Nostr client.

The New Leaf Journal