You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since a trusted server is accepted in this project why not let each user (A) "draw" a cercle (of 2m radius) around him[her]self and monitore each in and out of other users (X) in his circle. If a user stays more than 60sec in his circle then record the "[temp]ID" of that user ?
If "A" moves to another aera without someone entering his circle then that position is not saved.
That makes more traffic between users and the trusted-server but is more efficient because only real contacts are recorded.
With the bluetooth many false contacts because no way to assess the distances (or am i wrong ?)
The text was updated successfully, but these errors were encountered:
Are you talking about using a GPS to draw this circle ? This goes against the principle of data minimization since actual positions will be queried/stored (i.e. the location you drew the circle at). There are studies on how BT correctly assesses (or not) distance, see for instance : https://github.com/opentrace-community/opentrace-calibration/blob/master/Trial%20Methodologies.md which was designed for the TraceTogether app.
Since a trusted server is accepted in this project why not let each user (A) "draw" a cercle (of 2m radius) around him[her]self and monitore each in and out of other users (X) in his circle. If a user stays more than 60sec in his circle then record the "[temp]ID" of that user ?
If "A" moves to another aera without someone entering his circle then that position is not saved.
That makes more traffic between users and the trusted-server but is more efficient because only real contacts are recorded.
With the bluetooth many false contacts because no way to assess the distances (or am i wrong ?)
The text was updated successfully, but these errors were encountered: