 |
 |
I appreciate the information about the change in Chrome. I agree that there are use cases, especially on shared machines, where it could be a big concern. However, I have personally resisted getting upset, despite the furor around me, because I don't feel it fundamentally changes anything for me (except make it easier to be logged in the way I expect). As someone who maintains two Google accounts (MPOW uses Google Apps and I have a personal Gmail/Google account), having separate profiles in Chrome meant I could run two browser instances side by side, each with their own synced bookmarks and login state. Profiles work best when you're logged into Chrome (although you can still get away being logged out, even in Chrome 69). I use a 3rd party password manager, so I don't sync passwords, payment methods, or addresses through Chrome. I have a browser extension that purges my browser history when I shut down the browser. I guess cookies could be a concern -- sometimes database access through the proxy will get a corrupted session and I have to purge the cookies out, but that happens to my colleagues once in a while and I suspect they don't all use sync or run multiple accounts. Again, I use a browser extension to delete cookies or, rarely, bare metal delete the history, sessions, and cookies. I confess being occasionally worried about what Google knows about me and reading various articles about the change hasn't reassured me. One article made a good point about the change making a mess of Chrome's previously very reasonable (and readable) privacy policy. And it raises the issue about Google not adequately notifying anybody that the change was coming. Tom On Wed, Sep 26, 2018 at 9:15 AM Adam Constabaris <[log in to unmask]> wrote: > By way of an update, Google has made an announcement about this issue (and > others, such as that currently, "delete all cookies" in Chrome 69 does not > delete google-domain cookies): > > > https://www.blog.google/products/chrome/product-updates-based-your-feedback/ > > So, it sounds like they will be reverting the most egregious changes in > Chrome 70. > > I am noisily resisting my urge to editorialize other than to note that they > evidently got a *lot* of <<loud>> pushback on this before they announced > the upcoming changes. > > cheers, > > AC > > On Mon, Sep 24, 2018 at 7:48 PM Sam Manderson <[log in to unmask]> > wrote: > > > Greetings library colleagues, > > > > I would like to propose the changes to Google Chrome make the use of the > > application in a Public PC environment unconscionable from a user privacy > > standpoint. > > https://www.wired.com/story/google-chrome-login-privacy/ > > > https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/ > > > > Mozilla's 'Firefox' is a comparable web-browser which is in my view a > good > > replacement, and the values of Mozilla more closely align with broader > > library values. > > https://www.mozilla.org/en-US/about/manifesto/ > > https://www.mozilla.org/en-US/firefox/ > > > > Best, > > > > Sam Manderson > > Librarian - Mobile & Outreach Services | Whangarei Libraries Whangarei > > District Council | Private Bag 9006, Whangarei 0148 | > > www.whangarei-libraries.com P 09 430 4206 | DDI 09 470 3002 | E > > [log in to unmask] > > >