https://bugzilla.wikimedia.org/show_bug.cgi?id=66450

--- Comment #32 from James Alexander <jalexan...@wikimedia.org> ---
(In reply to Ajraddatz from comment #31)
> The only person who has said this wouldn't be used unless integrated with
> existing workflows doesn't currently serve in a role which would make use of
> this. As I said in a post above, there would be no benefit to integrating it
> with CU - we'd be back to reactive, rather than proactive action since we'd
> only be able to find the IP if they successfully create an account.
> Integrating it with CU in addition to providing the IP would be beneficial.
>

I would question your statement that I would not make use of it as someone who
does quite a lot of log reading and checkusering in my job ;). 

That said there is no doubt it would be most useful to stewards and other
active global users which is why I was interested in their thoughts. If
they/you think it would be more actively used as a separate log that is a mark
in favor of having that separate log. My concern was mostly that relatively few
people would be actively using it and so having it in the CU tables would be
more beneficial (having it in the CU tables also allows it to take advantage of
the CU automatic self destruct). I agree it would be beneficial integrating it
with CU, and I can see some usefulness for the separate log if it would be
used.   

> To make perfectly clear the rationale for this: It gives us a unique
> opportunity to take proactive action while allowing us to confirm that we
> aren't generating ridiculous false positives using the TBL. It turns the TBL
> from an unusable extension to something which we can use alongside the
> abusefilter and spamblacklist to actively prevent abuse. With this, we could
> stop abuse before it has even happened - especially important when dealing
> with attack names. Is that a sufficiently-convincing rationale?

I think it is, to be clear (I know you didn't say this, but I think some did)
this current change is ONLY for accounts edits that trigger the TBL are not
logged. 

I am not yet completely convinced that there is sufficient need to display the
IP to non advanced users though (I would currently think CU/Steward) though I
don't have a real issue with the log itself (without IP) being shown to Sysops
or others who interact with the TBL/Abusefilter. My biggest worry is the
'ridiculous false positives' part, I can see a lot of cases where I'd be able
to piece together IP information on regular users in those cases (though I can
certainly see a high desire to want to KNOW when those cases are happening).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to