Ok, that should be fine as it's set to lowercase in both Damus settings and in the nostr.json file. I've checked server logs to ensure nothing getting blocked, and tested updating where other clients show it correctly. Anything else you could think of might be preventing it? My nostr.json file is minified. Would that matter? Cheers
Discussion
Are there any other criterion that would be unique to Damus that prevents a successful parsing of the json?
Found the issue. You have 2 entries for “lucas” with different keys. Remove one of them and it should work. Damus is probably testing against the first key and not the latest one.
Do a search. You’ll see it.
Hmm, shouldn't both technically work? Since it cross-references the username with the hex key? I've also tried others from the list (where they're unique) and those also do not work
Not sure how nip05 handles multiple keys per name but it’s not valid json. You cant really have key:value then the same key and value. Run your json through a validator. That’s how I found the issue.
Maybe swifts json parser doesn’t like that? Haven’t tested it
So, you have inadvertantly made me aware of a different issue I was not aware of lmao. Thank you!
It does seem that per the NIP-05 spec that you can only have one username in the json object: https://gothub.projectsegfau.lt/nostr-protocol/nips/blob/master/05.md
"if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying "bob@bob.com" for that user, as that will have become an invalid `"nip05"` property)."
So, that does explain one part. I also think I found the original root cause, which was a non-hex entry for a user, which may have errored out the Swift json parser. I now see users loading correctly again.
Appreciate you both jumping in here 👏
Happy to help because I was combing through the json on my iPhone wondering why it wasn’t working. I do obsessive stuff like that.