New Service Worker Event from GeoLocation

2016-02-10 Thread Richard Maher
WRT the Service Worker specification can I please request the inclusion of
a new event?

onTravel/Move/Position/Location/WhateverIsAppropriate.

The positionManager subscription should allow one to specify min distance
and/or time between GPS updates but the firing of this event must be
capable of re-instantiating a previously-terminated Service Worker.

May I also please draw your attention to two see-change posts currently
active in the W3C forums: -

https://github.com/w3c/geofencing-api/issues/25
https://github.com/slightlyoff/ServiceWorker/issues/745

"GeoLocation in ServiceWorkers" you know it makes sense?

Cheers Richard Maher


TPAC 2016 - meetings

2016-02-10 Thread Chaals McCathie Nevile

Dear all,

as you probably know, the W3C will hold its Technical Plenary meeting this  
year in Lisbon, September 19-23.


Rather than meet for several days in plenary, with an hour or two for any  
given topic we are considering an approach that gives more focused time to  
a few important areas of work.


We propose people ask for time to work on a particular area, for example  
"a day for editing and UI events", or "2 hours for File APIs".


If there are other topics you don't want to clash with, e.g. because of  
significant overlap, please say so.


We will have to reserve the physical spaces by the end of March, which  
means while we might be able to shuffle individual meetings a bit, we need  
to know pretty soon what sort of meetings we should be trying to  
accommodate.


We anticipate having a plenary session as some part of the final day,  
which will mostly be a quick wrap on what happened for each group that  
met, and a quick run-down of all the other work we have - much as webapps  
has traditionally done at the *start* of its TPAC meetings in the past.


As well as feedback on what meetings you think you will need, we of course  
appreciate feedback on the plan itself.


cheers

Chaals, for the chairs

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
 cha...@yandex-team.ru - - - Find more at http://yandex.com



Re: [ServiceWorker] Expose GeoLocation to workers (#745)

2016-02-10 Thread Richard Maher
@martinthomson 

I hate to make this a point of jurisdiction, but I think that this is a
discussion that needs to be had in the geolocation working group.

I've been careful to avoid any demarcation issues by always involving the
Service Worker AND GeoLocation communities. My lobbying has centered on: -

Forums:
https://github.com/slightlyoff/ServiceWorker/issues/745

https://github.com/w3c/geofencing-api/issues/25


Mailing Lists:
public-webapps@w3.org
public-geolocat...@w3.org

If there are better forums then please let me know.

Having said that, I am becoming more and more convinced that this is a
Service Worker issue. The following is what I believe is required to make
this work: -

ServiceWorkerRegistration.travelManager (getSubscription(),
permissionState(), subscribe())
The subscribe() method with take options such as (minMsecs/metersl between
position updates, accuracy, etc)

A new ServiceWorker "Travel" event will be created. The UserAgent must be
able to re-instantiate a previously terminated ServiceWorker on the
strength of this event.

One GeoLocation watcher per UserAgent sounds battery-friendly to me!

I'm very nervous when someone saves their hands when it comes to the
privacy story. The web has thus far had a great accountability story and
adding the ability to track someone when they aren't visiting your site is
one capability that could easily undermine all the good work we've done.
I'd want to see a clear plan for how a user is able to remain in control to
be even remotely comfortable that watchPosition could be exposed.

God gave us valium and SSRIs for just such occasions. Either way please
don't FUD a technical forum with tales of "There be dragons".

Users are running a WebApp and NOT "visiting your site". Permissions are
there for just such a requirement. BTW I tested Firefox last night and it
is the only browser that DOES continue to track you when the browser is in
the background.

But can I ask where have you articulated your fears about WAKE-LOCK and
CPU-LOCK back-dooring user-tracking functionality? What about the new
GeoFence API? If I throw a 5m GeoFence around my current location and get a
"leave" event then surely I can just drop that geofence and recreate
another around my new current location. What is that if not user-tracking?

Most importantly, can I stress that this is a user REQUIREMENT and not an
IMPOSITION! Ask all the permission questions you want but this simply has
to happen.