Re: [Commons-l] External click logging

2009-11-19 Thread Gnangarra
Reading the Privacy policy I dont see this would violate the policy as it specifically doesnt record private data(ip, username), in my reading of http://meta.wikimedia.org/wiki/Privacy_policy#Purpose_of_the_collection_of_private_informationthe policy specifically says *The Foundation limits the

Re: [Commons-l] Talking about Bert Roberts, Commons, and Wikipedia on ABC Radio in Queensland

2009-11-19 Thread John Vandenberg
On Sun, Nov 15, 2009 at 9:53 PM, Craig Franklin cr...@halo-17.net wrote: I’m not sure about the distributability of a recording, as I suspect that it won’t be under a free licence (I will have a recording).  I will try to get a transcript up somewhere. If you can obtain a CC/PD release from

Re: [Commons-l] External click logging

2009-11-19 Thread Andre Engels
On Thu, Nov 19, 2009 at 9:23 AM, Gnangarra gnanga...@gmail.com wrote: Reading the Privacy policy I dont see this would violate the policy as it specifically doesnt record private data(ip, username), in my reading of

Re: [Commons-l] External click logging

2009-11-19 Thread Andrew Gray
2009/11/19 Tim Starling tstarl...@wikimedia.org: Magnus Manske wrote: Hi all, as promised on the meeting, I wrote a small JavaScript/Toolserver setup that can log clicks on Commons leading to external pages. I believe this would be a violation of Wikimedia's privacy policy. If it contains

Re: [Commons-l] External click logging

2009-11-19 Thread Maarten Dammers
Hi everyone, Magnus Manske schreef: This will capture all external link clicks within the page content, tell the toolserver about it, and then load the intended page. Something else: Is the toolserver able to handle the load this will produce? Maybe make it part of http://stats.wikimedia.org/ ?

Re: [Commons-l] External click logging

2009-11-19 Thread Magnus Manske
On Thu, Nov 19, 2009 at 1:08 PM, Maarten Dammers maar...@mdammers.nl wrote: Hi everyone, Magnus Manske schreef: This will capture all external link clicks within the page content, tell the toolserver about it, and then load the intended page. Something else: Is the toolserver able to handle