[enhancement] avoid collisions with real contacts

[kollokollo]

I have an idea for enhancement of the contact generation principle. It is hard for the app to identify fake contacts it has created, e.g. for later removal. Using a certain name pattern (all names starting with the letter "z") is simple, but the poisoned database also can be easily cleaned. So I would suggest the user to enter a 4-digit PIN at the startup of the app. All contacts will be coded with that PIN so that later fake contacts can be identified only if you know that PIN.

How to do it: Maintain two lists of 1024 names, 1024 surnames and 1024 last names. Now randomly combine them, (gives 20 bits code) and also combine them with the 12 bits generated by the PIN. Together we now have a 32 bit value for each combination. Now calculate a hash from these 32 bit (lookup table or 8bit checksum). And discrard all combinations which have a hash other than one speicific, say 0. Then all fake contacts can be identified and the chance of a false positive (to be removed from the contact list) is 1/256 (in this example with a 8 bit hash) which probably is good enough. One can use a 6-digit pin to further bring it down.
Lists with 1024 Names can easily be obtained/generated. One even can use customizes list according to the nationallity or so.

[BillDietrich]

Thanks for the ideas, but it sounds a bit complicated. And I'd rather have all fake names in one bunch (alphabetically), so they clearly stand out (for the phone's user) from real contacts. Yes, the current scheme is a bit easy for someone to recognize as fakes. OTOH, if everyone just uses the default settings, the given fake names will appear in lots of Contact lists, and thus look more genuine.

I'll think about it. Thanks.

[kollokollo]

I have programmed this method (quick and dirty in a script) and it generates a lot of fake emails like these ones:
And I can identify them if you mix them in other lists with (real) names. Put only I can do it knowing the correct pin.

Miah Moran [email protected]
Erickg Nelson [email protected]
Everleigh Mcdaniel [email protected]
Jaysong Hendricks [email protected]
Joanna Gilmore [email protected]
Kyleigh Felix [email protected]
Reina Nelson [email protected]
Thaddeusg Lawrence [email protected]
Edith Yang [email protected]
Denverg Glover [email protected]
Zaniyah Acevedo [email protected]
Tatumg Callahan [email protected]
Anaya Reeves [email protected]
Lanceg Woodard [email protected]
Maryam Short [email protected]
Khalilg Acosta [email protected]
Noelle Bond [email protected]
Marcosg Melendez [email protected]
Erin Collins [email protected]
Jaydeng Baxter [email protected]
Londyn Guevara [email protected]
Kayla Andrade [email protected]
Milani Gutierrez [email protected]
Kyrieg Stevenson [email protected]
Paulg Bowen [email protected]
Ariadne Davidson [email protected]
Charlieg Jimenez [email protected]
Chaya Cain [email protected]
Alora Quintana [email protected]
Lukag Potter [email protected]
Ramong Swanson [email protected]
Elaina Mata [email protected]

If you are interested, see here: https://codeberg.org/kollo/X11-Basic_examples/src/branch/master/All/Internet/fake-email-names

It is a sort of BASIC dialect, sorry, but maybe you can read it anyways...
--> fake-names.bas

However, of course one need still to find a way to get these fakes out of the way of the user on the phone.

Another thought: What about adding fake profile pictures from deep fakes.....

[kollokollo]

OTOH, if everyone just uses the default settings, the given fake names will appear in lots of Contact lists, and thus look more genuine.

Yes, good point.