Last modified: 2012-04-14 10:21:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20080, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18080 - Log filter hits and filter changes to Special:Log
Log filter hits and filter changes to Special:Log
Status: RESOLVED DUPLICATE of bug 19494
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-21 04:11 UTC by Mike.lifeguard
Modified: 2012-04-14 10:21 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mike.lifeguard 2009-03-21 04:11:07 UTC
I seem to recall a request to send filter changes to RC, but I can't find it. They should go to IRC too.

As well, please send hits (anything that goes to AbuseLog) to IRC so we can create real-time monitoring tools.
Comment 1 Andrew Garrett 2009-03-22 23:13:50 UTC
I think I already replied to this bug (or a related one).

Please tell me what info you need for each event, and what sort of format you suggest providing it in. I have a half-done patch in my working copy.
Comment 2 Mike.lifeguard 2009-03-23 00:00:55 UTC
(In reply to comment #1)
> I think I already replied to this bug (or a related one).
> 
> Please tell me what info you need for each event, and what sort of format you
> suggest providing it in. I have a half-done patch in my working copy.
> 

I doubt it'll make much difference to us what the format is. I'll CC Pathoschild since he's done lots of work on parsing RC feeds for CVNBot. The info we want is probably:

*New filters: Who created it, what actions it can take, the filter name & number, (I'd add the summary, but the notes field is too big to include, ugh)
*Editing filters: Who edited it, what actions they added/removed, the filter name & number
*Filter hits: Who hit it, the filter name & number, page name/log type for the action, what actions AF took -- so, if AF disallowed the edit, we want to see that it was an edit and that AF disallowed it. If the filter has a throttle, some indication of the throttle being incremented.

I'm not sure how AF's actions are logged right now - a pseudo-user? If so, actions like blocking or desysoping should go to normal RC (and here too). Actions that can't go to RC like removing autoconfirmed status should come here.

It will probably be useful to take a look at what info is being made available in #wikipedia-en-abuse-log (via screenscraping, ugh) since that's basically the information we want, AFAIK.
Comment 3 Mike.lifeguard 2009-03-23 02:25:13 UTC
If 'tag' is one of the options, that tag should be included in the filter hit message.
Comment 4 Gurch 2009-04-11 16:52:22 UTC
#wikipedia-en-abuse-log@Freenode doesn't show everything in the log, there seems to be a list of filters that don't show (it's presumably intended for humans to read) and is thus suboptimal for machine reading. Putting the filter log in with the other stuff in the Wikimedia IRC channels would be much more useful for that (and have the usual benefits of IRC feed versus spamming API requests).
Comment 5 Andrew Garrett 2009-07-16 17:04:29 UTC
(Batch change)

These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.
Comment 6 Krinkle 2012-02-22 18:10:27 UTC
Rephrasing bug to what it should be. I don't think it makes sense for AbuseFilter to explicitly send any such stuff to IRC directly. It should go through logging, which will automatically send it to irc as well.
Comment 7 Krinkle 2012-02-22 18:11:26 UTC
If they are logged to Special:Log, irc goes automatically. There's no way around it.

Marking dupe of bug 19494.

*** This bug has been marked as a duplicate of bug 19494 ***
Comment 8 Beau 2012-04-14 10:21:50 UTC
I have submitted a change https://gerrit.wikimedia.org/r/#q,Ie4bda2f97aa295c0504ba869ef1a99c7a3d20f70,n,z for review.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links