@Vitor Pamplona when I use uppercase in my nostr address, it says unverified. Is this case sensitive? It seems not because @Bearetta 🐻❄️🇨🇿 has an uppercase B set in her profile but lowercase in her nostr.json and it says verified...
Login to reply
Replies (6)
It could be some redirection. Nip05 does not accept any redirections on the server side.
Thanks 👍 I was querying it using browser which I guess automatically changes it to lowercase before sending, which Amethyst mustn't. So why does it work for Bearetta@bitpunk.fm in Amethyst?
i'm pretty sure that in several places in the nips it is said that all hex and bech32 encodings are to be lower case only
Alright, thanks for the info. By the way, your LN address isn't working
I'm taking about the name key in the JSON that's associated with the pubkey
It looks like it's something to do with what @Vitor Pamplona said. At minestr.app I'm using path handlers to serve specific files for nostr.json queries. It works for lowercase for some reason, but for uppercase it bugs out. Whereas if I test not using a redirect (just a plain hosted file at alpha.minestr.app/.well-known/nostr.json, and then try to use Chris@alpha.minestr.app (despite the JSON name key being lowercase "chris"), it verifies as OK. This behaviour confuses me.