Language Selection

English French German Italian Portuguese Spanish

Google Web Accelerator sparks privacy fears

Filed under
Security
Web

Google Web Accelerator, which was released in beta, is set up to automatically work with Firefox and Internet Explorer once it's been downloaded. The service stores copies of sites frequently accessed by individual PCs and automatically retrieves new data from those pages, so that a Web browser needs to process only updates to those sites when asked to load them. It can also automatically "pre-fetch" frequently used Web sites before the user downloads it.

However, users are concerned that the service can cache more data from their computers than they would prefer.

On a Google Labs discussion group, one user said that the security implications of Google caching details of Internet sessions were unacceptable.

"I went to the Futuremark forums and noticed that I'm logged in as someone I don't know. Great, I've used Google's Web Accelerator for a couple of hours, visited lots of sites where I'm logged in. Now I wonder how many people used my cache. I understand it's a beta, sure, but something like that is totally unacceptable."

Google was not immediately available for comment, but said in a Web site statement that the service can receive information such as the user's IP address, computer and connection information, and "personally identifiable information", such as an e-mail address.

Full Story.

More in Tux Machines

today's howtos

GNOME: Mutter, gresg, and GTK

  • Mutter 3.25.2 Has Bug Fixes, Some Performance Work
    Florian Müllner has pushed out an updated Mutter 3.25.2 window manager / compositor release in time for the GNOME 3.25.2 milestone in the road to this September's GNOME 3.26 release. Mutter 3.25.2 has a number of fixes ranging from fixing frame updates in certain scenarios, accessible screen coordinates on X11, some build issues, and more.
  • gresg – an XML resources generator
    For me, create GTK+ custom widgets is a very common task. Using templates for them, too.
  • Free Ideas for UI Frameworks, or How To Achieve Polished UI
    Ever since the original iPhone came out, I’ve had several ideas about how they managed to achieve such fluidity with relatively mediocre hardware. I mean, it was good at the time, but Android still struggles on hardware that makes that look like a 486… It’s absolutely my fault that none of these have been implemented in any open-source framework I’m aware of, so instead of sitting on these ideas and trotting them out at the pub every few months as we reminisce over what could have been, I’m writing about them here. I’m hoping that either someone takes them and runs with them, or that they get thoroughly debunked and I’m made to look like an idiot. The third option is of course that they’re ignored, which I think would be a shame, but given I’ve not managed to get the opportunity to implement them over the last decade, that would hardly be surprising. I feel I should clarify that these aren’t all my ideas, but include a mix of observation of and conjecture about contemporary software. This somewhat follows on from the post I made 6 years ago(!) So let’s begin.

Distro News: Alpine, Devuan, and openSUSE

OSS Leftovers