HTML pages shipped in the python-matplotlib-doc package contain
javascript that tries to report back tracking data to upstream via
sourceforge.net. I'm sure that such data is very valuable to upstream
in some way, but it poses two problems:
* When you have an intermittent or flakey network connection, loading
this tracking data must time out before you get to see the actual
documentation. Users shouldn't have to jump through hoops like turning
off javascript in their browser (which would also break the search
facility in the documentation).
* There is also a privacy issue here. I'm sure there will be a number
of Debian users who are unhappy that viewing local HTML files is being
tracked in this way.
The offending code is as follows (from
/usr/share/doc/python-matplotlib-doc/html/api/axes_api.html):
<!-- Piwik -->
<script type="text/javascript">
var pkBaseURL = (("https:" == document.location.protocol) ? "https://apps.sourceforge.net/piwik/matplotlib/"; : "http://apps.sourceforge.net/piwik/matplotlib/";);
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
</script><script type="text/javascript">
piwik_action_name = '';
piwik_idsite = 1;
piwik_url = pkBaseURL + "piwik.php";
piwik_log(piwik_action_name, piwik_idsite, piwik_url);
</script>
<object><noscript><p><img src="http://apps.sourceforge.net/piwik/matplotlib/piwik.php?idsite=1"; alt="piwik"/></p></noscript></object>
<!-- End Piwik Tag -->