I have a question, my profile patch is gone and if I look my nostr profile in Iris it strikes my nip-05.... Look at the screenshot....
How do you see it? #nostr #plebchain #asknostr
Discussion
I don't know what a profile patch is, but as for the nip05 strike through, I wonder if that's how they indicate a failed check on the nip05? On Amethyst is shows a red symbol if the nip05 doesn't resolve.
It looks good in Amethyst.
Thank you
I'm not sure if the actual results returned from https://nostr.lima.zone/.well-known/nostr.json?name=rubenstorm are completely valid, though.
```
{
"names": {
"rubenstorm": "b2caa9b3ef30faad605e5eeed8da2c8fd7b4ca872becdc440029f4fb9eab0fb5",
"ruben": "b2caa9b3ef30faad605e5eeed8da2c8fd7b4ca872becdc440029f4fb9eab0fb5",
"storm": "b2caa9b3ef30faad605e5eeed8da2c8fd7b4ca872becdc440029f4fb9eab0fb5",
"rs": "b2caa9b3ef30faad605e5eeed8da2c8fd7b4ca872becdc440029f4fb9eab0fb5",
"nip05": "dd84c71a1f082fc9a59374dd4b6e0aac9f8309682f21b7c0b1a48f41243be4e2",
"services": "dd84c71a1f082fc9a59374dd4b6e0aac9f8309682f21b7c0b1a48f41243be4e2"
}
}
```
Looks a bit suspicious to me. Maybe you should stick to the [NIP-05](https://github.com/nostr-protocol/nips/blob/master/05.md) more closely to be sure that it will act consistently across different clients.
And there is one more thing, the "Access-Control-Allow-Origin: *" header is missing.
```
HTTP/2 200
server: openresty
date: Sat, 27 Dec 2025 10:24:24 GMT
content-type: application/json
content-length: 511
x-lima-id: atIeDnLUtSPg3hZxeJ
last-modified: Fri, 26 Dec 2025 16:29:55 GMT
etag: "1ff-646dd675269fa"
accept-ranges: bytes
content-security-policy: upgrade-insecure-requests
strict-transport-security: max-age=31536000; includeSubDomains; preload
```
Thank you.... If I take that URL, shouldn't it just show the pub key of that one user?
https://nostr.lima.zone/.well-known/nostr.json?name=rubenstorm