Aryeh Gregor schrieb:
On Wed, Jun 17, 2009 at 5:39 AM, Daniel Kinzlerdaniel@brightbyte.de wrote:
As to disabling on Wikimedia projects: this would make things easier for the toolserver mainly. We don't need this info there, and having it might conceivably make WMDE the target of legal action. We can easily exclude cu_changes from replication, but we can't easily filter rc_ip from recentchanges. So it would be better if it wasn't there in the first place.
We could create a trigger to stop rc_ip from being populated, or maybe something fancy with inserting into views. Or even change rc_ip to a CHAR(0) or something so MySQL silently truncates the insert value.
Hehe, nice hack :) But tricky when new databases get added.
Naw, in the end, I want to get rid of the entries in recentchanges alltogether. One clean solution would to simply say that retroactive autoblocks become tied to checkuser functionality. But I suppose that, too, is a bit awkward.
-- daniel