Open HonkMonster opened 7 months ago
oh, look like some issue prevent lume fetch your nip-05, maybe cors issue, I will look into it
It's entirely possible it's a misconfiguration on my end, let me know if I need to change anything.
ah nope, your NIP-05 is fine, lume cannot verify your nip-05 cause by case sensitive issue, I've pushed new commit to fixed it
new build will be release in the weekend
I thought that might be it. I have another minor nitpick with NIP-05. When a user does _@example.com
, the "_@" should be excluded and it should only say the domain name. Example:
oh, I will support it in lume too
Hi, I've pushed new update for NIP-05 improvement, https://github.com/luminous-devs/lume/releases/tag/v2.2.2
Still getting issue on 2.2.3
_@'s are displaying correctly though
Sorry about that, my latest changes are override old changes I've pushed new commit to fix it, but I not release new version yet, maybe at the weekend when I push some other large changes
Lume says my NIP-05 is unverified
Other clients like noStrudel think it's fine
My NIP-05: https://honk.monster/.well-known/nostr.json