Sentry issue: AWS-LAMBDA-BACKEND-1N

Define cost function satisfying the defined criteria in #33

Matching of zip codes is based on proximity and the number of times that helper has been called. To ensure the behaviour of the cost function that is minimized to find the best match is as expected, define situations where a specific behaviour is prescribed. Then choose a cost function that passes all scenarios.

Ideas

• if two helpers are equally close to the caller's zip code, choose the one that has had less calls
• if two helpers' distances are differing by less than <TOLERANCE>, choose the one that had less calls
• What does "equally close" mean?
• How much distance is one call worth in terms of the optimization?

• extend backend capabilites to match on a global scale
• implement different hotline numbers based on country

• avoid storing the caller's phone number while still being able to match them with the same helper
• store matches encrypted by caller's phone number
• from all the stored, encrypted matches, how do we find the right one for the caller? -> index table by primary key made up from hash of phone number + zip code and then find plain-text helper number

example:

+4917611111111 + 10407 = ioashgawiogwieniu353iu4ik

table:

hash	helper
ioashgawiogwieniu353iu4ik	+4916599999999

Are there methods to provide a unique output? If not, how do we solve this problem?

• save previous matches of caller/helper numbers
• if helper available, match with same caller
• optional: Ask caller if connection to same helper should be made (also twilio topic)

Right now calls to /phone require no authentication. This means people can just get all phone numbers saved in our system by bruteforcing over all zip codes.

Jonas Bulik (963430cf) at 23 Mar 09:08

Jonas Bulik (19b61778) at 23 Mar 09:05

Nils Krüger (0eec7174) at 22 Mar 22:37

Closes #27

endpoints, their parameters and responses have to be documented

Nils Krüger (62e3d1f1) at 22 Mar 22:37

... and 5 more commits

You are pushing commits at a very fast pace (across the whole organization). Due to that, we cannot deploy the commit 4110b951.

You can try again later or upgrade your plan.

You are pushing commits at a very fast pace (across the whole organization). Due to that, we cannot deploy the commit 2cc9524c.

You can try again later or upgrade your plan.

Moritz (4110b951) at 22 Mar 22:36

... and 1 more commit

Viktor Lorentz (2cc9524c) at 22 Mar 22:36

Deployed the commit a7b815ef to following URLs:

• https://coco-frontend-haarsl7hz.now.sh
• https://coco-frontend-git-develop.viktorlorentz1.now.sh

^{(via the Now + GitLab integration)}

Moritz (a7b815ef) at 22 Mar 22:35

Nils Krüger (0eec7174) at 22 Mar 22:32

... and 2 more commits