-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find near matches #50
base: main
Are you sure you want to change the base?
Conversation
|
There is probably room for optimization. Rana no longer uses all cores to their full extent |
Hi @chGoodchild I like this idea, but the implementation is not giving a good UX IMHO, if I executed
Here rana got a best match found 25% similar, in a four letter word 25% is just one letter, if we are going to allow a behavior like this we should increase the percent to something over 75% let's see this one:
Here rana found 50% similar, word |
How about something like this?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it works really well, can you please change the output to this:
Target: n0str
Found match with 80.00% similarity:
Vanity npub found: n0stjw04hnxmhc4ctxlzt72vqep3c84n34537uul40kxs6fhljqqv735x6
Found matching Nostr public key:
Hex public key: 9be0b939f5bccdbbe2b859be25f94c06431c1eb38d691f739fabec686937fc80
Hex private key: f5e86007c2e7a769910ea67c300d69adeae4cc7020a3f20a33f287bc9129780e
Npub public key: npub1n0stjw04hnxmhc4ctxlzt72vqep3c84n34537uul40kxs6fhljqqv735x6
Nsec private key: nsec17h5xqp7zu7nknygw5e7rqrtf4h4wfnrsyz3lyz3n72rmeyff0q8qqmz9fg
I just moved target
and removed current
Find near matches