---------- Forwarded message ----------
From: Adam Baso <abaso(a)wikimedia.org>
Date: Thu, May 1, 2014 at 7:52 PM
Subject: Re: [Wikimedia-l] Mobile Operator IP Drift Tracking and Remediation
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
After examining this, it looks like EventLogging is more suited to the
logging task than debug logging and the trappings of needing to alter debug
logging in the core MediaWiki software.
EventLogging logs at the resolution of a second (instead of a day), but has
inbuilt support for record removal after 90 days.
Please do let us know in case of further questions. Here's the logging
schema for those with an interest:
Here's the relevant server code:
On Wed, Apr 16, 2014 at 2:20 PM, Adam Baso <abaso(a)wikimedia.org> wrote:
> Great idea!
> Anyone on the list know if there's a way to make the debug log facilities
> do the YYYYMMDD timestamp instead of the longer one?
> If not, I suppose we could work to update the core MediaWiki code. 
> 1. For those with PHP skills or equivalent, I'm referring to
> Scroll to the bottom of the function definition to see the datetimestamp
> On Wed, Apr 16, 2014 at 12:47 PM, Andrew Gray <andrew.gray(a)dunelm.org.uk>wrote:
>> Hi Adam,
>> One thought: you don't really need the date/time data at any detailed
>> resolution, do you? If what you're wanting it for is to track major
>> changes ("last month it all switched to this IP") and to purge old
>> data ("delete anything older than 10 March"), you could simply log day
>> rather than datetime.
>> enwiki / 127.0.0.1 / 123.45 / 2014-04-16:1245.45
>> enwiki / 127.0.0.1 / 123.45 / 2014-04-16
>> - the latter gives you the data you need while making it a lot harder
>> to do any kind of close user-identification.
>> On 16 Apr 2014 19:17, "Adam Baso" <abaso(a)wikimedia.org> wrote:
>> > Inline.
>> > Thanks for starting this thread.
>> > >
>> > > Sorry if I've overlooked this, but who/what will have access to this
>> > data?
>> > > Only members of the mobile team? Local project CheckUsers? Wikimedia
>> > > Foundation-approved researchers? Wikimedia shell users? AbuseFilter
>> > > filters?
>> > >
>> > It's a good question. The thought is to put it in the customary
>> > location (with, for example, filename "mccmnc.log") on fluorine.
>> > It just occurred to me that the wiki name (e.g., "enwiki"), but not the
>> > full URL, gets logged additionally as part of the wfDebugLog call; to
>> > the implicit explicit, wfDebugLog adds a datetime stamp as well, and
>> > useful for purging old records. I'll forward this email to mobile-l and
>> > wikitech-l to underscore this.
>> > > And this may be a silly question, but is there a reasonable means of
>> > > approximating how identifying these two data points alone are? That
>> > > Using a mobile country code and exit IP address, is it possible to
>> > > identify a particular editor or reader? Or perhaps rephrased, is this
>> > data
>> > > considered anonymized?
>> > >
>> > Not a silly question. My approximation is these tuples (datetime, now
>> > it hit me - XYwiki, exit IP, and MCC-MNC) alone, although not perfectly
>> > anonymized, are low identifying (that is, indirect inferences on the
>> > in isolation are unlikely, but technically possible, through
>> examination of
>> > short tail outliers in a cluster analysis where such readers/editors
>> > in the short tail outliers sets), in contrast to regular web access logs
>> > (where direct inferences are easy).
>> > Thanks. I'll forward this along now.
>> > -Adam
>> > _______________________________________________
>> > Wikimedia-l mailing list
>> > Wikimedia-l(a)lists.wikimedia.org
>> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> > <mailto:firstname.lastname@example.org?subject=unsubscribe>
>> Wikimedia-l mailing list
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
The Mobile App team had their monthly retrospective today. Notes,
further discussion, and action items are below.
= Further discussion items =
* We should probably whittle Saved Pages down a bit. Me and dbrant
have started on patches. +++ [Yuvi]
* Communication / Interaction with Design (+)() [Maryana]
* Release timeline. Beginning of sprint we mentioned android to beta
at end of sprint and then no mention after ++ [Maryana]
* Not enough comments and discussion on the design trello board+++ [team]
Thanks team and all involved.