On 18.02.2015, at 12:04 , Gervase Markham <[email protected]> wrote: > On 17/02/15 18:19, Victor Ng wrote: >> - SSID blacklists have been removed as this is handled better by the >> server-side. > > This changes the privacy story here from "I can read the code and see my > _nomap SSID is not being sent to Mozilla" to "I have to trust Mozilla to > throw away information about my _nomap SSID."
The _nomap optout is of course maintained and the client still does this. We never send the SSID to the service, so we couldn't do this filtering on the service side [1]. This only removes the manual SSID blocklist entries looking for things like "train" or "bus". The problem with those is, that we'd need to have the exact same blocklist on all clients to be really effective. Otherwise client A reports a train wifi into our db, but client B never sends us data about the same train wifi also being spotted in a different place. We actually need those reports for different/conflicting positions to figure out a wifi is indeed moving. This is most effective if we get the data from all clients, incl. the data from potentially moving wifi networks. Hanno [1] https://github.com/mozilla/MozStumbler/blob/dev/libraries/stumbler/src/main/java/org/mozilla/mozstumbler/service/stumblerthread/blocklist/SSIDBlockList.java _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
