Jump to content

Wikipedia talk:How to revert a page to an earlier version

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

I tried reverting and I did *not* get a warning. By design? Sebastian 04:38 Jan 25, 2003 (UTC)

You do get a warning, it's just not very obvious in my opinion. I have suggested before that you get a pop-up box warning, but it's wasn't thought a good idea, by various people. Mintguy
count my vote on your side. Sebastian 04:55 Jan 25, 2003 (UTC)

ATTENTION!!! Content has been moved from this page. Please see the following pages for extremely important but long, drawn-out discusson, votes and polls which are still in progress.


Why not automate page protection?

[edit]

As proposed in meta:Edit wars: Why not automatically page protect an article for 48 hours when it has been reverted to the same version three times?

  • Not practical. It'd be easily circumvented by trivial edits instead of reversions.
  • Eminently practical, like a forcing draw in a game of chess. Nonsop reversions would trigger it without sysop intervention; it would maintain the status quo; sysops could either cancel the protection or make it permanent. It would protect the edit history and force a cooldown period.
    • Page protection in general is bad. If you want a technical solution for edit histories, make them easy to delete redundant entries, and we don't need it.
  • This would unquestionably be abused: in chess, people force draws when they're losing. It would increase, not decrease, sysop workload.

Hastiness in reverting

[edit]

Don't be hasty to revert. You can always revert later.

  • But we don't want blatant POV to remain for any length of time!
    • Who is "we"? Some articles have had POV for years anyway. If you're not hasty, the benefit: Second thoughts may be more valuable than the first.
  • This is difficult. They are too hasty sometime. But then some edits are just bad, and we don't need them in public view. Maybe we should have a sandbox mode- allow a page to be edited, but the edits would not show up until some time passed or someone used the Publish button.
    • Why not have a voluntary one-hour wait on reversions of edits that are being debated; wait for a response on the talk page before you revert.
      • But people often don't do that and are unwilling to discuss. This means a bad page (inaccurate, misleading) is visible longer. Most initial reversions are just antivandalism.
      • Simpler idea. Why not just have a 2-3 minute "cool off" period following a revert? Also, this idea has no chance of being implemented.
      • Why not just use the talk page?
        • The talk page isn't as "tactile", and it helps to be able to see context better, with actual article text.
          • Yes, but you can always copy article content or add a subpage.
  • Repeated reversion is pointless. But this guideline might confuse new users, if they even know about it.
  • The reverts aren't the problem, it's the lack of discussion. All reverts should be justified and all reverters should be ready to discuss.
  • (Newbie Opinion) If it's clear that an edit war is underway, why not just acknowledge the dispute within the article until it is resolved (e.g. with a discreet talk-page link at the appropriate place noting that the statement is currently under dispute)? Then someone can fix it later once the war has cooled off and discussion has taken place. Meanwhile, newcomers to the article won't be misled by bad edits/POV. --68.85.27.88 04:01, 16 Mar 2004 (UTC)

The protection option

[edit]

On the "vile mailing list", there's been some talk of making the so-called three revert rule an enforceable rule. I can see two obvious routes to enforcement, each with advantages:

  1. Temp-ban option: Sysops may apply a 24 hour temporary ban on those who revert the same page more than three times in the same day.
  2. Protection option: Sysops, in choosing to protect pages, may choose to protect the version whose supporters have (individually) not violated the three revert rule. So, if Martin reverts 4 times, and 5 people revert once - the version the 5 people want, and that Martin doesn't want, gets protected.

I'm leaning towards the protection option, personally. What do folks think? Martin 23:17, 8 Mar 2004 (UTC)

I personally like the protection option. Sysops should use a light touch, and that option encourages it. It also allows users to edit other articles (which in some cases may be a bad thing, but I think it's mostly good) →Raul654 23:25, Mar 8, 2004 (UTC)

I'm more inclined to ban anyone who accumulates six reverts of things which are not simple vandalism in one day for 24 hours. That indicates a pattern of reverting which is unlikely to be in a single article and suggests that protection is getting in the way of legitimate contributors. We know that there are comparatively few contributors who habitually choose revert wars rather than discussion and consensus seeking. Better to try to act against those not choosing to act within the community than to protect every page those people choose to fight over. If someone accumulates seven bans for this reason within some moderately short period, that suggests to me that it's arbitration committe time. Jamesday 23:28, 8 Mar 2004 (UTC)

Banning is the better option in the case of continued reverts as it affects only the person doing the reverting, rather everyone else who wants to edit the page, which is the effect protection has. Angela. 00:57, Mar 9, 2004 (UTC)
Pages with prolonged edit wars tend to get protected anyway, so I'm just proposing we use that as leverage.
The complaints over "meta:The Wrong Version" indicate that people who often succumb to revert wars may be particularly susceptible to this form of stick - if they did not mind it, they would not squeal so. Martin 21:42, 9 Mar 2004 (UTC)

I'm liking the protection option. -- Cyan 22:02, 9 Mar 2004 (UTC)

Temp ban is much better. Page protection hurts everyone. But temp bans are a bad idea too. If a logged in user continually adds various different non-obvious vandalism (but trolling nonetheless), many people would quickly run out of their reverts for the day. Anthony 06:22, 10 Mar 2004 (UTC)

Protection is, of course in my personal view, better for the wikipedia community. Protection encourages discussion, banning disencourages. It's good if the protecting sysop follow the principle of reverting to a page whose supporters are less aggressive, but maybe such a rule ought not be written in stone. There must be space for the sysop to make a sensitive choise - and also for doing mistakes without being heavily criticized.--Ruhrjung 11:46, 10 Mar 2004 (UTC)

Why not combine the two options? Martin's protection option on a per article basis and then have a three-strike rule for users: If a user gets more than three articles protected (the user violates the 3-revert rule) in some time period, then the user gets a 24 hour time out. --mav

What objective evidence do you have that people who revert are the problem? What if the problem is POV writers that need reverting? It makes just as much sense - that is to say little - to tempban people who have more than 3 edits reverted, than the other way around. Stirling Newberry 17:51, 28 Jun 2004 (UTC)

Hmmm. So what happens to the page protections at this point? Are they lifted as soon as the user is banned, or do they stay protected for longer than the user is banned? Of course this could get complicated... picture three users engaging in revert wars for no good reason, the people this rule would be aimed at. What happens when reverter A gets three articles protected and gets a 24 time out. On two of these pages reverter B was the only other involved, and on the other reverter C was involved. A gets a ban, B and C don't, so if the page protection is lifted at the start of A's ban, B and C can revert back to their POV. fabiform | talk 22:06, 13 Mar 2004 (UTC)
We unprotect when protection is no longer necessary, which I expect would still work. Martin 17:16, 14 Mar 2004 (UTC)

I'm liking mav's idea. Given Jimbo's support, I've edited wikipedia:protection policy. We can add 24hr temp-bans to that, if folks support it (I'm personally abstaining for now). Martin 17:16, 14 Mar 2004 (UTC)

For the record, Anthony DiPierro (as of now) believes that this is not policy. That's something of a meta-issue: the more relevant question for Anthony is - why does he oppose the policy (if indeed he does). Martin 01:08, 16 Mar 2004 (UTC)

Well, as I wrote above, page protection hurts everyone. Furthermore, the fact that one person is reverting slightly more than another means nothing as to the value of the reversion. And page protection lasts indefinitely. That's far too serious of a "punishment", especially when it relies on the judgement of a single sysop. Finally, and most importantly, reverts aren't necessarily a bad thing in the first place. Anthony
Excessive reverts are a bad thing, though. Kingturtle 01:20, 16 Mar 2004 (UTC)
Thanks for the insightful explanation. Anthony
Also, since this is optional, it allows sysops to get involved in forcing their views into Wikipedia. The rule that sysops were not supposed to edit protected pages was made for a reason, after all. Anthony 01:22, 16 Mar 2004 (UTC)

Well, page protection does hurt everyone, but the change to protection policy is for cases where we would be protecting anyway. It's not a change to when to protect, only what to protect. So I don't think that argument (while valid) is relevant to the recent change in protection policy.

Yes, the fact that one person is reverting slightly more (or very much more) is not necessarilly relevant to the value of the reversion, but the protection policy is about discouraging revert wars, not evaluating reversions, so I'm not seeing the link here.

Page protection lasts until unprotection, and since any sysop can unprotect at any time, it relies on the judgement of ~200 sysops, not just one. So I think this is just incorrect, unless I misunderstand you.

I understand that you believe that reversions aren't necessarilly a bad thing. The many people in the community who occasionally revert pages, including myself, agree with you. I'm guessing what you mean to say is that repeated reverts (four or more to the same page, on the same day, by the same person) aren't necessarilly a bad thing. Do I understand you correctly on this point? Martin 01:24, 16 Mar 2004 (UTC)

I would guess that this new twist to page protection is going to cause a lot more pages to be protected, as now sysops can force their viewpoints while protecting them. As for protection being able to be lifted at any time, that's still indefinite, and it generally lasts much longer than 24 hours. You understand me correctly. There's nothing wrong with reversions, so obviously there's nothing wrong with 4 reversions. Anthony 01:36, 16 Mar 2004 (UTC)

So far it looks like people are reverting more, without discussion on the talk page, as they feel that as long as they outnumber the other side they have no need to compromise and attempt to reach consensus. It's too early to say for sure if that's what's going to happen, but that's my suspicion, and so far evidence is leaning that way. Anthony 04:52, 16 Mar 2004 (UTC)

One immediate practical effect is that it is going to cause a lot more escalation of user issues. Perhaps this is good, there are an awful lot of contributors who don't write NPOV. Before after a revert war, generally NPOV won out. Now with the restrictions and the rule favoring the numerically superior side, it is going to mean a lot more gets kicked upstairs for review. Good, bad ? I don' know. Stirling Newberry 17:48, 28 Jun 2004 (UTC)

Well, every policy gets to be modified in light of how it works in practice. Perhaps this will all be a huge mistake - if so, it can be reversed quickly and easily enough. That's one of the benefits of Wikipedia not having a written constitution and formal policy change procedure: we can be as flexible as we like. However, I don't think the handful of protected pages over the last three days is much evidence even of a correlation, let alone cause-and-effect, for either of our positions. We'll have to wait a little longer. Still, since you don't believe that more reverts are bad, it's unclear to me why you're opposing this policy on that basis. Martin 18:43, 16 Mar 2004 (UTC)
My point is, even if reverts are bad, this policy does nothing to stop them, and in fact encourages them. Worse yet, it promotes reversion without discussion, which I do agree is generally a bad thing. Anthony 19:06, 16 Mar 2004 (UTC)
Perhaps we should add something to the page to discourage reverting without discussion, and to encourage providing good edit summaries? Martin 21:31, 17 Mar 2004 (UTC)
I thought that was already in there. If not, yes, it should be, but it's not going to accomplish anything. Anthony 22:01, 31 Mar 2004 (UTC)

Take a look a Jerusalem for an example of this policy being used inconsistently. Anthony 12:01, 17 Mar 2004 (UTC)

Yes, there will be inconsistency, due to the "may" aspect of it, and that I haven't been running around like a wild monkey promoting my change. There are other examples, of course.
If my alternative of protecting a specific version catches on widely, then this issue will go away. If it doesn't, then maybe it should be rethought. As I think we agreed earlier, it's too early to tell. Martin 21:31, 17 Mar 2004 (UTC)
How will the issue go away? People are still not going to fairly apply it in all circumstances. Anthony 22:01, 31 Mar 2004 (UTC)
If it becomes standard practice, then I think people will, without really thinking about it much. Hard to predict the future, though. Martin 13:52, 24 Apr 2004 (UTC)

I'm currently involved in an edit war, so take my comments from the POV of someone who this potentially applies to. Reversion banning rules favor users with less invested - they "force a draw" by vandalizing or POVing. The sensible user reverts (Strike 1), the Povian reverts (Strike 1) and so on. Meaning the vandal has a first mover advantage. He reverts twice without cost, and the sensible user is faced with a 24 hour ban, or allowing the POV version to stand for some period, at which point the cycle repeats and the POV version stands, again. And so on. Any policy should look at the history of the page and the users to determine what should be done. Page protection for "cooling off" is much better, and allows time for the other mechanisms to run their course. Stirling Newberry 15:36, 27 Jun 2004 (UTC)

Actual vandals can be blocked. See wikipedia:dealing with vandalism.
Regards POVing - if it's really bad, someone else will notice it, and revert it. Then the POV editor loses their "first mover advantage" and is at a numerical disadvantage. You're not alone in the fight for balance! :) 00:46, 28 Jun 2004 (UTC)
That's not the case in my little corner of wiki. As noted above the conditions that prevail in a large actively editted page - where page protection hurts many people, and one can assume there is someone else who will revert POV edits - do not prevail on pages with fewer editors. The rules as proposed are not fair to those of us in smaller conflicts. Stirling Newberry 02:03, 28 Jun 2004 (UTC)

Draft pages proposed for resolving disputed articles

[edit]

My advice would be when a page gets protected, a draft page would be created where the editorial wrangling can continue. Discussion could continue on the talk page and people could edit war till the cows come home on the draft page, but the main article wouldn't get unlocked until somebody reached an agreement. And the page would best be locked in a most recent stable condition, not the most recent condition represented after somebody or somebodies started making uncollaborative changes.

How would we go about doing this cleanly? A Draft: namespace, perhaps? - Fennec

Failure to participate the editorial process on a draft page would result in the page going front without that parties interests included. This would put both parties in a dispute in the position where neither could go forward without winning consent from the other side, and would provide a more workable format in which to work out comprimise.

This site is all about making up rules it can never enforce, based on an assumption that disputes are immutable conflicts, often involving bad people, rather than a result of people with conflicting views being invited to create the same article. - User:172.198.46.33


Getting Lost on this Discussion Page

[edit]

Is anyone else finding it almost impossible to work out where the new comments are being added to this page? Does anyone care to volunteer to archive and refactor so that it's easier to follow the debate? I got lost about three days ago. And unsigned comments don't help. Tannin 10:24, 12 Mar 2004 (UTC)

I tried a little, refactoring a section and adding more headings. The table of contents is my friend. :) Fennec 14:37, 12 Mar 2004 (UTC)
Thankyou! I'm off to bed (it's nearly 2AM here) but I shall look forward to seeing the results of your labour in the morning. Tannin
There... that should help. Our biggest problem is that this page isn't one discussion, but at least eight or ten. Fennec 20:22, 12 Mar 2004 (UTC)

What is a day?

[edit]

Does the 3-revert limit apply based on a 24-hour period, a UTC day, or some other meaning of day? Current practice has been to use a 24-hour period (see User talk:Wik#Arbitration committee ruling). This also makes the most sense, since otherwise people could get in up to 6 reverts in an hour or so and claim not to have violated this rule/guideline. --Michael Snow 21:52, 31 Mar 2004 (UTC)

I only cited a single instance, because it's the most clearcut example, but the current practice extends to far more than just one person. For example, the quickpoll for Lord Kenneth is based on 4 reverts in a 24-hour period, but only 2 in any one UTC day, yet it currently has five voters in favor (while you commendably stick to your principles in your opposing vote).

To the extent that quickpolls make this a rule, we need to provide a clear definition of the time period involved (there is no "just that" meaning of day, as your own uncertainty demonstrates). I believe that is best accomplished by using a 24-hour window. We shouldn't have to rely on the user's time zone, because the information is difficult to prove and not readily available. And using a UTC day would provide an unfair advantage to users who, due to their location or personal schedule, frequently edit from, say, 23:00 - 01:00 UTC (gee, look what time it almost is now). --Michael Snow 22:28, 31 Mar 2004 (UTC)

Well, we probably disagree on how closely it approaches consensus. But obviously we need more opinions here, so maybe we should advertise the discussion a little more.

I don't understand what reverting first or last has to do with it, that's not the issue as I see it. People have to accept that the last revert before protection will probably be the wrong version. My point about the advantage is that if someone edits during the window I suggested (whether the day is UTC or any other time zone), they can revert at 23:25, 23:40, 23:50, 00:05, 00:10, and 00:20 without ever violating the rule. Six reverts in less than an hour - that's a classic instance of "gaming" the rule, which using a 24-hour window prevents. --Michael Snow 22:55, 31 Mar 2004 (UTC)

Is there any reason for it not to apply to a 24-hour period? It saves having to work out timezones, and as this is what the arbitration committee have already applied to Wik, it seems sensible to continue that. Angela. 21:34, Apr 1, 2004 (UTC)

It's not harder to figure out, because if we leave "day" up to people's individual definitions, then it will be utterly impossible to figure out what a day is. And I have no problem "penalizing" somebody who reverts at noon one day and 11 am the next. People who revert frequently in a short period should recognize that they're on thin ice, and edit accordingly. The rule is supposed encourage discussion instead of reverting. --Michael Snow 23:10, 1 Apr 2004 (UTC)

Being able to identify violations is important both for the person doing the reverting, and for other people, as long as any kind of sanction is attached to the guideline, such as quickpolls. Team-reverting is a separate issue, and anyway there is little benefit to it under the rule since once the "day" is over, you would just have to go back and fight the same war all over again. In my opinion, any limitation of reverting inherently encourages discussion. --Michael Snow 00:02, 2 Apr 2004 (UTC)

It is important for the person doing the reverting if that person wants to avoid having sanctions imposed. Martin's advice is an attempt to communicate the spirit of this rule to someone who seemed primarily interested in maximizing the "legal" use of reverts. Limiting reverting encourages discussion because when you exhaust the ability to revert, the only options left are to discuss the problem or walk away. --Michael Snow 00:38, 2 Apr 2004 (UTC)

Someone being banned is a kind of sanction. Protection is another tool to prevent reverting (by technical means for non-admins, and by community pressure for admins). Realizing that endless reversion is futile is a form of walking away. Without developing appropriate tools and policies to limit it, reverting can go on long enough to harm the community (this assumption, not "reverting forever", is what my argument is really about). And reverting is much easier than discussing, so there's an incentive to that as the path of least resistance. If we create disincentives to revert, they will necessarily encourage people to choose other options. --Michael Snow 03:32, 2 Apr 2004 (UTC)

Given that you have already stated your opposition to this guideline, Anthony, it seems obvious that you will also oppose anything that makes it a "tighter" rule. I think we can take that for granted. I'm more interested in knowing if anyone who supports the guideline has a problem with day = any 24 hour period. Martin 23:24, 1 Apr 2004 (UTC)

I'm not opposed to this guideline. In fact, I voted in favor of it. anthony 23:41, 1 Apr 2004 (UTC)

Oh, my apologies Anthony: I saw you'd voted for it being pointless, and didn't realise you'd voted in favour of it despite that. Martin 23:50, 1 Apr 2004 (UTC)

More specifically, I voted that I "think its [sic] pointless to declare an 'end to revert wars' without advocating another means of solving disputes". I don't think the guideline itself is pointless. I think presenting it as a strict rule without having some other way to determine what page to display is pointless. In fact, considering that a strict rule would essentially enforce plurality rule (most people=most reverts), it's perhaps even worse than pointless. anthony 00:00, 2 Apr 2004 (UTC)

Hmm, it only amounts to a plurality for a single day (and even there, it's weighted by motivation). Over the longer term, it reduces to multi-party iterated prisoner's dilemma - not fantastic, but not terrible either.

Anyway, thanks for clarifying for me. Martin 17:30, 2 Apr 2004 (UTC)

(I don't see how it's redundant. It could mean as determined by the reverter.)

Well, if there are less that 24 hours seperating four reverts, there are less than 24 hours seperating four reverts. That's not going to change depending on who is "determining" things. Hence, any 24hr period. Perhaps that's unclear? Martin 21:58, 2 Apr 2004 (UTC)

Having it as 24 hours makes logical sense. Change the policy to "no more than three reverts in any 24 hour period" if the term "day" is the sticking point. --Ben Brockert 23:59, May 3, 2004 (UTC)

this page is still listed on Wikipedia:Requests for comment... anyway - I agree with Ben if that helps. Erich 04:52, 20 May 2004 (UTC) and Erich 06:43, 21 Jun 2004 (UTC)[reply]

Title

[edit]

Why does this (and so many other policy/civics articles) have a title that is uselessly long? Add to this target links... Wikipedia:How_to_revert_a_page_to_an_earlier_version#Revert_wars_considered_harmful_(the_three_revert_guideline) SeewhatImean? -SV(talk) 02:07, 5 Apr 2004 (UTC) PS. Quicklink - WP:3RR -Should be Wikipedia:Revert > Wikipedia:Reversion

Wikipedia:revert already redirects. Isn't that sufficient? Martin
No - the policy name should just be Reversion. All extra info is contained in the body. Apply this to other articles, and you will see some method to the madness. -Stevertigo 04:46, 10 Apr 2004 (UTC)

Rollbacks marked minor

[edit]

Could somebody please explain to me why a rollback by a custodian is marked minor by the software? I find that they are seldom minor edits. Thanks. moink 00:01, 27 Apr 2004 (UTC)

Seems an old feature. My guess is that it hails from WikiWiki / MeatballWiki / ... days, when normal approach was to revert vandalism with a MinorEdit. Could be wrong, though. Martin 21:33, 5 May 2004 (UTC)[reply]
Hmm. I disagree with having them marked minor. Does anyone else care? moink 00:05, 7 May 2004 (UTC)[reply]
I care, they should not be marked minor IMO theresa knott 08:18, 7 May 2004 (UTC)[reply]
I don't think this feature should be given to sysops but not other editors in the first place. anthony (see warning)


They should be marked minor. The rollback feature is only for vandalism. Why would you want vandalism reversion showing up on recent changes? Angela. 10:18, May 7, 2004 (UTC)
But other users have marked their reversions as minor using the rollback feature as an excuse. What's wrong with rollbacks showing up on RC? It alterts others to the fact that a vandal is about. theresa knott 10:24, 7 May 2004 (UTC)[reply]
People chosing not to view minor edits are not likely to want to know about vandalism. They'd be checking minor edits if they did. Also, if bot rollback is used, it won't show up even on the default recent changes, so you'd need to choose hidebots=0 if you really wanted to see all of the vandalism. Angela. 19:24, May 10, 2004 (UTC)
How about "reverts should only be marked minor in the case of vandalism, as defined at wikipedia:dealing with vandalism". The corrollary of that is that sysop rollback should only be used for vandalism. Martin 18:10, 11 May 2004 (UTC)[reply]
I have found that there are situations where it is appropriate that really don't quite rise to the level of vandalism, as with the recent matter involving User:Mike Church. He was edit warring over several different articles at once to defend links to his vanity page. I rolled back these changes, as did Brian Corr. Rationale was the same for all edits and was explained on his talk page by Brian and me (now at User_talk:Mike Church/archive2). He declined to respond other than by reinstating his edits. I don't think there is anything wrong with using a rollback in a situation like that, and I wouldn't want us to have to debate whether a particular rollback was applied to "vandalism" or just something that an admin didn't agree with. UninvitedCompany 23:46, 20 May 2004 (UTC)[reply]

coping with banned users

[edit]

When a banned user comes back with vengeance, on multiple IPs, it seems clear that people should ignore the 3-rv rule (and simultaneously work to block an aggressive vandal). There may be only ten interested parties online, and a vandal can easily blank a page thirty or fifty times in a day. Some people rv'ing vogelisms today apparently (iir[#irc]c) stopped after three per page, perhaps an unfortunate side effect of this guideline. I added two relevant sentences to section 4. +sj+ 19:45, 2004 May 10 (UTC)

There is no reason for a vandal to be able to blank a page 50 times in a day. Just protect the page! I see no need for an exception to the 3 revert rule here. Angela. 07:20, May 11, 2004 (UTC)
Like Angela, I'd say protecting pages and/or temp-blocking IPs should be simple enough, with current policy, so I don't see that an exception for banned users is necessary. It might also generate some strife in the case of suspected reincarnations (whether mistaken identity or otherwise). Martin 18:06, 11 May 2004 (UTC)[reply]

Removing page history entries

[edit]

A user asked me to roll back a page that had undergone several vandalism-reversion cycles, because the vandal had included rude remarks in the edit summaries. That is, he wanted the offensive edit summaries removed. I couldn't figure out how to do it. For the time being, I moved the page to an inconspicuous place, deleted the original page, then re-created it with the same contents. Advice welcome. Sorry if I missed something obvious. (The "rollback" function simply appears to be a convenient way to revert, and preserves all previous page history). Dpbsmith 22:28, 26 May 2004 (UTC)[reply]

Right now there is no way to remove the history. If the user was the only one to have edited the page (besides any vandalisms), that's fine, but if someone else had edited it, then the history should have been preserved instead of creating a new page with the old content. Dori | Talk 23:48, May 26, 2004 (UTC)
Only developers can remove edit summaries and the rollback does exactly the same as manually reverting a page, only with less clicks. Bot rollback will additionally hide the edits from recent changes, but not from the page history or from watchlists. Angela. 01:41, May 27, 2004 (UTC)
In my opinion, the inability to remove the histories is an advantage. You don't want people deleting histories, especially if they have vandalism. — [[User:33451|Mr. Grinch (Talk)]] 20:59, 2 Aug 2004 (UTC)

Reverts

[edit]

The way I understand things now, sysops can quickly rollback a page by clicking a link on the page history, whereas anyone—even anons—can achieve the same effect by editing an old version of the page. Is there any reason for this difference? It seems to me that if anyone can revert a page, there's no point in making non-sysops go through an extra couple of clicks and pageloads (which can be a real pain on a slow server day). Does the rollback link do something sysop-only that I'm not aware of? If not, can the rest of us have the link? Thanks for reading. -Etaoin 05:49, 27 May 2004 (UTC)[reply]

Simply put, because we don't want to make it easy for non-sysops to rollback the work of others. For anti-vandalism purposes, ordinary users should have it, but if it were too easy, "certain users" might abuse the feature. →Raul654 05:52, May 27, 2004 (UTC)
Makes sense, but isn't that possible anyway? The lack of a rollback link isn't going to stop someone from reverting other people's work. Tangling the user interface doesn't seem like the right way to solve the problem. Additionally, I like to believe that there are many more good Wikipedians out there than bad; is it not written, "Assume Good Faith"? -Etaoin 06:01, 27 May 2004 (UTC)[reply]
The "tangled user interface" is supposed to force the reverting parties into talking - at least by forcing each user to look at edit summary box. The rollback button bypasses that and thus discourages talk. That's probably as much as a reason as there is. Pete/Pcb21 (talk) 07:11, 27 May 2004 (UTC)[reply]
I think the idea of not making features like this too easy is a kind of soft security. Looking at MeatBall's article (MeatBall:SoftSecurity) I see this as an example of a PricklyHedge - although the name Speed Bumps has also been suggested. Basically, it being a fairly slow process (and yes, sometimes "a real pain") is likely to make people think before doing it, but admins/sysops have the power to bypass this if they have to do a whole bunch (i.e. for reverting a vandalism rampage). - IMSoP 18:58, 27 May 2004 (UTC)[reply]

Reverting process — too many steps?

[edit]

I've been going through recent changes (live) a little lately, and frequently have to revert vandalism. I find that there are too many steps involved:

  1. Check the diff.
  2. Go to the old version.
  3. Click "edit".
  4. Add summary and save.

If there were an "edit this version (for reversion purposes only!)" button in the diff-viewing page, it'd help:

  1. Check the diff.
  2. Click "edit".
  3. Add summary and save.

I propose that. (In fact, if there were a "revert to this version with summary ____" form on the diff page, it'd be even fewer steps:

  1. Check the diff.
  2. Add summary and revert.

— but I'm not proposaing that. I think it would be too easily abused and take up too much room on the page.) What think you all?msh210 14:11, 7 Apr 2005 (UTC)

Sysops can do that (using the rollback feature), but if we gave that ability to every user, it would make causing vandalism just as easy as reverting it. Also, could you imagine the edit wars ;) -Frazzydee| 00:33, 23 Apr 2005 (UTC)

Edit summaries when reverting tests

[edit]

I see that many users reverting newbie tests use the edit summary "rv vandalism". Is this the proper summary or should something "kinder", such as "rv testing" or just "rv" be used? After all, newbie tests are specifically listed under what Vandalism is not. With that said, RC-patrollers are making very valuable contributions! Sjakkalle 08:43, 29 Apr 2005 (UTC)

I think "rv vandalism" should be discouraged in the case of simple newbie tests: Wikipedia:Assume good faith. (It doesn't hurt to err on the charitable side at first if it is vandalism, since you can be sterner in the future; it does hurt to drive people away who were just testing by calling them vandals.) Mindspillage (spill yours?) 04:38, 7 Jun 2005 (UTC)
I see Reverted edits by User to the last edit of Author and the user will have a hyperlink to their contirbution. It seems easy enough but I havn't figured that out (somone reply with the text to do that with). It also dosn't give a POV link Mindspillage said. Supercoop 16:38, 3 October 2005 (UTC)[reply]

Edit conflict

[edit]

The article says Reverts never cause an edit conflict. And then goes on to say that they can. Or do I get something wrong? DirkvdM July 8, 2005 17:46 (UTC)

And another thing. I suppose that a revert only works for the last edit unless you're ok with reverting all the edits that follow it as well. That sounds obvious, but maybe it should be mentioned. I just experienced something like this in the Cuba article; I wanted to revert several edits except one (or two), so I just made notes of the ones I wanted to keep and then did those edits again. DirkvdM July 9, 2005 07:50 (UTC)

[edit]

Wikipedia:Administrators' how-to guide says that there's a rollback link on the article history page for admins. Well, I'm an admin, and I can't find one. There's one on the diff page, and on the user contributions page, but not on the history page. Having one at the history page would speed up revertions. JIP | Talk 16:35, 13 September 2005 (UTC)[reply]

Revert glitch?

[edit]

I've noticed one issue surrounding page reverts that I find annoying.

Several times, I've reverted obvious vandalism—but with an unexpected result. This has happened when I was reverting to a version that was credited to me. The article reverts to the last edit made by someone else other than me.

I can somewhat understand why this is, assuming it's Wikipedia policy... but it makes it VERY inconvenient to revert a page when I know I made the last helpful edit.

Any comments? – Dale Arnett 15:57, 26 September 2005 (UTC)[reply]

"Reverted Edits by User to last version by User2"

[edit]

How do I do such thing? I revert a lot of vandalism, but sometimes, I see people who use that line in their summary. How can I do this? Is this even possible to do automatically, or is it manual? Sorry, I'm still quite new to Wikipedia. Could someone maybe put it in my talk in case I don't get back to this page? Thanks -Tcwd (talk) 21:41, 13 October 2005 (UTC)[reply]

  • I wondered about that myself, so I'll answer it here. If you look at the Wikipedia:Revert article, it describes the rollback feature for admins, and how it automatically adds that to edit summaries. For those of us who aren't admins, we can manually add the whole rigamarole to our edit summaries, but it's not necessary. I tried it for awhile, but it was too much typing and I was too lazy to set up a macro. -Abe Dashiell 17:28, 19 October 2005 (UTC)[reply]

Revert trolls problem

[edit]

Increasingly, I see reverts not for any problem in the improvements I contributed, but with the given reason that my little essay explaining them insufficient to placate the reverter. The essay appears only in the History section. Our mission with Wikipedia is a world-beating encyclopedia, not a world-beating set of edit descriptions.

Part of the burgeoning problem may be a snippet that I saw somewhere in Wikipedia's instructions incautiously encouraging reverting changes as a way to get discussions started. This section should be clarified to indicate that the reasons for the revert should be stated in full -- i.e., giving the reasons why the original article text was deemed superior. What I'm seeing instead is demands to make the little essay explaining the changes (which are in any event self-explanatory) a better essay, without saying what was lacking with it in the first place (my little essays often take up much or all of the space allowed in the little "Edit summary" field as it is).

The proliferation of these "Revert Trolls" diminishes my enthusiasm for contributing to Wikipedia. An effective mechanism for identifying them and shutting them down or educating them about the inadvisability of failing to follow the reverting guidelines is needed.