Nip05 does not verify. nostr:nevent1qqsvpydmlm24ejpufffpr5ap546svvtw9cgsvrqpsancwh3azd6g35qpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzp57hgyjdm76mm3sm3uvdzlpnxkamf7x8zxp2xhhzwv22fxjwk7caqvzqqqqqqyuppw4a
I remember some discussing Nip05 itself isn't that useful to really verify if the user is real. For instance I think @jack did remove his because of this. To check if is Saylor's real npub we should check if he posted his Npub on X and see if it corresponds
@jack removed NIP05. This supposed Saylor still has it listed but does not verify or validate.
Yeah I see that..
I don't have X to check.
Jack is still verified though. (Via Primal I believe)
Jack lists a lightning address from primal, but there's no verification associated with that.
A Primal address doubles as a NIP-05.
And external sites correlate. https://i.nostr.build/qnXn.jpg
A primal address can be used as a nip-05, but there's no validation done if I just put it as my lightning address. You need that verification link to point back to prove that primal recognizes the pubkey
Yep
Just done it to myself now within Damus. I had a personal domain nip-05 verification before. Now I am verified by Primal.
Looks like it's not working. https://i.nostr.build/gdmB.jpg
Interesting - looks ok for me. (Following myself and all)
nip05 should be user@domain.xxx no? https://github.com/nostr-protocol/nips/blob/master/05.md
Should be but why is no domain visible for Jack?
Jack doesn't use nip05 verification.
But then how is he showing as verified on Damus?
I'm not sure. No other client shows him being verified. Damus bug? He does have a primal lightning address, but no nip05 verification.
Just have multiple. Then publish in the profile which one you want. I'm at gary@shenandoahbitcoin.club and gary@bitcoinveterans.org
Yeah same here ahahaha I just tried to check and do a research on browser X , looking for his tweet with npub word in it, but I can't without the app 🤣
I'd imagine its there but they are just redirecting based on their CMS setup not recognizing it. I had that issue with Litespeed. It doesn't look like they've enabled CORS either so I'd say it was a half start if it was real at all.
Doesn't negate my point. No way to validate.