Last modified: 2008-05-14 18:22:04 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 T16106, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14106 - RC-Team requests feed for desighting
RC-Team requests feed for desighting
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
http://de.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-13 06:40 UTC by P. Birken
Modified: 2008-05-14 18:22 UTC (History)
1 user (show)

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


Attachments

Description P. Birken 2008-05-13 06:40:25 UTC
We now had the first case of someone removing a flag to make anothers version invisible and the recent changes team has requested that this is sent to the usual IRC-Feed, so that they can monitor this easily.
Comment 1 Aaron Schulz 2008-05-13 16:53:56 UTC
Is this really necessary? There are already 8 special pages for this. Can't this be monitored like other edits?
Comment 2 mnh 2008-05-13 19:27:26 UTC
Special pages must be polled, and you can't even fetch their
contents via API, as no support has been implemented yet.  
Only chance to integrate "unreview" events into any kind of
software tool (like the Vandalfighter) is to directly parse
the entire HTML-pages and diff the results yourself.  Can be
done, but it's not a particularly satisfying solution.  Since
most tools already rely on the IRC feed anyway, it seems a 
logical choice to simply push those few messages along with
the rest of the recent changes.

As for checking the special pages manually: there currently
are somewhere around 800-1000 absolutely boring "review" log
entries per hour, with just a handful of interesting "unreview"
cases per _day_ in between.  There's no way to filter the log
either (which would be another solution to the problem. Still
isn't optimized for tools, though).

So unless there's a special page I'm not yet aware of:
Yes, it is necessary.

Regards, mnh
Comment 3 Aaron Schulz 2008-05-13 22:25:24 UTC
(In reply to comment #1)
> Is this really necessary? There are already 8 special pages for this. Can't
> this be monitored like other edits?
> 

I mean 8 for the extension as a whole. Which is pretty high. I suppose I could try and whip up another page like QualityOversight.
Comment 4 Aaron Schulz 2008-05-14 18:22:04 UTC
Done in r34822

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


Navigation
Links