It should be noted somewhere that this only works for WikiMedia projects and not independent Wikis using the MediaWiki software.
Talk:XTools
How come that I can see the monthly counts bar chart and the timecard punch chart although I didn't create a EditCounterOptIn.js page?
Are you logged in? I don't see those stats at xtools:ec/de.wikipedia/NordNordWest.
I am logged in. This might have started since I see an angry rabbit with a "Please log in to continue" when I open that page (~ 3 or 4 weeks). In past years OAuth was able get the permission by itself.
Requiring OAuth is a measure to help with performance. Web crawlers click on the links and fire off expensive queries at high rates, sometimes taking down XTools for all users. We don't require OAuth in all situations, but we do for queries which are deemed to be expensive, such as running the Edit Counter on your account.
I'm completely fine with OAuth but I don't want to see the detailed statistics.
You don't want to see your own detailed statistics? Or is the concern that others can? Because I can assure you others cannot :)
If your concern is it takes too long, note you can choose which sections of statistics you want at xtools:ec.
I don't need this information, it hasn't been displayed all the years until now, it says ''These statistics are only shown if the user has opted in to showing restricted statistics'' which I haven't.
It has always been displayed for logged-in users. It's just that recently we've had to enforce that users login. If you don't want to see these stats, my advice is to unselect them at xtools:ec. I'm not sure what else I can do.
Can the edit summary analysis tool be extended to make counts of the content users leave in their summaries? I occasionally see users leave hundreds of edit summaries that are just "edit" or "fix" which taken together are essentially useless. These users who don't properly describe their edits can often have in excess of 99% edit summary usage with the current tool, but in my opinion these vague edit summaries might as well not exist (and in some cases may be used to intentionally obscure edits).
| Text | Count | Frequency |
|---|---|---|
| rv | 4,156 | 15.0% |
| copyedit | 2,014 | 7.2% |
| none | 1,012 | 3.7% |
| fix typo | 401 | 1.5% |
Ideally, this would be case-insensitive and ignore both trailing punctuation and the /* section title */ syntax as I don't see how discerning between for instance "Fix article" and "→History: fix article." would be informative for this type of analysis.
Just like XTools shows the data and statistics for the last 50,000 revisions of a page, en:WP:ANI as an example, it should show the data and statistics for the last 1,000,000 edits of a user instead of stopping completely and rejecting the request, eg BD2412's edit counts. The feature available for Page Info can also be implemented for User edit counts.
This is phab:T182182. It's been a while since I've done any tests, but in the past it was just too slow, even with the date range constraints. Things are probably more realistic now that we require OAuth. I'll revisit this when I have the time.
Hi, Is there a any way to add a parameter to exclude bots from this list:
https://xtools.wmcloud.org/adminstats/es.wikipedia.org/2024-01-01/2024-06-16
Thanks.
Hello,
Could you please raise your upper limit of edits to beyond 600,000? I look at my XTools page several times a day for a variety of different up-to-date data and features and I'm close to reaching the maximum number of edits. It's hard to imagine that this is a resource that wil soon be unavailable to me. There aren't that many editors on the English Wikipedia that have this many edits, would it really be unworkable to be able to break down their edits and admin tasks? Thanks for considering my request.
I see I'm not the only person here with this request. But if you haven't responded in a month, I wonder if any developers are looking at this talk page.
I see every message here :) If I don't reply, it's probably that I don't have a good answer – and that's the case here. XTools has to service a very large amount of traffic, so long-running queries are automatically killed. The 600,000 edit threshold is just arbitrary to avoid running queries that won't finish. If we didn't have this, XTools would constantly go down.
There are couple tasks tracking this, the main one being phab:T318036. I think the rough plan is two have two thresholds – one is the actual limit that can never be exceeded, and that's something really high like 1 million edits. The other is the lower provisional limit that only requires you to login to proceed. I can't say for sure when I'll get this implemented, but probably in early 2024.
In the meantime, I can probably raise the limit from 600K to something just higher so that it will hold you off for a while. You can also use a host of other tools that don't have the same traffic problems as XTools:
Hope this helps!
Well, I hit 600,000 and I wish I had made copies of my last edit count page as now I just have an edit total and no more information. I use to check this page throughout the day to check some admin tasks so this is unfortunate.
MusikAnimal, if you could raise my threshold, well, I'll send you virtual gift baskets! I think an upper limit of 1 million would just rule out about a dozen editors instead of dozens. Thanks for the links! I'll try them out.
@Liz We don't seem to have too many "queries gone wild" at the moment so I've upped the cap to 650,000K edits across the board. Your comment got me thinking… being able to look up your own account without limitation is a genuine use case I think we can accommodate. After all, the problem isn't that XTools can't handle counting that many edits, it's just doing so at scale. It'll take me a bit before I can implement this, but it should be before you make another 50K edits :)
@MusikAnimal I was just thinking that it has been a while since I asked about the edit count threshold. I saw your comment above regarding the possibility of allowing editors to look up their own accounts without limitation, and I was curious as to whether any progress has been made in the past two months in that regard. It would be great to be able to view my account's XTools data again.
Hello, also see
- https://phabricator.wikimedia.org/T361829 wikiscan.org returns 502 Bad Gateway (workaround for XTools limitation)
Help, @MusikAnimal. I guess I hit 650,000 edits because I just have a blank Edit Count page again. It looks like it took me 5 months to rack up those 50,000 edits.
I feel like I was blessed when you raised my limit last time because I check my edit count page for different reason throughout a regular business day. Any way I could get another boost in my upper limit? That should take care of things until the end of the year as I'm going to be taking a break later on in 2024.
There can't be that many of us that have this problem, on the English Wikipedia it's about 53 editors. I've noticed that the Commons has some very high edit accounts but I'm not sure about other projects. But it can't be more than a few hundred people who are running into this problem. Considering how many registered accounts there are, that's a drop in a bucket! Now that realization could go either way, either it's a problem that affects only a few editors and so isn't that important to address or it's a problem that only affects a few so raising the limit of edit counts wouldn't have a lot of impact on the operating system. Which would be the better argument?
I'm working on a longer-term solution. I hope to have it deployed in the next ~48 hours. Apologies for the disruption.
No problem, @MusikAnimal. I appreciate you addressing the issue. It's the kind of problem that doesn't affect a wide swath of editors but it does impact some of our most active ones.
Okay, deployed! I hope this works. A week or two's time should tell us. If it does, I'll likely be able to increase the thresholds until we find the "sweet spot" where we can allow people like you to get the data you need, but not take down all of XTools in the process.
To be clear, it's not you who's taking down XTools – it's everyone collectively looking up accounts like yours. If too many long-running queries happen simultaneously, we can't make any new queries and so XTools is effectively unusable.
I'm going to resolve this thread for now. Please re-open if you have any related issues.
Hello, thanks a lot!
I still get the follow error message:
User has made too many edits! (Maximum 700,000). Showing Simple Counter instead.
I have just increased it to 800K. If all goes well over the next few weeks, I'll keep raising it.
Thank you so much! It's really cool to be able to access the data again.
I'm still getting the simple counter, even when re-logging in. @MusikAnimal, is the solution deployed already? I'm getting the message "This user has made a substantially high number of edits. Showing limited results." with 652K edits.
@Liz It worked for me: xtools:ec/en.wikipedia/Liz and took only 73 seconds too!
Maybe the redirect from Edit Counter to Simple Counter is cached by your browser. Can you try in a different browser or in private mode?
I just put down more information (below) but I'll try out your suggestions.
Okay, instead of using the open XTools tab and refreshing the page, I went to a new my Contributions page and hit "Edit Count" and after a long wait, it opened up to the familiar page.
Many thanks! I guess I don't have to worry again for a while.
Now, it keeps logging me out of the system and gives me no information about my account at all. What's up with this "fix"?
I get "For performance reasons, the requested data is only available to logged-in users." and then when I try to log in, OAuth states "This request has already been completed and cannot be resubmitted. Go back to the application and try to connect your account again, or contact the application author." Would that be you?
I managed to once again go to the New tab>My contributions>Edit count to get the page back. But I should be able to refresh the XTools page and get the most recent totals without all of this rigamorole, right?
Yes, you should. Login sessions not lasting very long is a known issue that effects many tools, see phab:T224382. I'm not sure about the OAuth issues you're experiencing. It sounds like the login wall you get is also cached… and so the token you send to OAuth is same token as before, and that's why you get the "This request has already been completed" error. Which browser do you use? Do you have any special browser extensions that you think could play a role here?
Apologies for the unwanted behaviour. On the bright side, the "fix" of putting up that login wall has had a dramatic effect on our server load. I've already increased the max edit count threshold to a million edits, and I might even raise it higher.
I'm going to be working on the login issues in the coming weeks, so hopefully that much will be resolved in due time.
When I try to refresh the XTools screen, I'm still getting logged out of XTools even though I've used it for years without problems. Then I try to use OAuth and that doesn't work. But for some reason, if I keep persisting, logging in and refreshing a couple of times, I can eventually get to an updated XTools screen, it just takes jumping through a few hoops. But it would be best not to get logged out when trying to refresh XTools. Just thought I'd post an update, @MusikAnimal.
@MusikAnimal I might have a solution to this, I have posted it above as a new topic, please look at it.
It'd be nice if XTools could break down an editor's (semi-)automated editing history by month, instead of just providing a list of their non-automated edits. It'd look a lot like the month counts section, except that instead of breaking it down by namespace it'd break it down by non-automated or the automated tool used. This data would be both interesting for analysis (e.g. "how much of my increased edit volume during this period was just since I started using an automated tool?") and for detecting when an editor is trying to pad their edit count.
Administrators (at least on en-WP) have access to the number of watchers of a page when it is less than 30. However, it seems this info shows up neither at XTools nor in the ArticleInfo gadget. Would it be possible to get it to appear for the relevant accounts?
@MusikAnimal, just quickly circling back, do you think this would be feasible?
Yes, this we can do :) With phab:T220475 on the horizon, I've been meaning to move more of the logic from the backend to WMF APIs where possible, and this would be one of them.
I'll try to look into it this week.
Also was looking for this. Guess I understand the difficulty in implementing if this pulls all the data from xtools.
@MusikAnimal, just wanted to quickly circle back about this. It's still of interest!
In the stats about de:wp/Flugzeugmodus there is no year 2007. ? --~~~~
Here https://xtools.wmcloud.org/authorship/en.wikiquote.org has only Wikipedia :-(