Oddbean new post about | logout
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag 
 NIP-05 speaks about the user part being case-insensitive, but they don't mention if it should be the client (before sending) or server that lower-cases it (before querying), so i think amethyst is correct passing it as-is
▲ ▼
Chris | 1 months ago (raw) | root | parent | reply | flag +1 
 Alright, thanks for the info. By the way, your LN address isn't working
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag +1 
 i was just restarting my node at the time... linux's OOM killer had eaten it during last build run 😠 

thank u for the zap !
▲ ▼
Chris | 1 months ago (raw) | root | parent | reply | flag 
 It looks like it's something to do with what nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau 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.
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag +1 
 yeah i fully agree it's confusing !

i assumed Vitor meant a HTTP redirect  (which never works with NIP-05) when he wrote that but you could be right

i don't know which HTTP server you're using, so can't tell you exactly how to do it, but i think the right behavior to configure would be make it so that NAME argument from "https://minestr.app/.well-known/nostr.json?name=<NAME>"  (or alternatively, the entire URL) is lower-cased before using it to find the specific per-user file (as the file system will be case sensitive).

that would make https://minestr.app/.well-known/nostr.json?name=Chris return the same as https://minestr.app/.well-known/nostr.json?name=CHRIS and https://minestr.app/.well-known/nostr.json?name=chris, and make the verification work in all software. 

That the JSON name key in the returned document is lowercase "chris" is ok; NIP-05 is sufficiently clear that clients need to do that comparison case-insensitively, which is why Beareatta's works