Joel_Koen
(Joel Koen)
9
I’m working on BeaconDB, a new alternative to MLS that hopes to publish data dumps under a public domain license. I’ve received a pretty significant amount of data over the past few weeks and am researching how I can protect the privacy of both contributors and AP owners before I publish any data.
Mozilla wasn’t able to publish any of their WiFi data because MAC addresses/SSIDs are personal information - if I was to publish data dumps containing these identifiers, I would be making it extremely easy to track where WiFi networks move over time. I’ve been experimenting with different ways to obfuscate this data, such as hashing the MAC and truncating it, creating collisions on purpose. This means that one WiFi network maps to multiple possible locations, and the client has to know multiple physically nearby WiFi networks in order to estimate an accurate location.
I’ve recently been thinking about how I can help prevent contributors from leaking information such as where they live, and figured I’d ask here as OSM contributors have much more experience with this. I recently asked the BeaconDB community about their opinions on using an account system to ensure that WiFi networks had been seen by multiple contributors, but I’m still not sure that this is the best solution.
When mapping OSM, users are aware of what data they’re changing, but with BeaconDB, users are uploading their location and where they’ve been, so I want to make sure that this information is protected.
1 Like