KYC = Kill Your Customer?

You’re right nostr:nprofile1qqsfrjd9ux5hgsg5cmlz6cdwfh5zv2024g8m2t6g9zqf83l8uqm0svspr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzfmhxue69uhkummnw3ezu7nzvshxwecjczf48 😭 Full interview is coming on Monday, stay tuned! 🫢

https://blossom.primal.net/8a1fb5edca5ca7879ed98ca23b22f77abe2c7fb613c314f16e0ff7d362bb7b13.mov

Reply to this note

Please Login to reply.

Discussion

Vexl might hash them internally but the fact is that most phone numbers are literally "live meatspace trackers" and there are reports every day of people being targeted thanks to location data

The responsible thing to do would be to completely remove the phone number dependency from their product, and not to normalise the sharing of such data within the community

Especially when phone numbers are KYC'd themselves in many jurisdictions. It's a dangerous (if client side) honeypot.

I'd love to use vexl but there's never anyone else to be found on it.

✌️✌️✌️✌️