Wikipedia_talk:Rollback
Wikipedia talk:Rollback
Wikipedia Help Project‑class Mid‑importance | ||||||||||
|
| |||
February 2015 RfC on granting of the Rollback permission (Archive A) |
|||
Sections older than 1 year may be automatically archived by lowercase sigmabot III. |
I read the project page and I still don't understand, how exactly Twinkle's rollback & restore version is any less powerful than Rollback. I came here to request this right, but I'm not even sure if I really get anything I can't already do. It's so easy and convenient to be able to leave custom summaries, or be able to choose one specific revision to restore rather than the tool choosing a revision itself, which may itself be problematic. ---CX Zoom(he/him) (let's talk|contribs) 16:36, 3 April 2022 (UTC)
- Your mileage may vary. I use both, as well as popups and manual reverting sometimes, but I use rollback by far the most. Rollback is quicker, more efficient, and more reliable, as everything is done on the servers, whereas Twinkle relies on JavaScript in your browser. I'm not sure, but I guess Twinkle might involve fetching the old content, then re-uploading it? From the client point of view, rollback involves a simple HTTP request. Rollback can sometimes work better when the revert is dispatched to a background tab, if browser tabs need to have focus to run JS effectively. Rollback also doesn't add pages to your watchlist, if that's a setting you have enabled. It doesn't, by default, have all the things you like about Twinkle, but it gets the job done most efficiently when applied correctly. -- zzuuzz (talk) 17:25, 3 April 2022 (UTC)
- In terms of functionality, the Twinkle rollback button is effectively identical to the software rollback. The software rollback may be slightly faster because of the reasons zzuuzz mentioned, but for everyday purposes, the Twinkle rollback button can stand in the place of the software rollback almost completely. In my view, the primary reason we continue to gate rollback behind WP:PERM is because certain fast-reversion software like Huggle require the rollback permission, and we want to check whether editors are ready to use such software before they begin using it. Mz7 (talk) 20:17, 24 April 2022 (UTC)
- Without having seen this thread, I recently made some changes to the page that include details on the differences between Twinkle rollback and true rollback. I will say, re Mz7, I've had rollback for 9+1⁄2 years, have never touched Huggle, and would still hate to ever part with the permission. The speed increase does add up—when I have to use Twinkle rollback on other wikis it rather frustrates me—but most importantly the ability to do mass rollbacks really is a huge time-saver when dealing with fast vandals or cleaning up after sockpuppets. -- Tamzin[cetacean needed] (she/they) 20:22, 24 April 2022 (UTC)
- Right, my point was more that, if it weren't for the Huggle/fast-reversion angle to the permission, there isn't that big a reason in my mind to simply make the rollback permission available to all autoconfirmed users, just as Twinkle rollback is. Mz7 (talk) 21:13, 24 April 2022 (UTC)
- @Mz7: Hmm. When combined with the right scripts, like User:Writ Keeper/Scripts/massRollback.js, it has a decent attack potential. Some wikis do hand rollback out automatically, but usually it's more like extendedconfirmed here. dewiki, for instance, does it at 60 days + 300 mainspace edits. But I mean, I take your point. If you ask me, though, we should be moving in the opposite direction. We have too many non-rollbacker recent change patrollers using Twinkle rollback to revert every IP they see; I'd rather we made it that to use any pseudo-rollback tool you need to be a rollbacker. -- Tamzin[cetacean needed] (she/they) 21:35, 24 April 2022 (UTC)
- Right, my point was more that, if it weren't for the Huggle/fast-reversion angle to the permission, there isn't that big a reason in my mind to simply make the rollback permission available to all autoconfirmed users, just as Twinkle rollback is. Mz7 (talk) 21:13, 24 April 2022 (UTC)
- Without having seen this thread, I recently made some changes to the page that include details on the differences between Twinkle rollback and true rollback. I will say, re Mz7, I've had rollback for 9+1⁄2 years, have never touched Huggle, and would still hate to ever part with the permission. The speed increase does add up—when I have to use Twinkle rollback on other wikis it rather frustrates me—but most importantly the ability to do mass rollbacks really is a huge time-saver when dealing with fast vandals or cleaning up after sockpuppets. -- Tamzin[cetacean needed] (she/they) 20:22, 24 April 2022 (UTC)
I was wondering, to have the rollback right, is it a requirement to be acting against vandalism or can I have the right only to have the extra functionality? Thinker78 (talk) 03:22, 22 August 2022 (UTC)
- In general, anything at Wikipedia needs a reason to occur. Attempting to gain rights with no particular reason related to improving the encyclopedia is disparagingly referred to as WP:HATCOLLECTING. Johnuniq (talk) 03:39, 22 August 2022 (UTC)
- I understand (not that I agree with the essay's premise very much, getting higher responsibilities is a general source of pride everywhere in society). But would it be a proper reason to just have the extra functionality of rollback rights? My main focus is not vandalism, but I do patrol daily my 700 pages watchlist. Therefore I revert vandalism when I see it. It is like someone who is not a mechanic but has a set of tools in case they are needed. Thinker78 (talk) 15:44, 22 August 2022 (UTC)
what are the differences between them and why use one above a another? Soulware2 (talk) 18:40, 10 February 2023 (UTC)
- My understanding is that, in a nutshell, reverting applies to undoing a single edit, while rollback is a way of undoing multiple consecutive edits. So, rollback is basically a bunch of reverts as a single action. Hope this helps! DonIago (talk) 19:03, 10 February 2023 (UTC)
- Maybe see Help:Reverting. Rollback is a subset of revert. It's suitable for situations involving single-user vandalism, where no explanation of the edit is required in the edit summary, and in circumstances where speed and efficiency may also play a role. The cons of rollback are the inability to use a custom edit summary (in fact being stuck with an edit summary which includes the vandal's username) and an inability to choose exactly which edits to revert. Manual reverting is almost the opposite. It probably gives the most flexibility to choose revisions, adjust content and provide explanations, and is an essential skill, though some user scripts such as Twinkle come close in terms of potential flexibility. Personally I use WP:POPUPS in addition to all the aforementioned tools, each in different circumstances. -- zzuuzz (talk) 19:13, 10 February 2023 (UTC)
Instead of having to explain that what Twinkle's "rollback" and "rollback (AGF)" isn't rollback (this confusion played a role in a WP:ANI issue in the past week), why don't we just change the Twinkle links to read "revert" and "revert (AGF)"?
When I was given the rollbacker role, I didn't even understand what had changed because I'd been seeing "rollback" links all along and didn't notice the new one right away. When I did notice it, I didnt realize it was new, I thought I was just first noticing it, and got confused over the multiplicity of these like-looking links.
So let's fix this.
Bonus: Having edited Twinkle code before, I volunteer to make the change if there's a consensus for it. Largoplazo (talk) 13:34, 23 December 2023 (UTC)