Please do not post any new comments on this page. This is a discussion archive first created in 2022, although the comments contained were likely posted before and after this date. See current discussion or the archives index.
Oh, misunderstood you. The requirement for rollback is to limit the abuse of tool because it offers very quick ways to remove edits and then warn. Without rollback anyone even trolls can abuse them. Also rollback isn't that hard userright, if you have it on any project you can use SWViewer there. ‐‐1997kB (talk) 03:00, 5 February 2022 (UTC)
[ADDITION, FEATURE]: Enable warning and edit summary differently
Latest comment: 2 years ago7 comments3 people in discussion
Type
Addition, feature
Setup
unknown
Please separate warning option and edit summary of rollback, As currently only if I enable warning then only I can use readymade rollback summaries, or the inverted like I want to use readymade rollback summaries then I need to use warning too. Seperating these two things would be more useful. I thought about it when a sysop on hiwiki got furious about the creation of IP talk pages because of used warning templates while reverting.(And they actually deleted such IP talkpages in bulk!!! as they think its useless to keep such IP talkpages with waring tags on it.Special:Diff/5272006) Though earlier I thought the dynamic or whatever IP tagged with warning templates would be useful.
+ Green color after enabling warning is to show that which quick summary support warn and it doesn't mean that they get enabled only after enabling warnings. ‐‐1997kB (talk) 03:07, 5 February 2022 (UTC)
Latest comment: 2 years ago3 comments2 people in discussion
Type
Bug
Setup
unknown
Hi, I am writing to report that SWViever is not working. It worked until this morning (my last actions with this program date back to 11:00 AM), but now, when I open the program, I see that it doesn't work (red exclamation point on discussions, warning indicating "disconnect from recent stream", queue naturally empty. I hope this can be corrected. Thanks
SWViewer is prompting to auto-report, rather than warning, one before the maximum warning count. For example, on enwiki where there are 4 levels of warnings, SWViewer does not warn if the user has already received a level-3 warning and instead prompts to auto-report (when it should do that with a level-4 warning instead.) I believe this comes from Line 551 of swv.js: var maxWarnCount = Number(SEdit.config.warn['countWarn']) - 1;, which subtracts 1 from countWarn for no immediate reason that I could see.
Actually, I'm struggling to figure out how the auto-report functionality works at all. It didn't warn and asked to report when the talk page of the user looked like this, even though it was able to add the level-1 warning the first time. I wonder if it is checking for a current month header and also a level-3 warning anywhere in the page, when in reality it should be looking for a level-4 warning under the current month header. If so, this functionality seems unintuitive and should be changed. Eviolite (talk) 13:52, 3 March 2022 (UTC)
Yeah, I find this really annoying actually. I would actually suggest disabling the auto report thing entirely until it can be made to work properly, as it currently seems to be more trouble than it is worth. Mako001 (talk) 10:40, 8 March 2022 (UTC)
Hrwiki has recently changed its deletion templates to enable automatic creation of discussion pages when somebody opposes a deletion. We have modified our deletion templates to use {{subst:brisati|reason}}. Please make the appropriate change where necessary. Thank you!
Just wanted to say this is an awesome tool! Years back User:Petrb & I talked about turning Huggle into a web app, and it looks SWViewer is just what we wanted to aim for!
Some {{delete}} templates require substitution (for instance, w:hr:Template:Brisati). SWV need a feature that allows specifying templates on what wiki should be subst'ed and recommend that to other users as well.
Latest comment: 1 year ago3 comments2 people in discussion
Type
Bug
Setup
unknown
Dear administrators of SWViever. I have been working with SWViewer rather frequently lately. I like it a lot. However, I notice that there are continuous problems with the recent changes, (recent stream) almost daily it needs to be reset by "an administrator" after a call. I think through that it is because it runs on Toolforge and that is not always stable, I understood. Can something be done about that? By the way: English is not my first language, in case I have put down something strange I hope you will still understand It. yours sincerely
Connection with recent stream is more of an issue of recent stream rather than SWViewer. We have tried best on our end to stablize the connection but it not in our hand when recent stream itself have issue and thats when the problem you mentioned happen. ‐‐1997kB (talk) 04:59, 4 May 2022 (UTC)
BTW there's no rule like that on Hindi Wiki. I myself is a hiwiki contributor and I frequently warn IPs which is a good thing to do before blocking them. ‐‐1997kB (talk) 11:36, 30 August 2022 (UTC)
Latest comment: 1 year ago12 comments3 people in discussion
Type
Feature
Setup
unknown
Give the ability to filter by the language or the script the Wikis are using. Even though sometimes is easy to see blatant vandalism in unknown scripts or languages, most of the time you'll have no idea what has happened if the change is in a script you cannot understand at all. If language filter may seem too restrictive, I believe a script filter would be overall beneficial.
@Iluvatar, maybe these should be proposed on a new thread but I'm going on here just because we already have context provided.
Currently when you add a new language to the filter you created or any other entry on the existing filters, you have no way of knowing if you added it correctly or not. The filters accept every value you provide for them, no matter if they work or not. I tried that out by adding random characters and they still accepted them. It would be good if you were told when the value you provided wasn't correct or made no sense (was unknown) from the SWViewer part.
Secondly, the presets part has always been a bit too underground, at least for me. I keep pressing either the button for queue settings or the other button for the general settings. The little up and down arrow beside the preset name, while elegant in looking, isn't that intuitive in usage. I'd advise for some changes in regard to that:
Make a general interface change to make it more understandable that you have other options in the preset name (like editing the default one or creating new ones).
When you double click on the preset's name, it opens it up for edit. Maybe when you right click on it, it can open it up for a quick rename.
[Important] Add a scroll bar when working with presets popups. 50% of its options don't appear for me in my laptop and if I accidently click outside of them, it closes the popup. Only option to scroll down is with the keyboard. Klein Muçi (talk) 11:32, 20 February 2022 (UTC)
About the second part, I happens to disagree. There is always going to be a learning curve when using a new software. But what it offers is that we have a less populated interface which also fits nicely when people use SWViewer on small screen devices, for eg mobile. And double click is unnecessary when we have a button to edit the used preset (the Queue setting button works individually for each preset). There’s no scroll bar because preset isn’t too long, but mouse scroll or double finger touchpad scroll works with it. ‐‐1997kB (talk) 06:28, 27 February 2022 (UTC)
@1997kB, thank you for providing opinions and for the tag!
I don't want to populate the interface either. I'm just thinking of a adding or changing certain minor elements. For example, if we want to keep the up and down arrow style, we can put an underline below the name preset to make it more understandable that it's something you've chosen and that you can change it (choose something else) if you so want. Or, a more heavy-addition, (which can go into the "populate the interface" territory): We can add the word "Preset:" in front of the preset, which only shows if you've already clicked the up arrow to "close" the stream.
As for the other 2 details... I believe double-clicking and right-clicking can be considered subjective ideas (even though I believe having multiple ways to accomplish something could be beneficial) but I would consider the scrollbar a cry for help. I don't have a mouse for my laptop and I've never, so far, used double-finger touchpad scrolls. I went to try it now that you mentioned it and after 5 failed tries, I gave up. I think I might have disabled that option ever since I've gotten the laptop. For the moment, I can only scroll down either by the keyboard or by selecting down all options in the popup and unselecting once the page has reached its bottom (a primal way to do it). I highly doubt adding scrollbars would cause any harm, interface wise or not. Klein Muçi (talk) 10:45, 27 February 2022 (UTC)
Hello! I noticed that if I click the button to disable the warnings and then re-enable them, either the vandalism or disruptive editing warnings won't work, and sometimes it's both. Logging out of SWViewer and then back in seems to fix the issue until you disable and re-enable the warnings again.
If we switch from a page to another one from the stream that page/edit is gone forever. It would be nice to be able to restore it into the edit screen somehow.
@1997kB, When I login, it shows -"Sorry, to use this application local or global rollback is required.
If you have rollback right and see that error, then report about it on talk page. Thanks!" ≈ Farhan «Talk»15:10, 24 December 2022 (UTC)
Latest comment: 4 days ago3 comments3 people in discussion
Hey, some of the Scowiki edit summaries are incorrect/Scotched. The Scots for "page" for example, is "page" rather than "paige", "Nae uiseful content" should be "Nae uissfu content", "Oot o projecht scope" should be "Oot o project scope" and "Baffle" should be "Haivers". I've asked a few other Scots editors to check in in case there's something I missed CiphriusKane (talk) 01:01, 11 November 2022 (UTC)
[ADDITION + FEATURE]: About warnings on eswiki and enwikiquote
Latest comment: 3 days ago3 comments3 people in discussion
Type
Addition + Feature
Setup
unknown
Addition: First of all, on enwikiquote there are some vandal warnings yet to be added: For Spam, Level 1 and Level 2 (Last). Promotional/Advertising Spam: Only warring. Vandalism: 1 (more like for test edits in general), Level 2 (vandalism in general), Level 3, Level 4, there's also another warning, but it should be used only by admins, Lvl 5. Please add them, they're necessary. Also: vandals who passed the 4th or only warning, should be reported on q:Wikiquote:Vandalism in progress, with the following syntax, for IP addresses: * {{IPvandal|INSERT IP ADDRESS}}<br> Vandalism after the last or only warning. ~~~~ and * {{Vandal|INSERT USER}}<br>Vandalism after the last or only warning. ~~~~ for accounts. The header or thread text should read: New report {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}, {{CURRENTTIME}}
Feature: On the other hand, I noticed that there's a problem with the speed deletion warnings in Spanish Wikipedia. SWViewer is using speedy deletions warnings from Huggle, which are now outdated and we now use the following syntax: {{subst:Aviso destruir|PAGE NAME HERE|REASON HERE}} ~~~~. The other speedy deletion criteria can be found in es:WP:CBR.
Done. 1 Iluvatar (talk) 16:31, 20 June 2022 (UTC)
Fixed. Iluvatar (talk) 15:30, 31 August 2022 (UTC)
