151–160 of 230 posts
Earlier quoted context omitted.
There is sourcecode for both front and backend and the creators linked their names. So check the sourcecode and decide whether you trust the people involved that this is actually the code that is running the site
How do you know that the source code they published is the same code that the site uses?
I am a co-author of the site. We are already aware of your concerns about giving out your phone number. The source code is free and reviewable on Github. We know it's not possible to verify what's running on a server but we hope it adds a level of trust. We are currently hashing all phone numbers so we don't have to deal with them anymore. We will keep you updated.
Heck. Allow even prehashed phone number to be entered.
If you don't want to input your full phone number, you can use this tool: https://codeeverywhere.ca/apps/fb_data . Searches use partial data from multiple fields to find matches.
I am a co-author of the site. We are already aware of your concerns about giving out your phone number. The source code is free and reviewable on Github. We know it's not possible to verify what's running on a server but we hope it adds a level of trust. We are currently hashing all phone numbers so we don't have to deal with them anymore. We will keep you updated.
Hash the phone number in the browser before sending it to your server. That way it is at least possible to verify via devtools what is being send. Heck. Allow even prehashed phone number to be entered.
So there's some ambiguity or incompleteness somewhere.
Not sure what’s going on but it says my number is not part of the leak, but I’ve checked myself and it is actually leaked. Just be aware that it may not be complete.
I am a co-author of the site. We are already aware of your concerns about giving out your phone number. The source code is free and reviewable on Github. We know it's not possible to verify what's running on a server but we hope it adds a level of trust. We are currently hashing all phone numbers so we don't have to deal with them anymore. We will keep you updated.
Hash the phone number in the browser before sending it to your server. That way it is at least possible to verify via devtools what is being send. Heck. Allow even prehashed phone number to be entered.
The only way to check without giving up personal info is to get the data and look locally, or perhaps search for so many phone numbers that yours is buried in the haystack.
Earlier quoted context omitted.
Search fbleaks on telegram
I tried and get no results.
Earlier quoted context omitted.
Hash the phone number in the browser before sending it to your server. That way it is at least possible to verify via devtools what is being send. Heck. Allow even prehashed phone number to be entered.
I understand the frustration but they have the data and hence, a rainbow table, sending a pre-hashed phone number is the same as sending an unhashed one, unless the worry is man in the middle, who is just as likely to get the data. The only way to check without giving up personal info is to get the data and look locally, or perhaps search for so many phone numbers that yours is buried in the haystack.