On 11.09.2013, at 02:06 , Gervase Markham wrote:
> On 10/09/13 19:05, Chris Peterson wrote:
>> Our location service (and stumbler) also collects cell data, so we can
>> geolocate with Wi-Fi AP and/or cell data.
>
> Sure. But in the rural areas I am thinking about, cells cover many
> square km. Th
On 10.09.2013, at 17:41 , Daniel Veditz wrote:
> That can't be right, so your database must be more complex. If you're
> storing more than originally implied that may have some impact on a
> security assessment.
We apparently haven't been clear about the scope of the proposal. It only deals
with
On 10.09.2013, at 20:23 , ianG wrote:
> On 11/09/13 03:27 AM, Daniel Veditz wrote:
>> "private" means we can't even /look/ at it, rather than merely can't
>> store it?
>
> The data regime might be simply put as this: you can't store a number
> suitable for tracking (or any derivative of it if t
On 10.09.2013, at 03:39 , Gervase Markham wrote:
> BTW, how does the service figure out the lat/long of an AP? Do we do
> anything at all with signal strengths? Could we?
This is a bit off-topic for the security discussion.
I suggest starting a new thread on dev-geolocation, if you want to know
On 10.09.2013, at 03:46 , Gervase Markham wrote:
> On 10/09/13 10:48, ianG wrote:
>> If that is the case, why not flip it around. Instead of trying to
>> interpolate the existing data that is broadcast out there, why not write
>> a protocol to broadcast the direct location from the wireless acces
On 10.09.2013, at 03:46 , Gervase Markham wrote:
> On 10/09/13 00:25, R. Jason Cronk wrote:
>> What happens if I move?
>
> The raw database notes that you are now being detected in a new
> location. What happens then is up for debate. I'd argue that if your
> position was fixed for N months befo
On 09.09.2013, at 18:41 , Eric Rescorla wrote:
> 1. How do I bootstrap? I turn on my device and want to get the coordinates of
> the aps I see. That requires a lat long for neighbors. What now?
We build the database by having people use a stumbler application to sent us
observations. The stumbl
On 09.09.2013, at 18:13 , Brian Smith wrote:
> On Mon, Sep 9, 2013 at 2:58 PM, Chris Peterson wrote:
>> Google's Location Service prevents people from tracking individual access
>> points by requiring requests to include at least 2-3 access points that
>> Google knows are near each other. This "p
