Sponsored Content
The Lounge What is on Your Mind? Individual Risk Management (Personal IT Security) and Browser Cache Management Post 303033322 by Neo on Wednesday 3rd of April 2019 07:56:15 AM
Old 04-03-2019
Quote:
Originally Posted by bakunin

You asked for a scenario where this might pose a risk to the user: let us say i search Google for ways to overcome personal debt repeatedly. If one of the "advertisement partners" of Google is the next bank and if Google is able to identify me across sessions i may well have lowered my credit rating effectively by doing that research - even if it might not even be for me. Given, that is a constructed example and includes a lot of conjecture - but the girl getting advertisement for baby food before even her parents were aware of her pregnancy was real. It is not a lot different (not in scope and definitely not in technical background) from what i presented here.
Yes, that first example is "constructed" and not really realistic.

The second is a real example, but that example is not because of "cookies and caches"... it was because the girl had made purchases with Target and so Target (a retail chain in the US) sent her a paper flyer in the mail based on her purchases.

Quote:
Pole identified 25 products that when purchased together indicate a women is likely pregnant. The value of this information was that Target could send coupons to the pregnant woman at an expensive and habit-forming period of her life.
Neither of your examples are related to clearing cookies and caches.

The first is just a fantasy based without facts or details.

The second is well documented NOT to be related to cookies or web caches, but is related to the computer records of the purchases of the girl in the story. The article ends with an apology:

Quote:
On the phone, though, the father was somewhat abashed. "I had a talk with my daughter," he said. "It turns out there's been some activities in my house I haven't been completely aware of. She's due in August. I owe you an apology."
Can we please stick to the facts of "cookies" and "caches" which you advised people to clear "for their own good".

Neither of the scenarios you posted are relevant to that. I am sorry to inform!!

On the other hand, even if the girl in the "real story" above cleared her cookies and cache, she would have still got the coupons because she was targeted (marketing) because of her purchase history with the company in their database, not because of "cookies" or "caches" in browsers.
 
App::Cache(3pm) 					User Contributed Perl Documentation					   App::Cache(3pm)

NAME
App::Cache - Easy application-level caching SYNOPSIS
# in your class: my $cache = App::Cache->new({ ttl => 60*60 }); $cache->delete('test'); my $data = $cache->get('test'); my $code = $cache->get_code("code", sub { $self->calculate() }); my $html = $cache->get_url("http://www.google.com/"); $cache->set('test', 'one'); $cache->set('test', { foo => 'bar' }); my $scratch = $cache->scratch; $cache->clear; DESCRIPTION
The App::Cache module lets an application cache data locally. There are a few times an application would need to cache data: when it is retrieving information from the network or when it has to complete a large calculation. For example, the Parse::BACKPAN::Packages module downloads a file off the net and parses it, creating a data structure. Only then can it actually provide any useful information for the programmer. Parse::BACKPAN::Packages uses App::Cache to cache both the file download and data structures, providing much faster use when the data is cached. This module stores data in the home directory of the user, in a dot directory. For example, the Parse::BACKPAN::Packages cache is actually stored underneath "~/.parse_backpan_packages/cache/". This is so that permisssions are not a problem - it is a per-user, per-application cache. METHODS
new The constructor creates an App::Cache object. It takes three optional parameters: o ttl contains the number of seconds in which a cache entry expires. The default is 30 minutes. my $cache = App::Cache->new({ ttl => 30*60 }); o application sets the application name. If you are calling new() from a class, the application is automagically set to the calling class, so you should rarely need to pass it in: my $cache = App::Cache->new({ application => 'Your::Module' }); o directory sets the directory to be used for the cache. Normally this is just set for you and will be based on the application name and be created in the users home directory. Sometimes for testing, it can be useful to set this. my $cache = App::Cache->new({ directory => '/tmp/your/cache/dir' }); o enabled can be set to 0 for testing, in which case you will always get cache misses: my $cache = App::Cache->new({ enabled => 0 }); clear Clears the cache: $cache->clear; delete Deletes an entry in the cache: $cache->delete('test'); get Gets an entry from the cache. Returns undef if the entry does not exist or if it has expired: my $data = $cache->get('test'); get_code This is a convenience method. Gets an entry from the cache, but if the entry does not exist, set the entry to the value of the code reference passed: my $code = $cache->get_code("code", sub { $self->calculate() }); get_url This is a convenience method. Gets the content of a URL from the cache, but if the entry does not exist, set the entry to the content of the URL passed: my $html = $cache->get_url("http://www.google.com/"); scratch Returns a directory in the cache that the application may use for scratch files: my $scratch = $cache->scratch; set Set an entry in the cache. Note that an entry value may be an arbitrary Perl data structure: $cache->set('test', 'one'); $cache->set('test', { foo => 'bar' }); directory Returns the full path to the cache directory. Primarily useful for when you are writing tests that use App::Cache and want to clean up after yourself. If you are doing that you may want to explicitly set the 'application' constructor parameter to avoid later cleaning up a cache dir that was already in use. my $dir = $cache->directory; AUTHOR
Leon Brocard <acme@astray.com> COPYRIGHT
Copyright (C) 2005-7, Leon Brocard LICENSE
This module is free software; you can redistribute it or modify it under the same terms as Perl itself. perl v5.12.3 2009-12-08 App::Cache(3pm)
All times are GMT -4. The time now is 02:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy