Matching profile history issues #4

New issue

Open

opened 2022-10-31 14:35:29 +01:00 by VityaSchel · 0 comments

VityaSchel commented

2022-10-31 14:35:29 +01:00

(Migrated from github.com)

Summary

Currently profiles are matched against full text, including name, age and place. However, there are several issues with that:

Place might change it's format (📍100м distance or exact name)
Age might increment over a long period of time
Text might be empty
Text might be non-unique, some examples of that are single emojies, common phrases, which leads to connecting profiles from different people
Text may change slightly over a long period of time: for example, user may correct grammar mistake and the app would never be able to connect new profile to older one

Solution

Maybe it makes sense to calculate image-specific type of hash on profile's photos and store them with profile's info. Then we can add matching weights, calculate text uniqueness and based on all these parameters make a decision whether this specific profile is connected to another one.

# Summary Currently profiles are matched against full text, including name, age and place. However, there are several issues with that: 1. Place might change it's format (`📍100м` distance or exact name) 2. Age might increment over a long period of time 3. Text might be empty 4. Text might be non-unique, some examples of that are single emojies, common phrases, which leads to connecting profiles from different people 5. Text may change slightly over a long period of time: for example, user may correct grammar mistake and the app would never be able to connect new profile to older one # Solution Maybe it makes sense to calculate image-specific type of hash on profile's photos and store them with profile's info. Then we can add matching weights, calculate text uniqueness and based on all these parameters make a decision whether this specific profile is connected to another one.