- From: Jason A. Novak <jnovak@apple.com>
- Date: Thu, 10 Jan 2019 17:56:26 -0600
- To: Craig Spiezle <craigsp@agelight.com>
- Cc: Pete Snyder <psnyder@brave.com>, "public-privacy (W3C mailing list)" <public-privacy@w3.org>
Hi Craig - IIRC there’s some discussion of what each browser does in this paper — https://www.blaseur.com/papers/www18privatebrowsing.pdf but I don’t know how much browsers have changed since. J > On Jan 10, 2019, at 12:14 PM, Craig Spiezle <craigsp@agelight.com> wrote: > > Thanks for your briefing today. As mentioned I believe there is a good deal of confusion of what private browsing means. From my recent work on VPN privacy, I have been surprised on the confusion within the privacy community of browser based tools. Your article provides some good context https://brave.com/private-mode-is-not-really-private/ I have been looking for is as comparisons of where browsers are today. Is anyone can point me to any such current report I would be most appreciative? > > -----Original Message----- > From: Pete Snyder <psnyder@brave.com> > Sent: Thursday, January 10, 2019 10:04 AM > To: public-privacy (W3C mailing list) <public-privacy@w3.org> > Subject: Suggestions for future meetings > > Hi all, > > A small suggestion for how we could have more productive meetings going forward: please prepare accordingly! When we have visitors presenting specs, lets all be sure to read spec documents before meetings, and not guess about the contents of spec documents have have been provided days / weeks earlier. It would help us use the short amount of time we have more productively, and allow us to focus on the ambiguities / problem-areas of specs, instead of well described functionality. > > And in the cases where time doesn’t allow for reading specs before hand, I suggest reading them offline and then following up with questions here. Asking the authors what their documents say just seems… sub-optimal. Just my 2c :) > > Pete
Received on Thursday, 10 January 2019 23:56:54 UTC