Bináris the root issue is that mediawiki doesnt see Null edits as an edit,
it sees them more as a purge with forcelinkupdate=True. The logs that
contain that information are not in mediawiki, but rather the webserver
logs. Exposing those logs is a privacy issue. Second if there are
performance issues the Ops staff have access to those logs and will use
them to troubleshoot. No one on wiki can do anything about Null Bots, nor
should it be something they worry about.

On Tue, Jul 25, 2017 at 8:58 AM, Bináris <[email protected]> wrote:

> 2017-07-25 14:35 GMT+02:00 Dan Garry <[email protected]>:
>
> > By definition, a null edit does not perform any change at all, and is
> > therefore not recorded publicly since there's technically nothing to
> > record. I suspect the only way you could find this kind of information is
> > in the server logs, and access to those is very tightly restricted for
> > privacy reasons.
> >
>
> I understand, but I think it would be worth to discuss this *therefore.*
> Nulledits are not subjects of privacy protection, they are now in protected
> logs only accidentally or for historical reasons. If there is an action
> noticed by the server (definitely there is, because it has an effect on the
> page, that's why people often do it), it may be logged in the way real
> edits are.
>
> This would be also be useful for researchers. One may be interested in the
> pattern of null edits, the quantity of them (e.g. is it useful to null edit
> 20.000 pages because of the change of a template, or is it actual to find
> some better way of making the changes visible?).
> If there is no reason to exclude these from logs (I don't see any), we
> should make them visible. Perhaps not by default, but with a switch.
> _______________________________________________
> Wikitech-l mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to