Re: Isolating Web apps (was: Making Web Apps first class citizen)

Le vendredi 08 mars 2013 à 17:51 +0100, Tobie Langel a écrit :
> > The threat I'm thinking of is being tracked across many other services
> > (from the same company or not) when I stay logged in into a service
> > (Facebook, twitter, google) because I use their associated tools on a
> > regular basis.
> >  
> How does not being logged in prevent you from being tracked?

Sorry, my language was sloppy; it prevent from tying my activities to my
account on the said service. It still allows tracking me anonymously for
sure (although DNT aims at reducing that risk).


> Agreed password handling would be nice, though this has to be at the
> OS level rather than at the UA level for the scenarios described here.

You mean for native apps? or for "Web apps as first-class citizens"? For
the latter, I would assume they would still be run by the UA one way or
another (but that might be too strong an assumption to make, I realize).

> Browserid needs more traction before it can be considered as a serious alternative login solution. It not there yet.

Right, but any new solution we could dream up in this space is even
further away to be there :)

> > * the interaction between a Web-app-in-browser and
> > Web-app-as-first-class-citizen (or two of the latter type); in
> > particular, how links are handled (when does a link end up where); and
> > that certainly seems like a critical technical piece that would need to
> > be handled (I'm not sure if SysApps has this in its plan)
> 
> Absolutely.

Looking at the SysApps runtime draft,
http://runtime.sysapps.org/#data-isolation
and http://runtime.sysapps.org/#navigation are relevant.

Dom

Received on Friday, 8 March 2013 16:57:51 UTC