Nostr Web Client

If you're seeing this on your profile for nip05 verification in nostrudel ...

then you may need to set this header for that resource

access-control-allow-origin: *

Also, make sure your json for /.well-known/nostr.json is actually well formed.

Please Login to reply.

Thanks. Can I ask you something else about it?

your nip05 fails validation because your json is not well formed. Add commas between fields.

{

"names": {

"moizen": "dbc828cc8b33efa73a60ce27bfcf6e039fd602af289f7deb717d766aed78a663",

"moiz_caminero": "dbc828ad90e9f0ebe417b0245d0865b232b3c8e46f5ec4ec7dbd30f6f532d1b0"

}

Thank you! I just stumbled on to this note; I missed its notification.

CORS is a pain for nip-05 on Web clients.

Can I add another common issue? Redirects break nip-05 and it's quite common to redirect to www. nostr.json should be excluded from the redirect

yes. redirects are explicitly called out as a nogo in the nip

Unlucky for all the nostrverified.com plebs...

Yep, I see this a lot

How do I do this when hosted on cloudflare pages? Should I move it back to GitHub?

I know why it’s necessary but I hate CORS so much lol

It’s such an easy fix but as a backend engineer it’s the thing I always the thing I totally forget about and bites me unexpectedly.