[pydotorg-www] Analytics

Michael Foord mfoord at python.org
Sun Apr 25 22:22:26 CEST 2010


On 25/04/2010 21:19, Georg Brandl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 25.04.2010 22:06, schrieb "Martin v. Löwis":
>    
>>> At work I went to a recent talk on Google Analytics, which provides an
>>> impressive number of analyses to track where people are coming from,
>>> what queries they're using, how long they stay on average, etc.  But
>>> visitors are only recorded if their browser supports JavaScript, and
>>> dumping that information into Google raises privacy concerns.
>>>        
>> -1 on Google Analytics, for the privacy reasons. I don't believe you
>> need JavaScript in the browser for it to do tracking, but with
>> JavaScript, even more information gets collected.
>>
>> Here in Germany, it is the law that users have to opt in to have
>> personal data being collected, and IP addresses are considered personal
>> information. So strictly speaking, even a plain webserver log without
>> user consent is against the law (the one exception being operational
>> necessity). This isn't really being followed in practice, but we should
>> not give personal data to anybody else (aggregated data is fine).
>>      
> I also don't really see the need to put something in every python.org page
> when the webserver collects enough data just fine.  No matter how little, it
> will slow down the user's browser.  In any case, do we *really* need the
> "advanced" stats that Google Analytics is offering?  (Remember, we aren't
> trying to sell something.)  If Google collects more data than the webserver
> would, do we want to collect and deliver that?
>
> If server-side tools work just fine for our needs: even if they don't produce
> graphs as pretty as Google's, what does it matter?
>    

If we don't need it, and I have no axe to grind on that score, then 
fine. If implemented correctly in the source then it shouldn't slow down 
rendering of page contents at all - however what information about our 
visitors and how they use the site is probably something for the site 
plan to determine.

Whatever technology best meets our need should be used - ultimately to 
be determined by the PSF board. This decision certainly shouldn't be 
held hostage by individual opinions.

All the best,

Michael

> Georg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAkvUo7wACgkQN9GcIYhpnLDNJACeKZjlO9MmUOMBJkaSMukkFfzX
> WtAAoIFtRu1gVamxOII4zuA/vb6AWMiB
> =55GC
> -----END PGP SIGNATURE-----
> _______________________________________________
> pydotorg-www mailing list
> pydotorg-www at python.org
> http://mail.python.org/mailman/listinfo/pydotorg-www
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.




More information about the pydotorg-www mailing list