Page Comparison

Info
This article is out of date. At the time it was written, there was no plan to encrypt published HA JSON data for MVP1 We now have a plan to encrypt this data - in part due to the arguments presented below. Details here: Design for MVP1 HA JSON Changes

Our current plan for MVP1 is to ship with the current implementation of redacted location data shared in plain text from Public URLs.

...

This means that it will be common for case data from individuals to have a publication delay of 2 or 3 days, perhaps even longer.

Countries we are taregtting targetting have total cases as follows:Haiti: 151; Guam: 151. As least 4 of the 7 targets would have this issue.

Mexio: 33,460, Puerto Rico: 2,173, Mexio: 33,460, , KCMO: 664 (on 5 May), Lake County FL: 223, Haiti: 151, Guam: 151, Teton County: 97.

...

This chart from Oxford (https://science.sciencemag.org/content/368/6491/eabb6936) shows why this is such a big problem.

This shows transmission from day of infection.

...

If it does allow us to reduce this number to low figures, 1, 2 or 3, say - then I think it makes MVP1 viable (as per above, I don’t think the current MVP1 plan is viable).
If it does not, then there is little point in spending time on a Hashing solution, and we should be working on the “full” solution as a priority, as a necessary part of MVP1.

References:

Versions Compared