zdlr
05-05-2005, 07:21 PM
Hey guys,
Just a quick heads up to not try Google's new Web Accelerator that is floating around the web. Basically the program works from a big cache and if you request the same page, instead of reloading it it gets it from Google's cache.
Sounds great right? Well, it isn't.
The problem lies mostly with forums and the like, for example, say Meter, Eyepatch, Saradin and I all used Google Web Accelerator and Saradin, Meter and Eyepatch all browsed this forum, the Officer board, and checked thier PM's.
Then I'd come along, get one of thier cached pages, since they were here first, and if I went to my PM's, it'd bring up a cached page from thier inbox. I could also possibly read thier PM's depending on how much was cached, and read the officer board.
So theres your heads up, take it as you will, but using normal http:// causes this problem and it wont be resolved until Google's decides to rethink the way the program caches.
I'm going to link to a somethingawful article, and although written in a humourous tone, the article highlights, with screenshots, what can happen and is spot on in highlighting the flaws mentioned above.
Thanks Google, I hate privacy.
http://www.somethingawful.com/articles.php?a=2858
edit: to avoid being called an idiot by Meter, as it seems anti-cache is in the page code, I only used DB forums as an example to highlight what can happen with viewing forums and other sites with the Accelerator, not saying it happens here. ;)
Just a quick heads up to not try Google's new Web Accelerator that is floating around the web. Basically the program works from a big cache and if you request the same page, instead of reloading it it gets it from Google's cache.
Sounds great right? Well, it isn't.
The problem lies mostly with forums and the like, for example, say Meter, Eyepatch, Saradin and I all used Google Web Accelerator and Saradin, Meter and Eyepatch all browsed this forum, the Officer board, and checked thier PM's.
Then I'd come along, get one of thier cached pages, since they were here first, and if I went to my PM's, it'd bring up a cached page from thier inbox. I could also possibly read thier PM's depending on how much was cached, and read the officer board.
So theres your heads up, take it as you will, but using normal http:// causes this problem and it wont be resolved until Google's decides to rethink the way the program caches.
I'm going to link to a somethingawful article, and although written in a humourous tone, the article highlights, with screenshots, what can happen and is spot on in highlighting the flaws mentioned above.
Thanks Google, I hate privacy.
http://www.somethingawful.com/articles.php?a=2858
edit: to avoid being called an idiot by Meter, as it seems anti-cache is in the page code, I only used DB forums as an example to highlight what can happen with viewing forums and other sites with the Accelerator, not saying it happens here. ;)