Nostr Web Client

I think it might actually be an issue with my json.

A space between the name and the key.

Which is funny, because I created this tool after I manually wrote the json, which is actually giving the correct json! ahahahah

https://resources.davidcoen.it/nip05creator/

Lurking Cat 2y ago

I think your guess is probably correct due to incorrect json. I have seen #[7] sucessfully set up his own NIP-05 using _@iefan.tech

One interesting thing is if you compare curl response your nostr.json and iefan's nostr.json then you will find the difference of content type. Iefan has additional atrribute charset=utf-8 .

curl -v https://iefan.tech/.well-known/nostr.json

Reply to this note

Please Login to reply.

Discussion

David Coen 2y ago

I need to check better the cors

Don't Believe The Vibe 🌱🍋🍊 2y ago

If you check #[10] jb55.com it's not set to utf and still works.

Lurking Cat 2y ago

Although currently Will uses jb55@jb55.com instead of _@jb55.com format, but agree this issus seems weird 😅