My comparison of Nostr and Bluesky goes on:

Verifying my username on Bluesky via my own domain was totally easy and straightforward by adding a TXT entry in the DNS panel. As long as one knows how to add a DNS entry.

The NIP-05 verification for Nostr is much more complex. You need different files, the HEX of your npub, put a folder in your public-html folder and add a htaccess file. The tutorials I found were all confusing to me. In the end I think I did it right or not?

Why is Amethyst showing this red icon?

How can I test my setup?

Reply to this note

Please Login to reply.

Discussion

Seems broken on my end.

I just don't use NIP-05, it's not needed

Why does it still say @getalby instead of anita@anita.link on Damus?

damus cache or relay still does not have the new update.

I think it’s not setup correctly.

nostr apps will request https://anita.link/.well-known/nostr.json?name=anita to get the matching hex, this link is not opening for me.

Maybe the problem is that anita.link is an addon domain to my main domain and hosting. I didn’t put the well-known folder into the public_html folder, because it’s under my main domain , but into the anita.link folder.

How can I move it into the public_html folder and direct it to work for the subfolder anita.link?

can't help with that unfortunately, I've never done it myself, I just know that is the url apps expect based on your nip05.

Thank you, the URL helps too.

That url is redirecting to https://anitaposch.com.well-known/nostr.json?name=anita

Notice that there is no slash between ".com" and ".well-known". I suspect that the redirect feature is misconfigured.

I tried anita.link/hello and it tried to send me to anitaposch.comhello (again missing the slash)

That said, you probably don't want to redirect at all. Do you know where this redirect is configured?

Yes, my main domain in that hosting account is anitaposch.com. One step above is public_html. So it’s: public_html/anita.link/.htaccess where I redirect from anita.link to other URLs.

The well-known folder is now at public_html/anita.link/.well_known

Thanks for the tip … the redirect problem is solved

And it looks like your nip-05 Nostr address is being correctly verified.

💪🚀🤝

DNS poetry vs. cryptographic haiku—both valid, but one requires fewer server-side tears. If you ever want to test your setup, just zap a note my way at I’ll be there, pixelating patiently.

Actually, NIP-05 verification using a TXT DNS record was proposed more than two years ago... but nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp preferred to keep just the http way, and the TXT option was discarded...

🙄

I would expect that most people manage to upload a file to their website but don’t even know what DNS is. I haven’t checked for some time: Is there no nip05-generator out there to create the file?

It’s not just one file. It’s easy to create the json, but there’s no explanation where the public-html folder has to be for an addon domain like in my case. And yes neither DNS entry nor this solution are something a regular user understands.

nostr:nevent1qqst0af3rxlp0lcfykzksz2eclwgpfz8dr0jvu3ctmk93qeleqqeracpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg4waehxw309ahx7um5wghxjmn0wd6xztnrvvq3wamnwvaz7tmpwshxummnw3e8wmmjddejucm0d5qs6amnwvaz7tmwdaejumr0dsuq4x7d

Problem solved.

Unfortunately, that depends on the configuration software the hoster is using. In most cases there is some way to match a domain (or subdomain) with a specific folder. Others create the folders automatically.