Add `.well-known/` directory verification for BlueSky / Nostr (NIP-05)

[0xdevalias]

• https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial#:~:text=How%20can%20I%20set%20and%20manage%20multiple%20subdomain%20handles%3F

  • Instead of using DNS TXT records, you can return each account's DID from the route https://${handle}/.well-known/atproto-did. The expected payload is a DID (such as did:plc:abcdef...) with content-type text/plain. The handle resolution function explicitly expects a HTTP 200 OK status.

• https://nostr.how/en/guides/get-verified
  • .well-known/nostr.json
  • Public Key: npub17s23s94ak33j4q8r46npgufeug9ryw73nm6t5xlm6unjrplrcnusa0085q
    • https://njump.me/npub17s23s94ak33j4q8r46npgufeug9ryw73nm6t5xlm6unjrplrcnusa0085q
  • https://damus.io/key/
    • Hex Key: f4151816bdb4632a80e3aea6147139e20a323bd19ef4ba1bfbd7272187e3c4f9
    • https://www.name.com/blog/how-to-get-nostr-verified-on-a-custom-domain
• https://stackoverflow.com/questions/55880919/how-to-add-well-known-on-github-pages-files-using-html