Wie kann ich das machen?
Talk:Edit Review Improvements/New filters for edit review
Return to "Edit Review Improvements/New filters for edit review" page.
Reply to "Änderungen durch einen bestimmten Bot von der Beobachtungsliste nehmen"
Reply to "Messed up"
Yeah, I figured as much — I just tried dropping down to 100 from 1000, and the whole page with new filters loaded in about 9 seconds with
Reply to "Plans to graduate the New Filters on Watchlist out of beta"
Reply to "*Exclude* redirects."
Reply to "I want to see article only on most recent date"
Reply to "Latest revision filter improvement idea"
Reply to "Live updates do not work (HTTP 204) on custom filters"
Reply to "The Filter "Logged Actions" needs better granularity"
Reply to "Error message disabled"
About this board
This page is about New Filters for Edit Review filtering tools and interface. These are now standard on Recent Changes and the Watchlist.
New filters for edit review are in maintenance mode. Major bugs will be fixed but no improvements are scheduled for now. This page is monitored by the maintenance team; however, we aren't watching it everyday.
Leave feedback in any language.
How to provide feedback
- Do you have that bug when you are not logged-in?
- Explain how to reproduce the bug (step by step)
- Tell us what is your configuration (browser version, scripts you use, etc.)
- Say on what page it is happening (Recent Changes, Watchlist, etc.)
Also see the FAQ.
Want to opt-out?
Check on your preferences on the wikis you are active on:
|Edit Review Improvements (ERI)|
Änderungen durch einen bestimmten Bot von der Beobachtungsliste nehmen
[übersetzt mit einer Übersetzungsmaschine]
Im Moment ist es nicht möglich, Bearbeitungen zu filtern, die von einem bestimmten Konto (Benutzer oder Bot) oder von einer bestimmten IP vorgenommen wurden.
At the moment, it is not possible to filter edits done by a specific account (user or bot), or by a given IP.
I come accross this thing first time just now at pt.wp, where I’m less active than in Commons (where it is not yet deployed). So I applied a few filters, and then tried to find an "OK" or "submit" button. Turns out there’s none — filter implementations happen on the fly.
This was a feature of the old Special:Watchlist which was changed a few years ago, with the addition of the "show" button, in the box labelled "Watchlist options". Back then a user sort of complained, saying he liked to tick the checkboxes on and off and get immediate results and now, oy vey!, an extra click is needed. This user was severely mocked and shown xkcd 1172 and yet here we are again, back to the old UI paradigm, with changes applied on the fly. (Of course the new UI’s elements are now very huge because reasons.)
@Tuvalkin Do you want to say that again in Portuguese or can you link to these conversations? I'm a bit confused. My apologies.
@MJL: What would you do with a Portuguese text? Your user page states you are only fluent in English…
As for a link to a discussion in Commons I vaguely remember from 3 years ago or so, sorry, it’s unlikely I can remember enough of it to allow a successful search.
I only meant to emphasize the way UI principles keep changing, in this case a whole 360°, and yet every time someone complains those principles are refered to by devs as abolutely enlightened and set in stone.
@Tuvalkin I meant that users who actually do speak it could be assistance.
Ah, gotcha, my apologies for misunderstanding.
Se o meu inglês não te serve, MJL, vai aviar-te a outra loja, que esta agora já fechou.
@Tuvalkin Point taken lol
I'm reacting to the "where it is not yet deployed": the filters are default on all wikis since almost one year. Maybe you've opted the filters out on Commons.
Check on your preferences on the wikis you are active on:
You will get the buttons back.
Thanks, I’ll do the same in pt.wp too.
Plans to graduate the New Filters on Watchlist out of beta
Collaboration team is announcing plans to graduate the New Filters for Edit Review out of beta on Watchlist by late June or early July. After launch, this suite of improved edit-search tools will be standard on all wikis. Individuals who prefer the existing Watchlist interface will be able to opt out by means of a new preference.
The New Filters introduce an easier yet more powerful filtering interface to Watchlist as well as a whole list of filters and other tools that make reviewing edits more efficient, including live page updating, user-defined highlighting, the ability to create special-purpose filter sets and save them for re-use and (on wikis with ORES enabled) predictive filters powered by machine learning. If you’re not familiar with the New Filters, please give them a try on Watchlist by activating the New Filters beta feature. In particular, it would be very helpful if you can test the new functionality with your local gadgets and configurations. The documentation pages provide guidance on how to use the many new tools you’ll discover.
Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us now with a post on this talk page. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed.
This is neither here nor there, but on an old machine (2009 macbook, 8gigs ram, SSD) the filters take a very long time to load on a large watchlist. I really enjoy them but use the old design rather than wait for the page to load. I'll be opting out, but look forward to using them with a new machine!
Hi @Amorymeltzer. Thanks for the kind words about the filters, but I'm sorry to hear load time is such a problem for you. Frankly, a 2009 Macbook isn't all that old. We'd like to look into this a bit more. Can you tell me a) how many pages are on your Watchlist, b) how many items you choose to show at a time, c) what browser you use?
If you have time, it would be especially helpful if you could turn on the New Filters beta and put in the settings you use, then copy and paste the URL (which contains all the settings) for us, so we can see what you're trying to do. i
I'm copying @Catrope and @Etonkovidova, since they will be interested in this thread.
@JMatazzoni (WMF): Sure. For starters, I use Modern with a dumb amount of userjs, including a number of scripts that dramatically slow down the watchlist (e.g., user highlighting, shading out already-seen pages, cross-out blocked users). In the interest of this, I've tested it using vector, for which I have no customizations or js loaded.
I'm on OSX 10.11.6, running Firefox 60.0.02. My watchlist just hit exactly 5,500 pages (although I had the same issue when I had it pruned to around 3, 3.5k), and I show 1,000 changes (that's ostensibly over the last 7 days, but assuming there's minimal drama at enWiki (lol), it usually spans about 24 hours).
Without the filters, it took about 13 seconds to load, whereas with the filters it took 27 seconds. Nearly all the extra time was with the loading dots for the filters. That url is: https://en.wikipedia.org/wiki/Special:Watchlist?hidebots=1&hidecategorization=1&hideWikibase=1&limit=1000&days=7&enhanced=1&urlversion=2 (no bots, page edits, page creations, logged actions). From there, adding a paramter (https://en.wikipedia.org/wiki/Special:Watchlist?damaging=verylikelybad&hidebots=1&hidecategorization=1&hideWikibase=1&limit=1000&days=7&enhanced=1&urlversion=2 aka very likely have problems) takes about 12 seconds to show. The interface itself is fairly laggy, often requiring a second or two after clicking an option before something registers.
FWIW, with modern and my userjs, it was 17 with the old system and 30 with the filters. Happy to provide more info if you like; I know I'm an edge case, so I appreciate the thought regardless.
Hi @Amorymeltzer. Thanks for all the detail. The engineers request that you try adding the following to your URL and see if it changes the times: ?safemode=1
That will turn off gadgets and user scripts, which will be a big help in diagnosing where the delay might be coming in. Let us know what you find!
@JMatazzoni (WMF) Sure, safemode is no issue. Below is average of two trials for each skin.
- Vector: 18s with beta filters, 8s on the old system
- Modern: 20s with beta filters, 9s on the old system
As before, majority of extra time is waiting for the panel to load, so technically the watchlist itself is visible.
@Amorymeltzer As you might have figured out, 12 seconds is the amount of time it takes to query the database and figure out what the recent edits to pages on your watchlist are and which of them match the filters you chose. This is a known problem with large watchlists, unfortunately, and affects both the old and the new UI. You also get hit by that 12-second delay every time you change your filters, because it has to rerun that query. There may be some optimization we can do for large watchlist, I'll look into that later if I have time.
As for the additional delay caused by the new filters UI, that should only depend on the number of results. I tried with 1000 results on RC (my watchlist isn't that big) in Firefox, and it only spent 0.6 seconds in the loading dots stage. I suspect gadgets and/or user scripts may be interfering here, which is why Joe suggested using safe mode, which disables those. If it's still slow with safe mode, we can do a more detailed performance analysis of your particular case; if you're interested in that, get in touch with me on IRC (RoanKattouw) or email/gchat (roan at wikimedia dot org) and I'll walk you through it.
Whoops, our messages crossed. It looks like it's still quite slow for you in safe mode, which I'm very surprised by. If you're willing to spend some time investigating this issue with me 1-on-1, I would be quite interested in that; it's hard to impossible for us to fix issues that we can't reproduce or observe ourselves.
Yeah, I figured as much — I just tried dropping down to 100 from 1000, and the whole page with new filters loaded in about 9 seconds with
safemode=true. At any rate, I know I'm an edge case here, so I do appreciate the thought. The filters really are excellent. And yes, anything that can every be done to speed up large watchlists will always be appreciated!
Just to add a little observation I had after seeing this interesting discussion. With my very tiny Watchlist consisting of only 29 pages and absolutely no user scripts that customize what appears in Watchlist, it took me 2 seconds for the list to appear and around 3 more seconds for the panel itself to load 500 changes. This is on a Firefox Nightly 62.0a1 on a Dell Inspiron 3542 running Debian 9. fast.com reports my internet speed as 4.8 Mbps which I find to be a decent speed in the place I live.
I'm reporting this as I find this very slow as compared to the 0.6s observation by Roan Kattouw (WMF).
I forgot to mention that this was for the URL,
I'm also seeing severe performance issues. The old watchlist takes 8 seconds to fully load, and is usable after ~4 seconds (the remaining 4 seconds are for the ORES highlighting to load). The new watchlist takes 34 seconds to load. While the watchlist comes on screen after 4 seconds, I cannot interact with it in any way until the three grey dots go away 30 seconds later.
I'm using the corporate-mandated IE11 running on a fairly modern computer, albeit inside a virtual machine. However, performance on other websites isn't this bad.
If the issue is large watchlists (mine has ~9000 pages), perhaps the new system should fall back to the old one once the watchlist is above a certain size. However, despite what @Roan Kattouw (WMF) said, my huge watchlist doesn't take 12 seconds to load in the old watchlist page despite my list being larger. I suspect that this comes down to server-side processing being faster than whatever the new watchlist is doing.
Thanks for your report @Ahecht. Can you please copy and paste the url when you're using your default filter set, so we can look for any patterns with that? Meanwhile, I'm pinging @KHarlan (WMF), who's also looking into this issue.
@JMatazzoni (WMF) https://en.wikipedia.org/wiki/Special:Watchlist?hidemyself=1&hidebots=1&hidecategorization=1&hideWikibase=1&limit=500&days=7&enhanced=1&damaging__verylikelybad_color=c5&urlversion=2
@Ahecht thank you for the URL. A few questions:
- Can you please try appending
&safemode=1to the URL, starting IE11 in "No add-ons mode" by running the Run command from the Start menu, and then typing
iexplore.exe -extoffinto the box, and then visiting your Watchlist page again?
- Could you please elaborate on "I cannot interact with it in any way until the three grey dots go away" -- you cannot click on links in the watchlist? Are there other things that are blocked, scrolling for example?
- Do you also encounter performance problems on Special:RecentChanges?
thank you for your help!
- After my last post, I took the opportunity to trip my watchlist down to 6750 items, which brough the load time to 20s.
&safemode=1shaved off about 1.5 seconds, and starting IE in no add-ons mode didn't have a measurable impact.
- Yes, I cannot click any links or scroll. I should mention that the three dots also stop animating about halfway through.
- Looks like I have the same issue with RecentChanges taking about 20-30 seconds to load. Hadn't noticed that before, as most of my recent changes patrolling is using Huggle.
@JMatazzoni (WMF) With 250 changes, it brings is down to a little over 10 seconds (with safemode)
Thanks @Ahecht, could you also please let us know the load time with a limit of 100 items, and also if you find the performance with 100 items (page load, toggling filters, etc) to be acceptable?
@KHarlan (WMF)That brings it to 6 seconds. While 6 second by itself is acceptable, the fact that I'd have to load the page 10 times (for a total of 1 minute) to see the same number of pages that I get on the old watchlist (which loads in 6 seconds now that I've trimmed down my watchlist) isn't.
@Ahecht I hear you :) thank you for this information, we will look into it further.
@Ahecht, the team is looking into this, so please answer another question. What happens if you reduce to 250 changes (instead of 500). As a side note, if you do end up reducing the search in this way, it might work for you to try using the "Unseen" filter (in the Watchlist Activity group). With that filter on, once you've looked at the first batch, you can move on to the next. But anyway, we're just trying to figure out how the system is working, and none of us has a test account as large as yours!
> none of us has a test account as large as yours!
Maybe you could ask if @Ahecht is interested in sharing their watchlist?
Thanks! I guess it's now upto the people involved to use it to test and fix the issue.
@Ahecht @Kaartic @Amorymeltzer thanks again for your feedback and help with diagnosing the performance issues. We're working on a few fixes, you can track our progress at https://phabricator.wikimedia.org/T197168
@Ahecht @Kaartic @Amorymeltzer we've deployed a set of fixes to address performance issues, if you have time we'd appreciate your feedback. Please look at "Send us your performance traces" in https://phabricator.wikimedia.org/T197168 for instructions on sending us your feedback. We are still investigating a few more optimizations as well but hope that you will see an improvement with the code that's been deployed already.
Performance is much better. With almost 9000 pages on my watchlist, viewing 1000 pages at a time, the page loads in ~9 seconds. The watchlist appears after 6 seconds, and the three dots take an additional 3 seconds to go away. I posted more details on Phabricator.
Thanks for your report @Ahecht! I just rolled out some more improvements, so hopefully it'll be a bit faster still if you try again.
Said as much on the phab, but the improvements are fantastic! Barely any difference now between old and new. Thanks so much!
Very happy to hear it, thanks for the feedback and help with the performance traces!
I also could confirm that Special:Watchlist loads faster than I observed previously for my tiny watchlist.
Thanks for these reports! We're now satisfied that the performance problems are under control, and a few days ago, we scheduled the deployment of this feature. The deployment date is July 9th for most wikis (mostly smaller ones) and July 16th for the remaining wikis (mostly larger ones). This was announced on Phabricator and in Tech News, but I forgot to announce it here.
Would be great if we could have a filter to exclude redirects. It would be breat to see only new creations with meaningful content on them. ElectricRay (talk) 15:27, 3 February 2021 (UTC)
I want to see article only on most recent date
I'm not sure to understand what you try to do.
Only the last revision of an article is shown on watchlists.
Can you explain it once again?
I linked to a screenshot. Note the duplication of, for example:
*Cannabinoid hyperemesis syndrome
Thank you for the screenshot. Now, it is more clear.
Have you tried to select the "Latest revision" filter?
Thanks. It would be nice to have all revisions shown since my last visit. But to have the page only listed on the date of the latest revision. Instead of breaking up the revisions into chunks by day. But I have no idea if that would require more server time per watchlist.
As I understand what you look for, it is not a feature at the moment. Maybe you should keep it for the next community wishlist survey?
Latest revision filter improvement idea
I think that it would be useful if the latest revision filter also showed revisions that would be the latest if it didn't count edits from the same user as being the latest revision. The point would be so that vandals couldn't make a random useful edit to make it harder for people to find their vandalism.
Is there a way to block out user creation logs?
If there is, how do you use it, and if there is not one yet, I think it would be useful and should be around.
Help:New filters for edit review may help you.
No, Help:New filters for edit review has nothing in there about blocking out user creation logs. Jidanni (talk) 11:17, 13 December 2020 (UTC)
https://abj.miraheze.org/w/api.php?action=help&modules=feedrecentchanges is also helpless against User creation logs. Jidanni (talk) 11:53, 13 December 2020 (UTC)
What's precisely the problem?
Live updates do not work (HTTP 204) on custom filters
Steps to reproduce:
- Set up a custom filter with a few edits, say unpatrolled, newcomers, #mw-reverted.
- Pause Live updates.
- Make a change on one of the listed pages (say patrol an edit).
- Resume Live updates.
The view will not change to reflect the change, and API responses to update requests will be empty (HTTP 204). Example request on hrwiki.
Hello, and thank you for reporting it.
How do you patrol the edit? You use a gadget to patrol it on RecentChanges, or do you open the link in a different tab, patrol the edit and close the tab?
No gadgets, I open the diff in a new tab and patrol it normally.
I checked on this and I can't reproduce it. Which browser do you use?
@Trizek (WMF) I use MS Edge 95.0 x64.
I'm still able to reproduce the bug. Here's a screenshot of browser network activity: https://i.imgur.com/UDbLxOT.png The URL in question is this one. Active filters: Unregistered and unpatrolled. I patrolled a single edit, enabled live updates and nothing changes, all the requests still return 204 No Response.
The Filter "Logged Actions" needs better granularity
The Filter "Logged Actions" needs better granularity / subpoints: 1) user creation log 2) block log 3) all the rest. So that I can disable 1) and/or 2) with 3) still being displayed. ~~~~
It seems that Special:Log covers these needs.
Error message disabled
Can i alert admin of this error. It happens when clicking on view messages.