Awesome, perfect!
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr has high standards lol 😂
Discussion
Did you do the last step?
Finally, make sure this file is served with the Access-Control-Allow-Origin header set to * as it needs to be accessible by clients.
How do you do that?
What are you using to provide the file? Nginx?
No, never heard of that. I use Vercel.
Then I don't know lol 😅
Maybe this will help? https://vercel.com/guides/how-to-enable-cors
Also if you view your profile in the next version of noStrudel I added some details if the client isn't able to verify your nip-05
https://mleku.dev/git/lerproxy
this is a fork of https://github.com/leproxy/leproxy that i made... with the intention of adding rewriting, haven't got to that yet
but it has a feature where you specify a nostr.json file path (should be absolute) and it will serve it up on the domain, in a mapping.txt file with a line like this:
n.mleku.dev: /home/git/nostr.json
in addition, you can use it as a simple to configure reverse proxy for other things, like i do, pointing a subdomain of my domain names to my relay and my testing fork of nostrudel which removes all the default hard coded relays and points only to mine
if you want to know how to set up go to build it, which i highly recommend:
https://github.com/quanterall/kitchensink?tab=readme-ov-file#install-go
IMO it's too simple, that if you can already use an ssh terminal you already know enough to setup and build the thing from source code, so, no, there will probably never be a binary release, gfy
ah yes, forgot to mention... it serves correct CORS wildcard and access method types headers so you get a purple check on web apps like nostrudel