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

Arno Scharl

• Assistant or Associate Professor in New Media Technology (Tuesday, 31 May)

Ayumi Hamasaki via GitHub

• Re: [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined (Sunday, 8 May)
• Re: [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined (Saturday, 7 May)
• [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined (Saturday, 7 May)

Jeffrey Yasskin via GitHub

• Re: [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined (Sunday, 8 May)

Lukasz Olejnik via GitHub

• Re: [deviceorientation] Malicious use of the phone's Gyroscope (Tuesday, 31 May)

Mandyam, Giridhar

• Geofencing API - next steps? (Thursday, 19 May)
• TPAC 2016 Registration Open (Wednesday, 11 May)

Marijn Kruisselbrink

• Re: Geofencing API - next steps? (Friday, 20 May)
• No longer working on Geofencing API (Wednesday, 11 May)

Martin Thomson

• Re: Geofencing API - next steps? (Friday, 20 May)

Richard Maher

• Re: Geofencing API - next steps? (Thursday, 26 May)
• Re: Geofencing API - next steps? (Friday, 20 May)
• Re: [geofencing-api] Uncaught (in promise) ReferenceError: CircularGeofenceRegion is not defined (Thursday, 12 May)
• Re: No longer working on Geofencing API (Thursday, 12 May)

Yossi Oren via GitHub

• [deviceorientation] Malicious use of the phone's Gyroscope (Saturday, 28 May)

Last message date: Tuesday, 31 May 2016 11:53:58 UTC