Comments (6)
burdges
commented on August 20, 2024
I think location histories via GPS do not give you much precision unless the device actively polls the GPS, which kills the battery, and even then not on many devices. There are many issues with bluetooth but devices can kinda run it in the background without draining the battery too badly.
from documents.
ekg
commented on August 20, 2024
You can easily obtain a retrospective location history from Google. These
can be very precise because they are based on wifi information as well as
occasional GPS polling. I suggest you look at your own log, should you have
one, to get a sense of how precise they can be.
…On Sun, Apr 5, 2020, 14:18 Jeff Burdges ***@***.***> wrote:
I think location histories via GPS do not give you much precision unless
the device actively polls the GPS, which kills the battery, and even then
not on many devices. There are many issues with bluetooth but devices can
kinda run it in the background without draining the battery too badly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDQEL4TUWZMFQPHLUIGQLRLBZJZANCNFSM4MAQC7UA>
.
from documents.
EliasA
commented on August 20, 2024
Privacy oriented individuals might choose not to use the app at all it features like this exist. Even if contact history (tokens) would be in the mobile phone, a user could very likely identify the contacts using the location history as a logbook.
from documents.
ekg
commented on August 20, 2024
I'm kind of bouncing around a variant of this. We give people who test
positive to retrospectively collect their location data from GDPR compliant
providers and put it into the public domain. After their review and
agreement of course. Then no one needs to install an app, and they can
consider the community when they are primed to do so (don't want to infect
others, want to help others know if they might have been infected). Apps
can pick up that data and help people know if they are at risk. Uptake
isn't perfect but it helps. The app contact tracing breaks down if you
don't have a large fraction of the public using a compatible contact
tracing tool. Has it worked anywhere? The only working model for this is in
South Korea. And there the location history sharing is non-voluntary,
retrospective, and broadcast to whole communities.
…On Sun, Apr 5, 2020, 19:42 EliasA ***@***.***> wrote:
Privacy oriented individuals might choose not to use the app at all it
features like this exist. Even if contact history (tokens) would be in the
mobile phone, a user could very likely identify the contacts using the
location history as a logbook.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDQEMDFN6BRMQSQTWRUS3RLC7IFANCNFSM4MAQC7UA>
.
from documents.
carmelatroncoso
commented on August 20, 2024
The app does not aim at identifying locations that may be dangerous due to concentration of infected cases. This is a design decision. We limit the purpose of the application to the two goals described in the White Paper (notifying at-risk users, and provide epidemiologists with data to understand the disease). This enables us to collect and process very little data. In particular it avoids that we collect location data, which are highly sensitive and very hard to publish in a privacy-preserving way.
from documents.
ekg
commented on August 20, 2024
Voluntary data release is completely compatible with your two design
decisions. If your implementation is ideal, perhaps it won't help to notify
the at-risk any more than a privacy preserving model. But, voluntary data
release will almost certainly provide far greater utility to
epidemiologists who study the dynamics of an outbreak over any privacy
preserving model over the same data.
You should consider supporting as a parallel thread in your approach. The
virus does not respect our privacy. If we want to maintain our right to
privacy, we need to provide a reasonable set of norms that yield good
performance in countering this threat, or there will be a stronger excuse
to violate this right in a long term way for the sake of pandemic control.
…On Tue, Apr 7, 2020 at 11:38 PM Carmela Troncoso ***@***.***> wrote:
The app does not aim at identifying locations that may be dangerous due to
concentration of infected cases. This is a design decision. We limit the
purpose of the application to the two goals described in the White Paper
(notifying at-risk users, and provide epidemiologists with data to
understand the disease). This enables us to collect and process very little
data. In particular it avoids that we collect location data, which are
highly sensitive and very hard to publish in a privacy-preserving way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDQEIK5NRNQPBZNCOU3ADRLOMNLANCNFSM4MAQC7UA>
.
from documents.
Related Issues (20)
- Was DP-3T Exposure Calculation.pdf Android only? HOT 1
- Stability of distance estimation in case of using a bluetooth Extender HOT 2
- [Public Engagement] Visual Explainer / Scrollytelling on Privacy Preserving Proximity Tracing
- Mistake in communicating how information is passed around, in CH implementations of the apps HOT 3
- Reproducibility of Figure 1 in "DP3T - Exposure Score Calculation.pdf" HOT 3
- Risk calculation when exposed to multiple infectors both for < 15 min. HOT 7
- Naive secret sharing would allow for "jamming" on a non-physical level
- Why did the SwissCovid team not disclose the existence of the LASEC report? HOT 15
- Add support for multiple epidemics HOT 1
- [DOCUMENTATION] FAQ on Apple/Google framework issues HOT 1
- App feature request: Show stored app data as visualization of contact events HOT 3
- Schedule for F-Droid (and/or direct download) release of the Android app HOT 3
- [DOCUMENTATION] Cartoon, Dutch version, one pager: wrong text in picture 6. HOT 1
- Smartwatch App - Market Analysis (WearOS, WatchOS, Fitbit OS and Garmin Watch OS) and way forward HOT 1
- Who controls the 0xFD68 Bluetooth UUID?
- Potential privacy issue of new Exposure Notifications Express? HOT 3
- Wrong text on panel 6 of the NL onepage graphic HOT 1
- Update French onepage translation HOT 2
- Would like to understand the time window for notification
- Question: Where can I find the BLE MAC randomization code in DP^3T?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from documents.