Last modified: 2014-11-18 18:07:21 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11181 - Mark bot edits in histories
Mark bot edits in histories
Status: NEW
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Low enhancement with 11 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: analytics, schema-change
: 11444 (view as bug list)
Depends on:
Blocks: 13516 14211 16228 17433 20783
  Show dependency treegraph
 
Reported: 2007-09-04 19:03 UTC by とある白い猫
Modified: 2014-11-18 18:07 UTC (History)
15 users (show)

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


Attachments

Description とある白い猫 2007-09-04 19:03:35 UTC
I think it would be better to tag bot edits with a 'b' by default just like how minor edits are marked with an 'm'.

I think this can be achieved with a schema change to the revision table.
Comment 1 Roan Kattouw 2007-09-04 19:17:10 UTC
This enhancement request really consists of two parts:

(In reply to comment #0)
> I think it would be better to tag bot edits with a 'b' by default
Part one: if the user is a bot, tag their edits as bot unless specifically requested is otherwise.

> just like how
> minor edits are marked with an 'm'.
Part two: make the 'b's show up in the page history.

> I think this can be achieved with a schema change to the revision table.

More specifically, a rev_bot field would have to be created, mirroring the rc_bot field that already exists in the recentchanges table.
Comment 2 とある白い猫 2007-09-06 23:07:34 UTC
Actualy while discussing this idea with pathoschild something interesting came about. Why not prod the issue a bit further. The code could add a "bot" (variable - so that it can be translated to the local language) to the bots name?

Current history line (from fr.wiki)

16:56, 2 September 2007 Ordinateur (Talk | contribs) m (43 bytes) (Robot : répare double redirection) (undo)

how it would be:

16:56, 2 September 2007 ([[link to what a wikipedia bot is|Robot]])Ordinateur (Talk | contribs) bm (43 bytes) (Robot : répare double redirection) (undo)
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-09-07 01:16:28 UTC
(In reply to comment #2)

That's unrelated.  Please create a separate bug requesting it.
Comment 4 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-09-07 02:32:56 UTC
Schema change committed in r25602 and r25604.  Once (and if) that's applied to Wikimedia sites, it should be simple enough to write the code to display it on history pages.
Comment 5 Platonides 2007-09-09 19:49:04 UTC
It was reverted in r25635.
As rev_minor_edit field is tinyint, it could be overloaded to also store the bot flag (treating it as a bitfield).
Comment 6 Roan Kattouw 2007-09-09 20:31:03 UTC
(In reply to comment #5)
> It was reverted in r25635.

Probably only temporarily though: schema changes can't just be added to the trunk at any given time.
Comment 7 Rob Church 2007-09-09 20:33:45 UTC
(In reply to comment #6)
> Probably only temporarily though: schema changes can't just be added to the
> trunk at any given time.

Not if we convert rev_minor_edit to a bitfield, which is what I'd have suggested. Although I'd also have suggested renaming the column to something accurate...
Comment 8 Roan Kattouw 2007-09-09 20:44:37 UTC
We could make rev_minor_edit a bitfield, but then it should be renamed to rev_flags or something similar.
Comment 9 Platonides 2007-09-09 21:18:31 UTC
I think MySQL was too inefficient on renaming fields (or is it only renaming tables?).
Comment 10 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-09-09 23:44:15 UTC
(In reply to comment #5)
> As rev_minor_edit field is tinyint, it could be overloaded to also store the
> bot flag (treating it as a bitfield).

Not if you want to be able to index it.  Although currently, we don't index it anyway, so it might well be fine.

Anyway, this would be a breaking change.  All code accessing rev_minor_edit would need to be updated, including third-party code.  It's not much less disruptive than a schema change.
Comment 11 Brion Vibber 2007-09-10 00:40:10 UTC
Do not repurpose existing boolean fields into bitfields, please.

Schema changes, if appropriate, will be made when we've got a clear opportunity to plan for them.
Comment 12 Roan Kattouw 2007-09-10 13:27:59 UTC
(In reply to comment #10)
> Anyway, this would be a breaking change.  All code accessing rev_minor_edit
> would need to be updated, including third-party code.  It's not much less
> disruptive than a schema change.
> 

Actually, adding a new rev_bot field would actually cause *less* trouble than the bitfield thing.
Comment 13 Brion Vibber 2007-09-24 21:11:04 UTC
*** Bug 11444 has been marked as a duplicate of this bug. ***
Comment 14 P.Copp 2009-02-10 11:28:32 UTC
Just a thought: Since we have now the change_tag table, couldn't it be used to tag bot edits (and maybe even minor ones) as well?
Comment 15 Happy-melon 2009-05-12 13:23:21 UTC
That would be something of a hack, and not really what it was designed for.  Are tags stored indefinitely? I'm not familiar enough with the feature to know that.
Comment 16 Happy-melon 2010-03-25 19:46:51 UTC
*** Bug 16228 has been marked as a duplicate of this bug. ***
Comment 17 Bryan Tong Minh 2010-11-27 18:36:28 UTC
But in fact both "minor" and "bot" are tag like entities as well. It is not unlogical to store both in change_tags.
Comment 18 wikiposta 2011-12-17 09:32:18 UTC
Some tasks need an analysis of the page history, and they are senseless without knowing which user is a bot. It is often necessary to separate bot edits from human ones.
Comment 19 Carl Fürstenberg 2013-02-16 21:18:26 UTC
Should we go through with this, or just scrap the whole idea?
Comment 20 とある白い猫 2013-02-17 04:15:15 UTC
There are a number of useful applications of such tagging. It is also useful to the user reviewing the edit itself. It also helps us catch people pretending to be bots when they aren't. I insist that going forward with the idea offers benefit.
Comment 21 Kunal Mehta (Legoktm) 2013-02-17 04:22:56 UTC
If this is done, bug 19322 should also be done, which adds the bot field to log entries.
Comment 22 wikiposta 2013-02-17 07:18:44 UTC
This is still very important, and many users wait for it being solved. I have a bot that analyses page histories and users want me to find the last human edit which I can't do now.
Comment 23 SpeedyGonsales 2013-02-18 12:46:18 UTC
This bug is with us from 2007. Every year which passes schema change becomes more expensive.

Maybe it is now time to made schema change?

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


Navigation
Links