First of all thank you for all the work in preparation of translation of SWViewer and SWViewer/header.
I am just opening this thread to track translation progress. I see that you guys are fixing little issues. Please ping me once the page is actually ready and have no issues left, so that I can announce it at various places to get translators.
I have also added you two to SWViewer/members, in case you don't want feel free to remove yourself.
@Minorax: this version seems stable, I think we can proceed now, but would like to suggest changing enwiki articles to Wikidata items. (P.S.: 1997kB, dummy edits are no longer needed. You can mark this page at Special:PageTranslation → SWViewer → mark for translation.)Sgd. —Hasley 14:20, 26 August 2020 (UTC)Reply[reply]
What about adding a feature where could be reported dubious edits and dubious newly-created pages (if an user si unsure whether a certain edit or newly-created page is vandalism or not, other users could verify those edits and pages)?
@NGC 54: Are there any pages onwiki where people do such requests or you asking it to be added in SWViewer? ‐‐1997kB (talk) 14:00, 22 April 2021 (UTC)Reply[reply]
It could look like the log where there are written the last edits/actions made with SWViewer (reverts, warnings, undos...). --NGC 54 (talk / contribs) 14:03, 22 April 2021 (UTC)Reply[reply]
Enable patrolling of the displayed edit/diff. This should be available only for patrollers (if not possible, add an option to disable it i.e. remove the button). Maybe a button for this action can be placed at the 1st position (as most of the edits are usually fine). Here's a link to the API reference: MediaWiki API help: action=patrol
Recently I made an improvement to config.json, preventing users from being pinged, but today someone reported that they got pinged, so I guess my change hasn't been processed yet. My question is: when will SWViewer load the new config?
defaultRollbackPrefix — is parameter for custom rollback: default prefix + custom reason. But here was used normal rollback. String is configured by the MediaWiki, not SWViewer.—Iluvatar (talk) 11:59, 24 April 2021 (UTC)Reply[reply]
UPD: see nlwiki and enwiki. You need to ask about settings of MediaWiki for nlwiki on Phabricator. Sorry for my English.—Iluvatar (talk) 12:09, 24 April 2021 (UTC)Reply[reply]
I see, so apparently both use the same string, but the MediaWiki rollback suppresses the ping. Otherwise I would have received pings from those. So I think this is an issue with SWViewer. --bdijkstra (talk) 12:52, 24 April 2021 (UTC)Reply[reply]
Bdijkstra, No MediaWiki doesn't supress pings. I get them all the time when people revert to my edits. I guess it's depends upon notification settings. ‐‐1997kB (talk) 16:39, 24 April 2021 (UTC)Reply[reply]
This isn't about user A receiving a ping when user B reverts their edit, this is about user C receiving a ping when user B reverts an edit by user A to the last revision by user C. In my notification settings, I have mention pings turned on, but I haven't received this kind of ping in ages, except recently with SWViewer. Presumably this user had the same experience. --bdijkstra (talk) 16:54, 24 April 2021 (UTC)Reply[reply]
[BUG]: Report function adds improper newline before report[edit]
Type
Bug
Setup
unknown
See diff on English Wikipedia: it's a list, so a blank line in between the list items ends the list and starts a new one, instead of adding an item to the list. This is minor, but it'd be nice if it was fixed. Tol (talk | contribs) @ 05:06, 23 April 2022 (UTC)Reply[reply]
@Tol Seems no issues and these are unbulleted list after all and I think some noticeboard prefer newline and that's why it was added. (Don't remember exactly which require it). ‐‐1997kB (talk) 14:18, 20 July 2022 (UTC)Reply[reply]
@1997kB, this is per English Wikipedia's w:en:WP:LISTGAP guideline section and for accessibility in general; this is problematic because it creates a new list instead of adding another item to the existing list. Would there be any way to change this just for English Wikipedia? Tol (talk | contribs) @ 00:11, 21 July 2022 (UTC)Reply[reply]
[ADDITION + FEATURE]: About warnings on eswiki and enwikiquote[edit]
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.
Hello! I feel like SWViewer shouldn't show edits to Custom Javascript and CSS pages since the majority of users can't do anything to them and it requires them to be an interface administrator. Including them in the SWViewer feed feels rather pointless if the majority of users can't do anything about them even if they're vandalism.
@Blaze Wolf On the English wikipedia if you come across inappropriate content in a user CSS or JS page you should place a speedy deletion tag on the associated talk page. 192.76.8.74 10:04, 15 September 2022 (UTC)Reply[reply]
That's something you can do? I didn't even know they did have talk pages. ― Blaze WolfTalkBlaze Wolf#6545 13:01, 15 September 2022 (UTC)Reply[reply]
Well I knew that all userpages had an associated talk page, but I didn't know that CSS and JS pages had one, I didn't even know you could edit them. ― Blaze WolfTalkBlaze Wolf#6545 15:47, 15 September 2022 (UTC)Reply[reply]
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)Reply[reply]
[FEATURE]: Remove edits that have already been reverted from the queue[edit]
Type
Feature
Setup
unknown
I wish SWViewer could be able to remove from the queue edits that have already been rolled back by other good-faith users or bots, so as not to stumble upon irrelevant cases of vandalism.
It's impossible. Too much load on the device, network and server. Every X seconds scan all queue for each user.—Iluvatar (talk) 05:56, 15 November 2022 (UTC)Reply[reply]
That's not entirely correct. If you enable "live updates" in the recent changes list and filter for "latest revision" vandalism (enwiki example), it does this just fine, so it's not just possible but rather already implemented in production somewhere. ToBeFree (talk) 20:45, 9 December 2022 (UTC)Reply[reply]
Has this been implemented? I've noticed some stuff whilst patrolling that makes me think it may have been, but I might be mistaken. Mako001 (C) (T) 🇺🇦 06:52, 8 July 2023 (UTC)Reply[reply]
No. Only edits removes from queue, which was reverted by another user via SWV. Also old edits are removes when gets a new edit event on same page. Sry for my English. Iluvatar (talk) 14:04, 8 July 2023 (UTC)Reply[reply]
I tried updating the config page a few times, but the updated edit summary is not showing, unless it’s related to the console or it’s something else that needs to be updated? Tropicalkitty (talk) 23:51, 11 December 2022 (UTC)Reply[reply]
I'd suggest a similar feature like this, can we provide the level of warnings that user received close to their edits like Huggle? Lemonaka (talk) 04:37, 6 January 2023 (UTC)Reply[reply]
As the title states, the talk doesn't seem to function on the Opera GX internet browser in that you are unable to send any messages. YOu can type a message and see others' messages, hwoever you can't send any yourself no matter what (clicking the send button doesn't work and neither does hitting enter). Works fine in Google Chrome
[FEATURE]: Mental health: Take a break popup and slow down stream[edit]
Type
Feature
Setup
unknown
It can be easy to "get lost" in the stream. Can we implement a popup that notifies you to take a break after a certain (programmable) amount of time has passed? This feature is becoming increasingly common in certain websites/apps and I believe it helps with mental health. Having a way to artificially slow down the stream could also be helpful. Personally speaking, it generates anxiety for me.
it can be same as sleep(); function or anything similar. 🌸 Sakura emad 💖 (talk) 09:26, 15 February 2023 (UTC)Reply[reply]
Sakura emad, I suppose in a typical sleep function you'd get something like this: get all edits from the stream in that moment, sleep for 5 seconds, get all edits that happened during those 5 seconds up until that moment, sleep for 5 seconds, get all edits... While what I'm mostly after is: Get precisely 1 edit, sleep for 5 seconds, get 1 edit that is known that it isn't acted upon by anyone at the time shown, sleep for 5 seconds, get 1 edit that is known that... — Klein Muçi (talk) 09:40, 15 February 2023 (UTC)Reply[reply]
[MINOR FEATURE]: Custom reverts should remember old given reasons (at least in the same session)[edit]
Type
Minor feature
Setup
unknown
Usually I tend to use only 2-3 general reasons on custom reverts. If they can be remembered and autosuggested in a dropdown menu it could save me a lot of hassle.
When tagging a page on any wiki for deletion, SWViewer gives the user a bunch of set reasons for the tagging. Often, though, it would be quite helpful and convenient if it allowed entering a reason manually instead of having to "edit" the page to do so. Similar to how undoing with reason works, I think this will be useful.
I'd love for this feature to be implemented. Many times I'm forced to give "empty page" as a delete reason when pages are very short but not empty because "very short page" doesn't exist as a reason on its own for many projects. - Klein Muçi (talk) 15:31, 3 March 2023 (UTC)Reply[reply]
When I go to SWViewer, the queue and chatboard don't active on my phone though my desktop still fine. I reloaded that page, but not useful. And day by day that error is still there. Can anyone help me? Quangkhanhhuynh (talk) 10:22, 20 February 2023 (UTC)Reply[reply]
[ADDITION]: Add a toggle for edits' and days' limits to make them differentiate between global and local experience[edit]
Type
Addition
Setup
unknown
Edits' and days' limits check for local edits on local projects. Currently there is no way to put a limit for global edits or global days since an account was created. This edit (and the subsequent conversation that issues) may provide more information about why such a change may be needed.
[ADDITION]: Add missing tooltips for presets options and bottom icons[edit]
Type
Addition
Setup
unknown
As a user I rely heavily on tooltips everywhere to understand what button does what. Currently SWViewer is well-supported in that direction beside only a few that are missing. The presets' chevron, plus, pencil and bin have no tooltip provided. The small icons at the bottom beside "Connected to stream" have no tooltips either, making it hard for me to understand what each of them means.
[ADDITION]: Make Wikis whitelist work with whole domains[edit]
Type
Addition
Setup
unknown
There are many occasions when I've wanted to skip edits from a certain domain, for example, Wiktionary, all languages included. Currently there is no way how to achieve this.
[BUG]: Edits limit doesn't work in conjunction with Days limit[edit]
Type
Bug
Setup
unknown
Scenario: Edit limit=100; Days limit=5 - User X has more than 5 days of experience but less than 100 edits. Their edits are shown. They shouldn't be. This already happened here (check bottom) and it seems like a problem that is shared with all SWViewer preferences (check "Language set" doesn't work when "small wikis" and/or "additional wikis" are enabled" bug above).
Yes. I was the "affected" user. Of course we could resolve the problem via Wikivoyage's talk page, but @Klein Muçi at first reverted my edits as they were showing as new (or can one say sus?). I haven't made 100 edits to en:wikivoyage, that is correct, but my first edit - even beyond the User and talk namespaces - was definitely more than five days old. Through this bug/mistake, my edits showed up and were reverted as I only made some minuscule edits including changing a population number (like vandals seemingly do?)... ObersterGenosse (talk) 20:21, 3 March 2023 (UTC)Reply[reply]
Could a checkbox be added which allows patrollers to modify the filter between "x edits AND y days" and "x edits OR y days"? Mako001 (C) (T) 🇺🇦 06:58, 8 July 2023 (UTC)Reply[reply]
When you click more options on an edit and thank somebody, the icon next to it is a thumbs up. Change it to show a thumbs up in the notifications as well instead of a warning icon.
Global Rollbacker have the ability to mark rollbacks as botedits. This is quite helpful to not spam watchlists. I want to suggest to mark rollbacks with no reason (“r”) and the manual reasons (“y”) which suggest obvious vandalism like “vandalism” and “test edit” for all projects automatically (maybe after activating it in the settings) as bot edits. But please not for content-based reasons, for example “no improvement” (in German “Keine Verbesserung”) is not used for obvious Vandalism and shouldn’t be marked as a bot edit.
If you report someone, the link is red / wrong because the Special-page is not existing. SWViewer links to Spezial:Benutzerbeiträge/<IP or username> but that’s wrong, it should be Spezial:Beiträge/<IP or username>. Example. That’s the bug, now two little suggestions: Change “Berichterstattung <IP or username>.” to “<IP or username> gemeldet” and the report-text from “Störung nach letzter Warnung . ~~~~” to “Vandalismus nach letzter Warnung --~~~~”. I Hope, improving the sourcecode / text is not so complicated than fixing bugs. Thanks,
Done. ‐‐1997kB (talk) 13:33, 25 August 2020 (UTC)
Support. --NGC 54 (talk / contribs) 12:02, 25 April 2021 (UTC)
Support 🌸 Sakura emad 💖 (talk) 09:23, 15 February 2023 (UTC)