I’m open to the idea but I can’t think of good solutions. Maybe something along the lines of a published list of hash(own number x other number), but it doesn’t feel right having that whole list out there. Maybe there also needs to be a relay spec where you can only query for a match but not retrieve the whole list.
I’m leaning toward this for the hashed phone number that you could optionally share on your profile so that damus could automatically find all your friends. It would really hard to build a rainbow table for this with a high argon2 security parameter.
What do you think nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z, nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe, any other mobile nostr devs ? Should we get a NIP going ? nostr:note1q8kxrrtlat9ezh6evwnqce4mhcqnt6xm5k5vn5xqwmmpeuqa0xusuzl6nc
Discussion
We should operate under assumption that the whole list can be accessed by a bad actor, since it is easy to have a relay that would collect the info or get hacked to get the list. It’s probably impossible to have something timelessly secure and accessible at the same time 🐶🐾🫡
yeah after running the numbers yesterday I haven’t got to a working solution yet other than a central server solution