User talk:DatGuy

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

DatBot: Page Triage Updater[edit]

Hi DatGuy. Would it be possible to also include the "oldest" values returned by in User:DatBot/newpagesbacklog? – Joe (talk) 11:27, 19 June 2023 (UTC)Reply[reply]

Should be added in the next run. DatGuyTalkContribs 12:08, 19 June 2023 (UTC)Reply[reply]
Wonderful, thanks! – Joe (talk) 15:03, 19 June 2023 (UTC)Reply[reply]
Hi again. Related to this, it was suggested to me at Wikipedia talk:Lua/Archive 12#Read data outside the module namespace that a bot could also maintain a historical record of this data, either on Commons (using mw:Help:Tabular Data) or here on enwiki as a Lua data module. That'd be very useful for an NPP dashboard I'm working on at the moment, and potentially also if we have to come up with a replacement for Wikipedia:New pages patrol/Backlog chart. Would you be interested in implementing that in DatBot, since it's working with the pagetriagestats API anyway? I'd imagine daily records would be sufficient. – Joe (talk) 09:01, 20 June 2023 (UTC)Reply[reply]
@Joe Roe: basically Wikipedia:New pages patrol/Backlog chart/daily but with tabular data? Regarding the backlog chart, is the issue MusikBot missing runs? I think it's best to wait a bit for MusikAnimal to respond. I wouldn't want to step on their toes and he may also like to tackle your first request, seeing the close relation of the tasks. DatGuyTalkContribs 15:20, 22 June 2023 (UTC)Reply[reply]
The missing runs are an issue, but my thinking was that this would be an update and a generalisation of MusikBot's task, which is fairly narrowly focused on providing data for that chart. Specifically, MusikBot only logs the size of the articles backlog, not any of the other columns, and only keeps the daily data for the last six months (the limit of the daily chart). MusikBot also gets its data from a database replica, not the API, but I don't know if that's significant. But yes, I'd also be very happy if MusikAnimal wants to take it on. – Joe (talk) 16:12, 22 June 2023 (UTC)Reply[reply]
I will gladly handover the task to DatGuy if he's interested! That's one less task I have to maintain :)
I'm not sure why the bot is bugging out. I didn't change any code or anything, and there are no relevant errors in the logs, so I'm tempted to blame Toolforge. With the future of graphs on the wiki looking grim, it seems this bot task is worthy of retirement, anyway.
Note the date range for which MusikBot stores data is configurable, but there's little sense in making it "forever" when the data going back to July 2016 is already publicly available on the s53463__actrial_p database on, supplied by Nettrom's code. MusikBot is merely copying that data to the wiki. There's a lot of other data in there that you might find interesting, by the way. Nettrom hopefully can point us to some documentation. MusikAnimal talk 18:45, 23 June 2023 (UTC)Reply[reply]
The code is in on GitHub. It’s not overly complicated, it runs one query to get the count of pages in the queue, and one to insert that into the database on toolsdb. This is done once every 6 hours through Toolforge’s new job system, the job specification is in /data/project/actrial/projects/actrial/jobs.yaml on TF. Cheers, Nettrom (talk) 16:46, 24 June 2023 (UTC)Reply[reply]
Thanks, MusikAnimal, Nettrom. The primary reason for copying the data from toolforge to either a data module on enwiki or tabular data on Commons would be to make it available to templates etc. As you say, we're not sure if graphs are ever coming back, so there's a need to come up with other ways to look at the trend in NPP stats. – Joe (talk) 04:17, 26 June 2023 (UTC)Reply[reply]

Administrators' newsletter – September 2023[edit]

News and updates for administrators from the past month (August 2023).

Guideline and policy news

  • Following an RfC, TFAs will be automatically semi-protected the day before it is on the main page and through the day after.
  • A discussion at WP:VPP about revision deletion and oversight for dead names found that [s]ysops can choose to use revdel if, in their view, it's the right tool for this situation, and they need not default to oversight. But oversight could well be right where there's a particularly high risk to the person. Use your judgment.

Technical news


  • The SmallCat dispute case has closed. As part of the final decision, editors participating in XfD have been reminded to be careful about forming local consensus which may or may not reflect the broader community consensus. Regular closers of XfD forums were also encouraged to note when broader community discussion, or changes to policies and guidelines, would be helpful.


  • Tech tip: The "Browse history interactively" banner shown at the top of Special:Diff can be used to easily look through a history, assemble composite diffs, or find out what archive something wound up in.

Sent by MediaWiki message delivery (talk) 09:21, 1 September 2023 (UTC)Reply[reply]

2023 CheckUser and Oversight appointments: candidate appointed[edit]

The Arbitration Committee is pleased to welcome the following editor to the functionary team:

The committee thanks all members of the community who participated and helped bring this process to a successful conclusion.

For the Arbitration Committee, Cabayi (talk) 20:18, 26 September 2023 (UTC)Reply[reply]

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § 2023 CheckUser and Oversight appointments: candidate appointed