nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh how do you calculate the WOT number?

Reply to this note

Please Login to reply.

Discussion

It's just 1 level WoT, meaning your contact list 😅 It's on my to do list to implement a real one

Ah 😊

Looking forward to your design - if you can drop your thoughts here:

https://github.com/nostrability/nostrability/issues/213

I have this situation with robosats and I honestly believe the best 1 line of defense method is NIP-05.

I believe some clients take it as a joke but its extremely useful to rapidly identify and discard impersonators.

And obviously the best but most expensive one is to use your WoT. Primal does a good job there by showing notorious people following an account, that's something reproducible with a 2nd level WoT of any user.

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn didn’t you just spoof a nip-05 for your impersonation testing the other week?

Yes, most clients just check that the address works and show a check mark, which is awful. NIP 05 can be good for validation only if you already know what name/domain to expect. This can be ok for comparing data across apps, or in a Soapbox style client which privileges a particular known NIP 05 provider.

what more should a client check with nip05?

NIP 05 is an "address" primarily. So it's for a scenario where someone tells you their nip 05 out of band, and you follow it to find their pubkey. Using it as a way to validate authenticity is qualified by context at best.

Use nostr:nprofile1qqstq4j6pk2sgaupru6l7ah9nq0dueafq356jllwcy7uzlek9yx7hlspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshs4kprv3

👀

3rd level following of following?