public-geolocation@w3.org from May 2009 by author

Alissa Cooper

Re: Additional security and privacy considerations? (Wednesday, 20 May)
Re: Additional security and privacy considerations? (Wednesday, 13 May)

Andrei Popescu

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Friday, 22 May)
Re: Additional security and privacy considerations? (Thursday, 21 May)
Re: Additional security and privacy considerations? (Wednesday, 20 May)
Re: aborting getCurrentPosition()? (Wednesday, 20 May)
Re: aborting getCurrentPosition()? (Wednesday, 6 May)
Re: aborting getCurrentPosition()? (Wednesday, 6 May)
Re: aborting getCurrentPosition()? (Wednesday, 6 May)
Re: updated editor's draft of the Geolocation API specification (Monday, 4 May)
Re: updated editor's draft of the Geolocation API specification (Monday, 4 May)
updated editor's draft of the Geolocation API specification (Monday, 4 May)

Angel Machín

Re: renaming enableHighAccuracy (Thursday, 21 May)
Re: geolocation privacy statement strawman (Friday, 1 May)

Anne van Kesteren

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: aborting getCurrentPosition()? (Wednesday, 6 May)

Doug Turner

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Thursday, 21 May)
Re: Additional security and privacy considerations? (Wednesday, 20 May)
Re: Additional security and privacy considerations? (Wednesday, 20 May)
Re: Additional security and privacy considerations? (Monday, 18 May)
Re: Additional security and privacy considerations? (Wednesday, 13 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Re: Support for GeoJSON? (Tuesday, 12 May)
Re: Review of Security & Privacy text in current editor's draft (Tuesday, 12 May)
Re: Support for GeoJSON? (Tuesday, 12 May)

Erik Wilde

Re: Additional security and privacy considerations? (Thursday, 21 May)
Re: Additional security and privacy considerations? (Monday, 18 May)
Re: Additional security and privacy considerations? (Monday, 18 May)
Re: altitude measurement (Tuesday, 5 May)

Greg Bolsinga

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)

Ian Hickson

Re: Additional security and privacy considerations? (Wednesday, 13 May)

Johann Hechter

RE: altitude measurement (Tuesday, 5 May)

Lars Erik Bolstad

Re: Additional security and privacy considerations? (Monday, 18 May)

Matt Womer

Restricting API access (Friday, 22 May)

Max Froumentin

Re: aborting getCurrentPosition()? (Wednesday, 13 May)
Re: aborting getCurrentPosition()? (Wednesday, 6 May)
aborting getCurrentPosition()? (Wednesday, 6 May)

Perry Tancredi

RE: Additional security and privacy considerations? (Wednesday, 27 May)
RE: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Wednesday, 20 May)

Peter Ecclesine (pecclesi)

RE: Additional security and privacy considerations? (Wednesday, 20 May)
RE: Additional security and privacy considerations? (Wednesday, 20 May)

Richard Barnes

Re: Support for GeoJSON? (Tuesday, 12 May)
Re: Support for GeoJSON? (Tuesday, 12 May)
Review of Security & Privacy text in current editor's draft (Tuesday, 12 May)
Support for GeoJSON? (Tuesday, 12 May)

Rigo Wenning

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Friday, 22 May)
Re: Additional security and privacy considerations? (Monday, 18 May)
Re: Additional security and privacy considerations? (Wednesday, 13 May)
Re: Additional security and privacy considerations? (Wednesday, 13 May)

Thomas Roessler

Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Wednesday, 27 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Tuesday, 26 May)
Re: Additional security and privacy considerations? (Monday, 25 May)
Re: Additional security and privacy considerations? (Thursday, 21 May)
Re: Additional security and privacy considerations? (Wednesday, 20 May)
Re: Additional security and privacy considerations? (Wednesday, 13 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Re: Additional security and privacy considerations? (Tuesday, 12 May)
Additional security and privacy considerations? (Monday, 11 May)

Thomson, Martin

RE: Additional security and privacy considerations? (Wednesday, 20 May)
RE: Additional security and privacy considerations? (Tuesday, 12 May)
RE: Additional security and privacy considerations? (Tuesday, 12 May)

Last message date: Wednesday, 27 May 2009 17:22:41 UTC