A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

index.md 6.5KB

4 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. title: App Assisted Contact Tracing
  2. url: https://lucumr.pocoo.org/2020/4/3/contact-tracing/
  3. hash_url: 42616669988094757bf9d4864ee4ab4f
  4. <p class=date>written on Friday, April 3, 2020
  5. <p>I don't know how I thought the world would look like 10 years ago, but a
  6. pandemic that prevents us from going outside was not what I was picturing.
  7. It's about three weeks now that I and my family are spending at home in
  8. Austria instead of going to work or having the kids at daycare, two of
  9. those weeks were under mandatory social distancing because of SARS-CoV-2.</p>
  10. <p>And as cute as <a class="reference external" href="https://en.wikipedia.org/wiki/Social_distancing">social distancing</a>
  11. and “flattening the curve” sounds at first, the consequences to our daily
  12. lives are beyond anything I could have imagined would happen in my
  13. lifetime.</p>
  14. <p>What is still conveniently forgotten is that the curve really only stays
  15. flat if we're doing this for a very, very long time. And quite frankly,
  16. I'm not sure for how long our society will be able to do this. Even just
  17. closing restaurants is costing tens of thousands of jobs and closing
  18. schools is going to set back the lives of many children growing up. Many
  19. people are currently separated from their loved ones with no easy way to
  20. get to them because international travel grinded to a halt.</p>
  21. <div class="section" id="technology-to-the-rescue">
  22. <h2>Technology to the Rescue</h2>
  23. <p>So to cut a very long story short: we can get away without social
  24. distancing with the help of technology. This is why: the most efficient
  25. way to fight the outbreak of a pandemic is isolating cases. If you can
  26. catch them before they can infect others you can starve the virus. Now
  27. the issue with this is obviously that you have people running around with
  28. the virus who can infect others but are not symptomatic. So we can only
  29. do the second next best thing: if we can find all the people they had
  30. contact with when they finally become symptomatic, we can narrow down the
  31. search radius for tests.</p>
  32. <p>So a very successful approach could be:</p>
  33. <ol class="arabic simple">
  34. <li>find a covid-19 suspect</li>
  35. <li>test the person</li>
  36. <li>when they are positive, test all of their close contacts</li>
  37. </ol>
  38. <p>So how do we find their cases? The tool of choice in many countries
  39. already are apps. They send out a beacon signal and collect beacon
  40. signals of other users around. When someone tests positive, healthcare
  41. services can notice contacts.</p>
  42. </div>
  43. <div class="section" id="avoiding-orwell">
  44. <h2>Avoiding Orwell</h2>
  45. <p>Now this is where it gets interesting. Let's take Austria for instance
  46. where I live. We have around 9 million residents here. Let's assume
  47. we're aiming for 60% of resident using that app. That sounds like a
  48. surveillance state and scalability nightmare for a country known for
  49. building scalable apps.</p>
  50. <p>But let's think for a moment what is actually necessary to achieve our
  51. goal: it turns out we could largely achieve what we want without a
  52. centralized infrastructure.</p>
  53. <p>Let's set the window of people we care about to something like 5 days.
  54. This means that if someone tests positive, that person's contacts of the
  55. last 5 days ideally get informed about a covid case they had contact with.
  56. How do we design such a system that it's not a privacy invading behemoth?</p>
  57. <p>The app upon installation would roll a random ID and store it. Then it
  58. encrypts the ID it just created with the public key of a central
  59. governmental authority and broadcasts it to other people around via
  60. bluetooth. It then cycles this ID in regular intervals.</p>
  61. <p>When another device (the infected person) sees this ID it measures signal
  62. strength and time observed. When enough time was spent with the other
  63. person and that contact was “close enough” it records the broadcast
  64. (encrypted ID) on the device. The device also just deletes records older
  65. than 5 days.</p>
  66. <p>When person is identified as infected they need to export the contacts
  67. from their app and send it to the health ministry. They could use their
  68. private key to decrypt the IDs and then get in contact with the
  69. potential contacts.</p>
  70. <p>How do they do that? One option does involve a system like a push
  71. notification service. That would obviously require the device to register
  72. their unique ID with a central server and a push notification channel but
  73. this would not reveal much.</p>
  74. <p>Another option could be to do the check in manually which would work for
  75. non connected IoT type of solutions. You could implement such a system as
  76. a token you need to regularly bring to a place to check if you are now
  77. considered a contact person. For instance one could deploy check-in
  78. stations at public transport hubs where you hold your token against and if
  79. one of your contacts was infected it would beep.</p>
  80. <p>Either way the central authority would not know who you are. Your only
  81. point of contact would be when you become a covid case. Most importantly
  82. this system could be created in a way where it's completely useless for
  83. tracking people but still be useful for contact tracing.</p>
  84. </div>
  85. <div class="section" id="the-phone-in-your-pocket">
  86. <h2>The Phone in your Pocket</h2>
  87. <p>I had conversations with a lot of people over the last few days about
  88. contact tracing apps and I noticed —&nbsp;particularly from technically minded
  89. people — an aversion against the idea of contact tracing via apps. This
  90. does not surprise me, because it's an emotional topic. However it does
  91. hammer home a point that people are very good at misjudging data privacy.</p>
  92. <p>Almost every person I know uses Google maps on their phone with location
  93. history enabled. With that, they also participate in a large data
  94. collection project where their location is constantly being transmitted to
  95. Google. They use this information to judge how fluid traffic is on the
  96. road, how many people are at stores, how busy public transit is etc. All
  97. that data is highly valuable and people love to use this data. I know I
  98. do. I'm also apparently entirely okay with that, even though I know there
  99. is an associated risk.</p>
  100. </div>
  101. <div class="section" id="the-future">
  102. <h2>The Future</h2>
  103. <p>My point here is a simple one: contact tracing if done well is
  104. significantly less privacy infringing than what many tech companies
  105. already do where we're okay with.</p>
  106. <p>I also believe that contact tracing via apps or hardware tokens is our
  107. best chance to return to a largely normal life without giving up all our
  108. civil liberties. I really hope that we're going to have informed and
  109. reasonable technical discussions about how to do contact tracing right and
  110. give this a fair chance.</p>
  111. </div>